Game of NFTs (GoN) is a program that provides public environments where the Interchain NFT Transfer technology can be extensively tested with community support and innovations can be created pioneeringly.
The program includes two phases:
- Phase 1 - Public Incentivized Testnets (Kick Off Now!)
- Phase 2 - Hackathon (April 2023)
Phase 1 of GoN now kicks off at 2023-03-01-06:00 UTC, and we have a number of tasks and rewards scheduled. Rewards will be distributed based on a point system, and allocated to winners who have completed certain tasks and submit an entry for dedicated awards.
Table of Contents
- Game of NFTs
Through the several rounds, participants are expected to gain knowledge and build an understanding of the Interchain NFTs feature and assist in the discovery of interesting attack vectors.
The testnet infrastructure includes:
- ICS-721 Enabled SDK and Wasm Chains
- ICS-721 IBC Channels and Ports
- Support Services in Cosmos Discord
- Testnet Faucets
- Testnet Explorers
Participants will utilize all GoN testnets for feature-testing, and for completing multiple tasks.
💬 Event coordinators will be available in the Cosmos Network Discord #🐇┇gon-testnet channel
📍 A leaderboard will be available at https://interchainnfts.dev/gon/scorecard.html
According to information provided via the registration form, eligible participants have been invited into Cosmos Network Discord #🐇┇gon-testnet channel to start coordinating their participation.
Before you start testing, please kindly check the join & evidence submission guidance provided at gon-evidence.
- Step 1. You need to submit qualification evidence to upload basic team information
- Step 2. After that, you need to add each task evidence into your own
infosheet as required and submit for verification and scoring - Step 3. For special award application, you should submit issues based on award application for judging
- Step 4. During the testing phase, if you find a bug/issue, please report based on bug submission
In order to verify the authenticity of identity, ensure fairness of the game, and protect participants' rights in receiving points and claiming rewards, please make sure to submit evidence as required.
Please note that all submissions will be public, so please make sure to create new addresses of test chains to participate in the public testing.
- The final number of points awarded to each participant is at the discretion of the testnet judges.
- The timeline for all stages and rounds may change depending on the outcome of previous activities.
- Available tasks/awards and points may be adjusted during the course of the testnet program.
- All evidence submitted for scoring points must be submitted to gon-evidence as required.
The Incentivized Testnets has 3 stages with different tasks. Tasks will be revealed gradually as the game progresses.
Participants can refer the installation doc to install the client software and the instruction doc to get familiar with Interchain NFTs Transfer operations.
Start from Mar 1
- Create Collections and NFTs
- Perform Interchain NFTs Transfer
Round 1: Warm-ups
IRISnet, Stargaze, Juno, Uptick and OmniFlix have prepared their testnets, allowing participants to create their collections and NFTs. These NFTs can be used for the next transfer tasks of the game, marking the first time participants can experience Interchain NFT Transfer.
Rules:
- Participant issue their own classes(collections, denoms) and must set class data as the JSON string below
- This allows participants to bind their classes to their GitHub account and prove they have control of the class owner
- All the following tasks related to NFT transfer must be minted under their classes
- Class owner must be the IRISnet address of each pariticipant at the time of registration
{
"github_username": "username, this is a must",
"discord_handle": "discord handle, this is optional",
"team_name": "your team name, this is optional",
"community": "if you come from a community"
}Tasks: A1, A2, A3, A4, A5, A6
Started from Mar 6
- Perform Interchain NFT Transfer through different flows
Round 2: Journey for One
Participants complete Interchain NFTs Transfer independently, which means they need to perform operations using their own account addresses on each chain. For each task, participants should start transferring with a different NFT. As a result, they need to create multiple NFTs under their collections.
Rules:
- Each NFT can only be used as evidence once for tasks in Round 2.
- Participants must use NFT minted under classes/denoms they issued in Round 1.
- Participants must use their own account addresses provided at the registration stage.
- Flow can be queried off-chain with flow-id.
Tasks: A7~A20
Expected to start from Mar 13
- Competitive race game
- Quiz game
In addition to tasks, there will be contributor awards for rewarding community-contributed content and tools, i.e, auditing services, public goods, community supports, NFT memes.
General tasks allow participants to fully experience the NFT-transfer functionality. The deadline for the general task submissions (stage 1&2) originally due on the 13th will be extended to around 27th, considering that more testing would be better.These tasks will be locked once the 3rd stage has begun. Participants must submit evidence generated before then (based on the specified block height). Details of flow and flow style in the task description can be found here.
| Id | Point | Task | Details | Evidence |
|---|---|---|---|---|
| A1 | 1 | Create one Collection on IRISnet | Must set ClassUri and ClassData | TxHash on IRISnet |
| A2 | 1 | Mint NFTs on IRISnet | Must set TokenUri and TokenData and mint at least two NFTs | TxHashes on IRISnet |
| A3 | 1 | Transfer an NFT from IRISnet to Juno or Stargaze | The NFT must be the one created in A2 | TxHash on IRISnet Destination Chain-ID Contract-Addr+NFTID |
| A4 | 1 | Transfer an NFT from IRISnet to Uptick or OmniFlix | The NFT must be the one created in A2 | TxHash on IRISnet Destination Chain-ID IBC-ClassID+NFTID |
| A5 | 1 | Transfer the NFT on Stargaze or Juno back to IRISnet | The NFT must be the one transferred in A3 Transfer back through the same channel in A3 |
TxHash on Stargaze/Juno Chain-ID |
| A6 | 1 | Transfer the NFT on Uptick or OmniFlix back to IRISnet | The NFT must be the one transferred in A4 Transfer back through the same channel in A4 |
TxHash on Uptick/OmniFlix Chain-ID |
| A7 | 2 | Perform cross-chain NFT transfer as flow-a1 | Transfer in a never-go-back style. | ClassID + NFTID |
| A8 | 2 | Perform cross-chain NFT transfer as flow-a2 | Transfer in a never-go-back style. | ClassID + NFTID |
| A9 | 2 | Perform cross-chain NFT transfer as flow-a3 | Transfer in a never-go-back style. | ClassID + NFTID |
| A10 | 2 | Perform cross-chain NFT transfer as flow-a4 | Transfer in a never-go-back style. | ClassID + NFTID |
| A11 | 3 | Perform cross-chain NFT transfer as flow-a5 | Transfer in a never-go-back style. | ClassID + NFTID |
| A12 | 3 | Perform cross-chain NFT transfer as flow-a6 | Transfer in a never-go-back style. | ClassID + NFTID |
| A13 | 2 | Perform cross-chain NFT transfer as flow-b1 | Transfer in a revisit style. | Every NFT-Transfer TxHash and Chain ID |
| A14 | 2 | Perform cross-chain NFT transfer as flow-b2 | Transfer in a revisit style. | Every NFT-Transfer TxHash and Chain ID |
| A15 | 2 | Perform cross-chain NFT transfer as flow-b3 | Transfer in a revisit style. | Every NFT-Transfer TxHash and Chain ID |
| A16 | 2 | Perform cross-chain NFT transfer as flow-b4 | Transfer in a revisit style. | Every NFT-Transfer TxHash and Chain ID |
| A17 | 2 | Perform cross-chain NFT transfer as flow-c1 | Transfer in a backtrack style. | Every NFT-Transfer TxHash and Chain ID |
| A18 | 2 | Perform cross-chain NFT transfer as flow-c2 | Transfer in a backtrack style. | Every NFT-Transfer TxHash and Chain ID |
| A19 | 3 | Perform cross-chain NFT transfer as flow-c3 | Transfer in a backtrack style. | Every NFT-Transfer TxHash and Chain ID |
| A20 | 3 | Perform cross-chain NFT transfer as flow-c4 | Transfer in a backtrack style. | Every NFT-Transfer TxHash and Chain ID |
Coming soon...
| Id | Points | Award | Details |
|---|---|---|---|
| 1 | 1200 | Best Auditor | Discover the most serious potential protocol and code vulnerabilities. |
| 2 | 800 | Public Good Awards | Provide the tools to help test Interchain Transfer NFT, including interchain explorers, NFT path visualization tools, wallets, dashboards, etc. At most two. |
| 3 | 350 | Community Star | Provide the most help for the game and participants. |
| 4 | 250 | Best Promoter | Create the best GoN promotional content on social media. We will take views and other metrics into consideration. |
| 5 | 200 | Bug Hunters | Find bugs that affect the functionality of ICS-721. At most five. |
| 6 | 100 | Best NFT Memes | Create the most popular NFT memes. |
| ... | ... | ... |
The Game of NFTs Phase 1 testing aims to provide mainnet-like environments for participants to better understand and become familiar with Interchain NFTs, and idenetify potential issues. Breaking the rules listed below will result in disqualification.
The rules for Game of NFTs Phase 1 are subject to change at any time through launch, and any changes will be committed here.
To participate, please note that:
- Employees of Organizer Teams (IRISnet, Stargaze, Juno, Uptick, OmniFlix) are eligible to participate, but ineligible for rewards.
- GitHub account used for testing must be registered more than one year.
The following behavior will result in disqualification from Game of NFTs Phase 1 Incentivized Testnets:
- Registering multiple teams in order to win more testnet prizes than you otherwise would.
- Copying or tampering with any information of other participants to join testing and win rewards.
- Engaging in any prohibited behavior.
- Engaging in any behaviour that might be unethical / not in line with the community ethics of the Cosmos Hub, IRISnet, Stargaze, Juno, Uptick and OmniFlix.
- Any attack against a node that violates the acceptable use policy outlined by that node's cloud service provider. Please familiarize yourself with those policies (such as Google's, Amazon's, or Digital Ocean's).
- Social engineering attacks against organizer-operated nodes. This includes but is not limited to phishing, compromising cloud account credentials, malware, and physical security attacks on data centers.
- Exploiting application-level security vulnerabilities in Cosmos and Tendermint code.
We are grateful to the individuals and teams who have contributed their time and expertise to assist in updating and enhancing this repo.