Proofline is an explainable transaction due-diligence layer for web3 products. It takes the wallet, token, contract and transaction signals a product already has, combines them with DD.xyz risk intelligence, and returns a policy decision that users can inspect before signing.
Most wallet warnings are opaque labels shown after a user has already made a decision. Teams need an auditable, product-native decision layer that can say why a transfer is allowed, needs review, or must be blocked.
Proofline is designed as a thin, privacy-aware layer between transaction composition and wallet signing:
- A dApp sends minimal transaction context to its server-side policy endpoint.
- The endpoint queries DD.xyz Threat, Approval and Transaction Risk APIs using a protected API key.
- Proofline normalizes provider evidence with local transaction decoding and the app's own allow/review/block policy.
- The client renders the decision, evidence freshness and the exact policy rule that applied.
No private keys, seed phrases or signing permissions are ever requested by Proofline.
The grant will fund production access to the DD.xyz API surface. The integration is deliberately server-side:
dApp transaction preview
-> Proofline /assess API
-> DD.xyz: threat + approval + transaction risk
-> local policy engine + transaction decoder
-> explainable allow / review / block result
The adapter will enforce request schemas, cache results by address and block height, tag evidence with source and timestamp, and fail closed when a policy requires evidence that cannot be obtained.
This repository contains a self-contained, dependency-free interactive demonstration in index.html. Run it with any static server:
npx serve .The “Run due diligence” control cycles through three deterministic scenarios: review, allow, and block. The UI intentionally uses fixture data until DD.xyz credentials are issued; no API keys are embedded in browser code.
- Week 1: typed API adapter, Solana transaction context parser, policy schema and audit log.
- Week 2: wallet / dApp SDK with transaction-preview integration and evidence states.
- Week 3: pilot integration, false-positive review loop and public security documentation.
DD.xyz credits will be used for server-side risk lookups during the pilot. The product will retain only normalized decision evidence necessary for user support and audit, with configurable retention by integrator.
MIT