Skip to main content
This path is intentionally short and evidence-led. Stop if a configured address has no Coston2 code, a TEE is not active for the displayed extension, or a receipt cannot be opened in the explorer. Current live checkpoint (2026-08-14): LandDeal is 0xd0Ba79C80B12fcfd72851FE7ffe08Fd8885C8bf9, SilentLotInstructionSender is 0xBC39A95F2CD04B3cfF0cD47Aed8596573f731f57, and extension ID is 66252. The FCC registry currently returns no active TEE for that extension, so the reproducible live path stops at deployment/registration verification. Steps below describe the complete path once an independently attested production TEE is registered; they are not a claim that those transactions already exist.

​
Two-minute walkthrough

1

Complete the guided product story

Open /demo. Complete parcel evidence, sealed offers, private clearing, FTestXRP escrow, consent evidence, and the completion packet. Amber labels identify every simulated adapter.
2

Inspect the live boundary

Open /app. Confirm the deployed addresses and extension ID, then verify that the active-TEE check remains blocked rather than selecting a simulated machine.
3

Open public proof

Open the two contract addresses and extension-registration transaction from deployed v0.1 identifiers.

​
Live infrastructure path

  1. Open / for the product, privacy and legal boundaries, then launch /app. Review the Overview and Evidence views before connecting an EVM wallet to Coston2 (chain 114). The workspace must show the live contract addresses and the current active-TEE state without fabricated deal activity.
  2. Enter a unique auction ID, Lagos parcel references, real user-selected evidence, reserve and deadlines. Confirm the file stays local and save the displayed salt privately.
  3. Register the parcel. Open the explorer receipt and compare the live deal seller/commitments.
  4. Bind the TEE. Verify the UI displays the registry-selected TEE ID, active status, public key, code hash, platform and registered URL for the displayed Nautilius extension. Run the commands in verify production attestation and retain the PASS line; an /info response alone is not fresh attestation proof.
  5. Sign and create the encrypted auction. Inspect the instruction transaction: sensitive JSON must appear only as opaque Go-Ethereum ECIES ciphertext.
  6. Copy the public CREATE_AUCTION action ID as a fallback. From a different wallet or browser session, enter the same auction ID and read live state; Nautilius recovers the recorded create action from InstructionSender.createActionForAuction (or accepts the copied ID if needed). Retrieve its successful signed result. Only then does Nautilius enable bidding. Sign and relay a sealed bid; confirm the bidder is not the transaction sender and plaintext bidder/amount/expiry/nonce are absent from calldata.
  7. After the close, request clearing. Retrieve the signed ActionResult, then relay it to LandDeal.consumeClearing.
  8. Open the receipt. Confirm the contract accepted the action only once and live state now shows the selected buyer, clearing amount and receipt commitment.
  9. Selected buyer approves the exact FTestXRP amount and funds escrow. Compare balance, allowance and two receipts.
  10. Seller records consent and registry-evidence commitments, preserves their displayed openings, completes, then withdraws the pull credit. Alternatively demonstrate deadline expiry and the selected buyer’s refund path. These seller-supplied hashes are tamper-evident references, not legal validation; in this prototype the contract does not independently verify their truth.
  11. Open Evidence and download the JSON evidence packet. Confirm it contains deployment, auction, commitments, transaction hashes and locally preserved openings, but no raw title document. Use the Lagos eGIS link only as the official-process handoff; no registry integration is claimed.

​
Evidence checklist

  • LandDeal and InstructionSender addresses and explorer code
  • extension ID, selected TEE ID/key/status/code hash/platform and attestation-verifier output
  • register/bind/create/bid/clear/result-consume transaction hashes
  • encrypted instruction calldata evidence
  • signed ActionResult payload/signature and successful onchain verification
  • FTestXRP approve/deposit/settlement or refund hashes
  • exact dated test/build logs

​
Claim boundary

Neither path proves legal title, replaces Lagos government processes, makes FTestXRP economically equivalent to XRP, hides public transaction metadata, or establishes hardware trust without fresh official attestation-verification output. The guided route also does not prove a production TEE, FCC action, token movement, or government response.