HanIdentity - Addendum

Contract `HanGovernor` inherits from some `openzeppelin` contracts which are related to governance design. One important point is that if a time lock was set, then the time lock could play as a governance role and execute some privileged functions. However, if the time lock wasn't set correctly, centralization issues may occur. ```solidity constructor( IVotes _token, TimelockController _timelock ) Governor("HanGovernor") GovernorSettings(1 /* 1 block */, 50400 /* 1 week */, 0) GovernorVotes(_token) GovernorVotesQuorumFraction(4) GovernorTimelockControl(_timelock) {} ``` **Privileged functions:** - relay(): Relays a transaction or function call to an arbitrary target. - setVotingDelay(): Update the voting delay. - setVotingPeriod(): Update the voting period. - setProposalThreshold(): Update the proposal threshold. - updateQuorumNumerator(): Changes the quorum numerator. - updateTimelock(): Public endpoint to update the underlying timelock instance. Any compromise to the time lock address may allow the hacker to take advantage of this authority and gain benefits by influencing governance functions.

All of the **HANeP** tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the anonymous deployer can distribute tokens without obtaining the consensus of the community. Any compromise to the deployer account that holds undistributed tokens may allow the attacker to steal and sell tokens on the market, resulting in severe damage to the project.

The function `release()` is used to releases tokens to payees based on the vesting schedule. According to the logic of the contract `TokenVestingLock.sol`, token distributors will send tokens to this contract directly, then anyone can execute the function `release()` to release tokens to payees. Since tokens are sent by distributors, it is best to determine if the current balance is sufficient, considering that the number of tokens sent to this contract may not be sufficient. ```solidity= token.transfer(payees[i].account, tokensToRelease); ```