casper-network / casper-network/roadmap
refresh uref lifetime
Open
- Dominant language
- No language data
- Stars
- 12
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the URef implementation and existing FFI boundaries, then trace how deploys update global state. Clarify the required lifetime-refresh behavior and its acceptance criteria before changing code; done means the new FFI can refresh a URef lifetime in global state.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100