How frequently will voting occur, and how many RSF tokens are typically required to cast a vote?
you can vote anytime. at the end of a voting round the token
- with the most votes
- that was not already selected in one of the previous rounds
wins.
Here is an example:
- NFT was winner of round #1 (with 169121872 votes).
- Winner of round #2 would be BTT with 2223000 votes (= the community spent/burned 2.223000 RSF to vote for BTT) unless nobody outbids
voting round interval is currently set to 1 month
Thanks for the additional information about the voting process.
Are there any limitations or requirements for the tokens that can be voted on, such as minimum market capitalization, trading volume, or liquidity?
currently the only restriction for the voted-on-token is that it has to be a TRC-20 compliant token.
Are there any plans to expand the voting process to include tokens from other blockchain platforms, such as Ethereum or Binance Smart Chain?
-
this is a great idea! i had this already in mind and on my future todo list.
-
but this would also imply the platform to be capable of interacting with mutliple chains (TVM and multiple EVM chains) + redesign of the user interface which leads to quite some effort to implement
-
i will consider this feature depending on how popular the platform gets!
I totally get it, thanks for clarifying
Hi @raidshift welcome to S4!
The Raidshift P2P token exchange exhibits some useful cases - I had a few curiosities about the project:
Is their a process for adding new trading pairs to the platform, and how does the RSF token play a role in this process?
Also are there any plans to prioritize performance or scalability issues, is that a concern you and the team thought about during this process?
Welcome to Hackathon Season 4!
Hi @EMerchant,
Yes, there is a process for adding new trading pairs. You can vote with the RSF governance token
(RSF spent for voting will be burned) for a Token/USDT trading pair to be listed on the platform.
Refer to my responses/comments above for more details.
Fixing of performance / stability / reliability issues is currently prio 1.
As the platform is operated on client side only (no server code required) scalability shouldn’t be an issue. But perhaps your understanding of scalability is different - could you please explain?