Changelog

Changelog

15 June 2023

• Upgrade to ArkenDexV4 on Ethereum chain

14 March 2023

• Upgrade to ArkenDexV4 on BSC chain

3 March 2023

• Upgrade to ArkenDexV4 on Arbitrum chain

15 July 2022

• Add new feature SLAMM on BNB chain

17 May 2022

• Deploy on Fantom Network

4 April 2022

• Deploy on Rei Network

15 March 2022

• Deploy on Aurora Network

3 March 2022

• Update per CertiK & Inspex Audit

• Add Multi-signature as privileged roles

  • Executor & Admin of Timelock

  • Owner of ArkenDex for configuration variables control

24 January 2022

• Add Arbitrum contracts

• Upgrade to ArkenDexV3

  • TransparentUpgradeableProxy now direct at ArkenApprove

  • ArkenDexV3 is no longer behind a proxy

  • Remove EtherWrapper

15 November 2021

• Deploy on Avalanche Network

2 November 2021

• Fix ArkenDexV2 implementation solving the SafeERC20: approve from non-zero to non-zero allowance error

• TransparentUpgradeableProxy changed the implementation addresses as follow:

  • BSC

    • New Implementation: 0xA50caa60772c56A0c193D75708E3Cd09b1DcB218

    • Timelock Execute Transaction: https://bscscan.com/tx/0x151e23fc775e33d84f8d60166c616e3d3eb679f08f9400978d863c80729372e7

  • Polygon

    • New Implementation: 0x3A6c590a1f7cbd9851606A5e2D6F97059289216f

    • Timelock Execute Transaction: https://polygonscan.com/tx/0xa4dbd351e9dbf1f26e3cf761b02b4cb8098d960f34ebab27f920f3aef0d0862e

28 October 2021

• ArkenDexV2 implementation -- uses wrapped ether instead of the ether when trading.

• TransparentUpgradeableProxy changed the implementation addresses as follow:

  • BSC

    • New Implementation: 0x0446CbfFE16bF88ea35cd4b3DB24d66c18D0270b

    • Timelock Execute Transaction: https://bscscan.com/tx/0x5aee2254519c613293c6cb207e258e2107f81571bd216d99b4ed41d90d5b7c46

  • Polygon

    • New Implementation: 0xdc7d6737FAA38cEA99276421836f3a8da0818a64

    • Timelock Execute Transaction: https://polygonscan.com/tx/0x30bd5e09a50b9d373e510571e74c0e3ec3be48475f3cd21c5c0a352d56a3b203

• Deployed new smart contracts EtherWrapper to handle the transfer() proxy interaction issue.

  • BSC: 0xc2CbD2f01cAbDBeA25132ffF55cC001cC1944cb0

  • Polygon: 0xaDeE472407F127E575F5B80349C2380064659b9E

• More information about the issue can be found here: https://forum.openzeppelin.com/t/openzeppelin-upgradeable-contracts-affected-by-istanbul-hardfork/1616

• The team will monitor the new implementation on BSC and Polygon, and if no issue is found the Ethereum contracts will be updated.