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

Handling of Payload and/or OP_RETURN #451

Open
coderofstuff opened this issue Apr 11, 2024 · 1 comment
Open

Handling of Payload and/or OP_RETURN #451

coderofstuff opened this issue Apr 11, 2024 · 1 comment

Comments

@coderofstuff
Copy link
Collaborator

Payload and/or OP_RETURN would allow for storage of data in the blockdag in some form. While Kaspa currently supports these, they're considered non-standard transactions and would be rejected by nodes.

This task is to revisit the discussion around it.
@coderofstuff coderofstuff added this to the First Higher BPS Hardfork milestone Apr 11, 2024
@KaffinPX
Copy link
Contributor

KaffinPX commented Apr 11, 2024 •
edited
Loading

I was proposed a "data" per output(not UTXO) that would be prunable, would be way more scalable

(lets just enable OP_RETURN hopefully)

@coderofstuff coderofstuff removed this from the First Higher BPS Hardfork milestone Apr 12, 2024
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
High BPS upgrade
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KaffinPX @coderofstuff