Conversation
Prepares the `op-proposer` to no longer depend on the `op-bindings` package. This will enable releases of the `op-proposer` to work with specific releases of the contracts more easily by using `abigen` at a specific release of the contracts to create bindings. We will be gutting `op-bindings` as a package because it is not versioned, implying all versions must be backwards and forwards compatible. It also adds a lot of overhead to smart contract development with having to create the bindings and commit in a diff every time there is a solidity source file change.
|
Warning Rate Limit Exceeded@tynes has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 32 minutes and 47 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Removes the `op-challenger` from requiring the global bindings. This allows the service to be explicit about contract versions that it supports. The `op-bindings` were not versioned and added a lot of pain when it came to smart contract development as they needed to always be updated. Follows: - #10213 - #10218
Removes the dependency on the `op-bindings/bindings` package. This is to improve devex in the monorepo and reduce CI time as maintaining the bindings autogenerated in each PR just doesn't scale. Now each service is responsible for their own bindings. In the future, we can work towards releases of the bindings when contracts are released. Follows: - #10213 - #10218 - #10221
Removes the dependency on the `op-bindings/bindings` package. This is to improve devex in the monorepo and reduce CI time as maintaining the bindings autogenerated in each PR just doesn't scale. Now each service is responsible for their own bindings. In the future, we can work towards releases of the bindings when contracts are released. Follows: - #10213 - #10218 - #10221
* indexer: remove bindings Removes the dependency on the `op-bindings/bindings` package. This is to improve devex in the monorepo and reduce CI time as maintaining the bindings autogenerated in each PR just doesn't scale. Now each service is responsible for their own bindings. In the future, we can work towards releases of the bindings when contracts are released. Follows: - #10213 - #10218 - #10221 * indexer: add missing binding
Description
Prepares the
op-proposerto no longer dependon the
op-bindingspackage. This will enablereleases of the
op-proposerto work with specificreleases of the contracts more easily by using
abigenat a specific release of the contracts to create bindings.
We will be gutting
op-bindingsas a package becauseit is not versioned, implying all versions must be backwards
and forwards compatible. It also adds a lot of overhead to
smart contract development with having to create the bindings
and commit in a diff every time there is a solidity source file
change.