Vite demo application

Repo: signal-k/sytizen on branch wb3-5...

Package management

• Build manager: React/Vite
• RPC manager: npx thirdweb > hardhat

Contract-side

• Solidity code

Migration & functionality improvements

Obviously, we’ll need to migrate back to Next.js (potentially using Snowpack as a replacement for Vite) once we finish the testing phase. This is because the main application is built on Next.

• Vite package.json:
• Next package.json (proposal):
• Current (main app) package.json:

Smart contract adjustments & documentation

The first release of this application will follow a slightly different approach to voting on proposals/classifications as compared to regular Decentralised Autonomous Organisations. Rather than voting on specific proposals using custom ERC20 tokens, users will create proposals and pledge their “classification tokens” to different proposals in a Kickstarter model. I’m experimenting with this model for three reasons:

• Sample documentation that we’re following for this build uses this as a base
• It could potentially be more friendly to newcomers to the DAO space, and alleviate some problems with regular voting
• Some classifications (whether it’s between data set types like Planets 🪐 & Seismic data 🌋 , or between different “types” on one data set [type]) may require a heavier weighting (e.g. if a user has claimed something special, or if there are >2 choices (not every proposal would be a binary decision e.g. “is a planet” vs “is not a planet”, there could be a third option “is a planet with x property”. It is not yet determined if we will vote on properties alongside the ‘binary’ classification result in a single transaction). So some proposals may require more tokens, or two different wallets may propose different classifications that are both true.