Skip to content

Uncap datacarrier by default#1552

Draft
ivanlele wants to merge 2 commits into
ElementsProject:elements-23.xfrom
ivanlele:cherry/uncap-datacarrier-by-default
Draft

Uncap datacarrier by default#1552
ivanlele wants to merge 2 commits into
ElementsProject:elements-23.xfrom
ivanlele:cherry/uncap-datacarrier-by-default

Conversation

@ivanlele
Copy link
Copy Markdown
Collaborator

@ivanlele ivanlele marked this pull request as draft May 21, 2026 15:20
@ivanlele ivanlele force-pushed the cherry/uncap-datacarrier-by-default branch 2 times, most recently from 97d48ec to 96c6166 Compare May 22, 2026 12:43
@delta1
Copy link
Copy Markdown
Member

delta1 commented May 22, 2026

Looks good so far, just needs an update to one of the functional tests (or a new functional test) to check it's working correctly

ivanlele and others added 2 commits May 22, 2026 17:43
a189d63 add release note for datacarriersize default change (Greg Sanders)
a141e1b Add more OP_RETURN mempool acceptance functional tests (Peter Todd)
0b4048c datacarrier: deprecate startup arguments for future removal (Greg Sanders)
63091b7 test: remove unnecessary -datacarriersize args from tests (Greg Sanders)
9f36962 policy: uncap datacarrier by default (Greg Sanders)

Pull request description:

  Retains the `-datacarrier*` args, marks them as deprecated, and does not require another startup argument for multiple OP_RETURN outputs.

  If a user has set `-datacarriersize` the value is "budgeted" across all seen OP_RETURN output scriptPubKeys. In other words the total script bytes stays the same, but can be spread across any number of outputs. This is done to not introduce an additional argument to support multiple outputs.

  I do not advise people use the option with custom arguments and it is marked as deprecated to not mislead as a promise to offer it forever. The argument itself can be removed in some future release to clean up the code and minimize footguns for users.

Tree-SHA512: 3da2f1ef2f50884d4da7e50df2121bf175cb826edaa14ba7c3068a6d5b2a70beb426edc55d50338ee1d9686b9f74fdf9e10d30fb26a023a718dd82fa1e77b038
@ivanlele ivanlele force-pushed the cherry/uncap-datacarrier-by-default branch from 96c6166 to b521a1b Compare May 22, 2026 14:43
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.

3 participants