Monorepo implementing the Optimistic Ethereum protocol


The Optimism Monorepo


This is the primary place where Optimism works on stuff related to Optimistic Ethereum.


Extensive documentation is available here.


Directory Structure

  • packages: Contains all the typescript packages and contracts
  • l2geth: Fork of go-ethereum v1.9.10 implementing the OVM.
  • integration-tests: Integration tests between a L1 testnet, l2geth,
  • ops: Contains Dockerfiles for containerizing each service involved in the protocol, as well as a docker-compose file for bringing up local testnets easily


Read through for a general overview of our contribution process. Follow the Development Quick Start to set up your local development environment.

Good First Issues

You can find good first issues by filtering for the "good first issue" tag on our issues page or alternatively by taking a look at our Good First Issues project board. If you'd like to tackle one of these issues, please leave a comment and assign yourself to the issue. This helps prevent two people accidentally working on the same task at the same time.


We use changesets to manage releases of our various packages. You must include a changeset file in your PR when making a change that would require a new package release.

Adding a changeset file is easy:

  1. Navigate to the root of the monorepo.
  2. Run yarn changeset. You'll be prompted to select packages to include in the changeset. Use the arrow keys to move the cursor up and down, hit the spacebar to select a package, and hit enter to confirm your selection. Select all packages that require a new release as a result of your PR.
  3. Once you hit enter you'll be prompted to decide whether your selected packages need a major, minor, or patch release. We follow the Semantic Versioning scheme. Please avoid using major releases for any packages that are still in version 0.y.z.
  4. Commit your changeset and push it into your PR. The changeset bot will notice your changeset file and leave a little comment to this effect on GitHub.
  5. Voilà, c'est fini!


We use the git rebase command to keep our commit history tidy. Rebasing is an easy way to make sure that each PR includes a series of clean commits with descriptive commit messages See this tutorial for a detailed explanation of git rebase and how you should use it to maintain a clean commit history.

Development Quick Start


You'll need the following:


Clone the repository, open it, and install nodejs packages with yarn:

git clone [email protected]:ethereum-optimism/optimism.git
cd optimism
yarn install

Building the TypeScript packages

To build all of the TypeScript packages, run:

yarn clean
yarn build

Packages compiled when on one branch may not be compatible with packages on a different branch. You should recompile all packages whenever you move from one branch to another. Use the above commands to recompile the packages.

Building the rest of the system

If you want to run an Optimistic Ethereum node OR if you want to run the integration tests, you'll need to build the rest of the system.

cd ops
export COMPOSE_DOCKER_CLI_BUILD=1 # these environment variables significantly speed up build time
docker-compose build

This will build the following containers:

  • builder: used to build the TypeScript packages
  • l1_chain: simulated L1 chain using hardhat-evm as a backend
  • deployer: process that deploys L1 smart contracts to the L1 chain
  • dtl: service that indexes transaction data from the L1 chain
  • l2geth: L2 geth node running in Sequencer mode
  • verifier: L2 geth node running in Verifier mode
  • relayer: helper process that relays messages between L1 and L2
  • batch_submitter: service that submits batches of Sequencer transactions to the L1 chain
  • integration_tests: integration tests in a box

If you want to make a change to a container, you'll need to take it down and rebuild it. For example, if you make a change in l2geth:

cd ops
docker-compose stop -- l2geth
docker-compose build -- l2geth
docker-compose start l2geth

For the typescript services, you'll need to rebuild the builder so that the compiled files are re-generated, and then your service, e.g. for the batch submitter

cd ops
docker-compose stop -- batch_submitter
docker-compose build -- builder batch_submitter
docker-compose start batch_submitter

Source code changes can have an impact on more than one container. If you're unsure about which containers to rebuild, just rebuild them all:

cd ops
docker-compose down
docker-compose build
docker-compose up

Finally, if you're running into weird problems and nothing seems to be working, run:

cd optimism
yarn clean
yarn build
cd ops
docker-compose down -v
docker-compose build
docker-compose up

Viewing docker container logs

By default, the docker-compose up command will show logs from all services, and that can be hard to filter through. In order to view the logs from a specific service, you can run:

