CCIP-012 / CCIP-013 Remaining Work Items

[whoabuddy]

CCIP-012 / CCIP-013 Remaining Work Items

---

Note: for a more recent list of tasks see citycoins/protocol/issues/34

---

This discussion summarizes the remaining tasks for each phase of CCIP-012/013, and will serve as the main place to see status updates throughout the voting and implementation.

• CCIP-012: Stabilize Emissions and Treasuries
• CCIP-013: Stabilize Protocol and Simplify Contracts

Preparing for the Vote

Check that all repositories are merged and up-to-date.

citycoins/contracts

• Update clarinet library contracts#204
• BREAKING CHANGE: Release v2.0.0 contracts#205
• tag main with new version 2.0.0
• make develop default branch

citycoins/ui

• Include community updates ui#156
• make develop default branch

citycoins/api

• good to go!

citycoins/governance

• add CCIP authors and supporting materials
• finalize CCIP-012 details
• update README with activation details
• check/fix CCIP-009: Rename map for readability #7

---

Add Ryan Waits (StackerDAO Labs) to the GitHub org.

• done!

Create voting contract for CCIP-012

• Add vote and tardis contracts contracts#207 (finalized, awaiting review)
  • blocker: V3 Tardis read-only function costs exceed limits contracts#208
  • workaround: API can query historical info
• determine vote scale factor (V1 and V2 scale factor calculations)
  • MIA cycles 21 and 22
  • NYC cycles 15 and 16
  • MIA scale factor: 0.8605 (prev: 0.6987)
• test with new tardis contract (deployed)
• include references to CCIP-012 (finalized version)
• fix read-only contract call budget issues
• simplify and update contract code
• update CCIP-011 with vote details and spreadsheet
• create timeline graphic (see Miro for v1 example)

Create voting UI to interact with contract

• get access to repository with previous UI framework
• decide domain to deploy - stabilize.minecitycoins.com ?
• update vote UI information to new contract
• deploy new vote UI at stabilize.minecitycoins.com

Phase 1: Reduce CityCoin Emissions

• finalize 2% emissions modeling (linked here)
• convert spreadsheet to ods format, store with CCIP-012
• add table to CCIP with block rewards v1-v2-v3
• simulate upcoming changes Add CCIP-012 tests contracts#209
• finalize Miro outline of implementation flow

For MIA/NYC implementation:

• create job in auth contract
• add uint parameters for coinbase amounts
• compare amounts to existing results
• activate job for approval voting
• get 3/5 approval
• execute job

Phase 2: Move CityCoin Treasuries to Smart Contract Vaults

• create new citycoins/protocol repo to store DAO contracts

Plan initial DAO structure with 3-of-5 signers

• develop launch plan similar in structure to the EcosystemDAO launch plan
• collab with StackerDAOs, EcosystemDAO

Implement initial DAO proposals

• Initial DAO configuration protocol#1
  • base-dao.clar
  • ccd001-direct-execute.clar
  • ccd002-treasury-mia.clar
  • ccd002-treasury-nyc.clar
  • double-check all contract interactions
• Initial DAO configuration part 2 protocol#2 (in final review)
  • add relevant contract tests
  • request peer reviews on final design
  • generate deployer address: SP1XQXW9JNQ1W4A7PYTN3HCHPEY7SHM6KP98H3NCY
• implement fixes for tests Fix print events and code cleanup protocol#9
• deploy DAO contracts to testnet

Update the wallet address in core contracts

• uses 3-of-5 auth job like the coinbase amounts
• simulate upcoming changes Add CCIP-012 tests contracts#209
• review list of impacted entities similar to this one
  • CityCoins UI (minecitycoins.com)
  • Syvita UI (syvitamining.com)
  • miamining/mining.nyc dashboards
  • Twitter bots or anything that reports wallet balances

Phase 3: Simplify the CityCoins Contract Design

• deploy and activate CCIP-013 vote Add CCIP-013 vote contract contracts#210
• develop simplified version to perform initial testing
  • ccd003-user-registry.clar
  • ccd004-city-registry.clar
  • ccd005-citycoin-mining.clar
  • ccd006-citycoin-stacking.clar
• research better migration paths for mining/stacking data
  • mining should not miss any blocks due to code-as-proposal implementation
    • could activate only if previous contract is shut down first?
  • stacking should migrate state between contracts for the current cycle
    • or refer back to the original until the active cycle is complete
• setup proposal with Clarity to execute that:
  • sets up and enables the extensions
  • initializes any contracts in the protocol
  • note that both above could be separated if needed
• research old issues / improvements to incorporate
• opportunity for code cleanup / flow control checks (simplify!)
• convert from current auth patterns to Executor DAO extensions
  • generalize as a "legacy connector"?
  • coinbase amounts
  • coinbase thresholds
  • set token URI
  • set city wallet

Phase 4: Update Registration, Mining and Stacking Flows

• develop design for current stacking model (pooled delegation)
• prepare design for Stacks 2.1 launch (Nov-Dec 2022)

Design Goals

• 100% of STX spent mining CityCoins is transferred to the city’s treasury
• 100% of the STX within the city’s treasury are stacked for STX rewards
• 100% of the STX rewards are claimable by anyone who stacks CityCoins, such that:
  • rewards are distributed per past stacking cycles
  • rewards are distributed proportionally to the amount of CityCoins stacked
  • if they are not claimed within n cycles, they can be claimed by the DAO? (open for discussion)

Reward Cycle Participation - MIA

Reward Cycle	Total Stacked MIA	Total Supply MIA	Percentage
16	3,337,657,374	4,825,550,000	69.17%
17	903,513,362	4,997,150,000	18.08%
18	1,101,162,929	5,100,150,000	21.59%
19	1,751,845,435	5,204,100,000	33.66%
20	2,274,467,272	5,310,300,000	42.83%
21	2,469,371,221	5,411,200,000	45.63%
22	2,593,145,882	5,516,000,000	47.01%

Reward Cycle Participation - NYC

Reward Cycle	Total Stacked NYC	Total Supply NYC	Percentage
10	2,803,440,578	3,558,250,000	78.79%
11	1,128,337,110	3,747,150,000	30.11%
12	1,514,271,882	3,961,550,000	38.22%
13	2,371,806,059	4,164,750,000	56.95%
14	2,625,652,238	4,384,250,000	59.89%
15	2,980,119,157	4,598,450,000	64.81%
16	3,036,819,828	4,805,950,000	63.19%

Nice to Haves

citycoins/scripts

• remove references to documentation
• remove workflow for documentation build
• release V2 scripts from feat/implement-v2

[Rapha-btc]

Hello Jason,

do you know when Stacks will have moved to delegated / smart contract and when it will be time to do stacking with new contract?

Thank you.