Hashflow

Simple Summary: Build and deploy HashVerse contracts on a dedicated chain (could be a side chain). Use HFT as main utility token.

Abstract: There are multiple chain choices that we can make when building the HashVerse. For example, it could be built on Ethereum, Polygon, or Avalanche.

Learning from past experiences (see Otherside mint), the TPS of the metaverse is going to be limited by the TPS of the chain that it runs on. Many popular apps (BAYC, Wolf Game) have spiked gas prices in the past, making UX quite terrible for their users.

As a further example, Avalanche introduced subnets to solve for this exact problem. DFK is a great example of how a subnet can work independently and not clog the entire chain, while sometimes achieving higher TPS than the base chain.

While this proposal DOES NOT suggest a solution for which technology to use, it suggest that HashVerse lives on a separate chain, and HFT is the utility (gas) token on that chain. On top of better UX, this greatly increases the utility of HFT.

Together with that, a few fundamental pieces of infrastructure would also have to be built:

Cross-Chain bridges for NFTs Cross-Chain bridges for HFT Native NFT marketplace in the HashVerse Motivation: This proposal aims to both create better UX in the HashVerse (cheaper, faster transactions), as well as increase HFT utility.