Skip to content

Put P2TR and P2WSH reward recipients in the MPMA from tip 971,699 - #52

Merged
droplister merged 1 commit into
mainfrom
fix/mpma-next-block
Sep 30, 2026
Merged

droplister merged 1 commit into
mainfrom
fix/mpma-next-block

Conversation

@droplister

Copy link
Copy Markdown
Member

Follow-up to #48. Core applies mpma_taproot_support to the block after its tip, and that is the earliest block a send composed now can land in. A reward send composed when the tip is 971,699 therefore lands in 971,700 or later, and Core's compose already accepts 32-byte programs.

  • scripts/lib/mpma.mjs: mpmaCapable returns true for every destination once tip + 1 >= 971,700. If the tip is unknown (NaN or not an integer), the old packed-length rule still applies.
  • scripts/reward-batch.mjs: the header comment now says the same.
  • tests/mpma-capable.test.ts: tips 971,698 and 969,320 still send P2TR/P2WSH to manual. Tips 971,699, 971,700 and 971,701 take every address. An unknown tip keeps the old split.

Gates run locally: npm run check (111 files, 1426 tests, typecheck, lint, numeric, i18n) and next build. No api code changed, so there was no wrangler dry run.

Core applies mpma_taproot_support to the block after its tip, which is
the earliest block a send can land in, so a send composed at tip 971,699
already lands in 971,700 or later. mpmaCapable now allows every
destination once tip + 1 reaches the activation; an unknown tip keeps
the pre-activation split.
@droplister
droplister merged commit a05b0fd into main Sep 30, 2026
1 check passed
@droplister
droplister deleted the fix/mpma-next-block branch September 30, 2026 17:50
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