Skip to content

SUBMISSION.md

Latest commit

 

History

History
118 lines (93 loc) · 6.63 KB

SUBMISSION.md

File metadata and controls

118 lines (93 loc) · 6.63 KB
Raw

Build X Series — Final Submission

Project summary

XGuard helps users and wallet/dApp integrations understand what an EVM transaction will do before signing. It keeps deterministic facts, bounded provider evidence, AI advisory, receipt integrity, deployment-key authenticity, policy action, and on-chain anchoring as separate claims.

Transaction → Evidence → Receipt Integrity → Deployment-key Authenticity → Policy Action → Mainnet Receipt Anchor

Final public capabilities:

  • Deterministic transaction decoding and explainable known-risk rules
  • X Layer RPC intelligence and bounded eth_call / eth_estimateGas preflight evidence
  • OKX OnchainOS read-only transaction simulation on X Layer Mainnet
  • Intent vs Reality comparison
  • Evidence-grounded AI Advisory that cannot lower deterministic known risk or control policy
  • Versioned Analysis Receipt with schema 1.0.0
  • xguard-c14n-v1 canonicalization and SHA-256 receipt integrity
  • Ed25519 deployment-key attestation of the exact receipt fingerprint
  • Deterministic Policy Guard actions: ALLOW, WARN, REQUIRE_REVIEW, and BLOCK_RECOMMENDED
  • X Layer Mainnet Receipt Anchor for an exact bytes32 receipt digest
  • Read-only Published Mainnet Proof verification

Public chain evidence

The two public evidence paths use the same hexadecimal address on different chains. They are different contracts with different purposes and must always be identified by network and chain ID.

A. Historical Testnet Evidence

This historical path records that a user explicitly reviewed an assessment. It does not execute the analyzed transaction and is not the Mainnet Receipt Anchor.

B. Current Mainnet Receipt Anchor

The Mainnet anchor proves only that this exact digest was recorded by the configured contract in a confirmed Chain 196 transaction. It does not prove transaction safety, provider truth, authorship, ownership, execution, or legal identity.

Final competition demo

The demo story is:

  1. XGuard positioning
  2. Suspicious Airdrop
  3. Deterministic 78 HIGH
  4. Intent MISMATCH
  5. BLOCK_RECOMMENDED
  6. X Layer RPC evidence
  7. OKX Mainnet evidence
  8. Analysis Receipt
  9. INTEGRITY VERIFIED
  10. Ed25519 Attestation
  11. ATTESTATION VERIFIED
  12. Deterministic Policy Guard
  13. Published X Layer Mainnet Proof
  14. anchored(bytes32) = true
  15. Evidence → Integrity → Authenticity → Policy → Anchor

The historical demo/xguard-ai-build-x-demo.mp4 is preserved unchanged and is not the final competition demo.

Claim boundaries

  • Receipt Integrity means the receipt content is consistent with its canonical SHA-256 fingerprint.
  • Ed25519 Attestation means the deployment key signed that exact receipt fingerprint.
  • Policy Guard is a deterministic integration recommendation; AI Advisory never controls it.
  • Mainnet Anchor means the exact digest was recorded on X Layer Mainnet Chain 196.
  • Empty OKX risk entries mean only that no entries were returned; they do not prove safety.
  • RPC preflight and OKX simulation are bounded current-state evidence, not a full trace, state-diff, or smart-contract audit.
  • No layer guarantees transaction safety.

Final checks

  • Canonical Production is public.
  • GitHub repository is public.
  • The application baseline passed 362 tests and the Production release gates.
  • Receipt integrity and Ed25519 attestation verification are independently demonstrated.
  • Deterministic Policy Guard behavior is demonstrated.
  • Live OKX Mainnet evidence is labeled as evidence, not a safety verdict.
  • Historical Testnet 1952 evidence and current Mainnet 196 evidence are disambiguated.
  • The Published Mainnet Proof is independently readable without wallet interaction.
  • The final demo uses no wallet connection, signature, broadcast, or new blockchain transaction.

Deployment tooling note

Repository deployment scripts are historical/developer tooling and are not part of current Production execution. The Mainnet XGuardReceiptAnchor is already deployed through an explicit human wallet flow and is publicly verifiable at the links above.