GP 2: Upgrade Contracts to v1.0.0

The following changes were made as a result of the Security Audit conducted by ChainSecurity and published on January 5, 2023.

• GP #2

• Timestamp: Jan-10-2023 11:29:05 AM +UTC

• Tx: 0x755e2e240563b151e96b9bb52721e8361e1782697b092f32bb9fc23a8797cfb2

The transaction contained 6 actions described below.

1) BobToken contract upgrade

• BobToken contract 0xB0B195aEFA3650A6908f15CdaC7D92F8a5791B0B

• New implementation contract 0x525b4E120dDC602fF055Aa86803acD7D71F0c753.

The upgrade uses the upgradeToAndCall method (the selector is 0x4f1ef286) and is combined with the DOMAIN_SEPARATOR call (the selector is 0x3644e515). The method call is only used in tandem with Tenderly to check that the domain separator is not being changed from the old implementation to the new one during the upgrade.

2) BobVault contract upgrade

• BobVault contract 0x25E6505297b44f4817538fB2d91b88e1cF841B54)

• New implementation contract 0xd96587Eaa3CD5957EeC567df6BdF0B816792D125

Applied with the upgradeTo call (the selector is 0x3659cfe6).

3) zkBobPool contract upgrade

• zkBobPool contract 0x72e6B59D4a90ab232e55D4BB7ed2dD17494D62fB

• New implementation contract 0x4b8c0B14AA7CB5a7cFF3546415bBDCAcd7C75a2E

Applied with the upgradeTo call (the selector is 0x3659cfe6).

Note: the zkBobPool implementation contract introduces new events which are emitted when the pool parameters are being setup/changed. The next three actions are required to emit the events for the current set of parameters. These events can be displayed later through an analytics dashboard.