Constructs
Overview of Constructs
In the Haircomb system, constructs are fundamental building blocks that define how data, transactions, and operations are managed. These constructs enable Haircomb's unique functionalities, including privacy, scalability, and secure off-chain data management. Each construct serves a specific purpose within the system architecture, allowing for secure, private, and efficient transactions, data verification, and contract management.
Overview
Keys in Haircomb are cryptographic entities used for creating and verifying signatures, ensuring data integrity, and securing user accounts. They are critical for ensuring both security and privacy in the system.
Creation and Structure
- Key Generation: Keys are generated using a post-quantum cryptographic algorithm designed to withstand potential future quantum computing attacks.
- Key Formats: Haircomb employs unique key formats, optimized for both post-quantum resistance and compatibility with existing blockchain systems.
- Key Management: Keys are securely stored off-chain, and users are responsible for managing private keys. Haircomb offers built-in key recovery and rotation mechanisms.
Signing and Verification
- Signing Process: Keys are used to sign transactions and data packages within Haircomb, ensuring authenticity and non-repudiation.
- Verification Process: Signatures are verified using cryptographic operations, which check whether the data has been tampered with and whether it originates from the correct sender.
Overview
Transactions are the core operations that move assets within Haircomb. Each transaction includes essential data such as the sender, recipient, amount, and cryptographic proof, facilitating secure and private transfers.
Process and Structure
- Transaction Flow: Transactions are initiated by users, signed with their keys, and submitted to the BTC chain for consensus. Haircomb utilizes off-chain storage for scalability.
- Data Structure: Transactions contain cryptographic proofs, sender and receiver details, and off-chain references. They also include signature data to ensure validity.
Example Use Cases
- Private Payments: Transactions are used for sending NATs between users securely.
- Multipayments: With stack functionality, transactions can handle multiple recipients in a single operation.
Overview
Stacks are constructs that manage how funds are distributed between multiple addresses. They allow for complex transaction scenarios such as stealth payments and multipayments.
Functionality and Usage
- Stack Operations: Stacks hold funds until they are triggered to send to specified addresses. They can also redirect leftover amounts to a change address, enabling complex, multi-step payments.
- Use Cases: Stacks can be used for stealth addresses, making fundraising easier and enabling multipayment setups where multiple recipients can be paid in a single transaction.
Example Use Cases
- Stealth Transactions: Stacks allow funds to be redirected to stealth addresses for privacy.
- Multipay Transactions: A stack can be constructed to send funds to multiple recipients, reducing transaction costs and improving efficiency.
Overview
Merkle segments are constructs used for verifying data integrity in Haircomb's off-chain storage. They allow for efficient data routing and verification using Merkle trees, a structure that ensures data consistency without needing to store all data on-chain.
Structure and Routing
- Merkle Tree Structure: Data in Haircomb is structured using Merkle trees, where each leaf represents a hash of data, and the root node serves as a single hash representing all data in the tree.
- Routing Mechanism: Merkle segments allow for efficient proof verification by routing through these Merkle trees. Data can be confirmed as untampered by verifying its segment within the Merkle tree.
Use Cases and Examples
- Data Integrity: Merkle segments ensure that off-chain data remains consistent and verifiable.
- Examples: Verifying transaction history, ensuring the accuracy of large datasets without storing everything on-chain.
Overview
Deciders are decision-making constructs in Haircomb that determine outcomes in smart contracts and transactions based on predefined rules or conditions.
Purpose and Structure
- Function: Deciders operate based on a set of rules that dictate when certain actions should be taken. They are often used in contracts to evaluate conditions and execute outcomes.
- Structure: Each decider consists of logic that processes inputs, evaluates them against the rules, and outputs a decision (e.g., release funds, trigger a contract).
Use Cases
- Automated Payments: Deciders can be used to automate payments when specific conditions are met.
- Contract Execution: Smart contracts in Haircomb can use deciders to execute when specific conditions are fulfilled, such as time-based releases or multi-signature approvals.
Overview
Contracts in Haircomb allow users to define agreements that are automatically enforced by the blockchain. These can range from simple payment contracts to more complex multi-step processes.
Types of Contracts
- Standard Contracts: These are basic agreements like scheduled payments or conditional transfers.
- Advanced Contracts: More complex contracts include multi-party agreements or contracts that interact with external systems (e.g., oracle-based contracts).
Examples and Templates
- Examples: Time-locked payments, multi-signature approvals, or dynamic contracts that depend on external data.
- Templates: Predefined contract structures that users can adopt and modify for common use cases, such as recurring payments or crowdfunding campaigns.