Yes if, within 100 days of the first stable Bitcoin Core v30.x release, upstream bitcoin/bitcoin either
(a) merges a PR that reverts/restores the pre-v30 default behavior for the change defined below, or
(b) publishes a stable release (30.x/31.x) whose notes state the change was removed/rolled back or defaults restored.
Clock starts: the earlier of the GitHub Release “Published” time for the first stable v30.x or the bitcoincore.orgv30.x release page going live (all times PT).
Qualifying timestamp: earlier of the PR merge time or the stable release Published time that includes the reversion.
Excludes: RCs/prereleases, unmerged PRs, downstream forks/patches, doc/test-only changes, or runtime flags that merely hide the behavior without changing the default.
No if no qualifying reversion occurs within 100 days, or if no stable v30.x release occurs before market close.
Early resolution: Market may resolve Yes as soon as criteria are met.
Sources of record: bitcoin/bitcoin GitHub (releases/PRs/commits) and bitcoincore.org.

Define “the change” (binding): Bitcoin Core v30’s OP_RETURN relay-policy update (PR #32406) that raises the default -datacarriersize from 83 bytes to 100,000 bytes and allows multiple OP_RETURN outputs per transaction(aggregate bounded by datacarriersize/standard tx limits). The -datacarrier and -datacarriersize options remain available after being undeprecated via PR #33453.

Creator Reviews

@mega_dreamer

@mega_dreamer

Description