PR with Payload
Summary: Whitelist for veBAL voting [PAL-ETH on Arbitrum] (Balancer) The PAL/OHM gauge currently active on Arbitrum will be killed 4 weeks after this activation to give LPs sufficient time for migration to the new pool/gauge. See the previous proposal BIP-320 for further details.
References/Useful links:
https://twitter.com/Paladin_vote
Protocol Description:
Paladin is a governance lending protocol aiming to become the leading influence market and democratize activism.
Up to date, we have released a lending market for stkAave GHO discount, as well as a vote incentive marketplace for Balancer, Curve and Bunni and an index product for governance wars.
Motivation:
Paladin already has a tight history with Balancer. The PAL token was made transferable via an LBP on Balancer via Prime Launch . And a Balancer pool on mainnet has been there since PAL has been liquid. We are moving our PAL/OHM pool into a PAL/ETH in order to bring in more volume and better arbitrage on Ethereum.
Specifications:
- Governance: Paladin DAO is governed by holders of PAL, through snapshot votes and forum proposals.
Paladin DAO
https://signal.paladin.vote/#/ 1
- Oracles: None, we use Coingecko.
- Audits:
Audits - Docs 1 - Centralization vectors: Treasury functions and smart contract proxy updates are controlled through a 5/9 multisig.
- Market History: PAL was made transferable on Balancer via a dutch auction and now has liquidity on 3 DEXs on Ethereum (Balancer, Curve & Uniswap). PAL has a total depth of ~1M$.
Gauge: 0x1461C4a373d27977f0D343Ba33C22870c89F9dF0
Specifications:
A.
The Balancer Maxi LM Multisig eth:0xc38c5f97B34E175FFd35407fc91a937300E33860 will interact with the GaugeAdderv4 at 0x5DbAd78818D4c8958EfF2d5b95b28385A22113Cd and call the addGauge function with the following arguments:
gauge(address):0x1461C4a373d27977f0D343Ba33C22870c89F9dF0
gaugeType(string): Arbitrum
B. 4 weeks later:
The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptorEntrypoint at 0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA and call performAction using 0xab8f0945 for the data(bytes) argument and 0xd758454bdf4df7ad85f7538dc9742648ef8e6d0a will be used for the target(address) argument.