Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat] ETH Bridge - Gravity (prev. Peggy) #234

Closed
jim380 opened this issue Feb 14, 2021 · 0 comments
Closed

[Feat] ETH Bridge - Gravity (prev. Peggy) #234

jim380 opened this issue Feb 14, 2021 · 0 comments
Assignees

Comments

@jim380
Copy link
Contributor

jim380 commented Feb 14, 2021

Summary

  1. Bring CertikShield and other security focused products CertiK offers to Ethereum
  2. Bring ETH and ERC-20 tokens on Ethereum to the CertiK chain, and vice versa

Architecture Overview

⚠️ [WIP] Proceed with caution ⚠️

gravity

Compatibility with BSC

  1. Take some tokens on the BSC and send them to Ethereum
  2. Send the tokens from Ethereum to the Cosmos chain

Readiness

Governance proposal later this year

Quick Bites

  • Peggy is now Gravity, and the pegzone concept has been left behind

  • Same security guarantee as the Cosmos Hub (billions of dollars of staked ATOMs)

  • ATOM and every other asset in Cosmos ecosystem can be traded on Uniswap and other DeFi products on Ethereum

  • IBC vs Bridges

    • IBC is designed to connect heterogeneous blockchains. For the IBC module to work, it has to be accompanied with customized bridge modules like Peggy
    • IBC could potentially work with probabilistic chains like Ethereum but it's not a feature on the current research roadmap
    • Peggy enables IBC chains to allow funds to be moved from Ethereum to any other cosmos chain connected to a chain running Peggy via IBC. Ethereum 1.0 itself isn't capable of supporting IBC
  • A bridge Operator has to maintain 3 processes:

    • Validator
    • Eth Full Node (or a light client peered with shared full nodes)
    • Eth Signer

    They might possibly want to run the Relayers also, which submit batched txs and pay the gas

  • A validator for the Gravity bridge is identical to a validator for the cosmos chain that has the bridge deployed. If you are already a validator in a cosmos chain, having a Gravity bridge in that chain only adds workload to your existing ones

Deploy

$ git clone https://github.com/althea-net/peggy
$ cd solidity
$ npm install
$ npm run typechain
$ npx ts-node \
$ contract-deployer.ts \
$ --cosmos-node="http://localhost:26657" \
$ --eth-node="http://localhost:8545" \
$ --eth-privkey="<needs some eth to pay for the deploy>" \
$ --contract=artifacts/Peggy.json \

Learn More

@hacheigriega hacheigriega self-assigned this Feb 22, 2021
@yoongbok-lee yoongbok-lee self-assigned this May 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants