On-Chain Credentials
Publish your NAI report as a verifiable, tamper-evident credential on-chain. Soulbound, borrower-signed, lender-readable.
Overview
Once you have generated a report, you can publish it as an on-chain credential. The credential is a soulbound token — it lives in your wallet, it cannot be transferred, and any lender can independently verify its contents without trusting NAI to be honest after the fact.
Why bother? Three reasons. First, immutability — once published, the report cannot be silently rewritten by us or anyone else. Second, portability — a borrower verified through NAI can present the same credential to any lender that supports the standard. Third, composability — on-chain lending protocols can read your NAI grade directly as part of their underwriting.
Standards & Network
| Component | Standard | Network |
|---|---|---|
| Attestation | EAS (Ethereum Attestation Service) | Base |
| Token wrapper | ERC-5192 (Soulbound) | Base |
| Off-chain payload | IPFS (encrypted detail) | — |
EAS is the canonical attestation registry for the Ethereum and OP-stack ecosystem. ERC-5192 is the standard for non-transferable tokens. Together they let your credential show up in any wallet that supports SBTs while remaining independently verifiable on-chain.
What Gets Signed
When you publish, you sign an EIP-712 typed payload with your wallet. The payload commits to:
| Field | Purpose |
|---|---|
| Borrower address | Wallet that owns the credential — must match the signer |
| Report hash | SHA-256 of the canonical report JSON; proves the score was not rewritten |
| Source-data hashes | Hashes of every input (bank statement, wallet snapshot, document) the report was built from |
| Scoring model version | e.g. 2.0.0 — pins which formula generated the score |
| Net Asset Index grade | Public summary field (A+ through D) |
| Valid until | Expiry timestamp — credentials age out and need re-publishing |
| IPFS pointer | CID for the encrypted detail report (only the borrower and authorised lenders can decrypt) |
Why It Cannot Be Manipulated
Pre-publish, the report lives in our database and is editable like any draft. Post-publish, the chain becomes the source of truth.
If we silently rewrote your report in our database, anyone with the on-chain attestation UID would catch it: the new report would not match the hash you signed at publish time. We literally cannot rewrite history once it is on-chain.
Source-data hashes go a step further. Wallet and on-chain inputs are independently re-verifiable from the chain itself. Bank-API responses are committed to at publish time and are upgradable to provider-signed payloads as Plaid and similar issuers roll out signed responses.
Publishing Flow
| Step | Who | What Happens |
|---|---|---|
| 1 | Borrower | Generates a report and reviews the publish payload |
| 2 | Borrower | Signs the EIP-712 payload with their wallet (no gas) |
| 3 | NAI | Submits the delegated attestation to EAS on Base; pays gas |
| 4 | NAI | Mints or updates the borrower's soulbound credential token to point at the latest attestation UID |
| 5 | Borrower | Credential appears in their wallet; can be shared with any lender |
Borrowers do not pay gas. NAI relays the transaction and may charge a per-publish fee or a subscription depending on plan.
For Lenders
Given a borrower's wallet address, a lender can verify their credential entirely on-chain. No NAI API call required. The attestation UID resolves to the signed payload, and source-data hashes can be re-derived from primary sources (chain queries for wallets, signed payloads for bank data).
Lenders integrating into on-chain lending protocols can read the borrower's NAI grade directly inside their smart contracts.