Skip to content

feat: add AI Evidence Oracle example (Procedural Proof) - #1951

Open
fmdd123123-create wants to merge 1 commit into
LayerZero-Labs:mainfrom
fmdd123123-create:feat/oapp-ai-oracle
Open

feat: add AI Evidence Oracle example (Procedural Proof)#1951
fmdd123123-create wants to merge 1 commit into
LayerZero-Labs:mainfrom
fmdd123123-create:feat/oapp-ai-oracle

Conversation

@fmdd123123-create

Copy link
Copy Markdown

A new trust primitive for the AI era — OApp that verifies AI process compliance (not data correctness) and dispatches verified decisions cross-chain via LayerZero V2.

Four-layer architecture:

  1. Evidence: AI submits decision + evidence hash (IPFS commitment)
  2. Verification: Independent verifiers audit SOP compliance
  3. Distribution: LayerZero dispatches verified decisions cross-chain
  4. Execution: Target chain receives and acts

Trust model isomorphic to DVN:

  • DVN verifies transport integrity (hash comparison)
  • EvidenceOracle verifies process compliance (SOP audit)
  • Both are permissionlessly challengeable (fraud proof via replay)

Includes:

  • EvidenceOracle.sol — single OApp contract
  • Hardhat tasks: ai:submit, verify:decision, dispatch:decision, challenge:decision
  • SOP framework with example (rainfall trigger for insurance)
  • layerzero.config.ts for Sepolia ↔ BSC Testnet
  • Full README with architecture explanation

Live deployment:

  • Sepolia: 0xaa24CC417EC7ae219F52C400E64E600AAfD3f45d
  • BSC Testnet: 0xc7FFF00d2c2C6B0aC5D726d3E6e317cCae638214

A new trust primitive for the AI era — OApp that verifies AI process
compliance (not data correctness) and dispatches verified decisions
cross-chain via LayerZero V2.

Four-layer architecture:
  1. Evidence: AI submits decision + evidence hash (IPFS commitment)
  2. Verification: Independent verifiers audit SOP compliance
  3. Distribution: LayerZero dispatches verified decisions cross-chain
  4. Execution: Target chain receives and acts

Trust model isomorphic to DVN:
  - DVN verifies transport integrity (hash comparison)
  - EvidenceOracle verifies process compliance (SOP audit)
  - Both are permissionlessly challengeable (fraud proof via replay)

Includes:
  - EvidenceOracle.sol — single OApp contract
  - Hardhat tasks: ai:submit, verify:decision, dispatch:decision, challenge:decision
  - SOP framework with example (rainfall trigger for insurance)
  - layerzero.config.ts for Sepolia ↔ BSC Testnet
  - Full README with architecture explanation

Live deployment:
  - Sepolia: 0xaa24CC417EC7ae219F52C400E64E600AAfD3f45d
  - BSC Testnet: 0xc7FFF00d2c2C6B0aC5D726d3E6e317cCae638214
@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm yargs is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: examples/oapp-ai-oracle/package.jsonnpm/hardhat@2.29.1npm/yargs@17.7.3

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant