[codex] Fix Firo Spark Name v2.1 registration#1413
Open
reubenyap wants to merge 5 commits into
Open
Conversation
reubenyap
marked this pull request as ready for review
July 8, 2026 15:41
This was referenced Jul 16, 2026
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
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.
What changed
P2PKH + OP_SPARKNAMEID <name> OP_DROP <sparkAddress> OP_DROP.additionalTxSizeinput.flutter_libsparkmobile@53db5a06a7b7f3df68fe6263f1453f77513bec06, whose shared validator rejects underscores before transaction construction.Root causes
NAME_FOR_TESTINGwas rejected because Firo Core accepts only alphanumeric characters,-, and.in a Spark Name. The wrapper incorrectly allowed_, so Stack created a transaction that Core rejected as an invalid name.The v2.1 tagged fee output also adds bytes that Spark Mobile's standard 34-byte transparent-output model does not include. A confirmed
namefortestingregistration demonstrates the exact calculation:At Firo Core's default block minimum of 1,000 atomic units/kB, the 3,438-atom form is below the 3,473-byte transaction size and can remain unconfirmed. Measuring
taggedScript.length - baseScript.lengthrestores the estimator's existing 129-byte safety margin without hard-coding the tag layout.The exact-balance path separately attempted to subtract the miner fee from the mandatory name payment. Registration now requires enough balance for both values.
Related
Validation
git diff --checkpasses locally.NAME-FOR.TESTINGpasses the corrected pattern;NAME_FOR_TESTINGfails.aliceand the required opcode structure.