We saw the huge potential of NFT technology when it comes to the Creator Economy, and wanted to solve the challenges currently faced by centralized creator platforms:

  • Centralized platforms own the creators' content.

  • Creators only receive a fraction of the value generated by their content.

  • Fans capture zero value from their engagement and support.

  • High platform fees and limited monetization options are stifling creators.

  • Platforms come and go, and when they go, creators' content disappears into a black hole.

  • Centralized companies subject their users to censorship and other restrictions around their own data and content.

In short, the current way of operating immensely benefits centralized platforms at the detriment of their own users.


We then analyzed the NFT market and observed some fundamental flaws with current alternatives:

  • Incompatibility and fragmentation across platforms.

  • Complicated user experience, poor discoverability for both creators and users, and high barriers to adoption.

  • Lack of utility behind the tokens.

  • High transaction and minting fees.

  • A host of copycat projects flooding the market, with no added value.

  • No proposition that uniquely serves the needs of creators and fans.


We wanted to build something that addresses these limitations, and deliver a better solution for creators and their fans.

Melon would use a decentralized model, where users' content and their funds remain entirely in their control.

It would provide the simplest, slickest user experience so both creators and fans could use the platform easily.

It would also have low fees and remove the barriers to NFT adoption.

Overall, this is what excites us the most:

The opportunity to bring mass adoption to the world of NFTs, so more people can benefit from this incredible technology, be they creators or fans.

That's why we're here, and that's why we launched Melon: the first-ever NFT platform that lets creators turn their viral social moments into rare digital collectibles!

Did this answer your question?