The Protocol
The Local Proof Protocol
Proof for owned business identity in the AI era.
Created and operated by IdentityRecord.
Core Definition
The Local Proof Protocol is the framework underneath every Identity Record. It turns accepted, owner-controlled, evidence-backed business identity contributions into proof events that can earn Trust Credits, strengthen Trust Score, qualify Trust Badges, and eventually support portable attestations.
Section 01
How it works
IdentityRecord creates and operates the first implementation of the Local Proof Protocol.
The Identity Record is the owned business identity object.
The AI Page is the public, machine-readable surface of the Identity Record.
Accepted contributions become proof events on the protocol.
Proof events can earn Trust Credits.
Proof events strengthen Trust Score.
Proof events qualify Trust Badges.
Solana is the chosen roadmap direction for proof anchoring and portability.
Section 02
Today's constraints
No proof event is on-chain yet.
No token is live.
No wallet is required to participate.
Trust Credits are product credits, not cryptocurrency.
Section 03
The five proof categories
Proof of Business Entity
Shows the business exists and controls its Identity Record.
Proof of Industry
Shows what the business does, how it should be understood, and what industry-specific facts define it.
Proof of Activity
Shows the business is operating through accepted proof, updates, completed work, milestones, and recent activity.
Proof of Certification
Shows credentials, licenses, certifications, permits, insurance, memberships, awards, and reviewed trust assets.
Proof of Community
Shows how the business supports, participates in, sponsors, serves, or contributes to its local community.
Supporting proof
- Proof of Consistency
- Proof of Maintenance
- Proof of Contribution
These types still earn credits and feed Trust Score and Trust Badges. They describe operational hygiene and meta-effects rather than standalone proof a business would publish about itself.
Roadmap proof
- Proof of Service
Surfaces when the underlying module ships. Not yet emitting events.
Section 04
How proof becomes value
Accepted contribution
owner-approved, evidence-backed
Proof event
typed, audit-trailed, append-only
Trust Credits
product credits inside IdentityRecord
Trust Score / Trust Badges
record strength + earned signals
Portable attestation
roadmap, gated on Solana Anchor V1
The first four stages run today inside the product. The fifth — portable attestation — is gated on the Solana Anchor V1 milestone. Until that ships, the protocol records and rewards proof inside IdentityRecord; it does not anchor it externally.
Section 05
What is live today
- Identity Records
- AI Pages
- Local Trust Signals (Identity / Understanding / Proof / Consistency)
- Trust Credits ledger
- Trust Score foundation
- Trust Badges foundation
- Protocol annotation on Trust Credit events (typed proof + evidence-hash fields, never exposed publicly)
- Market-facing proof taxonomy (the five top-level categories above)
- Owner-controlled publishing and review flows
Section 06
What is on the roadmap
- Solana Anchor V1 — server-side memo-program submission of selected proof events to Solana mainnet-beta, paid by IdentityRecord
- Selected proof-event anchoring once Anchor V1 is live
- Daily record checkpoints
- Public attestation lookup
- Credential and contributor proof hooks
- Community Proof lane inside the Proof / Activity Engine
- Future token utility — only if and when designed and legally cleared
Section 07
Solana posture
Solana is the chosen protocol direction for future proof anchoring and portability. No proof event is on-chain today. No wallet is required. No token is live. The first Solana milestone is Anchor V1: a server-side memo-program submission of selected proof events to Solana mainnet-beta, paid by IdentityRecord. Until Anchor V1 lands at least one confirmed mainnet transaction, this page describes the direction, not a capability.
The protocol is built so the eventual flip from roadmap to live is small: every accepted proof event already carries a deterministic content fingerprint that anchoring will reference. That preparation is invisible to owners and never required to participate.