1 Poll Closing February 7, 2024
[Non-Constitutional]: Arbitrum Stable Treasury Endowment Program
Summary: This poll asks ARB holders whether they support the creation of a treasury diversification program, with an initial goal of diversifying 35,000,000 ARB into stable-value, yield bearing assets. This program would establish a screening committee to initiate an RFP, and then provide finalists to ARB holders for consideration. ARB holders would determine the final asset allocation (if any) through voting on these finalists.
Recommendation: Vote Yes. GFX Labs would be one of the screening committee members, and we fully support this proposal.
NB: GFX Labs would serve on the screening for this program
1 Poll Closing February 9, 2024
AIP: ArbOS Version 20 “Atlas”
Summary: This poll asks ARB holders whether they support an upgrade to support the anticipated Dencun Ethereum upgrade, allowing Arbitrum stack chains settling on Ethereum to post data as blobs or call data.
Recommendation: Vote Yes. Keeping Arbitrum up to date with the latest capabilities on Ethereum is a positive. We will caution, however, that we will not support this as executable code until audits have been completed and published. At the time of this Snapshot vote, they are still pending.
1 Poll Closing February 12, 2024
AIP: Batch Poster Manager and Sequencer Inbox Finality Fix
Summary: This poll asks ARB holders whether they support creating a batch posting manager. This would separate the addresses associated with this new role and the sequencer, which are currently shared. Bundled with this proposal is also a change to the futureBlocks value for the sequencer’s inbox. This proposal would raise the max block height from 12 to 64, which Offchain Labs states is in line with Ethereum’s security guarantees and less likely to result in valid batches reverting.
Recommendation: Vote Yes. The separation of batch posting address and sequencer address makes sense, and Offchain Labs’ argument is convincing that governance can still indirectly control the batch poster while the arrangement improves key rotation and other security options for the management of the role. Separately, the change to futureBlocks appears reasonable, as changing that one parameter alone doesn’t look like it will increase the ability of the sequencer to censor transactions.