Minting stage (0.1)

All pre-release (pre-1.0) versions of the Star Sailors SDK will only contain planets (built from Lightkurve) as candidates unless otherwise described in the patch notes/documentation. Exoplanet classification is the only data science tooling that is planned on being included for the first version.

Goals

Player experience

• Users will be able to mint anomalies
• Users will be able to classify anomalies
• Users will be able to create proposals with their classification data
• Users will be able to stake their NFTs to earn rewards
• Users will be able to use their rewards to add stats/items to their planets/NFTs
• Authentication will be handled via Thirdweb & Flask, Lens, and Supabase

Research results

• Users are given objects to classify and these results are recorded
  • For now, these traits will then be added to the NFT and all game interactions will be based on these calculated traits (e.g. a planet that has been confirmed to be “hot” will generate resources with a “heat” multiplier, but the visual metadata (e.g. image from Unity) will not be updated yet (once the planet is minted, the image will not be able to be updated). See The user’s classification parameters can adjust the subsequent generation of their objects (e.g. a user classifying a candidate as “hot” would update the input fields Unity-side to change the colour/texture of the object) for the next step
  • These results are classified into a database that can then be filtered through on the web app (show me all planets within 30 light years of Earth with these parameters OR confirmed parameters)
  • A basic structure for planet/object parameters & traits will be defined, and will be put into place across the API, database, Unity & the web application. Pseudocode examples of parameter input into these 4 apps will be provided, e.g. showing how proposal data updates/will update the in-game planet & NFT metadata.
• While proposals will be off-chain, users will have the option to create a Lens post with an IPFS link to the proposal data.
  • This will query the Supabase table for proposal data and have it fed into the publication field automatically

Data presentation

• Visible frontend view of object to be classified
• Render the object view in 3D (preferably generated via Unity) on the Next wrapper
  • For now, the object view will just be a 3D, rotating image/clip from Unity WebGL.
• Data from confirmed/approved proposals will be viewable via an online database

Required features

Classification