# Open questions and decisions

The source specification records eleven decisions: three settled (1, 2, and 4) and eight open. Recommendations are used by default until changed. None prevents development from starting.

| # | Decision | Recommendation |
| --- | --- | --- |
| 1 | $VIVRA pair asset on Pons (final) | settled: ETH |
| 2 | Cycle duration | settled: 1 week, 5 candidates from launch |
| 3 | Delay between signup and first vote | 24 h, except cycle 1 |
| 4 | Share of CTO token fees for its community | settled: 0%; everything buys back and burns $VIVRA |
| 5 | $VIVRA bought with CTO token fees | burned |
| 6 | Buyback cap per CTO token | its market cap at voting time |
| 7 | Early buyback stop | Day 3 if volume has not doubled |
| 8 | Team purchase at launch | small purchase announced 24 h ahead, with public amount and wallet |
| 9 | Day 7 Revived thresholds | average volume ×5 versus the 7 days before the vote, and holders +10%; graduation for a token on the curve |
| 10 | Domain name and X handle | check vivra.* and handle availability first |
| 11 | Dapp language | English in V1 |

## Questions for Pons before building the flywheel

- [ ] Can the same team submit a CTO every week?
- [ ] How long does application processing take?
- [ ] Can one wallet receive fees from multiple CTO tokens?
- [ ] What is the procedure for a v1 token?
- [ ] Does the deployed `claim` take an amount, unlike the published ABI?