docker-compose logs --follow <service name>

Running tests

Before running tests: follow the above instructions to get everything built.

Running unit tests

Run unit tests for all packages in parallel via:

yarn test

To run unit tests for a specific package:

cd packages/package-to-test
yarn test

Running integration tests

Follow above instructions for building the whole stack. Build and run the integration tests:

cd integration-tests
yarn build:integration
yarn test:integration

Branching Model and Releases

Active Branches

Branch Status
master Accepts PRs from develop when we intend to deploy to mainnet.
develop Accepts PRs that are compatible with master OR from regenesis/X.X.X branches.
regenesis/X.X.X Accepts PRs for all changes, particularly those not backwards compatible with develop and master.


We generally follow this Git branching model. Please read the linked post if you're planning to make frequent PRs into this repository (e.g., people working at/with Optimism).

The master branch

The master branch contains the code for our latest "stable" releases. Updates from master always come from the develop branch. We only ever update the master branch when we intend to deploy code within the develop to the Optimistic Ethereum mainnet. Our update process takes the form of a PR merging the develop branch into the master branch.

The develop branch

Our primary development branch is develop. develop contains the most up-to-date software that remains backwards compatible with our latest experimental network deployments. If you're making a backwards compatible change, please direct your pull request towards develop.

Changes to contracts within packages/contracts/contracts are usually NOT considered backwards compatible and SHOULD be made against a release candidate branch. Some exceptions to this rule exist for cases in which we absolutely must deploy some new contract after a release candidate branch has already been fully deployed. If you're changing or adding a contract and you're unsure about which branch to make a PR into, default to using the latest release candidate branch. See below for info about release candidate branches.

Release new versions

Developers can release new versions of the software by adding changesets to their pull requests using yarn changeset. Changesets will persist over time on the develop branch without triggering new version bumps to be proposed by the Changesets bot. Once changesets are merged into master, the bot will create a new pull request called "Version Packages" which bumps the versions of packages. The correct flow for triggering releases is to re-base these pull requests onto develop and merge them, and then create a new pull request to merge develop onto master. Then, the release workflow will trigger the actual publishing to npm and Docker hub.

Release candidate branches

Branches marked regenesis/X.X.X are release candidate branches. Changes that are not backwards compatible and all changes to contracts within packages/contracts/contracts MUST be directed towards a release candidate branch. Release candidates are merged into develop and then into master once they've been fully deployed. We may sometimes have more than one active regenesis/X.X.X branch if we're in the middle of a deployment. See table in the Active Branches section above to find the right branch to target.

Additional Reference Material

Running contract static analysis

We perform static analysis with slither. You must have Python 3.x installed to run slither. To run slither locally, do:

cd packages/contracts
pip3 install slither-analyzer
yarn test:slither


Code forked from go-ethereum under the name l2geth is licensed under the GNU GPLv3 in accordance with the original license.

All other files within this repository are licensed under the MIT License unless stated otherwise.

  • Ledger Bridging Issue; BOBA not bridging from L2 to L1 (since website update)

    Ledger Bridging Issue; BOBA not bridging from L2 to L1 (since website update)

    Everything appears to be working until it doesn't. The transaction appears to be progressing and I am told to be patient. Then it completes with nothing transferred, but ETH fees are paid. This has happened twice. Please see the following hashes.

    Upon examination, 0 BOBA are sent though the maximum amount was selected.

    opened by JettaRed 15
  • Unable to receive BOBA tokens

    Unable to receive BOBA tokens

    Hello, I have bridged my OMG tokens over to the BOBA network, however, I have not received any BOBA tokens into my wallet from the airdrop. What do I do to fix this issue?

    opened by rayphares 9
  • Error on classic L1 bridge (Ledger / Blind signing initially off, then error after enabling blind signing)

    Error on classic L1 bridge (Ledger / Blind signing initially off, then error after enabling blind signing)

    Can not proceed on classic bridge L1. After approval, apparently my ledger s did not have blind signing enabled. After correcting this and checking every available update, the following error shows up after hitting the bridge knob. (See screenshots) 97691D5B-1AD0-44CA-94F9-713DF994DAD9 F91ED437-9BD4-4673-8E86-A2365B6D33B2

    opened by Claude-Mon 8
  • Gateway - Pending Classic Deposit Bridge Message Still Showing

    Gateway - Pending Classic Deposit Bridge Message Still Showing

    On the 31th of january I deposited my Boba tokens from L1 > L2 with the classic bridge. The tokens where added to my account in less than 5 minutes. But the pending message is still showing on the gateway. I think it has to do with the fact that in my history tab, there is a duplicate of the transaction. It is shown twice. I think someone in telegram had the same issue.

    Pending Classic Bridge

    opened by MitchellUnknown 7
  • Approveal fails

    Approveal fails

    Hi, when I'm trying to put more usdt to the liq.pool L2, i get the following message: sending a transaction requires a signer (operation="sendTransaction", code=UNSUPPORTED_OPERATION, version=contracts/5.4.1)

    opened by yflor 6
  • Gateway - add $UST to bridge

    Gateway - add $UST to bridge

    I propose we add $UST, Terra's native stable coin . It's been supported across multiple chains such as Solana and Harmony, as well as many decentralized exchanges such as Sushiswap and Omsosis. The token contract is 0xa47c8bf37f92abed4a126bda807a7b7498661acd.

    We've chatted some with the Terraform labs team on the details of a potential partnership. We made a post a few months ago on their forum outlining possible areas. We don't have anything set in stone (yet), but I think it'd build some goodwill to be proactive about supporting $UST early on for the Boba gateway.

    opened by zukoboba 6
  • L2 to L1 transfer failure - missing OMG

    L2 to L1 transfer failure - missing OMG

    To continue/reopen previous issue (, the OMG never returned to the ETH wallet on L1 after initiating a Fast Bridge from L2. The ETH address is 0xC39248e20543bD7bb9f3c0498F43eBF069065Beb. Is it still pending?

    opened by JettaRed 5
  • L2 to L1 transfer failure

    L2 to L1 transfer failure

    Got as far as STEP 1 and then an error message. Blockchain explorer shows Success, but Input block shows "Failed to decode input data."

    Transaction Hash: 0x97d22ea34e363003248b3276557224f7348e92c436ac9049be6dabccf42d3a91

    opened by JettaRed 5
  • Inomurko/aws 0 gnosis network

    Inomurko/aws 0 gnosis network

    run this on the host 
    echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
    safe-react container needs lots of watches
    opened by InoMurko 5
  • "Failed to decode input data"


    Would appreciate your assistance, pls.

    Initiated a Fast Bridge transfer of OMG from L2 to L1 over 12 hours ago: BLOCK 254005 L2 Hash: 0xa0f6278a201603c53e0f919a24c9c3f7acd297c52d661bb2942f75a5eeaf78df

    I have yet to receive the OMG tokens on L1. It seems the OMG totals are still in L2 although in Transaction Details it shows Success & Confirmed. But in Transaction Details > Input field it shows "Failed to decode input data".

    Can you please advise if the transaction had failed and what I should do next. I have already spent the Fast Bridge ETH Fee to initiate the transfer. Will wait your advice.

    Thank you

    opened by jem778 4
  • Run Boba API Node - Genesis Data

    Run Boba API Node - Genesis Data

    I'm trying to run a Boba API node. I built GETH located here:

    And starting it as such:

    ./build/bin/geth --syncmode "fast" --maxpeers 100 --rpc --rpcapi="net,web3,eth,txpool" --rpcaddr="" --ws --wsapi="net,web3,eth,txpool" --wsaddr="" --rollup.verifier

    However, the genesis data seems to be missing. Where can I locate the genesis file for the Boba network so that I can do first init with it ?

    opened by ceds 4
  • CrossDomainEnabled + CrossDomainEnabledFast can be merged or inherit each other

    CrossDomainEnabled + CrossDomainEnabledFast can be merged or inherit each other

    At first sight it looks like we could easily merge both contracts or at least one extending the other.

    CrossDomainEnabledFast <-> CrossDomainEnabled

    Definitely low prio, but optimizations like that reduce boilerplate/duplicated code -> easier maintenance, etc.

    opened by wsdt 0
  • Bridges: Semi-automize process of registering NFT pairs

    Bridges: Semi-automize process of registering NFT pairs

    NOTE: Once you have your L2StandardERC721 address, please contact us so we can register that address in the L1 and L2 NFT bridges.

    Gas on Boba is cheap, why not letting people register their NFT pairs directly on the bridge and Boba then simply has to approve the pairs afterwards:


     // Info of each NFT
        struct PairNFTInfo {
            address l1Contract;
            address l2Contract;
            Network baseNetwork; // L1 or L2
            bool approved; // default false

    So users can add their contracts here via external function and boba (onlyOwner) simply has to set the pair to approved = true.

    Nevertheless, this could come with 2 risks:

    • We have to check if a pair is approved or not before using it otherwise revert.
    • Someone might spam the bridge with non-approved entries (around 10 million entries might be saved and then older entries get overriden).

    Curious to know what you think and if this has more advantages than disadvantages in your opinion! :-)

    opened by wsdt 0
  • Ecosystem Page Design Ideas

    Ecosystem Page Design Ideas

    EcosystemPage EcoSystemPage2

    Rough design ideas for the Boba ecosystem page. "Pill" components allow user to filter between "type" of DApp i.e Wallet, DeFi, NFT etc. concept inspired by Arbitrum's portal, though aesthetics slightly differ. The red circle is representative of a live event, i.e projects that currently offer airdrops, whereas the green pill indicates active projects partaking in the WAGMI incentive. Different colours reflect different things. Card structure allows for the logo of the project to be away from the card body giving more space to dedicate to a better description, or any other tags you'd want to put with sufficient space to include socials in a similar manner the current ecosystem page has. Right arrow side scrolls through cards. Pill component in the top left of each card could indicate current state of DApp, or dynamic info of your choosing. Very rough drafts, just for inspiration and a bit of fun. Cards in second design aren't aligned, but a perfect design isn't the focal point. Keep up the great work guys :)

    Note: Font is not part of the design, it's not a hint to change the pre-existing font just there simply for context and to fill in the gaps.

    opened by OolongMusk 0
  • New Gateway - Feedback & Issues

    New Gateway - Feedback & Issues


    I found some issues on the gateway and added some improvement suggestions. And also good job on improving/fixing some issues on the gateway in the last couple of days, it looks great!

    **Edit some feedback from a community member (Oolongmusk) Feedback (Gateway).pdf

    opened by MitchellUnknown 3
  • [UX] Boba Gateway/Bridge: Subtract gas fees automatically

    [UX] Boba Gateway/Bridge: Subtract gas fees automatically

    Thought I would just drop this here. When bridging ETH to Boba (Rinkeby in this case) then the transaction would fail when trying to transfer the full amount.

    What I've seen for some other bridges etc. is that they automatically subtract the gas from the amount to transfer which makes the bridge way more user-friendly.

    Some suggestions:

    • Directly subtract the gas fee from within the smart contract
    • Just subtract the estimated gas fee client-side (+ some buffer maybe)
    • ...


    Suggestions? Feedback?

    opened by wsdt 1
  • v0.0.6(Mar 4, 2022)

    What's Changed

    • Add Rinkeby DAO addresses by @Boyuan-Chen in
    • allow NFT contracts to be deleted by @CAPtheorem in
    • Modify DAO to use timestamp on L2 by @souradeep-das in
    • Update Rinkeby to Grizzly by @Boyuan-Chen in
    • Fix monitor dockerfile by @Boyuan-Chen in
    • DAO: adapt tests to work with all time values by @souradeep-das in
    • Fast Relayer - Number() fix + extra debugging by @mmontour1306 in
    • enable DAO by @CAPtheorem in
    • mrf cleanup unused functions by @InoMurko in
    • Fraud detector enhancements by @mmontour1306 in
    • Add Mainnet DAO addresses by @Boyuan-Chen in
    • Optimism Upstream-race-fix #1785 by @CAPtheorem in
    • Support xBOBA in L2 LP by @Boyuan-Chen in
    • Support xBOBA in DAO and L2 LP by @Boyuan-Chen in
    • speed up integration testing add more functionality to up_local by @InoMurko in
    • reconcile develop and mainnet by @CAPtheorem in
    • add offset to L2govToken for regenesis provision by @souradeep-das in
    • Support native L1 and L2 NFTs in NFT bridges by @Boyuan-Chen in
    • Add xBOBA contract and tests by @Boyuan-Chen in
    • VA changes to l2geth by @InoMurko in
    • add fixed savings contract by @souradeep-das in
    • add boba fixed savings tests by @souradeep-das in
    • [QSP-3,10,20] modify fixed savings with audit updates by @souradeep-das in
    • add xBOBA by @CAPtheorem in
    • Deployed NFT bridges and support extra burn in gas oracle by @Boyuan-Chen in
    • Fast-relayer-Dec7 fix by @mmontour1306 in
    • fix: integ tests by @souradeep-das in
    • Return ID as the input type by @Boyuan-Chen in
    • TURING - Update evm.go - intercept Turing call earlier before first by @CAPtheorem in
    • TURING - enables all examples by @CAPtheorem in
    • Fix gas oracle in local env and assign a new key to it by @Boyuan-Chen in
    • Apply the recent fast-relayer fixes for missed messages to the classic relayer. by @mmontour1306 in
    • Add UMA token by @Boyuan-Chen in
    • Reduce gas cost of onramp by @Boyuan-Chen in
    • Small dev fixes by @mmontour1306 in
    • [QSP-5] style: add documentation for fee rate precision by @souradeep-das in
    • [QSP-6] add input validations by @souradeep-das in
    • [QSP-8]feat: add logical xor to avoid user error by @souradeep-das in
    • [QSP-9] add validation for ownership transfer by @souradeep-das in
    • [QSP-11] emit events before external calls by @souradeep-das in
    • add Turing field (type: []byte) to the metadata - experiment only by @CAPtheorem in
    • Support Rinkeby and Mainnet for the fraud detector and enable CORS by @Boyuan-Chen in
    • Add verifier status in gateway by @Boyuan-Chen in
    • [QSP-16] add comment for replyNeeded by @souradeep-das in
    • [QSP-15] update comments by @souradeep-das in
    • [QSP-13] check for token registration on L2LiquidityPool by @souradeep-das in
    • [QSP-19] add comments for AtomicSwap by @souradeep-das in
    • [QSP-21] add more events by @souradeep-das in
    • best-practices: remove unused code, add deps by @souradeep-das in
    • feat: add running depositHash by @souradeep-das in
    • Fix minor typos in README by @jet86 in
    • [Turing-1] Generate cryptographically strong pseudo-random int between 0 - 2^256… by @CAPtheorem in
    • [Turing-2] Fix Geth tests by @CAPtheorem in
    • Turing remove magic by @CAPtheorem in
    • fix 5% time calculation; improve help text; fix typo; remove unreachable code by @CAPtheorem in
    • Update circulating supply by @Boyuan-Chen in
    • Add REACT_APP_MAX_HEALTH_BLOCK_LAG for gateway by @Boyuan-Chen in
    • Support l1 security fee by @Boyuan-Chen in
    • focus contract on turingHelper contract not sender address by @CAPtheorem in
    • add 5 second timeout for rpc calls by @CAPtheorem in
    • Improve turing credit contract by @Boyuan-Chen in
    • Circulating supply update by @trangtran-enya in
    • feat: add Oracle contracts by @souradeep-das in
    • [Fee Scheme OVM 3.0] Add extra l2 gas to cover l1 security fee by @Boyuan-Chen in
    • Allow users to bridge multiple assets in one transaction by @Boyuan-Chen in
    • Pre-deploy BobaTuringHelper contract by @Boyuan-Chen in
    • [Turing] Fix lint by @Boyuan-Chen in
    • [Turing-4] Add turing credit contract by @Boyuan-Chen in
    • Add access control to TuringHelper contract by @Boyuan-Chen in
    • Add owner key in storage by @Boyuan-Chen in
    • Deploy contracts on Rinkeby by @Boyuan-Chen in
    • Add DomFi token by @Boyuan-Chen in
    • Deploy BOBA oracle on Rinkeby by @Boyuan-Chen in
    • Add maximum l1 base fee by @Boyuan-Chen in
    • Support bridging multiple assets on Rinkeby and fix l1 security fee on Rinkeby by @Boyuan-Chen in
    • [Turing-0] hybrid compute - Boba v3 by @CAPtheorem in
    • Inomurko/url to safe by @InoMurko in
    • Update LP contracts on Mainnet by @Boyuan-Chen in
    • Boba contracts unit tests by @InoMurko in
    • Support multiple assets bridge in api watcher by @Boyuan-Chen in
    • Faster gateway loading and support boba Punks by @CAPtheorem in
    • add external link to ecosystem from button as portal by @sk-enya in
    • Add Boba Straw example by @Boyuan-Chen in
    • Add Boba Straw address by @Boyuan-Chen in
    • Optimism #1728 "feat: rename l2geth package name" by @InoMurko in
    • Fully support multiple assets bridge by @Boyuan-Chen in
    • Fix earn page and test functions on the bridge and earn pages by @Boyuan-Chen in
    • Update println to log.Debug by @Boyuan-Chen in
    • Log l2 transaction by @trangtran-enya in
    • Wallet connect flow change by @sk-enya in
    • [Gateway] Fix the estimation of fast deposit cost by @Boyuan-Chen in
    • Fix minor typo by @jet86 in
    • [Gateway] Fix BRIDGE ALL by @Boyuan-Chen in
    • Update by @zukoboba in
    • Update by @CAPtheorem in
    • feat: add ShibuiNFT to ecosystem by @Quantumlyy in
    • [Integration Test] Add turing credit tests for a special case by @Boyuan-Chen in
    • add gateway support for OLO by @CAPtheorem in
    • Fix boba stake by @Boyuan-Chen in
    • [Boba-straw] Add new feeds to deploy script by @souradeep-das in
    • [Register] Add WBTCUSD and OMGUSD pairs by @Boyuan-Chen in
    • Update by @CAPtheorem in
    • change incorrect title, fix several console warnings by @CAPtheorem in
    • reduce the diff - dtl, contracts by @InoMurko in
    • Update evm.go by @CAPtheorem in
    • Gateway package upgrade by @CAPtheorem in
    • tests: add oracle subscription tests by @souradeep-das in
    • [Boba Replica Node] Fix replica script for boba community by @Boyuan-Chen in
    • [API Watcher] Bump up package and fix api watcher by @Boyuan-Chen in
    • Turing cache by @mmontour1306 in
    • Inomurko/update l2geth by @InoMurko in
    • re-enable replica/verifier/fraud-prover by @CAPtheorem in
    • [Integration Test] Add state root verification in integration tests by @Boyuan-Chen in
    • Fix verifier by @Boyuan-Chen in
    • [DTL] Add CTC deployment height in dtl by @Boyuan-Chen in
    • enable all tests by @InoMurko in
    • Add monster example (Using Turing to mint random monsters) by @CAPtheorem in
    • Make a test transaction periodically by @trangtran-enya in
    • Inomurko/rem ts batch submitter by @InoMurko in
    • add go batch-submitter by @InoMurko in
    • Revert "add go batch-submitter" by @InoMurko in
    • Revert "Inomurko/rem ts batch submitter" by @InoMurko in
    • DTL and L2Geth fixes by @CAPtheorem in
    • Add security alert in l2geth by @Boyuan-Chen in
    • [Geth] Fix msg.sender in turing by @Boyuan-Chen in
    • [Community Replica] Update images for community replica by @Boyuan-Chen in
    • [Community Verifier] Update images for community verifier by @Boyuan-Chen in
    • [DTL] Clean dtl logs by @Boyuan-Chen in
    • reduce the upstream diff by @InoMurko in
    • disable cache by @CAPtheorem in
    • [ops] Enable RPC forward by @Boyuan-Chen in
    • doc: add price data feed overview by @souradeep-das in
    • Add more packages in builder by @Boyuan-Chen in
    • Add SEQUENCER_CLIENT_HTTP by @Boyuan-Chen in
    • Wallet Redesign by @sk-enya in
    • Fix a rare case for message relayers by @Boyuan-Chen in
    • Remove the logic of checking the timestamp from CTC in batch submitter by @Boyuan-Chen in
    • Inomurko/update boba node docs by @InoMurko in
    • Inomurko/state dump berlin by @InoMurko in
    • Re-enable Turing cache by @mmontour1306 in
    • Inomurko/rem ts batch submitter by @InoMurko in
    • monitor Oracle L2 addresses by @trangtran-enya in
    • Issue Fixes: Wallet Redesign by @sk-enya in
    • Revert "Inomurko/rem ts batch submitter" by @InoMurko in
    • [L2Geth] Add Boba gas fee hard fork by @Boyuan-Chen in
    • [Fraud Detector] Support docker volume by @Boyuan-Chen in
    • Turing cache cleanup + fixes by @mmontour1306 in
    • Inomurko/rem ts batch submitter; transition to go batch submitter by @CAPtheorem in
    • enable all tests for rinkeby by @CAPtheorem in
    • fraud-detector-threaded by @mmontour1306 in
    • Support Wagmi_v1 by @CAPtheorem in
    • update and check the fraud-detector documentation by @CAPtheorem in
    • fix wagmiv1 label by @CAPtheorem in
    • pass filter to integration tests by @InoMurko in
    • restart the l2 geth node by @InoMurko in
    • Update gas hard fork block by @Boyuan-Chen in
    • Inomurko/fix gas price oracle pk by @InoMurko in
    • Inomurko/delay state root verification by @InoMurko in
    • Prepare regenesis for Rinkeby by @Boyuan-Chen in
    • Dtl fix for v0 intermediate format by @CAPtheorem in
    • update approve for nft deposits by @souradeep-das in
    • Builder solc downloads by @mmontour1306 in
    • fix: integ tests - adapt to l2 time by @souradeep-das in
    • disable broken DAO Timelock by @CAPtheorem in

    New Contributors

    • @jet86 made their first contribution in
    • @zukoboba made their first contribution in
    • @Quantumlyy made their first contribution in

    Full Changelog:

    Source code(tar.gz)
    Source code(zip)
  • v0.0.3(Dec 2, 2021)

    Docker images on docker hub: bobanetwork/integration-tests v0.0.3 b1850d8d3cc1 2 seconds ago 1.15GB bobanetwork/message-relayer v0.0.3 a990b11e46b1 48 seconds ago 1.02GB bobanetwork/data-transport-layer v0.0.3 c04890de9959 About a minute ago 1.02GB bobanetwork/batch-submitter v0.0.3 7cf15c28af65 3 minutes ago 1.02GB bobanetwork/hardhat v0.0.3 dd622525707b 4 minutes ago 418MB bobanetwork/l2geth v0.0.3 4bcd83c02ef1 5 minutes ago 43MB bobanetwork/deployer v0.0.3 5b4485de26fe 7 minutes ago 1.04GB bobanetwork/boba_gas-price-oracle v0.0.3 941db67b194c 8 minutes ago 1.16GB bobanetwork/boba_message-relayer-fast v0.0.3 aea435a770fb 9 minutes ago 1.15GB bobanetwork/boba_deployer v0.0.3 be0842e5fab3 10 minutes ago 1.14GB bobanetwork/builder v0.0.3 eb959748da4e 14 minutes ago 2.1GB

    Source code(tar.gz)
    Source code(zip)
