How It Works
Hyperstate offers a unique approach to blockchain interoperability, specifically connecting Ethereum's smart contract capabilities with Bitcoin's robust network.
Core Concept
Hyperstate is a network for native-Bitcoin asset programmability. Its key innovation are network functions that allow on-chain interaction with Bitcoin, offering a superior UX over bridges.
This fundamental principle underlies Hyperstate's design, making it accessible for both developers and end-users while providing seamless integration with Bitcoin.
Hyperstate EVM: Ethereum + Bitcoin = Programmable Bitcoin
Hyperstate EVM is the only EVM blockchain with Bitcoin Core network bindings, callable via smart contracts, for native-Bitcoin read/write capabilities. This unique feature enables:
Low switching costs for developers
Native integration of Bitcoin functionality within Ethereum-compatible smart contracts
Validators play a crucial role in the Hyperstate ecosystem:
They run both Hyperstate EVM and Bitcoin Core
Manage synchronous state across both chains
Verify cross-chain interactions
Face slashing (penalty) for dishonesty, ensuring network integrity
Restaking: Enhanced Security
Hyperstate leverages recent restaking advances to:
Bootstrap network security
Optimize node operation
Reduce execution and GTM (Go-To-Market) timing risk
This approach enhances the overall security and efficiency of the network.
$HS: The Hyperstate Token
$HS serves multiple purposes within the Hyperstate ecosystem:
Network token for gas fees
Validator rewards
Sequencer incentives
By aligning economic incentives, $CRS helps maintain network health and promotes active participation.
Hyperstate Signing Flow
The Hyperstate signing flow demonstrates the seamless integration between web3 applications, the Hyperstate EVM, and the Bitcoin network:
Web3 Wallet: The entry point for users.
Apps prompt users to presign both BTC and EVM transactions.
Apps: Interface between users and the Hyperstate network.
Manage user interactions and transaction initiation.
Hyperstate EVM: The core of the Hyperstate network.
Protocols: Smart contracts that manage Bitcoin private keys.
Precompiles: Built-in network functions to parse Bitcoin intents.
Smart contracts utilize these components to interact with Bitcoin.
Bitcoin Network: The underlying Bitcoin blockchain.
Nodes read/relay to/from Hyperstate and Bitcoin Core.
Important: Assets never leave the Bitcoin network, ensuring security.
Key Features of the Signing Flow:
Dual Signing: Users presign both BTC and EVM transactions, enabling seamless cross-chain operations.
Smart Contract Key Management: Protocols within Hyperstate EVM manage Bitcoin private keys securely.
Native Bitcoin Parsing: Precompiles allow direct interpretation of Bitcoin transactions within the EVM environment.
Network-Level Signing: Hyperstate network signs and broadcasts transactions, monitors state, enabling protocols to govern assets via code.
Asset Security: Bitcoin assets remain on the Bitcoin network, eliminating the risks associated with wrapped tokens or external bridges.
This architecture allows for a superior user experience, enabling direct interaction with Bitcoin assets through familiar Ethereum-style interfaces and smart contracts, all without the need for complex bridging mechanisms.
Hyperstate Transaction Flow
The Hyperstate transaction flow involves several key components:
web3 Wallet / Apps: Entry point for users and applications interacting with the Hyperstate network.
Hyperstate Mempool: Collects and manages pending transactions.
Hyperstate Blocks: Transactions are organized and processed in blocks.
Hyperstate Execution Queue: Manages the order and execution of transactions.
Hyperstate Signing Service: Handles the cryptographic signing of transactions.
Bitcoin Blocks: The final stage where Hyperstate interactions are reflected on the Bitcoin blockchain.
This architecture allows for seamless interaction between Ethereum-based smart contracts and the Bitcoin network, all without requiring users to interact with complex bridging or wrapping mechanisms.
For more detailed technical information, please refer to our Whitepaper.
Last updated
