[PROPOSAL] Gamified NFT Burn Tool

Proposal for Gamified NFT Burn Tool Funding - April 2024

Project Name:

  • Kaizo

Proposal Information:

  1. Core Objective:
  • Build an NFT burn interface and admin panel, to allow burn events to be hosted by NFT collections and effectively tracked by them, in a way which provides an engaging and transparent experience for the NFT holders.
  • The primary purpose for the burn events would be transitioning their current collection to a new collection which allows for different utility verticals than they currently have, such as Dynamic NFT compatibility. Many collections are missing out on Dynamic NFT compatibility due to it being recent tooling, however, this would allow projects to host a burn event for their existing collections, to transition all or a portion of their collection to a new Dynamic NFT collection,in a streamlined way, which is engaging for their communities. (But there is potential for additional creative ways the tooling could be leveraged by teams).
  1. Vision:
  • The vision for the tooling is to allow the current Kaizo NFT collection to undergo a full rebrand and transition through the use of the burn tool. Where it would move the existing collection and existing holders to NFTs which are dynamic/composable, under a new art and branding. Therefore opening up new opportunities for the collection & community, through the utility of dynamic NFTs and the cross project collaboration which dynamic traits can bring.
  • Additionally, there is exciting Dynamic NFT tooling/platforms within the NEAR ecosystem such as Bodega, which bring a lot of opportunity for growth and engagement, which in the current landscape, existing NFT collections cannot tap into. This tool will allow existing NFT collections which are interested in that vertical, or even those looking for a refresh to the collection in terms of art, the access to frameworks to do so.
  1. Who would use this tool?
  • Kaizo is planned to be the collection used as an initial pilot of the tool. The community would then be engaged for feedback and exploration of opportunities amongst existing collections who would be able to use it afterwards.
  • Any project on NEAR that would like to switch to dynamic NFT compatibility.
  • Any project that was originally launched by launchpad which now wants control of their own smart contract and add utility to their collection at contract level.
  • Any projects where people are taking over from teams that have left and want to carve a new path for the project.

Overview of the desired flow:

1. Admin Flow
(The italics text at the end of each row is an example specific for Kaizo)
Set the requirements for the burning process by the end user:

  • Select NFT collection smart contract to be used and logged - Kaizo.
  • Select NFT/Project Image - v2 Kaizo Logo.
  • Select background Image - Blank Background.
  • Select Project Burn Title - Kaizo Portal Event.
  • Number of NFTs burned to qualify for a v2 NFT - 2x Kaizo NFTs = 1x v2 NFT.
  • Maximum supply of NFTs which can be burned in this event - 1755.
  • Select the time for which the burn period is open for (Can be indefinite also) - 6 weeks.
  • Select the cost for the user to burn their NFTs (If applicable) - free.
  • Set parameters for different stages if applicable.
  • Deploy to collections website.

2. v2 Collection minting:

  • Project mints the v2 NFT collection through Bodega at desired supply - 875.
  • Project views the logged transactions of burns, which have been tracked.
  • Project exports the details for eligible addresses and airdrops the v2 NFTs to users.

3. Example Flow by user:

The flow for the user would essentially be the same as when participating in a mint/launchpad, but instead of minting an NFT, they are burning their NFT from the participating collection.

  • Visit burn site URL.
  • Connect NEAR wallet through wallet selector.
  • View burning requirements for transaction.
  • View the information outlined by the project for the overall process and even future roadmap (If applicable).
  • Select their eligible NFTs shown on the Interface and initiate the burn.
  • User sees completed transaction animation/popup.
  • User is then retroactively airdropped their corresponding NFTs by the project within the timeframes they have as part of their activation/gamified event.

4. Flow Explanation:

  • This is just one example from Kaizo as a way in which the process can be carried out by a project. In the example, the “Kaizo Fighter” collection would have the potential to transition from 1755 NFTs to a collection called “Kaizo” with a supply of around 875 dynamic NFTs, new art and new branding, which could then be onboarded onto Bodega.

  • In the case of other projects, they are not restricted to the same process as the above example, the tool could also be used in very limited burn events by a collection to launch 100 dynamic NFTs for example - in exchange for their current NFT. Additionally, the v2 NFTs are not required to be dynamic, as the v2 collection, in terms of its art, composability and overall launch can be decided by the project themselves, the tool would give them the interface and efficient tracking to hold a gamified engaging event for their holders.

  • There is the point that this could be achieved by getting users to manually burn their NFTs or get them to manually send them to the burn wallet. However, this would not only become very tedious for NFT collections to deal with in terms of manually logging the transactions and tracking it all (likely resulting in them not doing it at all); but also I do not believe it would be something appealing to the users/communities in this way, as it is manual and also involves a lot more trust barriers than having an interface for the process. This allows for a lot more discoverability and exposure potential. Being open source, there is then the freedom for projects to deploy this onto their own websites to have full control of the process. Therefore, through the proposal flow, the process would be made a lot more engaging by the projects and open the potential to make it an experience for the end user - couple that with a marketing campaign and you can have a fresh wave of traction for your project and the inflow of upcoming new utility through transitioning to dynamic NFTs.

5. Example Wireframes of Burn Interface:


Funding Request Breakdown: $5500 (April 2024)

  • Frontend development of burn interface for the end user.
  • Smart contract development for burn process and logging of transactions.
  • Support/Guidance Docs for use by other projects.

Team:
jayythew:

  • Recently taken over as the solo lead for Kaizo.
  • Active NEAR NFT community member online and at events.
  • Bachelor’s Degree in Civil Engineering.
  • Masters in Transport Engineering, Planning and Management.
  • 5 years experience in planning, design, consultancy, and project/product management.

Contact:

  • Telegram: jayythew
  • Discord: jayythew

Payout Wallet:

  • kaizodao.near

Conclusion:
Through this funding, the aim is to provide the tools which can facilitate existing NEAR NFT collections (such as Kaizo) transitioning from their current smart contracts to a new one, in a way which is easy for the collections holders. Therefore, giving collections the freedom for creative/gamified initiatives to transition their entire collection or limited amounts of their collection to dynamic/composable NFTs while driving ecosystem engagement. There would also be the commitment to supporting any project through the process, if they wish to use the tooling. Overall this tool would provide a boost/opportunity to existing collections on NEAR, who are looking for an interesting pivot into leveraging NEAR native Dynamic NFT platforms such as Bodega; without the need for new mints or a search for liquidity events.

2 Likes

Hello Jay,

Thank you once again for submitting your funding application. We are optimistic that your tool will empower builders and founders to gamify their existing projects, adding excitement and traction to the NFT ecosystem. However, our support is contingent upon the direction set by the HoM. Before we can provide funding, you must obtain an attestation or recommendation from Devhub. Rest assured, we will keep your request on hold and look forward to supporting your project in the May funding round if you secure the necessary endorsement from Devhub.

1 Like

Hey @krikkraktrak after following the steps which were outlined previously and further discussions which were had to iterate the tool; I would like the opportunity for this proposal to be considered within the upcoming round.

For reference, here is a link to the Devhub post I made: https://near.org/devhub.near/widget/app?page=post&id=3212

If there is anything you require of me, please let me know.

Thanks,
Jay

1 Like