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: products/bridge/README.md
+45
Original file line number
Diff line number
Diff line change
@@ -193,3 +193,48 @@ The middle layer are cross-chain applications that use the cross-chain conctract
193
193
- the twin contract checks the expiration and whether the approved token and amount are as required, transfers the amount to user 1 and returns true as response
194
194
- the swap contract on Zilliqa receives the response of its twin and transfers the locked amount to user 2
195
195
- if the swap contract does not receive a response from its twin before the expiration, user 1 can claim the approved amount and the swap contract sends it back to user 1
196
+
197
+
## Roadmap
198
+
199
+
The bridge will have the following deliverables:
200
+
201
+
-**Smart Contracts** – these will be written with the combination of:
202
+
- Hardhat - E2E testing + deployment
203
+
- Foundry - Unit testing + fuzzing + invariant testing + gas reporting
204
+
-**Validator Node Lib**
205
+
- Written in Rust
206
+
- Should encapsulate most functionality required for a validator to run the bridge protocol
207
+
-**Off-chain Validator Nodes**
208
+
- Written in Rust
209
+
- Will use `Validator Node Lib` as a dependency for most shared code
210
+
- This will run the validator set
211
+
- Signature aggregation through a gossip network
212
+
- Validators run by Zilliqa
213
+
-**Frontend DApp**
214
+
- Written in React
215
+
- Simple DApp enabling bridge activities
216
+
-**Integrate bridge into ZQ2 consensus**
217
+
- Integrate `Validator Node Lib`
218
+
- Migrate validators to ZQ2 once released and stable
219
+
220
+
### MVP
221
+
222
+
The MVP bridge will run on a gossip network with validators managed by Zilliqa
0 commit comments