1. 11 Jan, 2022 6 commits
    • Noah Litvin's avatar
      feat: Adds depcheck to CI workflow · 2b74b986
      Noah Litvin authored
      2b74b986
    • Mark Tyneway's avatar
      Merge pull request #1982 from ethereum-optimism/feat/sequencer-timestamp · 89eab8f7
      Mark Tyneway authored
      l2geth: update timestamp logic
      89eab8f7
    • Mark Tyneway's avatar
      chore: add changeset for integration-tests · dad6fd9b
      Mark Tyneway authored
      dad6fd9b
    • Mark Tyneway's avatar
      integration-tests: fix timestamp assertion · a0235ecb
      Mark Tyneway authored
      Update the assertion to not expect that the timestamps are
      exactly equal but instead assert that the values are within
      5%. This is because now the timestamps in L2 no longer
      correspond to L1 timestamps and may be updated arbitrarily
      by the sequencer.
      a0235ecb
    • Mark Tyneway's avatar
      chore: add changeset · 3a77bbcc
      Mark Tyneway authored
      3a77bbcc
    • Mark Tyneway's avatar
      l2geth: update timestamp logic · 57742a04
      Mark Tyneway authored
      This commit updates the timestamp updating logic
      such that `time.Now` is used instead of relying on
      L1 timestamps. This gives a higher fidelity for the
      `TIMESTAMP` opcode as well as makes the time on L2
      be closer to the time on L1.
      
      L1 to L2 transactions no longer have the property of
      having the same timestamp on L2 as the timestamp
      of the L1 block they were included in.
      
      This should be able to be turned on without needing
      hardfork logic as replicas should always accept the
      timestamp that the sequencer sets. The sequencer is
      a trusted entity in the existing implementation and
      it is expected that the sequencer will become more
      trustless in future iterations of the protocol.
      
      This change is added to improve both UX and devex.
      Users are confused by the timestamps on Etherscan
      being ~15 minutes behind. This is due to the timestamps
      being set based on L1 block numbers, and the system
      only pulls L1 data once a secure amount of PoW
      is placed on top. Developers would like the timestamps
      to have a higher fidelity and be closer to the timestamps
      on L1.
      57742a04
  2. 10 Jan, 2022 2 commits
  3. 08 Jan, 2022 15 commits
  4. 07 Jan, 2022 5 commits
  5. 05 Jan, 2022 7 commits
  6. 04 Jan, 2022 5 commits