endeva gems ores web2

3 min read

just a gem transaction table and ore transaction table balances can be tracked wrt users

basically a database table that show mint/transfer of ores/gems and holdings

  • ores are recurringly “airdropped” based on a formula / directly from retool
  • ore is decremented in db table when a user burns an ore to mint a gem
  • when a ore is burned to “mint” a gem then the user is linked to that created gem
  • when a user views a gem, the amount of karma set by the minter is sent to the viewer
  • a user can turn of viewing any veda-gems (so they do not receive decremented karma per view)
  • ores
    • is burned to mint a veda ( ai content ) into that veda’s gem
      • you mint a gem by burning an ore
    • air dropped to users every week by amt of karma
  • vedas
    • are just ai content ( text, image, audio etc )
    • can be minted into a gem using an ore
    • veda gem has viewership royalties
      • to view a gem fully (first few characters will be visible ), viewer will have to intentionally click “show” which then reduces his karma
  • gems
    • vedas minted into an nft using an ore
    • bought with karma ( minting fees ) and 1 ore
    • exists on secondary markets for collection
      • eg. ABC wants to collect vitalik.eth’s deva’s post which says something remarkable

web2 gems & ores product / tech spec

Key Features

  1. Ores System:
  • Airdrop Mechanism: based on the formula below / from retool, ores need to be airdropped to users
  • Ore Burning for Minting: uers can create Gems by burning Ores, transforming Vedas into Gems (web2 for the timebeing, NFTs later ).
  1. gem minting:

just web2 for now, no NFT business until

  • Veda-to-Gem Conversion: users select a Veda and use Ores to mint it into a Gem, which is then linked to their account.
  1. Gem Viewing:
  • Karma transaction on viewing: Viewing a Gem’s full content deducts karma from the viewer and credits them to the Gem’s minter/owner.
  • Partial Visibility and Explicit Viewing Action: Gems are partially visible to all users. Full viewing requires an intentional action, which involves karma txn for royalty.

Technical spec

Ores Transaction Table

  • id
  • user_id
  • transaction_type
  • amount
  • transaction_date
  • related_gem_id ( optional, if gem was minted in this txn )

Gems Transaction Table

  • id
  • minter_id
  • owner_id (incase it’s been transferred)
  • minting_date
  • veda_id
  • viewership_royalty

Users Table changes / additions

  • ore_balance: no. of ores the user currently holds.
  • gems: gem ids owned by the user.

frontend stuff to be implemented

  • Create UI components for users to interact with ores and gems.
  • Options for users to burn ores to mint gems from vedas.
  • A privacy setting for users to turn off viewing of veda-gems.
  • Display of karma cost and a prompt to confirm viewing a gem which would deduct the viewer’s karma.

Graph View

Backlinks