agorix
AirdropMarketsCollectionsLeaderboardActivity
Agorix · Decentralized Marketplace
Independent · Resilient · Community-Run

A cross-chain marketplace, run by the community.

Discover, list, and trade across Bitcoin, Ethereum, and Solana on an open, community-run network.

Marketplace
CollectionsMarketsLeaderboardActivity
Network
GovernanceExplorerAirdropDocs
Account
ProfileSettings
Legal
Terms of ServicePrivacy PolicyYour Privacy Choices
agorix.io — Lasting Access
CID: 0xA60R1X · v0.1
AirdropMarketsCollections
D
Protocol Docs
Proof of AccessNetwork Fee RoutingRelease VerificationMPC Treasury SecurityPSBT SecurityNode AuthenticationRate LimitingBundle Integrity VerificationTransaction Session Reconciliation
Docs/Security & Verification/PSBT Security
Security & Verification

PSBT Security

Shamir secret sharing for PSBT distribution. GF(256) field arithmetic, AES-GCM encryption, manifest validation, reveal challenges, and race condition protection.

#PSBT Security

Partially Signed Bitcoin Transactions (PSBTs) are the atomic unit of Bitcoin ordinal trades. Because a PSBT contains enough information to complete a transaction, it must be protected during distribution to quorum nodes. The protocol uses Shamir's Secret Sharing to ensure no single node (or insufficient subset) can reconstruct the PSBT independently.

#Shamir's Secret Sharing over GF(256)

The sharing scheme operates over the Galois Field GF(256) using the irreducible polynomial 0x1b. All arithmetic (addition, multiplication, inversion) happens in this finite field, which provides the information-theoretic security guarantee.

Information-theoretic security: given T-1 shares (where T is the threshold), an attacker learns absolutely nothing about the secret. This is not computational security -- it holds even against an adversary with unbounded computing power.

#Distribution Process

  • Generate a random 256-bit AES-GCM key.
  • Encrypt the PSBT payload using AES-256-GCM with this key.
  • Split the AES key into N shares using Shamir's Secret Sharing with threshold T.
  • Distribute one encrypted PSBT copy and one key share to each quorum participant.

The default configuration is 3-of-4 threshold: 4 shares are created, and any 3 can reconstruct the AES key to decrypt the PSBT. This tolerates 1 node failure while preventing any pair of colluding nodes from accessing the PSBT.

#Manifest Validation

Every PSBT distribution includes a manifest that is validated before shares are accepted:

  • Unique participants: no duplicate node IDs in the share recipient list.
  • Share count: the number of shares matches the declared participant count.
  • Commitment verification: each share includes a SHA-256 commitment that is verified on receipt.
  • Threshold bounds: threshold T must satisfy 2 <= T <= N.

#PSBT Reveal Challenges

When a quorum needs to reconstruct the PSBT (at transaction finalization), nodes must respond to reveal challenges:

  • Each challenge is Ed25519 signed by the requesting node.
  • Challenges include a unique nonce to prevent replay.
  • Challenges have a 30-second TTL -- expired challenges are rejected.
  • Challenge IDs are tracked for dedup -- the same challenge cannot be answered twice.

A node only reveals its share in response to a valid, non-expired, non-duplicate challenge from an authorized quorum participant.

#Bitcoin Ordinal PSBT Validation

For ordinal trades, the PSBT structure is validated against specific sighash requirements:

  • Seller inputs use ANYONECANPAY | SIGHASH_SINGLE to allow buyer inputs to be added without invalidating the seller signature.
  • This sighash combination is mandatory for ordinal PSBTs and is enforced during PSBT construction and validation.

#Race Condition Protection

A critical failure mode in PSBT distribution is partial delivery: some nodes receive their shares while others do not, leaving the transaction in an unrecoverable state. The protocol addresses this with:

  • Atomic distribution: shares are distributed in a coordinated round with acknowledgment from all recipients before the round is considered complete.
  • Retry logic: failed deliveries are retried with exponential backoff within the distribution window.
  • Coverage validation: the coordinator verifies that all required participants have acknowledged receipt before advancing the transaction state.
  • Timeout handling: if coverage cannot be achieved within the distribution window, the entire round is aborted and can be retried cleanly.

#Full-Node Mode Isolation

Nodes running in full-node mode (storing all chat threads and media cache) do not gain access to PSBT shards outside their assigned quorum. PSBT share distribution is strictly scoped to quorum membership, regardless of the node storage configuration.

PreviousMPC Treasury SecurityNext Node Authentication

On this page

  • PSBT Security
  • Shamir's Secret Sharing over GF(256)
  • Distribution Process
  • Manifest Validation
  • PSBT Reveal Challenges
  • Bitcoin Ordinal PSBT Validation
  • Race Condition Protection
  • Full-Node Mode Isolation