iotaledger / iotaledger/notarization

[Request]: Investigate if we can timelock objects

Open
#113 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
5
Forks
7
Avg merge
10h 34m
Merged PRs (30d)
11

Description

### Feature description

We have the requirement to be able to lock and retrieve objects similar to a [`timelock`](https://docs.iota.org/developer/references/framework/iota/timelock), but unfortunately this doesn't work the same way with notarization.

### Motivation

See description and requirements section.

### Requirements

Examples of use cases for notarize-locked objects are:

- Notarize an Identity (locking it with Locked Notarization)
- Notarize a Hierarchy (locking it with Locked Notarization)

### Open questions

As far as I can see, this is not working due to:

- `State.data` having to be `store + drop + copy` and
- `Federation` (Hierarchy) being `store, key`
- `Identity` being `key`
- capability tokens in both being `key`
- (Maybe I've missed it somewhere, but) we don't allow "unlocking" a state as far as I can see. We have a `destroy` function, but that drops the state, if I understand correctly.

### Are you planning to do it yourself in a pull request?

No

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.