{"id":104058,"date":"2023-06-04T13:16:15","date_gmt":"2023-06-04T13:16:15","guid":{"rendered":"https:\/\/dripp.zone\/news\/index.php\/2023\/06\/04\/content-creators-need-more-token-standards-says-folklore-founder-crypto-news\/"},"modified":"2023-06-04T13:16:18","modified_gmt":"2023-06-04T13:16:18","slug":"content-creators-need-more-token-standards-says-folklore-founder-crypto-news","status":"publish","type":"post","link":"https:\/\/dripp.zone\/news\/content-creators-need-more-token-standards-says-folklore-founder-crypto-news\/","title":{"rendered":"Content Creators Need More Token Standards, Says Folklore Founder\n – Crypto News"},"content":{"rendered":"

<\/p>\n

\n

Ethereum’s ERC-721 and ERC-1155 are probably the most recognizable examples of token standards in blockchain today. <\/p>\n

They’re like blueprints, setting out rules for how tokens behave in a protocol and greatly simplifying the creation process. Their predetermined rulesets provide a sort of “package deal” with a variety of functionalities. Plus, they can be trusted as having been carefully audited and confirmed to be compatible with a range of applications.<\/p>\n

without standards<\/a>a creator might enjoy more customizability but can run into serious problems when attempting to interact with platforms and interfaces.<\/p>\n

So it might be surprising to find out that many common NFT<\/a> functions, like minting and burning, do not exist as standards. Even the manner in which the InterPlanetary File System, or IPFS, is used to store an NFT’s metadata is not, in fact, standardised.<\/p>\n

Folklore founder Rafa spoke to host Chase Chapman about the complexities of standardizing a broader range of NFT interactions on a recent episode of the On the Other Side podcast<\/a>,<\/p>\n

He recognizes that, as much as it’s a clich\u00e9 to say, we’re still very early. \u201cWe’ve barely scratched the surface as to what it means to interact with an NFT, so it’s probably too early to commit to specific standards, but having an eye toward actually developing those standards, that’s great.\u201d<\/p>\n

Token standards like ERC-721<\/a> are “very limited on purpose,” says Rafa. \u201cThe standard is as small as possible to enable interoperability between any interface that wants to connect\u201d with it.<\/p>\n

Using relatively limited standards provides flexibility to service providers, Rafa adds, to create additional types of contracts, like minting.<\/p>\n

\u201cWhat that means is that the protocol that you choose gives you the specific mint function that they have designed,\u201d Rafa notes. The function could be gas-optimized, enable air dropping or have burn mechanics, for example.<\/p>\n

\u201cYou might have a series of different functions that enhance the interaction with the specific NFT or token that you’re actually creating.\u201d<\/p>\n

\u201cThis is fantastic for creators,\u201d Rafa continues, \u201cbecause it allows you to experiment.\u201d<\/p>\n

But one thing that should not be assumed, he says, is that interfaces are going to build interoperability with all the possible custom functions of various mints.<\/p>\n

In the same way that an ERC-721 can not become an ERC-1155, contracts deployed on one platform, like Zora, says Rafa, “can’t become a contract that’s hosted on Manifold or Thirdweb.” Compatibility issues are unavoidable without standardization.<\/p>\n

Creators as content liquidity providers<\/h2>\n

Ultimately, Rafa says, a creator’s ability to distribute their content is “predetermined by the interfaces that support your protocol choice.”<\/p>\n

If a creator chooses to create a custom mint function, he notes, the ability for people to mint a given NFT will be restricted to the interfaces that support that particular method. This reduces what Rafa describes as the creator’s “content liquidity.”<\/p>\n

Rafa suggests a pathway to greater content liquidity for creators through the expansion of standard sets. Imagining creators as content liquidity providers, Rafa envisions an established standard for minting and burning NFTs as a first step in improving the system.<\/p>\n

“The slight downside,” Rafa says, is that whichever protocol “lobbies the hardest and has the largest voice” will be the most influential in determining the standard.<\/p>\n

Rafa adds that any protocols which do not already follow that particular standard will then have to be updated to compliance.<\/p>\n