Dolomite
Search
K
Comment on page

Transactions 38 - 50

Safe transactions numbered 38 through 50

Safe Transaction Logs

Transaction #38 - 2023-02-23

This transaction is enqueued behind DolomiteMargin's multisig time delay. The following actions may be effectuated after waiting 24 hours.

Transaction #39 - 2023-02-25

Transaction #40 - 2023-02-27

This transaction executes the queued transactions from Transaction #39 and Safe Transaction #40 since the 24-hour time delay has passed.

Transaction #42 - 2023-03-23

This transaction is enqueued behind DolomiteMargin's multisig time delay. The following actions may be effectuated after waiting 24 hours.
  • Changes the owner of DolomiteMargin from x to y (the PartiallyDelayedMultiSig is denoted in the Smart Contract Addresses section).
  • Tests that ownership transferred successfully by making a harmless call to ownerWithdrawUnsupportedTokens to pass 0.01 ARB to the original sender.

Transaction #44 - 2023-03-24

This transaction is enqueued behind DolomiteMargin's multisig time delay. The following actions may be effectuated after waiting 24 hours.
  • Transfers the 0.01 ARB from the PartiallyDelayedMultiSig to the original owner from Transaction #42. This is done to ensure ownership was passed to the right address, and the new owner has sufficient privileges to call ownerWithdrawUnsupportedTokens.
  • This transaction was canceled because the transfer of 0.01 ARB from the PartiallyDelayedMultiSig to the original owner was not needed.

Transaction #46 - 2023-03-25

This transaction executes the queued transactions from Transaction #42 and cancels Transaction #44.

Transaction #47 - 2023-04-04

This transaction is enqueued behind DolomiteMargin's multisig time delay. The following actions may be effectuated after waiting 24 hours.

Transaction #48 - 2023-04-04

This transaction is enqueued behind DolomiteMargin's multisig time delay. The following actions may be effectuated after waiting 24 hours.
  • Allows the multisig to bypass the time delay when calling GLPWrappedTokenUserVaultFactory::setUserVaultImplementation.
    • For the time being, we felt the need to bypass the time delay is necessary until vault contract has been live longer and is sufficiently battle-tested.