rusty-kaspa
rusty-kaspa copied to clipboard
kaspanet
Memo/arbitrary data field support for transactions
We would love to see support for a memo/OP_RETURN/Arbitrary data field in Kaspa. This would make Inscriptions, such as Kasplex and cross-chain actions like Maya Protocol much easier (eliminates the need of doing 2 tx's). Maya uses the memo field of transactions to pass on arbitrary data (swap to BTC, BTC address, limit, affiliate, etc.)
Size limit Bitcoin and its forks limit the OP_RETURN size to 80 bytes. Most other chains limit the memo field to 255 bytes, which allows more freedom for builders.
This is a breaking i.e. Hard-Fork change, so it cannot be implemented in consensus lightly. that being said, I do believe payloads are on the agenda for the crescendo Hard-Fork.
This is a breaking i.e. Hard-Fork change, so it cannot be implemented in consensus lightly. that being said, I do believe payloads are on the agenda for the crescendo Hard-Fork.
Hey yes I was aware it would be a breaking change. But it's great to know that it's on the agenda. Planning is Q1 2025 right?
This is a breaking i.e. Hard-Fork change, so it cannot be implemented in consensus lightly. that being said, I do believe payloads are on the agenda for the crescendo Hard-Fork.
Hey yes I was aware it would be a breaking change. But it's great to know that it's on the agenda. Planning is Q1 2025 right?
you can read about estimated timeline here, https://kaspa.org/crescendo-hard-fork-roadmap-10bps/ ..and ctrl-f for "payloads", it has one short bullet point towards the end.