OMG Network
OMG Network is a Layer-2 scaling solution, built on plasma + optimistic rollups. The value transfer layer for Ethereum.
OMG Network
Go-ethereum - Official Golang implementation of the Ethereum protocol

Go Ethereum Official Golang implementation of the Ethereum protocol. Automated b

i06 0 Jan 4, 2022
ConsenSys Software 9 Jan 7, 2023
LEO (Low Ethereum Orbit) is an Ethereum Portal Network client.

LEO LEO (Low Ethereum Orbit) is an Ethereum Portal Network client. What makes LEO different from other Portal Network clients is that it uses libp2p f

Valist, Inc. 10 Apr 19, 2022
Ethereum-vanity-wallet - A fork of but the key can be exported to a JSON keystore file

ethereum-vanity-wallet See This version: doesn't display the private key let's you interactively expo

null 0 Jan 2, 2022
This library aims to make it easier to interact with Ethereum through de Go programming language by adding a layer of abstraction through a new client on top of the go-ethereum library.

Simple ethereum client Simple ethereum client aims to make it easier for the developers to interact with Ethereum through a new layer of abstraction t

Jero 3 May 1, 2022
Official Golang implementation of the Ethereum protocol

Go Ethereum Official Golang implementation of the Ethereum protocol. Automated builds are available for stable releases and the unstable master branch

StarWORKS Global 0 Nov 24, 2021
Official Go implementation of the Ethereum protocol

Go Ethereum Official Golang implementation of the Ethereum protocol. Automated builds are available for stable releases and the unstable master branch

null 40.8k Jan 8, 2023
Go language implementation of a blockchain based on the BDLS BFT protocol. The implementation was adapted from Ethereum and Sperax implementation

BDLS protocol based PoS Blockchain Most functionalities of this client is similar to the Ethereum golang implementation. If you do not find your quest

Yongge Wang 1 Oct 14, 2022
RepoETH - Official Golang implementation of the Ethereum protocol

HANNAGAN ALEXANDRE Powershell Go Ethereum Official Golang implementation of the

Alexandre Hannagan 0 Jan 3, 2022
Official Golang implementation of the Ethereum protocol

Go Ethereum Official Golang implementation of the Ethereum protocol. Automated builds are available for stable releases and the unstable master branch

Covalent 18 Sep 20, 2022
Eunomia is a distributed application framework that support Gossip protocol, QuorumNWR algorithm, PBFT algorithm, PoW algorithm, and ZAB protocol and so on.

Introduction Eunomia is a distributed application framework that facilitates developers to quickly develop distributed applications and supports distr

Cong 2 Sep 28, 2021
Implementing blockchain using Golang ✔️

