Overview
What ARC Identity does
ARC Identity is a wallet credential layer for Arc and stablecoin applications. A user connects an EVM wallet, signs a verification message, claims a public .arcid profile, and receives an ARC Identity Score based on real indexed activity and verified transaction evidence.
The product is built for checks that happen before payments, lending, escrow, protected deals, merchant flows, and higher-value stablecoin interactions.
Launch phase
Production-minded, still improving
ARC Identity no longer depends on demo users, local JSON storage, or manual score farming. Current data flows through wallet signatures, Supabase, Arc transaction verification, external chain indexers, cached score snapshots, and verified trust graph records.
Some external chain providers can be rate limited or plan restricted. The UI treats those cases as LIMITED provider availability so the product stays understandable while Arc-native data and cached intelligence remain visible.
Core primitives
The building blocks
Wallet identity
Users connect an injected EVM wallet, sign an ownership message, and claim a public .arcid username.
ARC Identity Score
A single reputation score that combines indexed wallet behavior, Arc activity, verified attestations, and risk signals.
Global wallet profile
Multi-chain context including wallet age, transaction count, chain coverage, counterparties, and contract interactions.
Arc network footprint
Arc-specific activity from Arc RPC/indexing plus verified Arc transaction attestations when explorer coverage is limited.
Verified attestations
Transaction-backed trust evidence created only when a submitted Arc transaction is verified against both wallets.
Trust graph
Verified wallet-to-wallet edges, reciprocal relationships, network maturity, anomaly hints, and capped trust propagation.
Score model
One score, explainable components
ARC Identity exposes one primary score. Supporting components explain why the score moved, but they are not separate competing scores.
The score combines global wallet credibility, Arc-specific activity, verified attestations, trust graph context, and risk analysis. It is clamped from 0 to 100 and mapped into familiar risk levels: High Risk, New / Unproven, Reliable, and Trusted.
Global Wallet Age
Based on the earliest real indexed transaction across supported chains.
Cross-chain Activity
Based on indexed transaction volume, active chains, recent activity, and contract interaction history.
Arc Activity
Based on Arc Testnet footprint, Arc attestations, Arc counterparties, active days, and Arc balance signals.
Counterparty Diversity
Based on unique counterparties across indexed chains, with Arc relationships treated as higher-signal context.
Verified Attestations
Based only on transaction-backed attestations with unique tx hashes and registered counterparties.
Trust Propagation
A capped network signal from verified trust edges. It can help, but it cannot dominate the base score.
Risk Penalty
Applied when anomaly signals, low confidence, repetitive behavior, or suspicious trust patterns appear.
Score stability
Refreshes are dampened to avoid scary unexplained drops. Passive recalculations are labeled as score recalibrations, while strong negative styling is reserved for real risk events, anomaly signals, or suspicious behavior.
Verified Attestations
Transaction-backed trust
Verified Attestations are not social claims. A user submits an Arc transaction hash, a registered counterparty, and an interaction type. The backend verifies the transaction before any reputation or trust graph effect is applied.
Requires a real Arc Testnet transaction hash
Transaction must exist and succeed on Arc
Connected wallet and selected counterparty must both participate
Duplicate transaction hashes cannot be reused
Self-attestations and unsupported interaction types are rejected
Only verified transaction-backed attestations can create trust edges
Anti-spam model
Trust has friction
Attestations use duplicate prevention, self-attestation blocking, relationship cooldowns, counterparty checks, and diminishing relationship influence. Circular trust farming or low-diversity behavior can reduce trust confidence and trigger anomaly records.
Only submit attestations for legitimate economic interactions. ARC Identity is designed to reward real transaction evidence, not coordinated self-reporting.
Trust graph
Verified relationships, not social follows
Trust edges are created only from accepted, verified transaction-backed attestations. Usernames, manual profile data, and unverified activity do not create graph relationships.
The trust graph tracks trusted peers, strongest relationships, reciprocal edges, total trust weight, network maturity, anomaly hints, and capped propagated trust contribution.
Reliability model
Fast reads, careful refreshes
Score reads are cached-first. GET /api/score/:wallet returns the best available cached profile quickly, including cache status, refresh status, last indexed time, explanations, chain coverage, and trust summary.
Full indexing happens through POST /api/score/:wallet/refresh. The refresh pipeline uses lifecycle states so incomplete or failed provider checks do not overwrite the last good cached score.
INDEXED
Provider returned usable activity and the chain contributes real indexed data.
NO ACTIVITY
Provider responded successfully, but no transactions were found for the wallet.
LIMITED
External provider access is unavailable, rate limited, paywalled, or temporarily restricted.
NOT CONFIGURED
Required API key or provider configuration is missing.
PENDING
The wallet has not been checked yet or refresh is still running.
Developer API
Reputation data for builders
Any Arc app can use ARC Identity before payments, lending, escrow, protected deals, merchant flows, or high-value stablecoin interactions.
GET
/api/score/:wallet
Cached-first score, breakdown, explanations, chain coverage, and trust summary.
POST
/api/score/:wallet/refresh
Runs a full wallet intelligence refresh in the background-safe refresh pipeline.
GET
/api/profile/:username
Public profile, wallet, score, attestations, reputation events, and trust graph context.
GET
/api/users
Claimed public identities for the directory.
POST
/api/attestations/request
Creates a verified transaction-backed attestation after Arc transaction verification.
GET
/api/trust/:wallet
Trust edges, snapshots, anomalies, reciprocal peers, and network metrics.
{
"walletAddress": "0x...",
"username": "example.arcid",
"arcIdentityScore": 72,
"riskLevel": "Reliable",
"cacheStatus": "cached",
"refreshStatus": "committed",
"dataSource": "arc_rpc_plus_transaction_verified_attestations",
"breakdown": {
"globalWalletAge": 16,
"crossChainActivity": 12,
"arcActivity": 18,
"verifiedAttestations": 15,
"propagatedTrust": 6,
"riskPenalty": 0
},
"explanations": {
"globalWalletAge": "Based on earliest indexed transaction.",
"verifiedAttestations": "Based on verified transaction attestations."
},
"trustGraph": {
"trustedPeerCount": 2,
"networkHealth": "emerging",
"trustConfidence": 64
}
}FAQ
Common questions
Is ARC Identity a manual reputation form?
No. Profiles are wallet-owned, and reputation comes from indexed wallet activity, verified transaction-backed attestations, and trust graph context.
Why can some chains show LIMITED?
Some external indexers have rate limits, API plan restrictions, or temporary outages. LIMITED means provider coverage is constrained, not that the wallet is risky.
Can someone farm score with fake attestations?
ARC Identity only scores transaction-backed attestations. The backend verifies the Arc transaction, participants, duplicate use, and relationship rules before trust is created.
Does the score update instantly?
The score API is cached-first for fast UX. Full indexing runs through a refresh pipeline, and the dashboard keeps the last good cached score visible while refreshes complete.
Is the system final?
No. ARC Identity is in an active launch phase. Score explanations, provider coverage, trust safeguards, and developer responses will keep improving as usage grows.
Get started
Run the launch flow
Connect a wallet, sign the ownership message, claim a username, refresh wallet intelligence, inspect the public profile, and try a transaction-backed attestation when you have a real Arc transaction with another registered identity.