Skip to content

Adding "arc" as a hash prefix for ARC messages #75

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.

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

Merged
merged 2 commits into from
May 28, 2025
Merged

Conversation

fabrice102
Copy link
Contributor

ARC (https://github.com/algorandfoundation/ARCs) sometimes requires hashing of some messages. This change is to ensure that arcXXXX is reserved for that purpose. This change is already in the go-algorand code:
https://github.com/algorand/go-algorand/blob/2bc55c06f4dacf247b93a15f47530f57b4925d28/protocol/hash.go#L28

ARC (https://github.com/algorandfoundation/ARCs) sometimes requires hashing of some messages.
This change is to ensure that `arcXXXX` is reserved for that purpose.
This change is already in the go-algorand code:
https://github.com/algorand/go-algorand/blob/2bc55c06f4dacf247b93a15f47530f57b4925d28/protocol/hash.go#L28
@jannotti
Copy link
Collaborator

I don't know that this needs to be in the algorand spec, proper. These hashes always appear above L1, don't they?

@fabrice102
Copy link
Contributor Author

It's mostly to be sure there is no collision of prefix between L1 and above levels.
This ensures that prefixes conflicting with arc... will never be added to the specs.

Copy link
Contributor

@cusma cusma left a comment

Choose a reason for hiding this comment

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

@fabrice102 I think reserving the arc keyword in the specs to avoid its usage at L1 is justified, as the related ARC standards have reached a stable and mature state in the ecosystem.

@cusma cusma merged commit 259fdd2 into master May 28, 2025
1 check passed
@cusma cusma deleted the arc-hash-prefix branch May 28, 2025 09:54
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