Skip to content

feat: add support for OP_RETURN output on the send path - #2753

Draft
dorianvp wants to merge 1 commit into
zingolabs:devfrom
dorianvp:feat/add-opreturn
Draft

feat: add support for OP_RETURN output on the send path#2753
dorianvp wants to merge 1 commit into
zingolabs:devfrom
dorianvp:feat/add-opreturn

Conversation

@dorianvp

@dorianvp dorianvp commented Aug 31, 2026

Copy link
Copy Markdown
Member

Adds an optional OP_RETURN (null-data) output to the send path by keeping zcash_client_backend for planning and bypassing create_proposed_transactions only for the payload-carrying transaction.

@dorianvp dorianvp changed the title SKETCH: minimal OP_RETURN seam over the existing zcb spend path (alt to #2469) feat: add support for OP_RETURN output on the send path Aug 31, 2026
Adds an optional OP_RETURN (null-data) output to the send path.

`zcash_client_backend` still plans and, for payload-free sends, builds the
whole proposal. When a payload is present it rides the final transaction
of the proposal (the ZIP-320 TEX exposure step, or the single step
otherwise), which is built by driving the `zcash_primitives` transaction
builder directly so `add_transparent_null_data_output` can be called; a
Shield never carries a payload.

Adds a validated `OpReturnData` newtype (<=80 bytes) with a typed error,
and threads `Option<OpReturnData>` through `calculate_transactions`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

1 participant