This page is some documentation for the base web frontend game consisting of contract drops and ERC20 tokens.
Basically, we’re going to look at minting & interacting with nfts based on a user’s erc20 balance, and then performing different actions on the frontend (either Unity or web) based on users’ holdings and desires.
With these contracts, we’re delegating the key function calls to thirdweb.com base functions.
Base 1155 smart contract → used for testing the spaceships & calling via our API
1155 Edition drop contract for rovers. These will be updated to have a trait connecting them to a spaceship and a user (this might be off-chain first, and the on-chain metadata will pull from the Postgresql database).
Once rovers have mined enough resources, users will be able to mint an anomaly. This is slightly different behaviour to what will occur in-game, where users will be notified of an anomaly.
Could the mining animation be synonymous with “mining” a planet? Hmmm. Note that we may need to change the speed at which staking returns if this is one of the methods used to generate currency
The “currencies” (aka resources) should only be able to be mined or purchased…and these can be used to augment the user’s items in their inventory. In principle, though, the user will have to have staked at least something to be able to do anything (remember, they still need something to sell to be able to buy other resources).
How does crafting work? With erc20 + erc721/1155 tokens → do we require a burn function (like the poke-evolution example in issue 6)?
Figure out if Linear → GH Issues or GH Issues → Linear is better. We want both to be communicated & integrated automatically, without having to do special commits. Potentially we could make an action for this → tagging pull requests with relevant issues. Something to think about…or maybe an action that compares the names between GH Issues & Linear Issues as they should both have the same name