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

[ZSA] Describe state that full nodes must store for each asset, and explain the rationale for the 512-bytes asset_id limit #843

Open
daira opened this issue May 14, 2024 · 0 comments · Fixed by QED-it/zips#61
Open

[ZSA] Describe state that full nodes must store for each asset, and explain the rationale for the 512-bytes asset_id limit #843

daira opened this issue May 14, 2024 · 0 comments · Fixed by QED-it/zips#61
Labels
consensus Consensus changes, and errors or omissions in consensus specification ZIP clarification ZSAs
Milestone
NU7

Comments

@daira
Copy link
Collaborator

daira commented May 14, 2024

Also consider DoS attacks involving inflation of this state. If there is a hard limit on its size, that turns into a DoS attack on new asset creation.
@daira daira added the consensus Consensus changes, and errors or omissions in consensus specification label May 14, 2024
@daira daira mentioned this issue May 14, 2024
Open
@vivek-arte vivek-arte mentioned this issue Aug 12, 2024
Merged
@vivek-arte vivek-arte mentioned this issue Sep 1, 2024
Merged
@daira daira added this to the NU7 milestone Sep 4, 2024
vivek-arte added a commit to QED-it/zips that referenced this issue Sep 25, 2024
@vivek-arte
Improved description of the burn mechanism, and rationale for asset d…
32516a4 
…escription string size (#61)

This rewrites the burn mechanism description in ZIP 226 in order to
remove some ambiguously defined terms, and improve the clarity of the
specification.

It also adds the rationale for the choice of 512 bytes for the maximum
length of the asset description string in ZIP 227, which resolves zcash#843
(along with the additions in the already merged #59)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
consensus Consensus changes, and errors or omissions in consensus specification ZIP clarification ZSAs
Projects
None yet
Milestone
NU7
1 participant
@daira