- 14 Oct, 2022 5 commits
-
-
mergify[bot] authored
op-node: Use DoCtx in DialRPClientWithBackoff
-
mergify[bot] authored
-
mergify[bot] authored
op-e2e: action testing user
-
mergify[bot] authored
-
Joshua Gutow authored
This fixes an issue where if a short context was supplied to the call it would still take a long time to complete.
-
- 13 Oct, 2022 6 commits
-
-
Matthew Slipper authored
Version Packages
-
protolambda authored
-
github-actions[bot] authored
-
Matthew Slipper authored
Develop -> Master
-
Matthew Slipper authored
proxyd: Integrate custom rate limiter
-
Matthew Slipper authored
proxyd: Custom rate limiter implementation
-
- 12 Oct, 2022 5 commits
-
-
Mark Tyneway authored
Both op mainnet and op goerli The following script was used for the deployment. The commented out lines were used for mainnet. ```bash NETWORK=optimism-goerli npx hardhat deploy --network $NETWORK --tags MintManager ```
-
Matthew Slipper authored
The L2 head was being logged rather than the safe head's L1 origin.
-
Matthew Slipper authored
The handler returned from `log.LvlFilterHandler` wasn't being consumed anywhere, so log level configuration was being ignored. Co-authored-by:
mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
-
Matthew Slipper authored
Integrates the custom rate limiter in the previous PR into the rest of the application. Also takes the opportunity to clean up how we instantiate Redis clients so that we can share them among multiple different services. There are some config changes in this PR. Specifically, you must specify a `base_rate` and `base_interval` in the rate limit config.
-
Matthew Slipper authored
Our current proxyd deployment does not share rate limit state across multiple servers within a backend group. This means that rate limits on the public endpoint are artifically high. This PR adds a Redis-based rate limiter to fix this problem. While our current rate limiting library (github.com/sethvargo/go-limiter) _does_ support Redis, the client library it uses is not type safe, is less performant, and would require us to update the other places we use Redis. To avoid these issues, I created a simple rate limiting interface with both Redis and memory backend. Note that this PR only adds the new implementations - it does not integrate them with the rest of the codebase. I'll do that in a separate PR to make review easier.
-
- 11 Oct, 2022 1 commit
-
-
Chris Wessels authored
* fix: add optional data field to RPCError struct * fix: formatting lint * feat(proxyd): add changeset
-
- 10 Oct, 2022 7 commits
-
-
mergify[bot] authored
fix(ctb): remove unnecessary L2OO init param
-
mergify[bot] authored
-
Matthew Slipper authored
-
Matthew Slipper authored
-
Matthew Slipper authored
-
Matthew Slipper authored
-
Matthew Slipper authored
-
- 09 Oct, 2022 2 commits
-
-
Mark Tyneway authored
-
Mark Tyneway authored
-
- 08 Oct, 2022 12 commits
-
-
Kelvin Fichter authored
Removes an unnecessary parameter from the L200 initialization function since this parameter is already set in the constructor.
-
mergify[bot] authored
op-node: Fillbytes size check in l1 block info
-
Matthew Slipper authored
-
mergify[bot] authored
Add balance metrics to op-propose & op-batcher
-
Joshua Gutow authored
This was done to test the addition of the balance metric.
-
Joshua Gutow authored
-
Joshua Gutow authored
-
Joshua Gutow authored
This function periodically records the balance of the supplied account through metrics. The balance is recorded in Ether (not wei) to stay in bounds of a float64.
-
Maurelian authored
-
Maurelian authored
-
mergify[bot] authored
contracts-governance: allow deploy by ledger
-
Mark Tyneway authored
Adds the config for using a ledger with hardhat deploy. The env var `LEDGER_ADDRESS` must be set for this to work. Note that hh deploy is buggy and will always use the default path when creating a `LedgerSigner`. This means the `LEDGER_ADDRESS` env var is useless, it won't actually use that address when doing a deployment. Basically, if its set then it just means use the ledger's first derived address at the default path. This should be an easy thing to fix upstream, although kind of annoying. The paths would need to be searched linearly until a matching address is found, I think a better way to configure this is pass either: - A path + address - A path If both are passed, then it should validate that the path matches the address. If a path is passed, then yolo use the derived account.
-
- 07 Oct, 2022 2 commits
-
-
mergify[bot] authored
contracts-governance: mint manager deploy
-
mergify[bot] authored
-