casper-network / casper-network/roadmap

Make Urefs expirable

Open
#133 0 comments 0 reactions 1 assignee Claimed by @mpapierski View on GitHub
downstream ecosystem Epic
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.
Cost is set based on lifetime requested (more eras, more cost); economics will be set to motivate cost effective usage: longer lifetimes are more expensive because they are held in global state longer.
Lifetime can be extended by 'refreshing' the URef. This requires a new FFI to access the URef and update the lifetime. A deploy will be sent to make this change in global state
TODO: Need to define lifetime settings we will allow: block, session, contract are all viable options
Enhancement: Permanent lifetime is possible but very expensive?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.