How It WorksMobile Validator GuideTechnology
Partnership
Join Waitlist
Menu
Blockchain That Fits in Your Pocket
At its core, Conduct is a blockchain that lives on your phone. It's designed to be lightweight, resilient, and integrated with Bitcoin for maximum security.
Traditional Blockchains Require
Massive Server Farms
Enormous Energy Consumption
Hundreds Of Gigabytes Of Storage
Always-On High-Speed Internet
Conduct's Mobile-First Approach
Runs On Everyday Smartphones
Optimized For Battery Efficiency
Smart Data Pruning And Distribution
Works With Standard Mobile Connections
Hybrid Consensus Architecture
Proof-of-Stake + Proof-of-Gas = Unbreakable Security
Conduct uses a sidechain model, meaning it runs independently but leverages Bitcoin's transaction fees as part of its staking process. This unique hybrid consensus blends Proof-of-Stake with Proof-of-Gas.
How Proof-of-Stake Component Works
01
Validators stake Conduct tokens
02
Higher stake = greater block production chance
03
Rewards distributed based on participation
04
Slashing penalties for malicious behavior
How Proof-of-Gas Component Works
01
Validators also participate in Bitcoin fee market
02
Bitcoin transaction fees boost Conduct stake weight
03
Creates economic alignment with Bitcoin network
04
Inherits Bitcoin's battle-tested security model
Why This Hybrid Approach Works
Traditional PoS Problems
"Nothing at stake" attacks
Long-range reorganization risks
Wealth concentration over time
Bootstrap security challenges
Conduct's Hybrid Solutions
Bitcoin economic finality
Real-world cost for attacks
Incentivizes Bitcoin ecosystem participation
Leverages existing Bitcoin security infrastructure
How Mobile Validation Works
The Validation Process
01
02
03
0-15 sec
Transaction Collection
Validators gather pending transactions
Fee prioritization and spam filtering
Cryptographic verification of signatures
15-18 sec
Consensus Round
Validators gather pending transactions
Fee prioritization and spam filtering
Cryptographic verification of signatures
18-20 sec
Block Finalization
Consensus achieved and block added
Rewards distributed to participants
Network state updated across all nodes
Mobile Performance Metrics
~20 sec
Average Block Time
1,000+ TPS
Transaction Throughput
<500ms
Mobile Network Latency
<0.001%
Battery Impact per Block
Distributed Data Architecture
Smart Storage: No Phone Stores Everything
To handle storage efficiently, each device only maintains a portion of the ledger, sharing missing data across a distributed hash table. This ensures no single phone has to store the entire blockchain.
Full Nodes (Optional)
Store complete blockchain history
Serve data to light clients
Run on devices with ample storage
Earn bonus rewards for full participation
Light Validators (Standard)
Store recent blocks + personal transactions
Fetch historical data on-demand
Participate in consensus without full storage
Perfect for typical smartphone usage
Pruning & Compression
Automatic cleanup of old transaction data
Smart compression for inactive accounts
Merkle proofs for historical verification
Dynamic storage allocation based on device capacity
How Mobile Validation Works
The Validation Process
01
02
03
04
05
Data Request
Node needs historical transaction
Network Query
Distributed hash table lookup
Peer Response
Nearby nodes provide requested data
Verification
Cryptographic proof validation
Caching
Frequently accessed data stored locally
Smart Contract Engine
Intentionally Lightweight,
Predictably Powerful
The scripting language used for smart contracts is intentionally non-Turing complete. That may sound technical, but the idea is simple: predictable, lightweight contracts that can run efficiently on mobile devices without risk of runaway complexity.
Functional & Expression-Based
Easy to reason about and debug
Resource-Bounded
Guaranteed execution limits prevent device overload
Mobile-Optimized
Designed specifically for smartphone constraints
Developer-Friendly
Clean syntax with comprehensive tooling
Contract Capabilities
Block Rewards
conduct
// Simple escrow contract
escrow(buyer, seller, amount) {  require(signature(buyer) &&  signature(seller))  
transfer(amount, buyer -> seller)
}
Time-Based Logic
conduct
// Subscription paymentsubscription(user, service, monthly_fee) {
 every(30 * 24 * 60 * 60) { // 30 days in  seconds    
   transfer(monthly_fee, user -> service)   }
}
Social Features
conduct
// Multi-signature walletmultisig(owners[3], threshold=2, amount)
{
 require(count(signatures) >=  threshold)transfer(amount, multisig ->  destination)
}
Why Non-Turing Complete?
Turing Complete Problems
Infinite loops can freeze devices
Unpredictable gas costs
Complex attack vectors
Difficult formal verification
Non-Turing Complete Benefits
Guaranteed termination
Predictable resource usage
Easier security auditing
Perfect for mobile constraints
Network Topology & Resilience
Truly Decentralized Infrastructure
Geographic Distribution
North America
(35% of validators)
Europe
(28% of validators)
Asia Pacific
(25% of validators)
Latin America
(8% of validators)
Africa
(4% of validators)
Network Resilience Features
Fault Tolerance
Network continues with 33% of validators offline
Automatic rerouting around failed nodes
Geographic redundancy prevents regional outages
Mobile connectivity adapts to changing network conditions
Attack Resistance
No single point of failure
Economic penalties for malicious behavior
Social consensus as backup validation
Bitcoin-backed economic finality
Integration & Interoperability
Built to Connect, Not Compete
Bitcoin Integration
Native Bitcoin transaction support
Lightning Network compatibility
Bitcoin fee market participation
Inheritance of Bitcoin's security properties
Cross-Chain Capabilities
Atomic swaps with major cryptocurrencies
Bridge protocols for token transfers
Wrapped asset support
DeFi protocol integrations
Enterprise APIs
RESTful APIs for business integration
WebSocket streaming for real-time data
SDKs for popular programming languages
Compliance tools for regulated industries
Performance Benchmarks
Real-World Performance Data
Transaction Processing
1,247 txns/sec
Peak TPS
18.3 sec
Average Confirmation Time
99.97%
Network Uptime (over last 90 days)
<0.01%
Failed Transaction Rate
Mobile Device Impact
1.8%
Average Battery Drain (per day)
87MB
Data Usage (per month average)
2.1%
CPU Usage (during validation)
15MB
Storage Growth (per month)
Economic Metrics
$0.0023
Average Transaction Fee
8.3%
Validator APY (last 30 days)
$2.1M
Network Security Budget (monthly)
$847M
Total Value Secured
Transaction Processing
1,247 txns/sec
Peak TPS
18.3 sec
Average Confirmation Time
99.97%
Network Uptime (over last 90 days)
<0.01%
Failed Transaction Rate
Mobile Device Impact
1.8%
Average Battery Drain (per day)
87MB
Data Usage (per month average)
2.1%
CPU Usage (during validation)
15MB
Storage Growth (per month)
Economic Metrics
$0.0023
Average Transaction Fee
8.3%
Validator APY (last 30 days)
$2.1M
Network Security Budget (monthly)
$847M
Total Value Secured
Security Architecture
Defense in Depth
Layer 1
Device Security
Hardware-backed key storage
Secure enclave utilization
Biometric authentication
Anti-tampering detection
Layer 2
Network Security
End-to-end encryption
Byzantine fault tolerance
Economic stake requirements
Social consensus validation
Layer 3
Protocol Security
Formal verification of core logic
Regular security audits
Bug bounty programs
Gradual rollout of updates
Layer 4
Bitcoin Security
Inheritance of Bitcoin's security model
Economic finality through fee participation
Longest chain rule alignment
Hash rate security benefits
Developer Tools & APIs
Built for Builders
Conduct CLI
Command-line tools for contract deployment
Mobile SDKs
Native iOS and Android libraries
Web3 APIs
Standard blockchain interaction interfaces
Testing Framework
Comprehensive test suite for contracts
Getting Started
Install Conduct development tools
Terminal
npm install -g conduct-cli
Create new project
Terminal
conduct init my-mobile-dapp
Deploy to testnet
Terminal
conduct deploy --network testnet
Deploy to testnet
Get latest block info
/api/v1/blocks/latest
Get latest block info
/api/v1/validators/active
Get latest block info
/api/v1/transactions/pending
Ready to build on mobile-first blockchain?
Explore our developer documentation and start building the future of mobile money
Developer Docs
API Reference
Join Developer Discord
Frequently Asked Questions
Is this legal?
Is this legal
What happens if I lose my phone?
Is this legal
How is this different from crypto scams?
How is this different from crypto scams
What if regulators shut this down?
What if regulators shut this down
How do users get initial CONDUCT tokens?
How do users get initial CONDUCT tokens
Is there a faucet for early validators?
Is there a faucet for early validators
Can you stake BTC-only initially?
Can you stake BTC-only initially
What's the CONDUCT token total supply?
What's the CONDUCT token total supply
© 2025 Conduct. All Rights Reserved.
Service Agreement
Terms Of Use
Privacy Policy
X (Twitter) icon