LCP on Stellar — Storyboard
design mockup · 5 screens
01 · COVER
Set the stage
What LCP does, why Stellar
02 · STEP 1
Discovery
legal-context.json fetched
03 · STEP 2
Challenge
402 + muxed destination
04 · STEP 3
Sign & settle
agent-to-agent · binding animation
05 · STEP 4
Proof
the match · evidence ready
Step 3 of 4 · Sign & settle

The agents negotiate, bind, and settle

Buyer verifies ATR binding, signs a Soroban transfer to the muxed destination, and submits to Stellar mainnet. Terms and payment bind in one transaction.

B
Buyer Agent
did:pkh:stellar:pubnet:GBUY…K3Q
Online
Requesting premium resource.
21:12:32.391 · x402
ATR hash match
SHA-256(116196) = 0xcb294f36…46ce2
21:12:32.553
Muxed binding verified
mux_id ≡ atrHash[:8]
21:12:32.553
Signing Soroban envelope…
21:12:33.021 · transfer · 0.01 USDC
Cryptographic binding · live
stellar mainnet · cap-67 muxed
TERMS · SHA-256 = atrHash FIRST 8 BYTES → MUX_ID cb 29 4f 36 bf be 26 b4 STELLAR M-ADDRESS · CAP-67 MUXED M…GCIPZII cb 29 4f 36 bf be 26 b4
Settlement
0.01 USDC
Binding
in-band · crypto
Dispute
AAA · NY
S
Seller · Publisher
GCIPZII…PWVDX7X
Online
402 Payment Required
0.01 USDC to muxed destination. The mux_id encodes the atrHash — paying binds to the exact terms.
MCIPZII…PRGWS374
21:12:32.399
terms DocuSign · sealed PDF
/.well-known/legal-context-docusign.json
21:12:32.401
Waiting for PAYMENT-SIGNATURE…
21:12:33.021 · elapsed 4.2s