I read through your message carefully.
Below is a response limited strictly to what has already been formally explained or structurally defined.
No assumptions. No projections. Only what is confirmed and published.
1. Dynamic Airdrop and the 180-day timeline
The conversion rate continues from where it last left off on the 180-day progression. There is no reset.
Example: if the last reference was Day 64 and seven days passed, the applicable rate becomes Day 71.
This is explicitly stated in the Conversion 2.0 explanation.
2. Conversion output and staking durations
Conversion output becomes Staked RIVER.
The available durations are: 3, 6, 9, 12 months. Longer durations receive a larger share of the same base conversion output.
This behavior is part of the published mechanism.
3. Early Unstake
An Early Unstake option will exist, but details are not announced yet.
Until the official staking announcement is released, no one should assume specific rules.
4. Conversion 2.0 behavior
What is confirmed:
- Rate continues without reset
- Daily Conversion Cap
- Per Conversion Limit
- Dynamic Conversion Curve
- Half-Life Recovery
- Staked RIVER multipliers ( voting power )
- Conversion result is Staked RIVER
These are the only guaranteed components.
Everything else belongs to separate operational or token-economic decisions, which are not defined by the Conversion 2.0 document.
5. On topics not covered by Conversion 2.0
Your questions about:
- January unlocks
- price impacts
- future buyback budget
- team operating margin
- long-term price protection
- business model beyond the mechanism
These points are not defined inside the Conversion 2.0 specification, and the current document does not provide answers to them.
What I can confirm is this:
once the Conversion 2.0 mechanism is finalized and all parameters are locked, the team will begin addressing these broader topics one by one.
They require separate explanations and depend on components still in progress (staking module, treasury structure, operating flows, etc.), so giving partial answers now would create more confusion.
For now, everything that is fully defined and publicly confirmed regarding Conversion 2.0 is here: