Technical Details and Use Cases
Last updated
Last updated
1.Core FeaturesAnalyzes historical on-chain activity like lending, trading, and staking to generate a normalized reputation score (0–1000).
Reputation scores are synced across supported blockchains to provide a consistent, verifiable identity layer.
Patterns in wallet activity help filter real users from bots and malicious actors.
Lending protocols can dynamically adjust terms (e.g., LTV, rates) based on a user’s wallet reputation.
Protocols can reward long-term, high-reputation users with premium access, perks, or better terms.
2.Use CasesAdjust collateral requirements dynamically
Reward high-reputation users with better rates
Block bot accounts from public mints
Identify real collectors for whitelists and rewards
Set leverage limits or fee tiers by trading history
Enhance user segmentation based on wallet behavior
Prevent Sybil farming
Focus on wallets with authentic engagement
Enable features based on verifiable wallet trust
Build ecosystem tiers with trust-based criteria
3.Architecture OverviewEvent Collector monitors transactions across DeFi protocols (lending, trading, staking)
Data is indexed by wallet address → network → protocol
Updates every 6 hours
Uses zkTLS for integrating off-chain credentials where possible
Execution Service processes wallet data using distributed workers on Solana
AI-based behavioral models assign reputation scores (0–1000)
Each score is cryptographically signed and stored in RocksDB
A Merkle tree is updated for fast proof generation and verification
Validators stake ETH via EigenLayer to participate
New score batches are verified via random sampling and consensus
Requires 2/3 majority approval to finalize and publish scores
Secured by over $1B in restaked ETH
4.Onchain Storage & Proof SystemSmart contracts on each chain store the verified Merkle root
Roots updated every 6 hours post-operator consensus
Only root hashes stored on-chain → low gas costs
Scores stored off-chain but can be independently verified via Merkle proofs
ScoreRegistryReceiver handles incoming root updates via LayerZero
5.Cross-Chain SyncOnce scores are verified, a central attestation center commits the Merkle root to each blockchain
Uses LayerZero messaging to coordinate updates
Each chain has a Score Registry contract to maintain the latest state
Ensures every protocol accesses consistent, up-to-date data
6.Integration GuideProtocols can access wallet scores using the AVS API:
Each response includes:
Wallet’s normalized score
Timestamp of last update
Merkle proof for on-chain validation
Fetch score + Merkle proof from zkOS API
Submit to the smart contract
Contract verifies proof using latest stored Merkle root
Proceed with logic (access, rewards, rate adjustment, etc.)
7.Getting StartedComing soon: SDKs and developer resources for Solidity, Rust, and TypeScript to make integrating zkOS easy.
