Skip to content

Commit

Permalink
More fixes
Browse files Browse the repository at this point in the history
Signed-off-by: Andrei Baltariu <[email protected]>
  • Loading branch information
andreiblt1304 committed Jan 16, 2025
1 parent eef67bb commit 9ecd4a6
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
8 changes: 4 additions & 4 deletions docs/sovereign/from-sovereign.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,10 +21,10 @@ Each action that can be executed remotely through this contract is called an *Op

#### Execution from inside the Sovereign Chain to the MainChain flow
1. User deposits token to the ESDT-Safe smart contract on Sovereign.
2. The validators generate a proof on the Sovereign Chain for a batch of transfers, which will be sent to the mainchain ESDT-Safe contract.
3. Validators add this information to the sovereignChainBlockBody. Otherwise the block is not signed.
4. Leader will push the created txData to the mainchain
5. Bridge service will send the operations to to header-verifier for verification then to ESDT-Safe for execution.
2. Outgoing *Operations* are created at the end of the round.
3. Validators sign all the outgoing *Operations*.
4. Leader sends *Operations* to the bridge service.
5. Bridge service sends the *Operations* to the Header-Verifier for registration and verification, and then to ESDT-Safe for execution.
6. At the end of the execution success/fail, a confirmation event will be added which will be received in sovereign through the observer and then the cross chain transfer will be completed.

### Header-Verifier SC
Expand Down
6 changes: 3 additions & 3 deletions docs/sovereign/to-sovereign.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
# Execution going to a Sovereign Chain
![To Sovereign](../../static/sovereign/to-sovereign.png)

The ability to transfer tokens from the Mainchain to any Sovereign Chain is essential, since every Sovereign can connect to the Main MultiversX Chain. As a result, the customizable Sovereign can leverage any token available on the default network.
The ability to transfer tokens from the Main Chain to any Sovereign Chain is essential, since every Sovereign can connect to the Main MultiversX Chain. As a result, the customizable Sovereign can leverage any token available on the default network.

The most innovative part of the bridging mechanism from the Mainchain is that it is completely off-chain. The transfer of tokens is done by the *ESDT-Safe* contract after calling the `deposit` endpoint inside the `to-sovereign` module.
The transfer of tokens is done by the *ESDT-Safe* contract after calling the `deposit` endpoint inside the `to-sovereign` module.

#### Main Chain deposit to Sovereign Chain depositing flow
1. User deposits the tokens he wishes to transfer in the ESDT-Safe contract deployed on the Main Chain.
Expand All @@ -28,7 +28,7 @@ One key aspect of cross chain transfers from MultiversX Main Chain to a Sovereig
- The gas limit must be under the specified limit.
- The endpoint that has to be executed is not blacklisted.

As mentioned in the diagram, the bridging process to the Sovereign Chain is being done with events. At the end of the deposit() endpoint, an event will be emitted and then the bridging process is complete.
At the end of the `deposit()` endpoint, an event will be emitted and then the bridging process is complete.


```rust
Expand Down

0 comments on commit 9ecd4a6

Please sign in to comment.