k1rill-fedoseev
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
      • No invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
      Please check the box to agree to the Community Guidelines.
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
No invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Please check the box to agree to the Community Guidelines.
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
3
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# Hypothetical Post-Merge Ethereum cross chain bridge# Hypothetical Post-Merge Ethereum cross chain bridge Ethereum ecosystem is currently moving towards a multi-chain environment. This both includes work on the sharding as part of the ETH2.0, as well as appearence of different side chains and rollups independent of Ethereum Mainnet. One of the basic needs for a multi-chain environment, is an existence of a secure communication channel between the chains. This post is a high-level description for the cross-chain bridge between two independent ETH2.0 chains and their respective execution layers (e.g. a bridge between ETH2.0 and [SBC]( https://www.xdaichain.com/for-validators/consensus/sbc)). The implementation phase will start as soon as possible, this post will be updated once more details are known. ## Assumptions 1. Eth 1.0 is getting merged into the Eth 2.0 beacon chain 2. xDai is getting merged into the SBC 3. [EIP2537](https://eips.ethereum.org/EIPS/eip-2537) is implemented in some of the execution layer post-merge hardforks. Hopefully it will included in the first feature-hardfork after the Merge itself. 4. Altair hardfork is activated and works on both, ETH2.0 and SBC. 5. Beacon block contains an accessable reference to the head of the execution layer shard. (e.g. `latest_execution_payload_header` in https://github.com/ethereum/consensus-specs/blob/dev/specs/merge/beacon-chain.md#beaconstate) 6. Independent oracles are willing to submit new headers to the destination chain smart contract (at least 1 tx is required per sync committee period (27 hours for ETH2.0, 16 hours for SBC)). Possibly with a some form of compensation. ## Operation Model 1. Given that the assumed model is pretty much symmetric, the bridge is expected to work in the full-duplex mode. Thus, it is possible to "transfer" information in both directions by following the same algorithm. In reallity, a full-duplex bridge is just a pair of two independent half-duplex bridges capable of transferring information in a single direction. 2. The model does not consider a fixed set of priviledged oracles or validators who are expected to confirm or sign some data. Instead, the bridge relies on the committee members of the beacon chain, who are frequently rotated and being chosen in pseudo-random way. * We are using sync committee members and their signatures directly as a secure way of syncing the beacon blocks. * We are trusting to the underlying attestation mechanism of the beacon chain and the way of how execution layer blocks are being included into the beacon block. Thus, we are transitevely trusting attestation committee members to link correct execution layer blocks. ## Data transfer sequence diagram This is a high-level example for the ETH1.0 -> xDAI data transfer in the post-merge environment. However, an exact underlying chains can be freely interchanged by any other chains conforming to the initial requirements. ```sequence Title: ETH1.0 -> xDAI post-merge data bridge participant ETH1.0 data participant ETH1.0 participant ETH2.0 committees participant ETH2.0 participant Oracle participant XDAI Light Client contract participant XDAI receiver contract ETH1.0 data->ETH1.0: included in the merkle tree\nsecured by the ETH1.0 block hash ETH2.0 committees->ETH1.0: get updated blocks\nhashes for proposals ETH2.0 committees->ETH2.0: propose and attest updated\nETH1.0 block hashes ETH2.0 committees->ETH2.0: sync committee contributions ETH2.0 committees->ETH2.0: LMD GHOST votes ETH2.0->ETH2.0: beacon block is marked as finalized Oracle->ETH2.0: gather new blocks and\nsync committee signatures Oracle->XDAI Light Client contract: check if the known\nETH2.0 is outdated Oracle->ETH2.0: request beacon state, merkle proofs Oracle->XDAI Light Client contract: submit ETH2.0 block hash,\nmerkle proofs,\nsync committee signatures XDAI Light Client contract->XDAI Light Client contract: follow sync protocol\n verifications XDAI Light Client contract->XDAI Light Client contract: save verified\nETH2.0 block hash XDAI receiver contract->XDAI Light Client contract: get verified ETH2.0 block hash XDAI receiver contract-->ETH2.0: get associated ETH1.0 block hash and merkle proof for it XDAI receiver contract-->ETH1.0: get merkle proof for ETH1.0 data XDAI receiver contract->XDAI receiver contract: combine merkle proofs XDAI receiver contract->XDAI Light Client contract: verify combined merkle proof ETH1.0 data-->XDAI receiver contract: data transfer happened ``` ## Open questions 1. How to incentivize the oracles, so that there is always a sufficient(in terms of robustness) number of them? 2. How to choose delay parameters and timeouts for accepting non-finalized blocks in case of inactivity leak? 3. In case of oracle incentivization is used, how to prevent possible front running attacks for oracle transactions? 4. Does it makes sense to implement some non-strict sequencing for the oracles? How we can reduce possible number of failed transactions due to the race conditions in the Light Client contract updates?

Import from clipboard

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.
Upgrade
All
  • All
  • Team
No template found.

Create custom template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

How to use Slide mode

API Docs

Edit in VSCode

Install browser extension

Get in Touch

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Upgrade to Prime Plan

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

No updates to save
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully