-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snap Protocol #38
Comments
thanks for your proposal @DappCoderr! we'll review it soon and get back to you asap |
@DappCoderr before we review in depth, may I ask for two more things: First, could we add two more milestones?
Second, could you shed more light on the architecture you are envisioning and how projects could use Snap? Are there any requirements or limitations that emerge from the design? |
Hi @alxflw, I'm sorry for the delay in the response. As you know Fractionalisation is a bit-long and complex process, so I'm working on the in-depth architecture of snap so that it will be easier to understand and envision. Thank you for reaching out and providing us with valuable feedback. I appreciate your patience! |
got it! please let us know when you have more details for us to review |
Hey @alxflw, We have made significant changes, Previously we were focused on the Fractional NFT, but after doing market research, we have changed our architecture and now we are building liquidate market for NFTs which makes NFTs more easily tradable in the market. Kindly review the proposal and let us know if you have any queries. Happy to answer them :). |
thanks, we'll take a look soon! |
@DappCoderr we took a look at the updated proposal and it would be great if you could hop on a call to get more details. mind adding me on Discord to find some time? |
Sure, that works better @alxflw . |
hey @DappCoderr - thanks again for chatting with me. As mentioned on our call, I don't think this project is a good fit for the developer grants program. I suggest you check out https://flow.com/ecosystemsupport - maybe the other programs might be of relevance. Thanks again for your submission! |
Thanks, @alxflw, for the feedback & having a call with me. |
We appreciate your proposal and taking the time to fill it out. Given the time since this has been submitted I'm closing this down. |
Snap Protocol
Grant category
Please select one or more of the:
Website - https://snap-protocol.vercel.app/
Description
Snap Protocol is a protocol for creating a liquid market for illiquid Non-Fungible Tokens for the flow blockchain.
Users deposit their NFT into a Snap vault and mint a fungible token (sToken) that represents a claim on a random asset from within the vault.
sTokens can also be used to redeem a specific NFT from a vault.
Benefits include
Architecture
Working
(Note: Its price functionality is different from other NFTs)
Problem statement
Current & Future NFT projects, Artist, NFT Collector, Web3 Gamer.
Web3 is a growing ecosystem and Flow plays a major role in building the pillars of web3, flow is built for the fast and decentralized foundation for a new generation of games and digital assets.
But as a bear market appear, the market reveals (data from NFT Price Floor) that the average 30-day price floors of NFTs have declined by approximately 50% from a little over 40 towards the end of June. Transaction volumes have also declined significantly in the space. Artists and Collectors are facing issues, in selling NFTs at a good price.
Research Part -
According to the Financial Times and Chainalysis, approximately 360,000 NFT owners hold around $2.7 million in NFTs around the globe in 2021.
Proposed solution
We are building a Snap protocol, which will create a pool of NFTs for a specific collection and converts NFTs (illiquid assets) into fungible tokens, making them easily tradable.
Impact
Snap protocol will tokenise NFTs into the fungible token backed by the NFT collection. Anyone on the flow can easily liquidate NFT (that means, it will be easily tradable) with the native flow token.
Milestones and funding
Team
The text was updated successfully, but these errors were encountered: