0.22% was the original value but then shortly before the Shelley hardfork it was changed to 0.3%.
Adopting an exponential decay approach to prevent Cardano’s reserve from running out makes sense in this situation.
Calculating the 'reserve half life' (that is, the time that it takes for half of the reserve to be used up) visualizes the impact of choosing a specific value of ρ over another. This was the subject of much discussion, and eventually, the value assigned was 0.22%. The reason why is that mathematical projections showed that a ρ (the fixed percentage of ada going into the virtual pot every epoch) value of 0.22% would mean a reserve half-life of four to five years. In simple terms, just half of the remaining reserve would be used every four to five years.
Calculating the 'reserve half life' (that is, the time that it takes for half of the reserve to be used up) visualizes the impact of choosing a specific value of ρ over another. This was the subject of much discussion, and eventually, the value assigned was 0.3%. The reason why is that mathematical projections showed that a ρ (the fixed percentage of ada going into the virtual pot every epoch) value of 0.3% would mean a reserve half-life of four to five years. In simple terms, just half of the remaining reserve would be used every four to five years.
**Choosing τ**
Rename acronym field to ticker
![iohk-bors[bot]](https://avatars.githubusercontent.com/in/17473?v=4&s=80)
2409: Upgrade to cabal-3.4.0.0 for documentation r=newhoggy a=newhoggy Co-authored-by: John Ky <[email protected]>
These functions share the same general properties, so it makes senses to document these properties in a single place.
Use this function to replace the common functionality of: - `unsafePartitionCoin` - `unsafePartitionTokenQuantity`
- Model a lower-level "weakly-typed" metadata, which is essentially just a JSON object. - Model a level above this layer that translates from the "weakly-typed" metadata into a "strongly-typed" metadata. - Use the "weakly-typed" metadata type in all lower-level areas: - The database/storage layer - The server layer - The webhook layer - All these layers don't care much about what form the metadata is in, and so the weak type is more appropriate here. - Use the "strongly-typed" metadata type in the PR validator. - This is the only area where we want the stronger types. - Shuffle tests around accordingly, write new tests. - Cleanup the codebase a bit.