boomcrypto / citycoins2

CityCoins V2

citycoins-ui-v2

Upgraded front-end for CityCoins.

Development

This repository uses React + Vite with:

• micro-stacks for wallet auth
• Chakra UI for components
• Jotai for state management

To run locally:

npm install
npm start

Deployed via Cloudflare Pages.

citycoins2's Issues

Display STX stacking information per cycle and cycle

For each city and stx reward cycle, display

• when the city's STX were locked (similar to https://fast-pool-ui.vercel.app/u/SP8A9HZ3PKST0S42VM9523Z9NV42SZ026V4K39WH.ccd002-treasury-mia-mining-v2)
• the share in the pool (stacked STX / total stacked)
• how much rewards were received in STX (via https://explorer.hiro.so/address/SP21YTSM60CAY6D011EZVEVNKXVW8FVZE198XEFFP?chain=mainnet)
• the total BTC received (via statsonchain)

Store fetched data in local storage

The basic structure so far:

• query atoms fetch data and provide status
• hooks kicks off query, returns status based on query atom
• localstorage atoms store results, written to by components

Components can respond to the loading values in the hook or the null localstorage constant.

Components should write the fetched data with useEffect().

Display date for proposals

Not sure the best place for it yet, but seems relevant with vote titles when browsing.

Proposals accordion should allow multiple open

This should be a small change, mostly just noting it here. It'd be nice to be able to expand any proposal and leave it open, which helps if comparing information side-by-side. Each can still be closed by clicking its title.

Evaluate fetch options in hook

Each hook could return either the query atom or the local storage atom values.

Default would be local storage, pass parameter like update=true to force query.

Can set data same way a successful query would (hasData = true).

If local storage isn't found, use query atom and return.

Writing to the atoms still happens at the component level (or they can do whatever they want with the data at that point).