Spark Name transfers went live with the November 2025 upgrade, but there is still no wallet button for them. The Spark Names guide tells people to open Help → Debug window → Console and run three RPC commands across two wallets:
requestsparknametransfer and sends the hash to the sender,transfersparkname and sends a proof back,registersparkname with six arguments.All three calls must repeat the same name, addresses, years and additional data exactly. A mistake only shows up when the final transaction is rejected, and the node usually says nothing more than "Spark name transaction was rejected". The sender is also asked to sign a hash they cannot read: nothing in the console flow shows them which address they are giving the name to.
Names are starting to change hands (the registry has around 500 names, and short names cost 10–1,000 FIRO a year), so this is the step where users lose time or make mistakes. Neither Firo Core's GUI nor the mobile Spark library supports transfers today (sparkmobile's sparkname.h says "registration-only").
sparkname, a small open-source command-line tool, already built: https://github.com/apeirs/sparkname
sparkname request NAME: receiver creates a request file (looks up the current owner address, picks a fresh address from their wallet, calls requestsparknametransfer).sparkname approve request.json: sender's node recomputes the request hash itself and refuses to sign if it doesn't match, then shows name, from, to, term and fee, asks for confirmation and calls transfersparkname (optional unlock-and-relock).sparkname complete request.json proof.json: receiver re-checks everything and broadcasts the registersparkname transfer.sparkname status NAME --txid …: who holds the name, expiry, and whether the transfer has been mined.firod over JSON-RPC (same credential lookup as firo-cli). It never handles keys: signing stays in the wallet.275d8cc876a3e8b9a29e5656fa58fc37860264b8fc7aa8c703851bc377a11175 (bob paid 1 FIRO + 0.00076728 network fee; validity stacked to height 423302), then bob → alice from an encrypted wallet with --unlock and additional data, 65f56763f7f2c2e13c3049905942ed11914a7aaf9d9ac9310bf8558c59558322. The refusals (edited request, wrong wallet, stale proof, 15-year cap and others) were checked against the real node too. The run turned up two node behaviours a console user would trip over, and the tool now handles both: requestsparknametransfer hashes a wrong old address without complaint, and a locked wallet reports a non-zero unlocked_until.450 FIRO in total (≈ $418 at $0.93/FIRO).
| item | hours |
|---|---|
| Reading the transfer consensus code (PRs #1663, #1696, #1844, v2.1 inputs hash) and designing the flow | 3 |
| Tool: request / approve / complete / status, pre-checks, error mapping | 5 |
| Test suite (fake node with firod's rules, RPC transport tests) | 3 |
| README and worked example | 1 |
| Testnet end-to-end run, firo-site guide PR, review fixes (milestones below) | 2 |
| Total | 14 h |
14 hours at about $27/hour is $378; with the 10% volatility premium the FCS rules allow, that is $416, or 450 FIRO.
| # | deliverable | FIRO |
|---|---|---|
| 1 | Repository public and tagged v1.0 (done at submission; regtest run already done, see above). A real end-to-end transfer of a Spark Name between two wallets on Firo testnet, with both transaction ids and the command transcript added to the README so anyone can check them on the public explorer. | 300 |
| 2 | A pull request to firoorg/firo-site adding the tool to the Spark Names guide as an alternative to the console steps (merging is up to the maintainers), and 60 days of bug fixes for issues reported on GitHub or the forum. |
150 |
Payout per milestone to the address in the proposal. If the community would rather see this inside Firo Core's Qt wallet, the tested flow and checks here carry over directly, and I'm happy to discuss that as a separate follow-up proposal.
— apeir