splitwire · working public name · sku: ready

When a chain splits, know what you actually control.

Non-custodial EVM chain-split readiness. Server builds unsigned calldata. User wallet signs. No keys leave the wallet.

01 · Problem

Identical addresses can exist on two live branches with divergent state. Both may report the same chainId. A lock/claim valid on one branch can be invalid or unsafe on the other. Nominal balance ≠ completed counterparty-backed recovery.

02 · Mechanism (public · claims map §3.1)

stepbehaviourscope
1HTLC lock carries explicit branch tagdesign + source
2Compare funding-account nonces across branches before lockmethod in client
3Native value locked under hash-time rules; counterparty requiredno mint of native BDAG
4Claim/refund; wrong-tag claim revertsEVM behaviour
5Unsigned calldata out; user wallet signssigning out of server scope
6Ready assessment packages the above into org runbook + reportcommercial SKU

03 · Evidence status

claimstatusnote
HTLC + branch tag + wrong-branch rejectsource-supported§3.1
Nonce comparison methodsource-supported§3.1
Unsigned-tx client pathsource-supported§3.1
prove.py live RPC harnesseth_call override onlyno deploy · no coins spent · not a settlement
Public 10,000 BDAG live swap packnot publisheddo not claim
$1.9M / 64k uses headlineforbidden publicNDA/reference only

Every public technical claim must map to an evidence ID. Behavioural proofs ≠ funded live settlements.

04 · Ready SKUs · invoice only

skupriceincludespayment
Ready Standard$15,0001 network · readiness + replay review · recovery runbook · evidence report · certificate · technical reviewinvoice
Ready Enterprise$35,000multi-env · architecture review · emergency plan · test exercise · annual certificate · priority supportinvoice

No card checkout. No staking / pooling / retainer upsells in this sprint.

05 · Non-goals (7-day)

no mobileno tokenno daono liquidity networkno full rpc gatewayno custom domain yet