<aside> 📢 Each Gem NFT has a corresponding staked TON (L2 representation of staked TON on L1: WSWTON, wrapped staked WTON). This is specific to the specific L2.

</aside>

• Gem Utility: what users can do with gem

  • Buy & sell: users can buy the gem or sell their gems on the NFT market

  • Mining: use gem to get more gems of the same or lesser rarity

    • New gem NFT can be earned from mining

    • Each gem can be used to mine other gems

    • Cool down: fixed?

    • mining may fail → if there are no gems to be mined (probabilistic if there are multiple parties involved→ need to display %)

      • Do we want to prevent users from mining if mining is expected fail?

    • Users cannot accelerate mining speed

  • Forging: combining gems will generate more rare gem

    • multiple gem NFTs are burned to create a new gem
    • Trade off between increasing rarity & staked TON value
      • forged gem will have equal or lesser staked TON then the combined gems
      • forged gem will retain combined characteristics of gems
        • forged gem can mine more gem
    • Users can accelerate forging speed
    • Cool down: fixed?
    • Allow forging with multiple gems, 2 - 5?
• Gem Rarity (WIP): attributes that increases the value of the gem. VDF is leveraged to assign rarity of gems. Randomness is supplied after specific time is passed with a proof of randomness
  • Gem’s attributes is defined by gem DNA string
    • this string is generated using variety of the factor, including the randomness provided VDF
  • Attributes
    • Color
      • example
        • Blue → common
        • Other primary colors → very rare
        • Combined color → rare
      • @Ryan Murray will come up with different schemes
    • Shape
      • Single vs Multiple shards
      • different cuts
      • Symmetry - added bonus?
    • Pattern (+visual enhancements)
      • pattern (normal, check, etc)
      • Shading
      • Single shade vs Multiple shades
      • Shadow
    • Postion
      • center aligned, left or right aligned
    • Carat (Gem’s density/weight)
      • gem’s weight corresponds to staked TON amount
      • this determines the surface area of the gem?
        • Gem size should not correspond to staked TON
        • Lets try to see if we can connect it to shape
    • Mining capability
      • based on attributes of the gem
      • always equal or less of the gem’s rarity
      • examples
        • yellow gem can only mine yellow gems
        • green gem can only mine blue and yellow gems
        • gem with 10 staked TON can only mine another gem with 10 or less
    • Forge capability
      • based on attributes of the combined gem
      • always equal or less of the combined gem rarity
      • Forging multiple gems will give some kind of bonus
        • increases incentive
      • examples
        • blue gem + yellow gem ⇒ green gem with different proportions
        • gem with 5 staked TON + gem with 3 staked TON ⇒ at max 8 staked TON (minimum of 5 staked TON)
• Market Economics (WIP)
  • Funding based NFT minting
    • NFT that will be sold on primary market will be minted using the initial fund (TON) and then the next income will be used to mint next set of NFT that will be sold on primary market
    • Requires Treasury Interface
      • Users can cash in WSTON (representation of staked TON) to TON
      • Minting new set of gems for next phase (anyone can execute)
        • Move raised fund to L1
          • withdraw TON to L1 (takes 7 days)
        • Mint gem NFT to be sold
          • stake TON & mint WSTON and deposit to L2
          • Mint gem NFT based on market parameters (last market, fund available, randomness, etc)
    • Minted gems will be divided into two sections
      • standard
        • these gems are either sold in the market or mined
      • rare
        • gems that can be mined only using higher quality gem (has to be forged with gems with large staked TON or with different colors)
• Initial gem airdrop based on contributions (WIP)
  • Contributors
    • NFT
      • Tokamak NFT
      • Titan NFT
      • WTON uniswap pool NFT
      • TOS uniswap pool NFT
    • TON
      • TON genesis snapshot
      • TON Stakers
        • update seigniorage #
        • DAO candidate
        • staking amount
    • Titan Network
      • Users
        • Bridge
        • Withdraws
        • Number of Txns
    • WSTON Contributors
    • Users who provide Feedbacks
    • TOS
      • sTOS holders
  • snapshot
    • requires snapshot (offchain)

Some strict requirements for overall system:

Overall, there are no requirements that cannot be changed → but you have to explain why you are bringing in the change. In this section, I will describe minimum requirements that need to be followed when considering making the system for GEM NFT

1. Reliance on existing contract on L1: (W)TON staking is on L1. This is already deployed contract on L1 and it contains minting logic for WTON per block; WTON is wrapped version of TON. Please check
   1. original git repository related staked WTON
   2. upgraded git repository
2. This is an L2 application: GEM NFT dapp application must exist on L2
   1. however, minting & burning can be done on L1 if there are is a good reason to implement it that way, I would recommend minting and burning on L2 due to sheer gas issue and UX issue for forging (because forging always mints new NFT).
3. All offered functions and related economy must be solvent: System must be solvent at any point (solvency can be delayed, but needs to be solvent without new users)
   1. Any outflow must be matched with inflow
4. Must utilize randomness from existing project: Randomness should be from project DRB
   1. They will provide API / contract call similar to chainlink VRF API for randomness
      1. The exact specification will be provided later. For now, no need to finalize the interface for the randomness