Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(main): release protocol 1.1.0 #16315

Closed

Conversation

taiko-kitty
Copy link
Contributor

@taiko-kitty taiko-kitty commented Mar 4, 2024

🤖 I have created a release beep boop

1.1.0 (2024-03-29)

⚠ BREAKING CHANGES

  • protocol: apply bug fixes and introduce a few new features (#16543)
    • fix: Fix a proving bug when top-tier re-approves top-tier (reported by OpenZeppelin and Code4rena)
    • fix: Make each transition contesting only dependent on it's own cooldown period (reported by OpenZeppelin)
    • fix: Fix sender EOA check (reported by OpenZeppelin)
    • fix: Fix or improve comments (reported by Code4rena)
    • fix: Fix genesis script by add missing state variables (reported by OpenZeppelin)
    • feat: Emit event for client / node (Requested by Huan)
    • feat: Introduce DelegateOwner to become the owner of all L2 contracts
    • feat: Improve bridged nft tokens
    • feat: Improve Bridge _proveSignalReceived code readability
    • feat: Make testnets and mainnet have the same bridge configuration
    • feat: Rename tier providers
    • feat: Upgrade solhint to 4.5.2
    • feat: Update chain id for the upcoming Hekla testnet
    • feat: Adjust proving reward to increase valid contestation ROI
    • feat: Improve L2 1559 fee calculation code
    • feat: Make each transition contesting only dependent on it's own cooldown period
  • protocol: remove the blob-reuse feature (#16439)

Features

  • protocol: allow L2 contracts to read L2's parent block timestamp (#16425) (9b79359)
  • protocol: allow minGuardians be any value between 0 and numGuardians (#16384) (0b1385e)
  • protocol: enable EIP712 signature for TimelockTokenPool (#16335) (d93e4c5)
  • protocol: improve _authorizePause for Bridge (#16544) (f76c705)
  • protocol: remove the blob-reuse feature (#16439) (284447b)
  • protocol: risc0 verifier contract (#16331) (17abc18)
  • protocol: upgrade to use OZ 4.9.6 (#16360) (2a0fe95)
  • relayer: two-step bridge + watchdog + full merkle proof (#15669) (1039a96)

Bug Fixes

  • protocol: add address manager to taiko token (#16394) (c64ec19)
  • protocol: apply bug fixes and introduce a few new features (#16543) (37fa853)
  • protocol: fix a bug in changeBridgedToken (#16403) (42c279f)
  • protocol: fix bridge bug caused by incorrect check of receivedAt (by OZ) (#16545) (c879124)
  • protocol: fix bridge prove message issue using staticcall (#16404) (dd57560)
  • protocol: fix custom coinbase transferFrom issue (alternative) (#16327) (7423ffa)
  • protocol: make snapshot return value (#16436) (dcae54a)

This PR was generated with Release Please. See documentation.

@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--protocol branch 11 times, most recently from b0e4620 to 0433e65 Compare March 11, 2024 15:34
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--protocol branch 6 times, most recently from 16db133 to 39f3716 Compare March 14, 2024 07:51
@taiko-kitty taiko-kitty changed the title chore(main): release protocol 1.1.0 chore(main): release protocol 2.0.0 Mar 14, 2024
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--protocol branch from 39f3716 to c0e6954 Compare March 14, 2024 11:39
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--protocol branch 6 times, most recently from 5cbc239 to b5e991e Compare March 28, 2024 14:29
@taiko-kitty taiko-kitty force-pushed the release-please--branches--main--components--protocol branch from b5e991e to 50c8373 Compare March 29, 2024 01:20
@dantaik dantaik changed the title chore(main): release protocol 2.0.0 chore(main): release protocol 1.1.0 Mar 29, 2024
@dantaik dantaik closed this Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants