Network & UIDs
EAS registry version: v1.4.0.
Field reference
ABI schema string:
EAS envelope fields:
Lender-registry mirror (lenderCurrentStatus)
The reconciler sweeps every 6 hours and mirrors the current LenderRegistry status onto every ACTIVE Schema B row. A verifier reading the Droplinked API sees:
verify_credit_risk tool and the verifier API both expose this mirror.
Read via Droplinked API
Read via viem (TypeScript)
Read via ethers (TypeScript)
Read via Cast (Foundry)
Indexer access (EAS GraphQL)
- Base mainnet: https://base.easscan.org/graphql
- Base Sepolia: https://base-sepolia.easscan.org/graphql
subjectRootUid; for scale, query the Droplinked API (GET /v2/attestations/credit-risk/:merchantId) which serves an indexed projection.
Trust assumptions
A Schema B attestation is authoritative if and only if:- The on-chain
schemamatches the mainnet UID above. - The on-chain
attesteris currentlyACTIVEinLenderRegistry. Check viaGET /v2/lenders/:lenderIdor read the Droplinked-API envelope’slenderCurrentStatusmirror. revocationTime == 0ANDexpirationTime > now.- The
methodologyHashresolves to anACTIVErow in the methodology registry for that lender — the lender’s published methodology document is the explanation surface for the verdict.
A Schema B attestation issued by a lender that has since been SUSPENDED or ARCHIVED remains on-chain ACTIVE — the chain has no opinion on the lender’s current standing. The Droplinked reconciler exposes the current registry status via
lenderCurrentStatus. Verifier-side policy decides whether to honor it. The agentic PM shadow protocol is explicit: this is a verifier decision, not a reconciler decision.Related
- Trust Fabric overview
- Schemas overview
- Lender Registry Lookup
- Methodology Registry Lookup
/v2/underwriting-signals/:merchantId— composite Schema B + C read