StackChain Layer 2 Rollup Implementation #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Defined error codes for various contract errors including invalid operator, invalid commitment, challenge period, invalid proof, insufficient funds, invalid input, and unauthorized access.
- Defined data maps for tracking registered operators, state commitments, user balances, and active challenges.
- Defined `contract-owner` data variable to store the contract owner's principal. - Added private functions for validating principals, uint values, commitment hashes, and Merkle proofs.
…ubmission - Added `register-operator` function to allow the contract owner to register new operators. - Added `submit-state-commitment` function to enable operators to submit new state commitments with validation and STX transfer.
- Added `challenge-commitment` function to allow users to challenge existing state commitments by providing a challenge block, commitment hash, and challenge proof. - Validates inputs and transfers a challenge bond before storing the challenge details.
- Added `deposit` function to allow users to deposit tokens into the rollup. - Validates the amount and token identifier before transferring tokens and updating the user balance.
…he rollup - Added `withdraw` function to allow users to withdraw tokens from the rollup, validating inputs and Merkle proof before updating balances and transferring tokens. - Added `transfer-in-rollup` function to enable token transfers between users within the rollup, ensuring sufficient balance and updating user balances accordingly.
…or getting user balance - Added `resolve-challenge` function to resolve challenges against state commitments, validating inputs and ensuring the existence of the challenge and commitment. - Added `get-user-balance` read-only function to retrieve the balance of a user for a specific token.
…tion guidelines, License, Security policy, and Technical specifications
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR implements a comprehensive Layer 2 rollup solution for the Stacks blockchain, enabling high-throughput transactions with robust security guarantees.
Changes
Core Contract Implementation
Public Functions
Operator Management
register-operator: Secure operator registrationsubmit-state-commitment: State commitment submission with validationChallenge System
challenge-commitment: Challenge submission with bond requirementresolve-challenge: Challenge resolution mechanismToken Operations
deposit: Secure token depositswithdraw: Merkle-proof based withdrawalstransfer-in-rollup: Efficient internal transfersget-user-balance: Balance query functionDocumentation
Security Considerations
Testing
Deployment Steps
Documentation Updates
/docsChecklist