casper-network / casper-network/roadmap
Set expiry time on uref
- Dominant language
- No language data
- Stars
- 12
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
New urefs will expire by default- lifetime must be set on creation. Lifetime is number of eras as cost will be set according to the number of eras.
Expiry is at end of era, when it is pruned if expired. Allows more data to be purged. Note: EE doesn't have a concept of 'era' so it will be a forward calculation of block-time.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating where urefs are created and where expired data is pruned, then compare era-based expiry with the forward block-time calculation described for EE. Done means lifetime is required at creation, expiry is evaluated at the intended boundary, and expired data can be purged consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100