Skip to content

[Ceres]: Document FATE delegation signatures#520

Merged
hanssv merged 2 commits intomasterfrom
delegation_signatures
Jan 9, 2024
Merged

[Ceres]: Document FATE delegation signatures#520
hanssv merged 2 commits intomasterfrom
delegation_signatures

Conversation

@hanssv
Copy link
Member

@hanssv hanssv commented Nov 22, 2023

In Ceres we introduce better, more structured, delegation signatures. This (a) properly documents the old delegation signature, and (b) documents the new more structured signatures.

This PR is supported by the Æternity Foundation

Copy link
Member

@davidyuk davidyuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


There are five different delegation signatures:
- `AENS_PRECLAIM` - the user signs: `owner account + contract`
- `AENS_CLAIM`,`AENS_UPDATE`, `AENS_TRANSFER`, `AENS_REVOKE` - the user signs:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- `AENS_CLAIM`,`AENS_UPDATE`, `AENS_TRANSFER`, `AENS_REVOKE` - the user signs:
- `AENS_CLAIM`, `AENS_UPDATE`, `AENS_TRANSFER`, `AENS_REVOKE` - the user signs:

We use the tag `0x1a01` to identify delegation signatures. We use the following
tags/types to identify the different delegation signatures:

| Tag | Delegation type |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With this tag, we don't need prefixed ids and can use binary as before, but I don't have a preference.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's do it like this, it is in line with the other serializations...

@ThomasArts ThomasArts self-assigned this Dec 11, 2023
@hanssv hanssv requested review from ThomasArts and removed request for ThomasArts December 11, 2023 15:03
- `ORACLE_RESPOND` - the user signs: `query id + contract`

To protect about cross network re-use of signatures, the data to be signed is
also prefixed with the _network id_.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not mention the net id everywhere? When I see "the user signs" I would expect that the user signs exactly that with no qualifications in a paragraph after.

This is what I hate in law language the most.

@hanssv hanssv merged commit 8a9d1d1 into master Jan 9, 2024
@hanssv hanssv deleted the delegation_signatures branch January 9, 2024 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants