Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The use of the term "metadata hash" in AQP 1.1 is confusing #9

Open
rht opened this issue Jan 19, 2022 · 1 comment
Open

The use of the term "metadata hash" in AQP 1.1 is confusing #9

rht opened this issue Jan 19, 2022 · 1 comment

Comments

@rht
Copy link

rht commented Jan 19, 2022

The verification hash is composed of hash_sum(content_hash + metadata_hash + signature_hash + witness_hash). With metadata_hash defined as domain_id + time_stamp + previous_verification_hash. It doesn't make sense to group those 3 as the metadata of a revision, whereas a signature, or a witness detail of a revision could also be considered as metadata as well.

The term "metadata" should be used to describe all of them.
@FantasticoFox FantasticoFox transferred this issue from inblockio/aqua-docs Sep 27, 2024
@rht
Copy link
Author

rht commented Oct 13, 2024

The term will be made obsolete in inblockio/aqua-verifier-js#28.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rht