How do you trust data
before it hits the blockchain?
Smart contracts can't see the real world. They can't verify that an event happened, a task was completed, or a condition was met. That's the oracle problem. And that's exactly what Fexr solves.
The Oracle Problem Explained
Why can't smart contracts just read data from the internet? Because blockchains are deterministic systems that need consensus. External data breaks that model.
Events, actions, conditions, sensor data, human attestations
Deterministic, isolated, trustless by design
Centralized Oracles
Single points of failure. One compromised node means corrupted data for everyone. Traditional oracles trust infrastructure, not verification.
Automated Feeds
Great for price data. Useless for subjective events. Did the contractor finish the job? Was the product authentic? Machines can't judge nuance.
Economic Attacks
If corrupting an oracle is cheaper than the value it protects, someone will corrupt it. Most systems don't align incentives properly.
The Fexr Solution
We didn't invent oracles. We reinvented who verifies the data. Instead of trusting infrastructure, we trust communities with skin in the game.
Community Verification
Real humans with reputation stakes verify events. Not anonymous nodes—accountable community members with badge history, trust scores, and economic incentives to be honest.
- Verifier pools with minimum reputation
- Quorum-based consensus (3-of-5, 5-of-9, custom)
- Slashing for provably false attestations
- Rewards for accurate verification
Smart Contract Triggers
Once verified, data flows to on-chain contracts automatically. Payouts release, NFTs mint, access grants, governance votes execute—all based on proven truth.
- Multi-chain deployment (Polygon, Solana, Avalanche)
- Configurable trigger conditions
- Atomic execution with rollback
- Gas-optimized batching
Proof-Based Trust
Every verification carries cryptographic proof of who attested, when, and with what evidence. Full audit trail from real-world event to on-chain action.
- Immutable verification logs (DVI)
- Optional zero-knowledge proofs
- Tamper-evident timestamps
- Regulatory-grade audit trails
From Real World to Blockchain
Follow the journey of a verification request through the Fexr oracle system.
Event Occurs
A real-world event needs verification: task completion, product delivery, event attendance, sensor reading, or any observable occurrence.
Proof Submitted
The claimant submits evidence: photos, GPS tracks, sensor data, video, or attestations. Multiple proof types can be combined for higher confidence.
Verifier Pool Activated
Qualified verifiers from the club's pool are selected randomly. Only members with sufficient trust scores and relevant badges can participate.
92
87
95
89
91
Consensus Reached
Verifiers independently review the evidence and cast votes. When quorum is reached (e.g., 3-of-5 agree), the verification is finalized.
Challenge Period
A configurable window (minutes to days) allows disputes. Anyone with counter-evidence can challenge. Challenged verifications go to expanded review.
On-Chain Execution
Verified data is committed to the blockchain. Smart contracts trigger: rewards release, NFTs mint, governance votes execute, access grants.
The Verification Engine
Our verification system is designed to be both rigorous and efficient. Every component is calibrated to balance speed, accuracy, and security.
Verifier Pools
Club operators define who can verify: minimum trust score, required badges, geographic restrictions, or specialized expertise. Pools can overlap for cross-validation.
Weighted Voting
Not all votes are equal. Verifiers with higher trust scores, relevant domain badges, or longer track records carry more weight. A 95-score vote counts more than a 70.
Slashing Mechanism
Verifiers stake reputation and tokens. Provably false attestations result in slashing: reduced trust score, lost stake, and temporary or permanent pool exclusion.
Escalation Paths
Disputed verifications can escalate: larger verifier pool, higher-tier reviewers, or even external arbitration. The system is designed for edge cases.
Trust Scores: Earning Credibility
Every member has a trust score that evolves based on their behavior. It's not just about participation—it's about accuracy, consistency, and integrity.
How Scores Are Calculated
Trust Tiers & Privileges
Novice 0-30
Can participate in low-stakes verifications. Limited voting weight.
Member 31-60
Standard verification access. Earns participation credits from accurate votes.
Verified 61-80
Increased voting weight. Access to higher-value verifications.
Expert 81-95
Priority pool placement. Can review escalated disputes.
Oracle 96-100
Maximum voting weight. Final arbitration authority. Highest rewards.
Proof Types We Support
Different claims require different evidence. Our multi-modal proof system accepts various data types, each with its own verification protocol.
Photo & Image
Timestamped photos with EXIF metadata verification. AI-assisted tampering detection. Multiple angle requirements for high-stakes claims.
Video Attestation
Short-form video proofs with face verification optional. Continuous timestamp validation. Ideal for task completion or presence verification.
Geolocation
GPS coordinates with accuracy radius. Can require location consistency over time. Perfect for attendance, delivery, or geographic claims.
IoT & Sensors
Direct integration with IoT devices. Temperature, humidity, motion, weight sensors. Signed data streams with device attestation.
Document Attestation
Upload documents with hash verification. Third-party notarization integration. OCR extraction for structured data claims.
API Verification
Connect external APIs as proof sources. OAuth integrations for third-party attestations. Webhook callbacks for real-time events.
Peer Attestation
Other members vouch for claims. Weighted by attester trust scores. Useful for community validation of soft claims.
Zero-Knowledge Proofs
Prove claims without revealing underlying data. "I'm over 18" without sharing birthdate. Privacy-preserving verification for sensitive data.
Multi-Chain Deployment
Verified data can trigger actions on any supported chain. Choose based on your speed, cost, and ecosystem requirements.
Polygon
Low-cost, high-speed EVM chain. Ideal for high-volume verification workloads and consumer-facing dApps.
- EVM compatible
- Massive DeFi ecosystem
- Enterprise adoption
Solana
Ultra-fast finality with sub-second confirmation. Best for real-time applications and gaming use cases.
- Highest throughput
- Native mobile SDKs
- Growing NFT ecosystem
Avalanche
Subnet architecture for custom chains. Perfect for enterprises needing dedicated verification infrastructure.
- Custom subnets
- Interoperable
- Institutional grade
What Gets Verified
Our oracle system supports diverse verification needs across industries. Here's how clubs use it today.
Fitness Challenge Verification
A fitness club runs a 30-day challenge where members earn tokens for completing workouts. The oracle verifies each claim.
Member submits workout proof: GPS track showing 10km run with timestamps
3 verifiers with "Fitness" badge review the evidence
Consensus reached: valid 10km run confirmed
Smart contract releases 50 FIT tokens to member wallet
Product Authenticity Verification
A luxury goods club verifies authentic purchases. Members submit proof of purchase and receive authenticity badges.
Member submits receipt photo + product serial number
5 verifiers cross-reference with brand database
Quorum confirms: authentic product verified
Authenticity NFT minted to member's wallet
Event Attendance Verification
A conference club issues POAPs (Proof of Attendance) only to verified attendees, preventing farming and ensuring authenticity.
Attendee scans QR code at venue + submits location proof
Location verified within venue geofence
Time-in-venue threshold met (>2 hours)
POAP NFT + loyalty tokens released
Governance Action Verification
A DAO club requires verified identity for governance votes. Oracle ensures one-person-one-vote without revealing identity.
Member requests voting eligibility verification
ZK-proof generated: "unique human" without revealing identity
Oracle confirms: eligible voter, not duplicate
Vote recorded on-chain with privacy preserved
Decentralized Verified Insights (DVI)
Every verification creates an immutable audit trail. DVI is our decentralized data layer where all verification events, proofs, and outcomes are permanently recorded.
Permanent Storage
Verification records stored on IPFS with blockchain anchoring. Data persists even if Fexr disappears.
Queryable API
GraphQL interface for querying verification history. Filter by club, member, time, outcome.
Export & Compliance
Generate audit reports for regulators. GDPR-compliant data handling with selective disclosure.
Third-Party Access
Partners can verify claims against DVI. Build trust with external stakeholders.
0x7f4e...a3b2
0x3a9c...d7e1
0x9b2f...c4a8
0x1d8e...f5c9
Battle-Tested Infrastructure
Our oracle system has been audited, stress-tested, and hardened against the attack vectors that plague other verification systems.
Smart Contract Audits
All on-chain contracts audited by leading security firms. Public audit reports available. Bug bounty program active.
Audited by Trail of BitsSybil Resistance
Multi-layered identity verification prevents fake accounts. Cost to create fake verifiers exceeds potential gains from manipulation.
Economic security modelDecentralized Infrastructure
No single point of failure. Verifier pools are distributed globally. System continues operating if any node fails.
99.99% uptime SLAEncryption at Rest & Transit
All sensitive data encrypted with AES-256. TLS 1.3 for all communications. HSM-backed key management.
SOC 2 Type II compliantHow We Compare
Traditional oracles solve different problems. Here's where Fexr excels.
Frequently Asked
What happens if verifiers disagree?
If consensus isn't reached, the verification enters a dispute state. Additional verifiers from a larger pool are recruited. If still unresolved, it escalates to higher-tier arbitrators with proven track records.
Can verifiers collude to approve false claims?
Random selection, anonymous voting (until reveal), stake slashing, and challenge periods make collusion economically irrational. The cost of collusion exceeds potential gains.
How fast is verification?
Simple verifications with available verifiers: 30 seconds to 2 minutes. Complex claims with challenge periods: hours to days depending on club configuration.
What if there aren't enough verifiers?
Clubs can configure fallback pools, extend timeout windows, or use AI-assisted pre-screening to reduce load. Small clubs can share verifier pools with trusted partners.
Is this compliant with regulations?
DVI provides audit trails for regulators. GDPR-compliant data handling with selective disclosure. We work with legal counsel to ensure compliance in multiple jurisdictions.
Can I use my own smart contracts?
Yes. Our SDK lets you connect verified data to any contract. Standard callback interfaces for Solidity, Rust (Solana), and other environments.
Ready to Build Verifiable Trust?
Join clubs already using Fexr oracles to power their verification workflows. Start with our free tier or talk to our team about enterprise solutions.