https://github.com/prof-faustus/idattr-onchain
Anchor identity-registry roots on the BSV chain: build/sign a standard BIP143/FORKID tx committing a 32-byte root, broadcast to Teranode regtest (verified live, mined). Companion to identity-attribution.
https://github.com/prof-faustus/idattr-onchain
Last synced: about 2 months ago
JSON representation
Anchor identity-registry roots on the BSV chain: build/sign a standard BIP143/FORKID tx committing a 32-byte root, broadcast to Teranode regtest (verified live, mined). Companion to identity-attribution.
- Host: GitHub
- URL: https://github.com/prof-faustus/idattr-onchain
- Owner: prof-faustus
- Created: 2026-06-02T03:25:42.000Z (about 2 months ago)
- Default Branch: master
- Last Pushed: 2026-06-02T07:54:54.000Z (about 2 months ago)
- Last Synced: 2026-06-02T09:23:58.801Z (about 2 months ago)
- Language: Rust
- Size: 12.7 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# idattr-onchain
Anchor an identity-registry root **on the BSV chain**. Builds and signs a standard BSV transaction
(BIP143 / SIGHASH_FORKID) that spends a funded P2PKH output and commits the 32-byte registry/anchor
root through the SCARCITY / TEA-BSV **note-anchoring template** — never OP_RETURN — for broadcast to
a Teranode regtest node via `sendrawtransaction`.
It reuses the audited BSV primitives from `overlay-broadcast` (path deps): `bsv` (tx build, P2PKH,
`sighash`, serialize) and `ckd` (k256 ECDSA `sign_prehash_der`). It is a **separate workspace** from
the self-contained `identity-attribution` system precisely because it depends on the sibling repo.
## Use
```powershell
# 1) a key + its regtest P2PKH address (mine coins to ADDRESS)
idattr-onchain keygen
# -> PRIVKEY .. / PUBKEY .. / H160 .. / ADDRESS m...
# (mine 101 blocks to ADDRESS so a coinbase matures; read its txid = block.merkleroot and value)
# 2) build the signed anchor tx
idattr-onchain build-anchor --privkey --pubkey \
--coinbase-txid --vout 0 --value \
--anchor-root <32-byte-hex> [--fee 500]
# -> TXID .. / RAWTX (broadcast RAWTX with sendrawtransaction)
```
The transaction has a single output — the **possession outpoint** — whose locking script is the
note-anchoring carrier ` OP_DROP OP_DUP OP_HASH160 OP_EQUALVERIFY OP_CHECKSIG`: the
32-byte root rides as pushdata (carried, not executed) ahead of a native P2PKH spend tail, so the
output stays a genuinely spendable UTXO and the act of spending the funded input is bound to
committing the root in one transaction. This satisfies REQ-CHAIN-0003 (state root committed by the
possession transaction), REQ-CHAIN-0001/0002 (standard P2PKH), and the absolute OP_RETURN prohibition
(REQ-CHAIN-0051 / REQ-BUILD-0010). It mirrors `bsvscript::BuildEnvelopeDrop` and
`SPV/03-identity/anchor` (SYS-ENC-001/002, ID-CON-001).
## Verified live
See [ANCHOR_RECEIPT.md](ANCHOR_RECEIPT.md) — a real `idattr` registry root committed on-chain on the
Teranode regtest node, accepted by `sendrawtransaction` and mined into a block.