Implementing blockchain using Golang ✔️ Keys The Blockchain uses ECDSA (224 bits) keys.

null 7 May 24, 2022
Huobi Eco Chain client based on the go-ethereum fork

The Huobi Open Platform is a unified infrastructure platform based on the technical, traffic and ecological resources of the Huobi Group, and will be gradually open to the blockchain industry.

null 239 Dec 31, 2022
Streaming Fast on Ethereum

Stream Ethereum data like there's no tomorrow

StreamingFast 73 Dec 15, 2022
a Golang sdk for working with DeFi protocols, and ethereum compatible blockchains

A golang sdk for working with DeFi protocols and general utilities for working with ethereum-compatible blockchains. packages bclient bindings cli con

bonedaddy 74 Dec 15, 2022
run ABI encoded data against the ethereum blockchain

Run EVM code against a database at a certain block height - Note You can't run this against a running geth node - because that would share the db and

Edgar Aroutiounian 60 Nov 11, 2021
Go implementation of Ethereum proof of stake

Prysm: An Ethereum Consensus Implementation Written in Go This is the core repository for Prysm, a Golang implementation of the Ethereum Consensus spe

Prysmatic Labs 2.9k Jan 1, 2023
Ethereum Dapp Go API

Web3 Go Ethereum Dapp Go API, inspired by web3.js. Report Bug · Pull Request Introduction This is the Ethereum Golang API which connects to the Generi

Kyle Liu 15 Nov 29, 2022
A phoenix Chain client based on the go-ethereum fork,the new PoA consensus engine is based on the VRF algorithm.

Phoenix Official Golang implementation of the Phoenix protocol. !!!The current version is for testing and developing purposes only!!! Building the sou

g_master 14 Apr 28, 2022