1. 14 Jun, 2022 2 commits
    • Mark Tyneway's avatar
      contracts bedrock: implement simple proxy + admin (#2728) · 14dd80f3
      Mark Tyneway authored
      * ci: better check for snapshot diff
      
      * contracts-bedrock: unified solmate import
      
      * contracts-bedrock: fix solmate import
      
      * contracts-bedrock: implement Proxy
      
      * contracts-bedrock: implement ProxyAdmin
      
      * bedrock: snapshot
      
      * contracts: make admin work with legacy proxies
      
      * contracts-bedrock: review fixes
      
      * contracts-bedrock: linting
      
      * contracts-bedrock: lint
      
      * contracts-bedrock: review fixes
      
      * contracts-bedrock: snapshot
      
      * contracts-bedrock: rename
      
      * contracts-bedrock: renames
      
      * contracts-bedrock: renaming
      14dd80f3
    • sam-goldman's avatar
      feat: nft bridge from l1 to optimism (#2662) · da1633a3
      sam-goldman authored
      * feat: nft bridge from eth network to optimism
      
      * Update yarn.lock
      
      * feat: added event tests
      
      * fixed import path
      
      * feat: added integration tests to nft bridge
      
      * fix: removed constructor logic from l2 bridge so it can exist as a proxy
      
      * fix: updated pr based on maurelian's comments
      
      * deploy scripts
      Co-authored-by: default avatarMark Tyneway <mark.tyneway@gmail.com>
      da1633a3
  2. 13 Jun, 2022 1 commit
  3. 11 Jun, 2022 2 commits
  4. 10 Jun, 2022 14 commits
  5. 09 Jun, 2022 18 commits
  6. 08 Jun, 2022 3 commits
    • smartcontracts's avatar
      feat(cmn): BaseServiceV2 exposes internal options (#2688) · 9ecbf3e5
      smartcontracts authored
      BaseServiceV2 will expose internal options (loop interval, metrics port,
      etc) as environment variables or command line options.
      9ecbf3e5
    • Matthew Slipper's avatar
      proxyd: Fix concurrent WS write panic (#2711) · 552cd641
      Matthew Slipper authored
      Fixes a panic in the websocket proxyd logic. Normally, the `clientPump` and `backendPump` methods in `WSProxier` send data in one direction. However, when the client sends an invalid RPC, the `clientPump` will send a response _directly to the client_ in order to avoid unnecessary roundtrips to the backend. This could be interleaved with concurrent writes to the client's WS in `backendPump`, and would cause a panic in the WS library.
      
      To test this, this PR includes a dedicated integration test that reliably triggers the issue. In addition, this PR adds additional testing for WS functionality.
      552cd641
    • Matthew Slipper's avatar
      Revert "contracts: optimize `L1Block.setL1BlockValues` (#2596)" · 0577e787
      Matthew Slipper authored
      This reverts commit 2d791301.
      0577e787