Rave V2, the evolution and what it could mean.

Rave is being reworked. Why is this good, and what it means.

What is Rave V2?

Rave now, is pretty clunky. Especially on the developer side. Approvals are hard to work with, when there are already many standards for this. Rave V2 proposes to fix these (and more) problems. Lets dive in.

Problems with Rave

• Incompatiability with the ERC721 standard

  • Issue description

  Rave (as it is) is not a standard NFT. The safeTransferFrom() and transferFrom() are broken. No protocols (NFT marketplaces, etc.) are willing to support the new transferName() (and approveName()) function(s). This is a big problem for adoption.

  • Issue solution

  Use the ERC721 standard and ERC721Enumerable extension to allow integration with NFT marketplaces and other protocols.
• One username per address

  • Issue description

  As of now, every address can only hold a single name. This is due to early decisions made by Rave team. This is bad for adoption.

  • Issue solution

  Employ the ERC721 standard to allow for many names to be held by an address.

Rave V2

Rave V2 solves all of the problems above, and more. Rave V2 also allows for on-chain tokenURI generation.

Rave V2 would also transform all 0x names into 0x[name].ftm names. For example, 0xPeepo would turn into 0xPeepo.ftm in the migration.

We are planning on migrating within the next month, but want to ask the community for input