fix(overlay-topics): reject unlinked Mandala token outputs; release 1.7.3 - #535
Merged
sirdeggen merged 2 commits intoSep 15, 2026
Merged
Conversation
Bumps @bsv/overlay-topics to 1.7.3 for the Mandala admin-chain anchoring and spender-identity fixes, with the governed release notes, health baseline and package documentation (docs page, stack facts, API migrations) updated to match. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> (cherry picked from commit 7a4ffc6fc7a14e4cda2b91f72d04655f28ef7b1f)
…ed linkage verifyFtOutputs skipped a MandalaToken-shaped output whose linkage was missing, mismatched or unreadable, and conservationHolds summed only the admitted subset. A transaction could therefore carry an extra token output of any value, still have its siblings admitted, receive the overlay's admission signature and be broadcast: a phantom coin mined inside an attested transaction, credited by any offline verifier that stops its coverage walk at "this txid was admitted". Such an output now rejects the whole transaction with "output N: MandalaToken-decodable output with no verified linkage" (wire contract §6), byte-identical to the Go engine. Plain non-token outputs are unaffected. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
sirdeggen
requested review from
BraydenLangley,
tonesnotes and
ty-everett
as code owners
September 15, 2026 20:50
|
12 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two things, both for
@bsv/overlay-topics:verifyFtOutputsused tocontinuepast aMandalaToken-shaped output whose linkage was missing, verified to a different key, or could not be opened, andconservationHoldssummed only the admitted subset. A transaction could therefore carry an extra token output of any value, still have its siblings admitted, receive the admission signature and be broadcast: a phantom coin mined inside an attested transaction, which an offline verifier that stops its coverage walk at "this txid was admitted" then credits. Such an output now rejects the whole transaction withoutput N: MandalaToken-decodable output with no verified linkage(wire contract §6, byte-identical to the Go engine). Plain non-token outputs are unaffected.mainstill says 1.7.2. This carries the bump (package.json, health baseline, release notes, package docs, stack facts, API migrations) covering fix(overlay-topics): anchor the Mandala admin chain and name spenders from state #532 and this fix.Tests
UnlinkedTokenOutput.test.ts: fully linked transfer admits; one unlinked sibling rejects; wrong-party linkage rejects; malformed linkage rejects; plain change output is outside the rule; reason string pinned.mandala.test.ts: the former "does not admit FT outputs lacking valid linkage" now asserts the rejection.docs:facts:checkand the governance/documentation health tests pass.🤖 Generated with Claude Code