feat(docs): Add Advanced OnchainKit Patterns Tutorial #800
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
This document outlines advanced patterns for using OnchainKit, including atomic batching of transactions, custom theming, and syncing on-chain events with off-chain databases.
Collaborator
🟡 Heimdall Review Status
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR creates a new "Advanced Patterns" tutorial for OnchainKit users.
Key Features:
Transaction Batching: Demonstrates passing an array of calls (Approve + Deposit) to the component to leverage EIP-5792 atomic batches.
Custom Theming: Explains the CSS variable override strategy for creating brand-specific design systems (fonts, colors, border-radius).
State Synchronization: Implements the onSuccess callback pattern to trigger off-chain database updates immediately after transaction finality.
Why: Most existing docs cover basic "Send" buttons. This guide addresses the two most common production requests: "How do I make it look like my app?" and "How do I handle multi-step flows efficiently?"