sora-xor · bgodlin · Oct 30, 2023 · May 30, 2023 · May 31, 2023 · May 31, 2023
diff --git a/.vitepress/config.ts b/.vitepress/config.ts
@@ -132,13 +132,15 @@ export default defineConfig({
           },
           {
             text: "Interoperability",
+            link: "interoperability",
             collapsed: true,
             items: [
               {
                 text: "EVM",
                 items: [
                   {
                     text: "HASHI",
+                    link: "hashi",
                     items: [
                       {
                         text: "Adding a token",
@@ -149,10 +151,15 @@ export default defineConfig({
                       },
                     ],
                   },
-                  { text: "Trustless" },
                 ],
               },
-              { text: "Substrate", items: [{ text: "Become a relayer" }] },
+              {
+                text: "Substrate",
+                link: "substrate-bridge",
+                items: [
+                  // { text: "Become a relayer" },
+                ],
+              },
             ],
           },
           { text: "Referral system", link: "/referral" },

diff --git a/src/assets/sidechain-token-registration.png b/src/assets/sidechain-token-registration.png
diff --git a/src/assets/substrate-bridge-components-svg.svg b/src/assets/substrate-bridge-components-svg.svg
diff --git a/src/assets/substrate-bridge-components.png b/src/assets/substrate-bridge-components.png
diff --git a/src/assets/thischain-token-registration.png b/src/assets/thischain-token-registration.png
diff --git a/src/assets/token-burn.png b/src/assets/token-burn.png
diff --git a/src/assets/transfer-to-parachain.png b/src/assets/transfer-to-parachain.png
diff --git a/src/hashi.md b/src/hashi.md
@@ -0,0 +1,13 @@
+# HASHI bridge
+
+This article is about a HASHI bridge - a decentralized two-way bridge connecting SORA and Ethereum. HASHI means bridge in Japanese, and it will be the plumbing that links many different chains, like pipes connecting the world's assets. This bridge was a significant component of the plans for the beta launch of the SORA network in Q1 2021.
+
+## Flows
+
+To move assets from Ethereum to the SORA v2 network, users send their ETH or supported ERC-20 tokens to a bridge contract on Ethereum; then, the user submits proof of the ETH transaction to the SORA network via an extrinsics call.
+
+![](https://miro.medium.com/v2/resize:fit:1100/format:webp/1*YiwUB4-nsN6QE_xjYBcB8A.png)
+
+To move assets from the SORA v2 network to Ethereum, a user needs to send their assets to a designated account on the SORA network, then once grandpa finality is complete, the cryptographic proof of the transaction is submitted to the Ethereum smart contract.
+
+![](https://miro.medium.com/v2/resize:fit:1100/format:webp/1*5QA0OxvpM0yg0djoSPU7rw.png)
diff --git a/src/interoperability.md b/src/interoperability.md
@@ -0,0 +1,15 @@
+# Interoperability
+
+## History
+
+The SORA blockchain serves as an ecosystem for robust DeFi projects like SORA's decentralized global economic system and [Polkaswap](./polkaswap), a DEX specifically designed for an interoperable future. In line with this vision, we recognize that blockchain maximalism is no longer viable, and we acknowledge the importance of secure, fast, and efficient asset migration between blockchains.
+
+As an initial step towards achieving this, we have developed the source code for [HASHI](./hashi), a decentralized two-way bridge connecting SORA and Ethereum. In addition to Ethereum, SORA aims to establish connections with various ecosystems. Being built on Substrate, it is advantageous to utilize the built-in cross-chain transfer capabilities to facilitate communication with projects running on the Polkadot and Kusama ecosystems. To achieve this, the [Substrate bridge](./substrate-bridge) was developed.
+
+With multiple bridges already in operation, it becomes necessary to streamline the bridge interface to ensure consistent software components for cross-chain transfers across different heterogeneous blockchains. As a solution, the "Federated Bridge" was created to serve as the gateway between the SORA mainnet and the external world. The term "federated" is used because this bridge inherits certain features from a federated architecture.
+
+The federated bridge follows the following workflow; The user initiates a transfer by calling an extrinsic. Upon detecting a new transaction on the source network, each peer signs it with their respective key and registers the signature on the source network. Subsequently, active peers add their signatures to the user's transaction. Once a sufficient number of signatures are gathered, the transaction is forwarded to the target network via relayers. The relayers sign the messages before transmitting them. As a result, only the owner of the peer's private key can initiate this process. The target blockchain then verifies the recipient's compliance with the signature authority based on the consensus mechanism. If the verification is successful, the tokens will be released to the designated transfer agent's address on the new network.
+
+## Security
+
+As all bridges are quite technically complex, teams building on the SORA network may want guarantees that there will not be financial loss resulting from any technical difficulties with the bridge. While this will be explained more in a future article, the SORA Parliament will provide insurance for infrastructure that is deemed systemically important to the ecosystem. [Systemically Important Infrastructure (SII)](./social-insurance) will need to concede governance to the SORA Parliament, but in exchange, the Parliament will commit to socialize any losses, in order to give network participants the confidence to use the SORA network. Details will be laid out in a future article.