You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/base-chain/quickstart/base-solana-bridge.mdx
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,11 @@ This guide covers the bridge architecture and provides practical examples for im
22
22
## How it works
23
23
24
24
### On Base
25
-
The Base bridge contract locks or burns your tokens and emits a message. Validators collect these messages into Merkle trees and post roots to Solana every ~15 minutes. You then prove your message exists in the tree to complete the transfer on Solana.
25
+
The Base bridge contract locks or burns tokens when sending messages to Solana,
26
+
and mints or unlocks tokens when receiving messages from Solana.
27
+
The Bridge contract itself builds Merkle trees from outgoing messages.
28
+
Validators verify the Merkle root every 300 finalized blocks and relay it to Solana.
29
+
You then prove your message exists in the tree to complete the transfer on Solana.
@@ -37,7 +41,7 @@ It represents the `msg.sender` on Base when you send an arbitrary contract call
37
41
</Tip>
38
42
39
43
### On Solana
40
-
The Solana bridge program locks or burns your tokens and emits events. Validators relay these messages to Base where they're executed through your personal Twin contract - a smart contract that acts as your execution context on Base.
44
+
The Solana bridge program handles token transfers by locking or burning tokens and emitting events. For messaging, validators relay these messages to Base where they're executed through your personal Twin contract - a smart contract that acts as your execution context on Base.
**Flow:** Burn SOL (on Base) → Wait 15min → Generate Proof → Execute on Solana
119
123
120
124
The Base to Solana flow requires manual proof generation. You burn wrapped SOL on Base, wait for finalization (~15 minutes), then generate a cryptographic proof to execute on Solana and receive native SOL.
121
125
122
126
<GithubRepoCardtitle="Base to Solana Example"githubUrl="https://github.com/basebase-bridge-examples/tree/main/bridgeSolFromBaseToSolana" />
0 commit comments