Releases: ferrumnet/linear-release-engine
v1.10.0
Release Notes - Version 1.10.0
Overview
In this release, we have addressed and resolved the issues identified in the first audit report for the Ironvest Extended Version and its precheck phase. This marks a significant step in enhancing the security and stability of the platform.
Audit Report can be found here:
Ferrum Network 10 (IronVestExtended) (Sep 18, 2023)
Bug Fixes
- Fixed issues reported in the initial audit to ensure improved security and overall reliability.
What else Changed
- ironvest extended and precheck audit report fixex by @SibghatUllah1997 in #20
Full Changelog: v1.9.0...v1.10.0
v1.9.0
Release Notes - v1.9.0
Release Notes
Emergency Withdrawal Enhancement
- The emergencyWithdrawal function is now limited to withdrawing only allocated tokens.
IronVestAdminRequired Contract
- Introducing IronVestAdminRequired, which mirrors the audited IronVest contract.
- This release deploys the contract using the factory pattern, where the deployer's role can be customized by providing it as a parameter.
- The contract file and name are distinct from the audited version, enhancing separation.
IronVestDeployer Contract
- A new contract, IronVestDeployer, has been added to facilitate streamlined deployment.
- This contract is utilized for deploying both IronVestAdminRequired and the extended contract version.
IronVestExtended Contract
- Located in a separate directory, IronVestExtended.sol offers the ability to update beneficiary addresses.
- This contract inherits functionality from IronVestPreCheck.sol, which is a read-only contract.
- IronVestPreCheck.sol is deployed once and can be utilized multiple times to validate function preconditions.
Optimization Activation
- Deploying IronVestExtended.sol now requires activation of a 200-point optimization.
- This optimization enhances execution efficiency.
Additionally, a contract named IronVestPreCheck.sol exists, serving as a read-only contract that only needs to be deployed once. It validates preconditions for function execution.
These updates enhance the IronVest ecosystem's security, functionality, and deployment efficiency. Please refer to individual contract files for more details.
7:42
esy shai hai
What else Changed
IronVestAdminRequried
this is the same contract as our audited iron… by @SibghatUllah1997 in #18
Full Changelog: v1.1.0...v1.9.0
v1.1.0
What's Changed
- contract seperation, irvonVestDeployer and ironVestAdminRequired added by @SibghatUllah1997 in #16
- QA will commence by @AmirFerrum
Full Changelog: v1.0.0...v1.1.0
Architecture: @taha-abbasi
PM: @MaiwandSultan
v1.0.0
Iron Vest Audit Completed by Vidma and added to Repo
- The audit can be found here: Ferrum Network - IRONVEST - Audit by Vidma (Oct 24, 2022).pdf
- The documentation for the Linear Release Engine and Iron Vest has also been updated to reflect the Vidma Audit.
Auditor: @vidma-security
Architect: @taha-abbasi
Solidity Engineer: @SibghatUllah1997
Front-end Engineer: @talhaazeem19
Back-end Engineer: @zikriya
Project Manager: @MaiwandSultan
QA: @AmirFerrum
Full Changelog: v0.5.5...v1.0.0
v0.5.5
What's Changed
- Third Audit Report issues resolved by @SibghatUllah1997 in #15
Full Changelog: v0.5.4...v0.5.5
v0.5.4
What's Changed
- Minimum
cliffPercentage
removed by @SibghatUllah1997 in #14
This check was added at the request of the auditor, but it prohibits a core requirement of cliff vesting where an admin wants to setup vesting with a lock period, but not cliff tokens, instead they only want to release nonCliffTokens. For example 10% TGE (Released through airdrop not vesting), 3-month cliff (no cliff release), and 9-month linear vesting of 100% vesting tokens.
Full Changelog: v0.5.3...v0.5.4
v0.5.3
What's Changed
- Audit Issues Fixation by @SibghatUllah1997 in #13
- Modifier:
onlyAdmin
modifier changed toonlyOwner
. - Struct Variable Change: The
userNonCliffInfo
struct variablenonCliffVestingEndTime
was replaced withnonCliffVestingPeriod
. PreviouslynonCliffVestingEndTime
was being used by calculating the difference betweenvestingEndTime
andcliffVestingEndTime
. This resulted in accelerated vesting for non-cliff tokens which would end prematurely. This has been fixed by implementingnonCliffVestingPeriod
instead ofnonCliffVestingEndTime
.nonCliffVestingEndTime
is calculated by subtracting thecliffPeriodEndTime
fromvestingEndTime
.
Full Changelog: v0.5.2...v0.5.3
v0.5.2
What's Changed
- vestingPoolSize increment after event by @SibghatUllah1997 in #12
Full Changelog: v0.5.1...v0.5.2
v0.5.1
v0.5.0
What's Changed
- truffle project added and converted to upgradeable proxy by @SibghatUllah1997 in #10
Full Changelog: v0.4.0...v.0.5.0