Revolutionary blockchain architecture that lives in your pocket, not in massive data centers.
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.
Validators gather pending transactions
Fee prioritization and spam filtering
Cryptographic verification of signatures
Selected validator proposes new block
Other validators verify and vote
Hybrid stake weighting applied
Consensus achieved and block added
Rewards distributed to participants
Network state updated across all nodes
Validators gather pending transactions
Fee prioritization and spam filtering
Cryptographic verification of signatures
Selected validator proposes new block
Other validators verify and vote
Hybrid stake weighting applied
Consensus achieved and block added
Rewards distributed to participants
Network state updated across all nodes
Average Block Time
Transaction Throughput
Mobile Network Latency
Battery Impact per Block
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.
Store complete blockchain history
Serve data to light clients
Run on devices with ample storage
Earn bonus rewards for full participation
Store recent blocks + personal transactions
Fetch historical data on-demand
Participate in consensus without full storage
Perfect for typical smartphone usage
Automatic cleanup of old transaction data
Smart compression for inactive accounts
Merkle proofs for historical verification
Dynamic storage allocation based on device capacity
Node needs historical transaction data
Distributed hash table lookup
Nearby nodes provide requested data
Cryptographic proof validation
Frequently accessed data stored locally
Node needs historical transaction data
Distributed hash table lookup
Nearby nodes provide requested data
Cryptographic proof validation
Frequently accessed data stored locally
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.
Easy to reason about and debug
Guaranteed execution limits prevent device overload
Designed specifically for smartphone constraints
Clean syntax with comprehensive tooling
conduct
// Simple escrow contract
escrow(buyer, seller, amount) {
require(signature(buyer) && signature(seller))
transfer(amount, buyer -> seller)
}conduct
// Subscription payment
subscription(user, service, monthly_fee) {
every(30 * 24 * 60 * 60) { // 30 days in seconds
transfer(monthly_fee, user -> service)
}
}conduct
// Multi-signature wallet
multisig(owners[3], threshold=2, amount) {
require(count(signatures) >= threshold)
transfer(amount, multisig -> destination)
}
Network continues with 33% of validators offline
Automatic rerouting around failed nodes
Geographic redundancy prevents regional outages
Mobile connectivity adapts to changing network conditions
No single point of failure
Economic penalties for malicious behavior
Social consensus as backup validation
Bitcoin-backed economic finality
Native Bitcoin transaction support
Lightning Network compatibility
Bitcoin fee market participation
Inheritance of Bitcoin’s security properties
Atomic swaps with major cryptocurrencies
Bridge protocols for token transfers
Wrapped asset support
DeFi protocol integrations
RESTful APIs for business integration
WebSocket streaming for real-time data
SDKs for popular programming languages
Compliance tools for regulated industries
Peak TPS
Average Confirmation Time
Network Uptime (over last 90 days)
Failed Transaction Rate
Average Battery Drain (per day)
Data Usage (per month average)
CPU Usage (during validation)
Storage Growth (per month)
Average Transaction Fee
Validator APY (last 30 days)
Network Security Budget (monthly)
Total Value Secured
Hardware-backed key storage
Secure enclave utilization
Biometric authentication
Anti-tampering detection
End-to-end encryption
Byzantine fault tolerance
Economic stake requirements
Social consensus validation
Formal verification of core logic
Regular security audits
Bug bounty programs
Gradual rollout of updates
Inheritance of Bitcoin’s security model
Economic finality through fee participation
Longest chain rule alignment
Hash rate security benefits
Command-line tools for contract deployment
Native iOS and Android libraries
Standard blockchain interaction interfaces
Comprehensive test suite for contracts
npm install -g conduct-cliconduct init my-mobile-dappconduct deploy --network testnetTry API calls directly in your browser
Get latest block info
/api/v1/blocks/latestList active validators
/api/v1/validators/activeView pending transactions
/api/v1/transactions/pendingExplore our developer documentation and start building the future of mobile money