1. Vote-escrow governance
The implementation of this mechanism exactly mirrors that of Curve; as such, there exists a VotingEscrow contract whose create_lock, increaseUnlockTime, and increaseAmount are used for manipulating the locks, which can range from 1 week to 2 years, with the voting power scaling linearly. Once the lock expires, the funds can be withdrawn by invoking the VotingEscrow.withdraw method of the veALMANAK contract (should the user have more than one expired lock, this method would withdraw all of them). These are all the methods for maintaining one’s locks. Note that the maximal time differs from Curve's 4 years.
Addutionally, unlike Curve, ALMANAK possesses deployments of its veToken contract on all the chains ALMANAK is natively present at, eschewing the need to bridge onto mainnet in order to lock one's tokens.
2. Governance implementation [ASSUMES CURVELIKE - PLS CONFIRM]
Participation in governance is then assured on the Ethereum chain by interacting with a custom fork of the Aragon voting app. veALMANAK is linearly weighted by the remaining lock time, but also within each (weeklong) voting period: past the halfway point, the veALMANAK decays linearly to zero at the voting period endpoint; in this way, it becomes infeasible to sway the outcome of the vote with a last-minute vote injection (likewise, changing the vote is forbidden for the same reason).
Cross-chain governance is implemented how (question for the team)? I have seen committees in the whitepaper - is the governance done by electing committees? I have seen such models before.3. Vaults
As a portion of ALMANAK's functionality pertains to boosting users' weight in Vaults, we must mention that those follow a 4626-like model, namely, being ERC-7540 asynchronous 4626 vaults. The full scope of the implementation is out of the scope of this document; what is pertinent, however, is the mechanism of allocation. The ALMANAK emission contract what is the minter contract?? collects and stores the data on the short-term historic TVL and ROI of the vaults and compiles their weights; these weights are then adjusted by applying a governance-distributed total boost.
The distribution of emissions within the vault itself is proportional depending on the TVL contributed by the users; it is, however, also weighted.
TO VASILY: I'LL ADD OMITTED DETAILS ONCE I GET THE INFO IN BOLD - DON'T WORRY