13:["$","$L6c",null,{"protocol":"","showProposals":true,"combinedObjects":{"hottest":[{"id":37553,"title":"The Next 2 Years: DAO Resolution Pt.1","summary":"$6d","tldr":"This is a discussion about @Kash's draft vision and resolution for the Jupiter DAO, proposing a two-year transition to operational independence by May 1, 2027, with a $10 million USDC and 100 million JUP budget, and reforms to governance, funding, and utility for $JUP. With 124 replies, the community is actively debating the balance between team control and true decentralization, with overall positive sentiment but notable concerns about the pace of empowerment, clarity of benefits for JUP holders, and the proposal’s specifics.","lastPost":"2025-04-24T02:17:43.616Z","created":"2025-04-17T18:51:19.576Z","views":5066,"slug":"the-next-2-years-dao-resolution-pt-1","replies":48,"postCount":125,"likes":291,"score":3217.750729255771,"totalWordsAllPosts":18891,"totalWordsSummary":659,"updated":1745461559361,"protocol":"jupiter","discussionUrl":"https://www.jupresear.ch","author":{"username":"Kash","url":"https://www.jupresear.ch/u/Kash"},"relatedLinks":["https://docs.google.com/document/d/1CqAOYJASZSgspikmQPrw_ByZES0S3cYEYmppZlRQevk/edit?usp=sharing","https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1oEF2qvTw5pej7NSOPNrmAcIbgFWlm8sGcRa6qP43dig%2Fedit%3Fusp%3Dsharing&followup=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1oEF2qvTw5pej7NSOPNrmAcIbgFWlm8sGcRa6qP43dig%2Fedit%3Fusp%3Dsharing&ifkv=AXH0vVsR5fmlvEdVr8xT0jq1RZH67hXErGEDvS3SDx_f-NvLnqzT0vewer7FCqnRVrNOoW9F2TFJEg<mpl=docs&osid=1&passive=1209600&service=wise&flowName=GlifWebSignIn&flowEntry=ServiceLogin&dsh=S-1424016296%3A1745077"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Affecting Governance"],"localTags":["Jupiter DAO","Operational independence","JUP","Governance reform","Funding reform","Utility reform","Decentralization","Team control","JUP holders"],"headline":"Jupiter DAO Debates Draft Plan for Two-Year Transition to Independence with $10M USDC, 100M JUP Budget (124 replies)","type":"discussion"},{"id":23617,"title":"Long-term L1 execution layer proposal: replace the EVM with RISC-V","summary":"$6e","tldr":"This discussion is about @vbuterin's proposal to replace the EVM with RISC-V to improve ZK-EVM proving efficiency, simplify the execution layer, and leverage mature tooling, but it may introduce higher verification costs, compatibility challenges, and questions about long-term flexibility. With 65 replies, the community response is active and mixed, showing both strong support for the potential benefits and significant concerns about technical feasibility, verification complexity, and strategic alignment.","lastPost":"2025-04-24T02:08:47.539Z","created":"2025-04-20T11:20:02.654Z","views":17225,"slug":"long-term-l1-execution-layer-proposal-replace-the-evm-with-risc-v","replies":27,"postCount":63,"likes":142,"score":7632.110879424313,"totalWordsAllPosts":11530,"totalWordsSummary":899,"updated":1745461322683,"protocol":"ethereum","discussionUrl":"https://ethereum-magicians.org","author":{"username":"vbuterin","url":"https://ethereum-magicians.org/u/vbuterin"},"relatedLinks":["https://chatgpt.com/share/6804c9df-863c-8012-a202-93190c0a6770","https://chatgpt.com/share/6804c9e3-d024-8012-add1-b1b1182481a0","https://github.com/nervosnetwork/ckb-vm","https://x.com/__tinygrad__/status/1863898910387003694","https://chatgpt.com/share/6804ca03-d870-8012-b1b5-b8e65558c36d","https://chatgpt.com/share/6804ca10-0824-8012-bb7c-804a03f11fa0","https://github.com/ethereum/EIPs/pull/9580","https://ethereum-magicians.org/t/eip-7668-remove-bloom-filters/19447","https://ethresear.ch/t/delayed-execution-design-tradeoffs/21877","https://ethproofs.org/","https://x.com/dlubarov/status/1845862467315920940","https://github.com/ethereum/EIPs/pull/9257","https://eips.ethereum.org/EIPS/eip-4444","https://github.com/paritytech/revive","https://www.paradigm.xyz/2024/04/reth-perf","https://github.com/cartesi/machine-emulator","https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-118.pdf","https://t.co/81cTBNeNAb","https://github.com/ethereum/EIPs/pull/9687","https://github.com/ethereum/solidity/issues/10381","https://github.com/NomicFoundation/hardhat-vscode/issues/522"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change","Newsworthy - Controversial","Newsworthy - Technical"],"localTags":["EVM replacement","RISC-V","ZK-EVM","Execution layer","Verification costs","Compatibility challenges","Long-term flexibility"],"headline":"Vitalik Buterin Proposes Replacing Ethereum EVM with RISC-V to Enhance ZK-EVM Efficiency; Community Debates Trade-offs (65 replies)","type":"discussion"},{"id":4881,"title":"Updated MEV-Boost relay settings","summary":"$6f","tldr":"This discussion is about new BuilderNet MEV-Boost relay submission guidelines designed to improve relay performance, independence, and transparency, with benefits including faster bundle processing and reduced conflicts of interest, but with concerns about potential centralization if only a few relays meet the strict criteria. With 7 replies, community reaction is mixed: some support the changes, while others worry about centralization, conflicts of interest, and seek clearer definitions and transparency.","lastPost":"2025-04-23T22:04:20.722Z","created":"2025-04-14T22:31:56.940Z","views":153,"slug":"updated-mev-boost-relay-settings","replies":3,"postCount":8,"likes":9,"score":3113.9011684964707,"totalWordsAllPosts":2334,"totalWordsSummary":479,"updated":1745461333211,"protocol":"flashbots","discussionUrl":"https://collective.flashbots.net","author":{"username":"shea","url":"https://collective.flashbots.net/u/shea"},"relatedLinks":["https://collective.flashbots.net/t/the-mev-letter-83/4885","https://collective.flashbots.net/t/tee-boost/3741","https://docs.titanrelay.xyz/builders/builder-integration#websocket-topbid-stream"],"globalTags":["Changes - Technical Change","Newsworthy - Controversial"],"localTags":["BuilderNet","MEV-Boost relay","Relay submission guidelines","Relay performance","Relay independence","Relay transparency","Bundle processing","Centralization risk"],"headline":"Flashbots Proposes New BuilderNet MEV-Boost Relay Guidelines to Enhance Performance and Transparency","type":"discussion"},{"id":21830,"title":"[ARFC] ACI Phase IV – \"Road to 80\"","summary":"$70","tldr":"The proposal seeks to renew and expand ACI’s mandate as Aave DAO’s Growth and Governance Coordination provider for 12 months with a 3M aEthLidoGHO budget, aiming for 80% market share in active DeFi loans and broader strategic initiatives, while clarifying ACI’s non-involvement in core protocol development. Community reaction is strongly supportive with some questions about the increased budget and mandate scope, and voting on the proposal is currently open as of the latest update.","lastPost":"2025-04-23T16:24:53.358Z","created":"2025-04-16T20:22:07.273Z","views":293,"slug":"arfc-aci-phase-iv-road-to-80","replies":0,"postCount":10,"likes":47,"score":3287.993853475154,"totalWordsAllPosts":1177,"totalWordsSummary":405,"updated":1745430325249,"protocol":"aave","discussionUrl":"https://governance.aave.com","author":{"username":"MarcZeller","url":"https://governance.aave.com/u/MarcZeller"},"relatedLinks":["https://governance.aave.com/t/aci-retrospective-2024-present/21825","https://snapshot.box/#/s:aavedao.eth/proposal/0x7bfe8ade2b8835f30655ca9b908e921ef89ba5061d8d6a64b422dc3643d83c14"],"globalTags":["Proposal - Currently voting"],"localTags":["ACI","Aave DAO","Growth and Governance Coordination","aEthLidoGHO","DeFi loans","Mandate renewal","Budget increase"],"headline":"Aave DAO Considers Renewing and Expanding ACI’s Growth Mandate with 3M aEthLidoGHO Budget","type":"discussion"},{"id":23459,"title":"A maximally simple L1 privacy roadmap","summary":"$71","tldr":"This discussion reviews @vbuterin's proposed roadmap for enhancing privacy on Ethereum L1 by integrating privacy tools into wallets, defaulting to shielded balances, and breaking cross-app activity links, while also considering technical and usability tradeoffs such as impacts on ENS and identity systems. With 38 replies, the community is actively debating the practicality, technical solutions, and broader implications, suggesting alternatives and highlighting projects like Cartesi, but no concrete next steps have been set.","lastPost":"2025-04-23T12:13:09.352Z","created":"2025-04-11T01:29:18.131Z","views":8650,"slug":"a-maximally-simple-l1-privacy-roadmap","replies":12,"postCount":40,"likes":53,"score":5550.476958814828,"totalWordsAllPosts":4419,"totalWordsSummary":590,"updated":1745415130459,"protocol":"ethereum","discussionUrl":"https://ethereum-magicians.org","author":{"username":"vbuterin","url":"https://ethereum-magicians.org/u/vbuterin"},"relatedLinks":["https://ethresear.ch/t/ethereum-privacy-the-road-to-self-sovereignty/22115","https://www.railway.xyz/","https://ethresear.ch/t/fork-choice-enforced-inclusion-lists-focil-a-simple-committee-based-inclusion-list-proposal/19870","https://privacypools.com/","https://eips.ethereum.org/EIPS/eip-7701","https://www.1rpc.io/ecosystem/automata","https://vitalik.eth.limo/general/2023/06/09/three_transitions.html","https://kyledenhartog.com/recreating-web3-cross-origin-tracking/","https://warpcast.com/geoffgolberg/0xee3cbbea","https://x.com/SCBuergel/status/1798031499318706484","https://datatracker.ietf.org/doc/rfc9458/","https://warpcast.com/nonlinear.eth/0x7763a1e8","https://en.wikipedia.org/wiki/Halo_effect","https://x.com/MacBudkowski/status/1863951819296153623","https://www.trueblocks.io/","https://codeberg.org/konkret/konkret-wallet"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Technical"],"localTags":["Ethereum L1 privacy","Privacy tools","Shielded balances","Cross-app activity links","ENS","Identity systems","Cartesi"],"headline":"Vitalik Buterin Proposes Roadmap for Privacy Enhancements on Ethereum L1; Community Debates Tradeoffs and Solutions","type":"discussion"},{"id":22115,"title":"Ethereum Privacy: The Road to Self-Sovereignty","summary":"$72","tldr":"The discussion is about a proposal to make privacy the default at the Ethereum protocol level, aiming to guarantee user self-sovereignty and credible neutrality, but raising concerns about technical complexity, regulatory compliance, and user experience. With 11 replies, the community shows active but mixed reactions, supporting the goal while emphasizing the need for selective disclosure, dissociation tools, and collaboration with existing privacy projects, and highlighting challenges in implementation and adoption.","lastPost":"2025-04-23T10:12:25.337Z","created":"2025-04-09T11:29:49.260Z","views":1530,"slug":"ethereum-privacy-the-road-to-self-sovereignty","replies":3,"postCount":11,"likes":43,"score":3106.281447873527,"totalWordsAllPosts":2982,"totalWordsSummary":382,"updated":1745415081009,"protocol":"ethereum","discussionUrl":"https://ethresear.ch","author":{"username":"pcaversaccio","url":"https://ethresear.ch/u/pcaversaccio"},"relatedLinks":["https://hackmd.io/@pcaversaccio/ethereum-privacy-the-road-to-self-sovereignty","https://ethereum-magicians.org/t/a-maximally-simple-l1-privacy-roadmap/23459","https://x.com/search?lang=en&q=dissociation%20(from%3Aameensol)","https://proofofinnocence.com/","https://x.com/delete_shitcoin/status/1521461832266956803"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change","Changes - Compliance","Newsworthy - Controversial"],"localTags":["Privacy by Default","Ethereum protocol privacy","Selective disclosure","Dissociation tools","Privacy projects collaboration"],"headline":"Proposal to Make Privacy Default in Ethereum Raises Technical and Regulatory Concerns","type":"discussion"},{"id":2967,"title":"CIP-draft : Moving from batch auction to the fair combinatorial auction","summary":"$73","tldr":"This discussion is about CIP-38, a proposal to upgrade CoW Protocol’s auction mechanism from batch to fair combinatorial auctions, aiming to increase order throughput, solver rewards, and fairness for traders, while removing the Uniform Clearing Price constraint to improve batching efficiency at the cost of reduced protection against atomic arbitrage trading. The change, scheduled for testing on May 6th, 2025 and full rollout around May 20th, 2025, has received generally supportive community feedback with some concerns about increased complexity, maintainability, and the implications of removing the UCP constraint.","lastPost":"2025-04-23T08:09:26.280Z","created":"2025-04-17T11:58:24.954Z","views":209,"slug":"cip-draft-moving-from-batch-auction-to-the-fair-combinatorial-auction","replies":4,"postCount":11,"likes":16,"score":3183.7344726113092,"totalWordsAllPosts":4772,"totalWordsSummary":598,"updated":1745399741536,"protocol":"cowdao","discussionUrl":"https://forum.cow.fi","author":{"username":"felixhenneke","url":"https://forum.cow.fi/u/felixhenneke"},"relatedLinks":["https://arxiv.org/abs/2408.12225","https://github.com/fhenneke/comb_auctions","https://forum.cow.fi/t/research-beyond-batch-auctions/2543","https://forum.cow.fi/t/combinatorial-auctions-from-theory-to-practice-via-some-more-theory-about-rewards/2877","https://docs.cow.fi/cow-protocol/reference/core/auctions/ebbo-rules","https://github.com/cowprotocol/Auction-simulation","https://forum.cow.fi/t/cip-38-solver-computed-fees-rank-by-surplus/2061","https://snapshot.box/#/s:cow.eth/proposal/0xfb81daea9be89f4f1c251d53fd9d1481129b97c6f38caaddc42af7f3ce5a52ec"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change","Newsworthy - Technical"],"localTags":["CIP-38","CoW Protocol","Combinatorial auctions","Uniform Clearing Price","UCP constraint","Batching efficiency","Atomic arbitrage trading"],"headline":"CIP-38: CoW Protocol Proposes Shift to Fair Combinatorial Auctions, Removing UCP Constraint","type":"discussion"},{"id":603,"title":"PIP-XX: Restructuring Paladin - Migration","summary":"$74","tldr":"The proposal suggests migrating Paladin DAO from the PAL token to a new token (NEWTOKEN) over a two-year period, aiming to unify value, streamline governance, and leverage the Rings protocol, with deployment options on Sonic or Ethereum and a total supply of 20,000,000 NEWTOKEN. While the migration could reduce fees and increase DAO revenue, it introduces complexity and development costs (40,000 EUR), and community feedback (8 replies) is mostly supportive but includes concerns about forced vesting, slashing, and added complexity.","lastPost":"2025-04-22T23:59:57.590Z","created":"2025-04-11T16:35:50.975Z","views":192,"slug":"pip-xx-restructuring-paladin-migration","replies":2,"postCount":9,"likes":6,"score":3343.5053957296514,"totalWordsAllPosts":1284,"totalWordsSummary":376,"updated":1745376737537,"protocol":"paladin","discussionUrl":"https://gov.paladin.vote","author":{"username":"Figue","url":"https://gov.paladin.vote/u/Figue"},"relatedLinks":["https://snapshot.box/#/s:pip.palvote.eth/proposal/0x7c43fa6b3e07f09b5e54358ed0f940196fa3607a861468408a98c91334cdfd77"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change","Newsworthy - Token Launch","Newsworthy - Affecting Governance"],"localTags":["Paladin DAO","PAL token","NEWTOKEN","Token migration","Rings protocol","Sonic","Ethereum deployment","Forced vesting","Slashing","DAO revenue"],"headline":"Paladin DAO Proposes Two-Year Migration from PAL to NEWTOKEN, Aiming to Streamline Governance and Leverage Rings Protocol","type":"discussion"},{"id":28962,"title":"A Vision for the Future of Arbitrum","summary":"$75","tldr":"ArbitrumDAO is considering a proposal to streamline operations by empowering a set of Arbitrum Aligned Entities (AAEs) to handle most strategic and operational decisions, aiming to boost efficiency but raising concerns about centralization and reduced delegate power. With 30 replies, the community is actively debating the trade-offs, showing both strong support for efficiency gains and significant worries about governance safeguards and accountability.","lastPost":"2025-04-21T14:42:35.697Z","created":"2025-04-09T06:00:20.372Z","views":2022,"slug":"a-vision-for-the-future-of-arbitrum","replies":2,"postCount":30,"likes":133,"score":4670.684121045354,"totalWordsAllPosts":12092,"totalWordsSummary":432,"updated":1745376672891,"protocol":"arbitrum","discussionUrl":"https://forum.arbitrum.foundation","author":{"username":"Arbitrum","url":"https://forum.arbitrum.foundation/u/Arbitrum"},"relatedLinks":["https://drive.google.com/file/d/1EXbtOGijrVBJnX1xn-bmOH5Q_x3OuvyN/view?usp=drivesdk","https://x.com/PinkBrains_io/status/1911732145376415929","https://x.com/AragonProject/status/1907451862917468625","https://x.com/lurenbian/status/1796333187288940957","https://forum.arbitrum.foundation/t/sos-submission-seedgov-strategic-objectives/28975","https://meet.google.com/sek-faiv-fgp","https://www.crunchbase.com/organization/offchain-labs","https://docs.arbitrum.foundation/dao-constitution","https://forum.arbitrum.foundation/t/sos-submission-max-lomu-strategic-objectives/28902/3","https://forum.arbitrum.foundation/t/sos-submission-entropy-advisors-strategic-objectives/28976"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Controversial","Newsworthy - Affecting Governance"],"localTags":["ArbitrumDAO","Arbitrum Aligned Entities","AAEs","Centralization concerns","Delegate power","Governance safeguards","Accountability"],"headline":"ArbitrumDAO debates proposal to grant strategic control to Aligned Entities, raising efficiency vs. centralization concerns","type":"discussion"},{"id":"0xe04a281294cc6aff175463cd8c61838512f1d55fd7b95efa323e71c74125d818","title":"PizzaDAO x Aavegotchi 2025 (UPDATED)","summary":"$76","tldr":"Aavegotchi DAO is considering sponsoring PizzaDAO’s Global Pizza Party on May 22, 2025, for either $6,000 or $10,000, in exchange for brand integration and onboarding at global events to boost visibility and community growth. Most voters so far support the $10,000 option, but the proposal has not yet reached the required quorum.","protocol":"aavegotchi","slug":"pizzadao-x-aavegotchi-2025-updated","snapshotUrl":"https://snapshot.box/#/s:aavegotchi.eth/proposal/0xe04a281294cc6aff175463cd8c61838512f1d55fd7b95efa323e71c74125d818","startDate":1745151926,"endDate":1745756640,"updated":1745441719,"relatedLinks":["https://app.ens.domains/dreadpizzaroberts.eth","https://opensea.io/item/matic/0x86935f11c86623dec8a25696e1c19a8659cbf95d/542","https://discord.com/channels/732491344970383370/1307288564458852384","https://opensea.io/item/matic/0x86935f11c86623dec8a25696e1c19a8659cbf95d/5421","https://docs.google.com/presentation/d/1Oycsq4YBOmyursmVCkr-6auI5bMnXOnb-KumDjWBWiU/edit?slide=id.g346aa5b3e98_0_105#slide=id.g346aa5b3e98_0_105","https://s3.amazonaws.com/charm.public/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/bfceae58-3fc9-4518-8c1a-9fdde90d8518/77e4fb7e-9d54-4102-97dd-97b1fbddff20.png","https://s3.amazonaws.com/charm.public/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/b473ab94-93f4-4dbe-a5ac-3bd4779d87a2/8b4e99f1-1af7-4423-a4e1-98c3d88ee6ad.png","https://stream.mux.com/r0102rWWVYRmMSApW7pMRzWOwFXM1xKljs401iaxyOCIts","https://x.com/GoobzGG/status/1806837269359403117","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/8fbac2a5-e0a1-4477-9e43-3b4d5dd584f5/pizzaavegotchi.webp","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/4d49a009-661e-49c4-9c11-3e988550b63f/merch.jpeg","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/1949954d-38b5-4cca-8292-06bcf54b8fbc/pizzaday2024.jpeg","https://x.com/Pizza_DAO/status/1869133689818619981","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/6e54ec34-4346-4f1e-9873-d2adf8d36385/art_basel_pizzadao.webp","https://x.com/Pizza_DAO/status/1778891140877434962","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/ad2dc1c9-65ac-4eb2-a461-51bfbfb363bb/pizza_bazaar_nyc.webp","https://x.com/Pizza_DAO/status/1902085732875039074","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/17f86e13-8573-435f-b911-e05e035822e2/GkRIY6PW0AAO26E.webp","https://www.globalpizzaparty.xyz/","https://www.instagram.com/pizza_dao/","https://x.com/Pizza_DAO","https://discord.com/invite/Bqv4AaVebK","https://www.facebook.com/thepizzadao","https://www.rarepizzas.com/mint","https://opensea.io/collection/rare-pizzas-box","https://oncyber.io/pizzadao","https://pizzadao.github.io/moltobennydelivery/","https://treasury.pizzadao.xyz","https://docs.google.com/spreadsheets/d/1vBdETWF_PjdVZioOuXXjKxz4kQK0rv5OXHIrG3Ple7o/edit?gid=0#gid=0","https://snapshot.box/#/s:aavegotchi.eth/proposal/0xe04a281294cc6aff175463cd8c61838512f1d55fd7b95efa323e71c74125d818"],"state":"active","results":{"quorum":9000000,"totalScores":"2785443.39","totalVotes":143,"choices":[{"id":0,"name":"Huumble Pizza Party","scores":"461426.09"},{"id":1,"name":"Spaacious Pizza Party","scores":"1517574.28"},{"id":2,"name":"No Partnership","scores":"251124.78"},{"id":3,"name":"Abstain","scores":"555318.25"}]},"decayedScore":0,"score":3620.1826700477327,"isFlagged":false,"globalTags":["Proposal - Currently voting","Grants - Grant Funding","Event - IRL"],"localTags":["PizzaDAO","Global Pizza Party","Brand integration","Onboarding","Community growth","Quorum"],"headline":"Aavegotchi DAO Weighs $10K Sponsorship of PizzaDAO’s 2025 Global Pizza Party for Brand Integration","type":"snapshot"},{"currentStatus":"started","currentStatusSinceTx":"0x3e0b1b6082d6d050d8a83b66e0e566579d9100dd7c48b224d55266c5d649417f","metadata":"ipfs:bafkreidyg7mws4tn33ce7klgmge2gcqnvqitt2i5apaxaanu7ah4ucneae","votingStartBlock":22246476,"ipfsData":"Update StableswapNG parameters for pool 0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F with: amplification factor from 500 -> 1000 ramped over 1 weeks starting on 2025-04-18 15:03:59+0000 and ending on 2025-04-25 15:03:59+0000.","proposer":"0xDAa094A0Ed166FeDF8a0a4310f3F74a1e96F9195","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreidyg7mws4tn33ce7klgmge2gcqnvqitt2i5apaxaanu7ah4ucneae","votingEndTime":1744988663,"votingStartTime":1744383863,"id":"1026","cid":"bafkreidyg7mws4tn33ce7klgmge2gcqnvqitt2i5apaxaanu7ah4ucneae","summary":"## What is this about?\n\nThis proposal suggests updating the parameters for the StableswapNG pool identified by the address `0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F`. Specifically, it involves increasing the amplification factor from 500 to 1000. This change is planned to be gradually implemented over a one-week period, starting on April 18, 2025, and concluding on April 25, 2025.\n\n## What could be the impact of this?\n\nIncreasing the amplification factor in a stableswap pool can enhance the pool's efficiency in maintaining stable prices, especially during large trades. This adjustment could lead to improved liquidity and reduced slippage for users, potentially making the pool more attractive for trading stable assets.","globalTags":["Changes - Technical Change"],"searchKeywords":["Proposal","StableswapNG pool","0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F","Amplification factor","500 to 1000","April 18, 2025","April 25, 2025","Efficiency","Stable prices","Large trades","Liquidity","Reduced slippage","Stable assets"],"localTags":["StableswapNG","Amplification Factor"],"totalVotersFor":3,"totalWeightFor":1.460855014882518e+26,"totalVotersAgainst":4,"totalVoters":7,"totalWeight":5.3339050283731235e+26,"totalWeightAgainst":3.8730500134906046e+26,"score":3642.008010825275,"proposalResults":"## How is the community reacting?\n\n- The proposal has attracted a total of 7 voters, representing a combined voting weight of 533,390,502.84.\n- 3 voters (146,085,501.49 weight, or 27.40%) supported the proposal.\n- 4 voters (387,305,001.35 weight, or 72.60%) opposed the proposal.\n- The majority of voting weight is against the proposal, indicating that the community sentiment is predominantly negative.","tldr":"A proposal to increase the amplification factor of the StableswapNG pool at address 0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F from 500 to 1000 between April 18, 2025 and April 25, 2025 aims to improve price stability and reduce slippage. However, the majority of the community voting weight (72.60%) is against the proposal.","headline":"Proposal to double Curve StableswapNG pool amplification factor from 500 to 1000 over one week","updated":1744769777,"timestamp":{"_seconds":1744769780,"_nanoseconds":515000000},"decayedScore":3523.3613349049956,"type":"onchain","governor":"ownershipGovernance","protocol":"curve"}],"latest":[{"id":37553,"title":"The Next 2 Years: DAO Resolution Pt.1","summary":"$77","tldr":"This is a discussion about @Kash's draft vision and resolution for the Jupiter DAO, proposing a two-year transition to operational independence by May 1, 2027, with a $10 million USDC and 100 million JUP budget, and reforms to governance, funding, and utility for $JUP. With 124 replies, the community is actively debating the balance between team control and true decentralization, with overall positive sentiment but notable concerns about the pace of empowerment, clarity of benefits for JUP holders, and the proposal’s specifics.","lastPost":"2025-04-24T02:17:43.616Z","created":"2025-04-17T18:51:19.576Z","views":5066,"slug":"the-next-2-years-dao-resolution-pt-1","replies":48,"postCount":125,"likes":291,"score":3217.750729255771,"totalWordsAllPosts":18891,"totalWordsSummary":659,"updated":1745461559361,"protocol":"jupiter","discussionUrl":"https://www.jupresear.ch","author":{"username":"Kash","url":"https://www.jupresear.ch/u/Kash"},"relatedLinks":["https://docs.google.com/document/d/1CqAOYJASZSgspikmQPrw_ByZES0S3cYEYmppZlRQevk/edit?usp=sharing","https://accounts.google.com/v3/signin/identifier?continue=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1oEF2qvTw5pej7NSOPNrmAcIbgFWlm8sGcRa6qP43dig%2Fedit%3Fusp%3Dsharing&followup=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1oEF2qvTw5pej7NSOPNrmAcIbgFWlm8sGcRa6qP43dig%2Fedit%3Fusp%3Dsharing&ifkv=AXH0vVsR5fmlvEdVr8xT0jq1RZH67hXErGEDvS3SDx_f-NvLnqzT0vewer7FCqnRVrNOoW9F2TFJEg<mpl=docs&osid=1&passive=1209600&service=wise&flowName=GlifWebSignIn&flowEntry=ServiceLogin&dsh=S-1424016296%3A1745077"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Affecting Governance"],"localTags":["Jupiter DAO","Operational independence","JUP","Governance reform","Funding reform","Utility reform","Decentralization","Team control","JUP holders"],"headline":"Jupiter DAO Debates Draft Plan for Two-Year Transition to Independence with $10M USDC, 100M JUP Budget (124 replies)","type":"discussion"},{"id":23617,"title":"Long-term L1 execution layer proposal: replace the EVM with RISC-V","summary":"$78","tldr":"This discussion is about @vbuterin's proposal to replace the EVM with RISC-V to improve ZK-EVM proving efficiency, simplify the execution layer, and leverage mature tooling, but it may introduce higher verification costs, compatibility challenges, and questions about long-term flexibility. With 65 replies, the community response is active and mixed, showing both strong support for the potential benefits and significant concerns about technical feasibility, verification complexity, and strategic alignment.","lastPost":"2025-04-24T02:08:47.539Z","created":"2025-04-20T11:20:02.654Z","views":17225,"slug":"long-term-l1-execution-layer-proposal-replace-the-evm-with-risc-v","replies":27,"postCount":63,"likes":142,"score":7632.110879424313,"totalWordsAllPosts":11530,"totalWordsSummary":899,"updated":1745461322683,"protocol":"ethereum","discussionUrl":"https://ethereum-magicians.org","author":{"username":"vbuterin","url":"https://ethereum-magicians.org/u/vbuterin"},"relatedLinks":["https://chatgpt.com/share/6804c9df-863c-8012-a202-93190c0a6770","https://chatgpt.com/share/6804c9e3-d024-8012-add1-b1b1182481a0","https://github.com/nervosnetwork/ckb-vm","https://x.com/__tinygrad__/status/1863898910387003694","https://chatgpt.com/share/6804ca03-d870-8012-b1b5-b8e65558c36d","https://chatgpt.com/share/6804ca10-0824-8012-bb7c-804a03f11fa0","https://github.com/ethereum/EIPs/pull/9580","https://ethereum-magicians.org/t/eip-7668-remove-bloom-filters/19447","https://ethresear.ch/t/delayed-execution-design-tradeoffs/21877","https://ethproofs.org/","https://x.com/dlubarov/status/1845862467315920940","https://github.com/ethereum/EIPs/pull/9257","https://eips.ethereum.org/EIPS/eip-4444","https://github.com/paritytech/revive","https://www.paradigm.xyz/2024/04/reth-perf","https://github.com/cartesi/machine-emulator","https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-118.pdf","https://t.co/81cTBNeNAb","https://github.com/ethereum/EIPs/pull/9687","https://github.com/ethereum/solidity/issues/10381","https://github.com/NomicFoundation/hardhat-vscode/issues/522"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change","Newsworthy - Controversial","Newsworthy - Technical"],"localTags":["EVM replacement","RISC-V","ZK-EVM","Execution layer","Verification costs","Compatibility challenges","Long-term flexibility"],"headline":"Vitalik Buterin Proposes Replacing Ethereum EVM with RISC-V to Enhance ZK-EVM Efficiency; Community Debates Trade-offs (65 replies)","type":"discussion"},{"id":3698,"title":"[FIP - 4XX] Preparation for frxUSD Payment Stablecoin Charter Compliance","summary":"$79","tldr":"This discussion is about a proposal to restructure FRAX stablecoins and operations to comply with upcoming U.S. payment stablecoin regulations, including separating balance sheets, ending guaranteed 1:1 migration between Legacy FRAX Dollar and frxUSD, and formalizing new governance and yield strategies. The benefits include improved regulatory compliance and operational clarity, while costs involve reduced user flexibility; community reaction is limited but includes questions about technical details, user experience, and concerns over migration and liquidity.","lastPost":"2025-04-24T01:46:31.048Z","created":"2025-04-21T16:56:03.774Z","views":131,"slug":"fip-4xx-preparation-for-frxusd-payment-stablecoin-charter-compliance","replies":0,"postCount":7,"likes":6,"score":2361.970309412744,"totalWordsAllPosts":1513,"totalWordsSummary":498,"updated":1745461332736,"protocol":"frax","discussionUrl":"https://gov.frax.finance","author":{"username":"amirnader","url":"https://gov.frax.finance/u/amirnader"},"relatedLinks":["https://gov.frax.finance/t/fip-419-launch-frax-usd-provide-upgrade-path-to-frax-stablecoin/3543"],"globalTags":["Proposal - Seeking feedback","Changes - Compliance","Newsworthy - Regulation"],"localTags":["FRAX","Stablecoin Restructuring","frxUSD","Legacy FRAX Dollar","Governance Strategies","Yield Strategies","Migration Process","Liquidity Concerns"],"headline":"Frax Proposes Restructuring Stablecoins to Meet Upcoming U.S. Regulations","type":"discussion"},{"id":"937","number":"937","title":"Update faq.mdx","description":"Added unichain, Added historical & price questions, cleaned up a few parts. Should pass formatting check now.","summary":"$7a","tldr":"This update to the graphprotocol/docs `faq.mdx` file adds detailed guidance on API authentication, token price retrieval, historical balances, supported networks, and pagination, ensuring users have accurate and up-to-date information for effective API usage. The changes clarify procedures, expand network support, and set a pagination limit, with no mention of costs or community reaction.","created":"2025-04-23T22:23:21Z","updated":"2025-04-24T01:41:07Z","merged":null,"sha":"83146a9254efa8327a4211a24c159447bc9a90ba","link":"https://github.com/graphprotocol/docs/pull/937","state":"open","commits":5,"additions":18,"deletions":10,"changedFiles":1,"score":154.00365995148192,"owner":"graphprotocol","repo":"docs","protocol":"thegraph","headline":"The Graph docs updated with expanded API guidance, network support, and pagination limits","type":"pr"},{"id":29054,"title":"Overview of overlapping ideas in SOS submissions","summary":"$7b","tldr":"This discussion summarizes overlapping themes from SOS matrix submissions for Arbitrum, focusing on institutional onboarding, user acquisition, DAO operational efficiency, DeFi prioritization, builder support, ARB token value, and verticals like AI, Social, and DePIN, with community members analyzing objective overlaps, questioning the lack of direct protocol outreach, and debating governance and feedback processes. With 12 replies, the community reaction is engaged but not exhaustive, highlighting the need for more actionable, data-driven objectives and improved stakeholder engagement, while no specific next actions have been set.","lastPost":"2025-04-24T00:55:25.383Z","created":"2025-04-17T16:31:01.751Z","views":146,"slug":"overview-of-overlapping-ideas-in-sos-submissions","replies":6,"postCount":13,"likes":22,"score":1113.332617541918,"totalWordsAllPosts":3219,"totalWordsSummary":1535,"updated":1745461186404,"protocol":"arbitrum","discussionUrl":"https://forum.arbitrum.foundation","author":{"username":"TempeTechie","url":"https://forum.arbitrum.foundation/u/TempeTechie"},"relatedLinks":["https://forum.arbitrum.foundation/t/sos-submission-max-lomu-strategic-objectives/28902","https://docs.google.com/spreadsheets/d/1hfDPLMPmDh29DQScrLQByRNiUncejlsa8twO8i8FlQE/edit?usp=sharing","https://forum.arbitrum.foundation/t/sos-submission-entropy-advisors-strategic-objectives/28976","https://forum.arbitrum.foundation/t/sos-submission-gabriel-strategic-objectives/28981","https://forum.arbitrum.foundation/t/sos-submission-tnorm-strategic-objectives/28977","https://rndadocs.notion.site/SimScore-API-What-is-it-1ba786e9377980bfbc28efffda47e3c4?pvs=4"],"globalTags":["Changes - Community Improvement","Proposal - Seeking feedback","Newsworthy - Affecting Governance"],"localTags":["SOS matrix","Institutional onboarding","User acquisition","DAO operational efficiency","DeFi prioritization","Builder support","ARB token value","AI vertical","Social vertical","DePIN vertical","Objective overlaps","Protocol outreach","Governance process","Feedback process","Stakeholder engagement"],"headline":"Arbitrum SOS Matrix Discussion Highlights Need for Clearer Objectives and Stakeholder Engagement","type":"discussion"},{"id":10593,"title":"Ramp A on all PegKeeper Pools from 500 to 2000 over 1 week","summary":"$7c","tldr":"This is about a proposal to increase the A parameter from 500 to 2000 for all Curve PegKeeper pools to enhance crvUSD peg stability and arbitrage activity, with simulations indicating it is safe and unlikely to harm liquidity depth. There are no reported community reactions or determined next actions, and the DAO is advised to monitor PegKeeper reserves and crvUSD mint rates.","lastPost":"2025-04-24T00:23:10.540Z","created":"2025-04-24T00:23:10.451Z","views":46,"slug":"ramp-a-on-all-pegkeeper-pools-from-500-to-2000-over-1-week","replies":0,"postCount":1,"likes":0,"score":632.5112556278139,"totalWordsAllPosts":469,"totalWordsSummary":296,"updated":1745461276237,"protocol":"curve","discussionUrl":"https://gov.curve.fi","author":{"username":"LlamaRisk","url":"https://gov.curve.fi/u/LlamaRisk"},"relatedLinks":[],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change"],"localTags":["Curve PegKeeper","A parameter","crvUSD peg stability","PegKeeper reserves","crvUSD mint rates"],"headline":"Proposal to Raise A Parameter in Curve PegKeeper Pools to Improve crvUSD Peg Stability","type":"discussion"},{"id":"916","number":"916","title":"fix(cache): automated cache update - updated addresses","description":"Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action","summary":"$7d","tldr":"This update adds `STATA_TOKEN` to the Aave V3 Ethereum configuration by defining its address in both Solidity and Typescript files, ensuring accurate asset representation and easier integration for developers. There are no mentioned costs, and the main benefit is improved protocol accuracy and developer experience.","created":"2025-04-24T00:15:15Z","updated":"2025-04-24T00:16:16Z","merged":null,"sha":"1c063e11e965b0ed00f6862557bdd90423cabe73","link":"https://github.com/bgd-labs/aave-address-book/pull/916","state":"open","commits":1,"additions":21,"deletions":2,"changedFiles":4,"score":0.9039390413480021,"owner":"bgd-labs","repo":"aave-address-book","protocol":"aave","headline":"Aave V3 Ethereum Adds STATA_TOKEN for Improved Asset Representation and Developer Integration","type":"pr"},{"id":6699,"title":"Implementation of COMP rewards on Unichain","summary":"$7e","tldr":"A user-reported issue with claiming COMP rewards on Unichain was resolved by enabling direct claims from the Compound Dashboard, with vaults.fyi also suggested as an alternative interface. Community response was limited, with only two replies focused on providing solutions and confirming the fix.","lastPost":"2025-04-24T00:13:55.015Z","created":"2025-04-22T18:28:38.288Z","views":43,"slug":"implementation-of-comp-rewards-on-unichain","replies":0,"postCount":3,"likes":2,"score":790.9796391285287,"totalWordsAllPosts":130,"totalWordsSummary":192,"updated":1745461242897,"protocol":"compound","discussionUrl":"https://www.comp.xyz","author":{"username":"sandy","url":"https://www.comp.xyz/u/sandy"},"relatedLinks":["https://app.vaults.fyi/opportunity/unichain/0x2c7118c4C88B9841FCF839074c26Ae8f035f2921","https://app.compound.finance/?market=usdc-unichain"],"globalTags":["Newsworthy - Technical"],"localTags":["COMP rewards","Unichain","Compound Dashboard","vaults.fyi","User issue","Claiming rewards","Community response"],"headline":"COMP Rewards Claim Issue on Unichain Resolved via Compound Dashboard Update","type":"discussion"},{"id":25467,"title":"Uniswap Accountability Committee (UAC): Season 3 Report","summary":"$7f","tldr":"The Uniswap Accountability Committee (UAC) Season 3 Report proposes renewing the UAC through December 2025 with a $370,000 UNI budget and rebalancing program accounts with an additional $280,142 UNI, aiming to maintain operational stability, stricter incentive requirements, and refreshed team composition. Community reaction is limited, with one request for clarification on committee rotation and term limits to ensure governance transparency.","lastPost":"2025-04-23T23:56:38.641Z","created":"2025-04-16T22:46:25.242Z","views":101,"slug":"uniswap-accountability-committee-uac-season-3-report","replies":2,"postCount":5,"likes":12,"score":2314.800234647638,"totalWordsAllPosts":5612,"totalWordsSummary":611,"updated":1745461780221,"protocol":"uniswap","discussionUrl":"https://gov.uniswap.org","author":{"username":"AbdullahUmar","url":"https://gov.uniswap.org/u/AbdullahUmar"},"relatedLinks":["https://dashboard.forse.io/main/uniswap/uniswap_incentive_analysis_terminal","https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0x90fab9ab51bb8ca09bab7d76e7ccacaf7dad184e697c870c30957770211cc95d","https://x.com/gnosischain/status/1905628466558763127"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Affecting Governance"],"localTags":["Uniswap Accountability Committee","UAC","Season 3 Report","Committee rotation","Term limits","Governance transparency"],"headline":"Uniswap Accountability Committee Proposes Renewal and Budget Increase Through 2025","type":"discussion"},{"id":29086,"title":"STEP 2 Committee Preferred Allocations","summary":"$80","tldr":"The Arbitrum DAO is finalizing the diversification of $10.66M ARB into three yield-bearing assets (WTGXX, USTBL, BENJI) as part of its STEP 2 initiative, with the proposal set for Snapshot ratification on May 1st, 2025. Community reaction has been limited but generally supportive, with some members providing resources and expressing enthusiasm for the DAO's treasury management and RWA integration.","lastPost":"2025-04-23T23:55:59.084Z","created":"2025-04-22T12:45:32.635Z","views":110,"slug":"step-2-committee-preferred-allocations","replies":2,"postCount":6,"likes":3,"score":497.9007262969669,"totalWordsAllPosts":695,"totalWordsSummary":405,"updated":1745461174738,"protocol":"arbitrum","discussionUrl":"https://forum.arbitrum.foundation","author":{"username":"Entropy","url":"https://forum.arbitrum.foundation/u/Entropy"},"relatedLinks":["https://forum.arbitrum.foundation/t/step-2-application-spiko-ustbl/28752","https://dune.com/entropy_advisors/arbitrum-rwa-case-study","https://forum.arbitrum.foundation/t/wisdomtree-wtgxx-step-application/28756","https://www.tally.xyz/gov/arbitrum/proposal/13323456481927947871314500108227684550647495448005726995657704713229313956489?govId=eip155:42161:0x789fC99093B09aD01C34DC7251D0C89ce743e5a4","https://forum.arbitrum.foundation/t/step-report-march-2025/28946"],"globalTags":["Proposal - Currently voting","Newsworthy - Affecting Governance"],"localTags":["STEP 2","Treasury management","RWA integration","WTGXX","USTBL","BENJI"],"headline":"Arbitrum DAO Proposes Diversification of $10.66M ARB into Yield-Bearing Assets for Treasury Management","type":"discussion"},{"id":629,"title":"Portugal Local Node - Regional Evaluation","summary":"$81","tldr":"This discussion is about a proposal to launch a Scroll local node in Portugal to position the country as a leader in zero-knowledge technology and strengthen local web3 talent pipelines, with support requested for branding, grants, and collaboration. While the benefits include fostering innovation and connecting local talent to global programs, community feedback highlights concerns about duplicating builder support, the need for vertical specialization, and unresolved issues around talent management and data compliance, with only 5 replies indicating limited but focused debate.","lastPost":"2025-04-23T23:52:30.210Z","created":"2025-04-23T08:05:10.983Z","views":27,"slug":"portugal-local-node-regional-evaluation","replies":4,"postCount":6,"likes":1,"score":420.2010402080416,"totalWordsAllPosts":3451,"totalWordsSummary":616,"updated":1745461743105,"protocol":"scroll","discussionUrl":"https://forum.scroll.io","author":{"username":"PauloGouveia","url":"https://forum.scroll.io/u/PauloGouveia"},"relatedLinks":[],"globalTags":["Proposal - Seeking feedback","Grants - Grant Proposal / Application","Changes - Compliance"],"localTags":["Scroll","Local node","Portugal","Zero-knowledge technology","Web3 talent pipeline","Branding support","Collaboration","Builder support","Vertical specialization","Talent management","Data compliance"],"headline":"Proposal to Launch Scroll Local Node in Portugal Aims to Boost Zero-Knowledge Tech and Web3 Talent","type":"discussion"},{"id":1364,"title":"[April 2025] Non-critical Parameter Updates by Risk Stewards","summary":"$82","tldr":"This discussion covers non-critical parameter updates for Euler DAO markets on Ethereum, focusing on increasing supply and borrow caps and updating interest rate models to support growth and transparency, with most changes backed by @Gauntlet’s risk assessments. The benefits include improved market utilization and transparency, while the main caution is around assets with low DEX liquidity; community feedback has been limited but generally supportive, with 13 replies reflecting a moderate level of engagement.","lastPost":"2025-04-23T23:16:35.626Z","created":"2025-04-10T07:46:10.476Z","views":138,"slug":"april-2025-non-critical-parameter-updates-by-risk-stewards","replies":5,"postCount":14,"likes":9,"score":669.3244886415191,"totalWordsAllPosts":1722,"totalWordsSummary":376,"updated":1745461309839,"protocol":"euler","discussionUrl":"https://forum.euler.finance","author":{"username":"Objective","url":"https://forum.euler.finance/u/Objective"},"relatedLinks":["https://etherscan.io/tx/0x7f3fd1a17596de07c3d46e1411c19b22c09e67b861890190d727912067a88323"],"globalTags":["Changes - Technical Change"],"localTags":["Euler DAO","Parameter updates","Ethereum markets","Supply caps","Borrow caps","Interest rate models","Gauntlet","Risk assessments","Market utilization","DEX liquidity"],"headline":"Euler DAO Proposes Parameter Updates for Ethereum Markets to Enhance Growth and Transparency","type":"discussion"},{"id":1365,"title":"Offboard tBTC, eBTC from Euler Prime","summary":"$83","tldr":"A proposal to offboard tBTC and eBTC from Euler Prime aims to reduce risk and improve platform attractiveness, as these assets have low utility and increase risk exposure. Community reaction is limited, with @Gauntlet supporting the rationale and suggesting a careful offboarding process without setting the IRM reserve factor to 100% during delisting.","lastPost":"2025-04-23T23:14:39.270Z","created":"2025-04-11T08:04:05.891Z","views":22,"slug":"offboard-tbtc-ebtc-from-euler-prime","replies":0,"postCount":2,"likes":1,"score":588.3030359736094,"totalWordsAllPosts":1026,"totalWordsSummary":325,"updated":1745461307397,"protocol":"euler","discussionUrl":"https://forum.euler.finance","author":{"username":"Objective","url":"https://forum.euler.finance/u/Objective"},"relatedLinks":["https://forum.euler.finance/t/offboard-wusdm-mtbill-wm-solvbtc-from-euler-prime/1301"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change"],"localTags":["tBTC","eBTC","Euler Prime","Offboarding","IRM reserve factor","Delisting"],"headline":"Proposal to Offboard tBTC and eBTC from Euler Prime to Reduce Risk and Improve Platform Utility","type":"discussion"},{"id":"451","number":"451","title":"Remote GSM","description":"# Changelog\r\n\r\nAdd RemoteGSM Implementation\r\nAbstract methods on GSM","summary":"$84","tldr":"This introduces the `RemoteGsm` and `GhoRemoteVault` contracts to enable cross-chain GHO token management within Aave, allowing authorized roles to handle deposits, withdrawals, and vault updates across different blockchains. The main benefit is streamlined cross-chain GHO operations, with no costs or community reactions mentioned.","created":"2025-04-04T00:05:01Z","updated":"2025-04-23T23:07:38Z","merged":null,"sha":"0b17427d4aa44074e81fbd78dff27a62b7cd6ca0","link":"https://github.com/aave/gho-core/pull/451","state":"open","commits":6,"additions":1955,"deletions":10,"changedFiles":9,"score":400.90534986339657,"owner":"aave","repo":"gho-core","protocol":"aave","headline":"Aave Proposes RemoteGsm and GhoRemoteVault Contracts for Cross-Chain GHO Management","type":"pr"},{"id":29049,"title":"DeFi Renaissance Incentive Program (DRIP)","summary":"$85","tldr":"The DRIP proposal seeks up to 80M ARB to fund targeted, season-based DeFi incentives on Arbitrum, managed by a small committee with broad discretion, aiming for measurable growth and protocol-neutral participation. While some community members support its focused, research-driven approach, others express concerns about transparency, DAO involvement, and oversight, with 24 replies reflecting a moderate level of debate and mixed reactions.","lastPost":"2025-04-23T22:56:22.733Z","created":"2025-04-17T00:05:20.483Z","views":569,"slug":"defi-renaissance-incentive-program-drip","replies":1,"postCount":25,"likes":29,"score":2145.766510810681,"totalWordsAllPosts":10722,"totalWordsSummary":779,"updated":1745461184274,"protocol":"arbitrum","discussionUrl":"https://forum.arbitrum.foundation","author":{"username":"Entropy","url":"https://forum.arbitrum.foundation/u/Entropy"},"relatedLinks":["https://forum.arbitrum.foundation/t/arbs-wake-up-call-a-critical-pivot-is-necessary/27706","https://forum.arbitrum.foundation/t/stip-analysis-ardc-risk-deliverables-insights-key-findings/25515","https://forum.arbitrum.foundation/t/mate-proposal-non-consitutional/27770","https://dashboard.forse.io/oxcart","https://github.com/emjicy/Oxcart/blob/main/OXCART-RESOURCES.md","https://forum.arbitrum.foundation/t/ardc-research-deliverables/23438/14","https://gov.optimism.io/t/season-6-rubric-feedback-thread/8599","https://arbiscan.io/address/0x140e4D8d4229D5437EfD6FC1BEeB86Cb2bCF9D98"],"globalTags":["Grants - Grant Funding","Proposal - Seeking feedback","Newsworthy - Controversial"],"localTags":["DRIP proposal","Season-based DeFi incentives","Arbitrum","Committee management","Protocol-neutral participation","DAO oversight"],"headline":"Arbitrum DRIP Proposal Seeks 80M ARB for Season-Based DeFi Incentives Amid Transparency Concerns","type":"discussion"},{"id":26307,"title":"Atlas Edit Weekly Cycle Proposal - Week of April 28, 2025","summary":"$86","tldr":"The proposal documents the addition of the SPBEAMHaltSpell, enabling Sky Governance to disable SP-BEAM in emergencies without altering existing rates, thereby improving risk management and system stability. There are no costs or community reactions noted, and no next actions have been specified.","lastPost":"2025-04-23T22:46:30.602Z","created":"2025-04-23T22:46:30.539Z","views":7,"slug":"atlas-edit-weekly-cycle-proposal-week-of-april-28-2025","replies":0,"postCount":1,"likes":1,"score":803.7002400480096,"totalWordsAllPosts":162,"totalWordsSummary":183,"updated":1745461434010,"protocol":"makerdao","discussionUrl":"https://forum.makerdao.com","author":{"username":"adamfraser","url":"https://forum.makerdao.com/u/adamfraser"},"relatedLinks":["https://sky-atlas.powerhouse.io/A.3.8.1.2_Stability_Parameter_Bounded_External_Access_Module/1d9f2ff0-8d73-80d8-a361-e66b4fed5df0%7C57eaf45219be"],"globalTags":["Changes - Technical Change"],"localTags":["SPBEAMHaltSpell","Sky Governance","SP-BEAM","Emergency disable mechanism","Risk management","System stability"],"headline":"MakerDAO Proposal Introduces SPBEAMHaltSpell for Emergency Disabling of SP-BEAM","type":"discussion"},{"id":37621,"title":"WTF is Abstain? — A Flawed Governance Option in JUP","summary":"$87","tldr":"The discussion centers on whether to remove, reform, or replace the Abstain voting option in JUP governance due to concerns that it inflates participation metrics and allows users to earn ASR rewards without meaningful engagement, with suggestions including more informative feedback options or engagement mechanisms like quizzes. With 19 replies, the community shows a mix of support for reform, concern about losing a neutral option, and calls for further discussion, while a Twitter poll has been launched to gather broader sentiment.","lastPost":"2025-04-23T22:41:48.019Z","created":"2025-04-20T09:54:29.602Z","views":102,"slug":"wtf-is-abstain-a-flawed-governance-option-in-jup","replies":6,"postCount":20,"likes":29,"score":2183.9910456992066,"totalWordsAllPosts":1544,"totalWordsSummary":341,"updated":1745461537131,"protocol":"jupiter","discussionUrl":"https://www.jupresear.ch","author":{"username":"n0tdapo","url":"https://www.jupresear.ch/u/n0tdapo"},"relatedLinks":["https://x.com/kashdhanda/status/1914239025361076583"],"globalTags":["Changes - Community Improvement","Proposal - Seeking feedback","Newsworthy - Controversial","Newsworthy - Affecting Governance"],"localTags":["JUP governance","Abstain voting option","ASR rewards","Twitter poll","Engagement mechanisms","Quizzes"],"headline":"Jupiter governance debates reforming or removing Abstain vote option to improve engagement metrics","type":"discussion"},{"id":"936","number":"936","title":"Update faq.mdx","description":"Added unichain, Added historical & price questions, cleaned up a few parts.","summary":"$88","tldr":"This update enhances the `faq.mdx` file with clearer information on Token API usage, including authentication methods, supported blockchains, token price handling, and historical data endpoints, helping developers use the API more effectively. There are no mentioned costs, and the update aims to address common issues and improve user understanding.","created":"2025-04-23T22:03:30Z","updated":"2025-04-23T22:39:59Z","merged":null,"sha":"b110ec90a9c054324e130a8e88a27c6933ecd412","link":"https://github.com/graphprotocol/docs/pull/936","state":"closed","commits":1,"additions":18,"deletions":10,"changedFiles":1,"score":11.898396793587175,"owner":"graphprotocol","repo":"docs","protocol":"thegraph","headline":"TheGraph updates FAQ with clearer Token API usage details and developer guidance","type":"pr"},{"id":"9678","number":"9678","title":"Add gas limit increase EIP","description":"EIP to recommend a new gas limit by the time Fusaka is released and update EL default configs.","summary":"$89","tldr":"EIP-7935 proposes that execution layer clients update their default gas limit to 60M for the Fusaka hard fork, aiming to increase L1 execution capacity and allow more transactions or complex computations per block. This change requires coordination with other EIPs and thorough testing for client compatibility, with no explicit mention of costs or community reaction.","created":"2025-04-23T04:03:42Z","updated":"2025-04-23T22:34:13Z","merged":null,"sha":"82037e12f76f0035a3ac8ede85b4d373f962eef1","link":"https://github.com/ethereum/EIPs/pull/9678","state":"open","commits":1,"additions":40,"deletions":0,"changedFiles":1,"score":21.102204408817634,"owner":"ethereum","repo":"EIPs","protocol":"ethereum","headline":"EIP-7935 Proposes Raising Ethereum Default Gas Limit to 60M for Fusaka Hard Fork","type":"pr"},{"id":20873,"title":"PIP-62: Heimdall v2 Migration","summary":"$8a","tldr":"The proposal discusses migrating Polygon PoS's Heimdall from v1 to v2, involving major technical upgrades that require a new, non-backward-compatible chain and raise questions about data preservation and migration timing. With only three replies, community engagement is limited and mainly focused on seeking clarification about data loss and the specifics of the chain state changes.","lastPost":"2025-04-23T22:23:54.621Z","created":"2025-04-11T18:59:05.841Z","views":36,"slug":"pip-62-heimdall-v2-migration","replies":0,"postCount":4,"likes":1,"score":1202.1439835246397,"totalWordsAllPosts":423,"totalWordsSummary":304,"updated":1745461682458,"protocol":"polygon","discussionUrl":"https://forum.polygon.technology","author":{"username":"H_Rook","url":"https://forum.polygon.technology/u/H_Rook"},"relatedLinks":["https://github.com/maticnetwork/Polygon-Improvement-Proposals/blob/main/PIPs/PIP-43.md"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change","Newsworthy - Technical"],"localTags":["Polygon PoS","Heimdall v1","Heimdall v2","Chain migration","Data preservation","Chain state changes"],"headline":"Polygon PoS Proposes Heimdall v1 to v2 Migration, Raising Data Preservation and Timing Questions","type":"discussion"},{"id":4881,"title":"Updated MEV-Boost relay settings","summary":"$8b","tldr":"This discussion is about new BuilderNet MEV-Boost relay submission guidelines designed to improve relay performance, independence, and transparency, with benefits including faster bundle processing and reduced conflicts of interest, but with concerns about potential centralization if only a few relays meet the strict criteria. With 7 replies, community reaction is mixed: some support the changes, while others worry about centralization, conflicts of interest, and seek clearer definitions and transparency.","lastPost":"2025-04-23T22:04:20.722Z","created":"2025-04-14T22:31:56.940Z","views":153,"slug":"updated-mev-boost-relay-settings","replies":3,"postCount":8,"likes":9,"score":3113.9011684964707,"totalWordsAllPosts":2334,"totalWordsSummary":479,"updated":1745461333211,"protocol":"flashbots","discussionUrl":"https://collective.flashbots.net","author":{"username":"shea","url":"https://collective.flashbots.net/u/shea"},"relatedLinks":["https://collective.flashbots.net/t/the-mev-letter-83/4885","https://collective.flashbots.net/t/tee-boost/3741","https://docs.titanrelay.xyz/builders/builder-integration#websocket-topbid-stream"],"globalTags":["Changes - Technical Change","Newsworthy - Controversial"],"localTags":["BuilderNet","MEV-Boost relay","Relay submission guidelines","Relay performance","Relay independence","Relay transparency","Bundle processing","Centralization risk"],"headline":"Flashbots Proposes New BuilderNet MEV-Boost Relay Guidelines to Enhance Performance and Transparency","type":"discussion"},{"id":"554","number":"554","title":"feat, test: adjust model parameters; fix bps unit bug; tau safety ceiling","description":"- Set a ceiling for `tau` for user safety (with test)\r\n- Fix bps unit bug in `f(extrinsic, intrinsic) -> pi, tau`\r\n- Adjust `targetWaitTime` to 8 blocks\r\n- Increase learning rates by 50%","summary":"$8c","tldr":"This pull request updates the UniMind component of the Uniswap protocol by refining model parameters, fixing BPS unit handling, and introducing a safety ceiling for the `tau` parameter to enhance stability and safety. The main benefit is improved reliability and prevention of unsafe parameter values, with no costs or community reactions mentioned.","created":"2025-04-23T21:00:54Z","updated":"2025-04-23T21:35:34Z","merged":"2025-04-23T21:35:32Z","sha":"c795b206aca0fa554c3c0dbd19dd8b8fc447c298","link":"https://github.com/Uniswap/uniswapx-service/pull/554","state":"closed","commits":4,"additions":63,"deletions":35,"changedFiles":5,"score":7.60988608527474,"owner":"Uniswap","repo":"uniswapx-service","protocol":"uniswap","headline":"Uniswap UniMind updated with refined parameters and safety ceiling for improved stability","type":"pr"},{"id":23782,"title":"A new standard for encoding chain ID + transaction hash","summary":"$8d","tldr":"This discussion is about a proposal to standardize encoding both EVM chain id and transaction hash in a single string to uniquely identify transactions across networks, aiming to improve clarity and user experience compared to existing standards. Initial community feedback is supportive but highlights concerns about chain id assignment, user interface clarity, and potential confusion with current standards; no next steps have been decided.","lastPost":"2025-04-23T21:29:37.825Z","created":"2025-04-23T10:58:42.547Z","views":21,"slug":"a-new-standard-for-encoding-chain-id-transaction-hash","replies":0,"postCount":2,"likes":1,"score":757.1450801060671,"totalWordsAllPosts":310,"totalWordsSummary":369,"updated":1745446043481,"protocol":"ethereum","discussionUrl":"https://ethereum-magicians.org","author":{"username":"microbecode","url":"https://ethereum-magicians.org/u/microbecode"},"relatedLinks":["https://eips.ethereum.org/EIPS/eip-3091","http://chainlist.org","https://eips.ethereum.org/EIPS/eip-3770"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change"],"localTags":["EVM chain id","Transaction hash standardization","Cross-network transaction identification"],"headline":"Proposal to Standardize EVM Chain ID and Transaction Hash Encoding for Cross-Network Identification","type":"discussion"},{"id":"935","number":"935","title":"Update utils.ts","description":"Unless the `TOKEN_API_NETWORKS` array is updated automatically, we will need to add `unichain` to it.","summary":"## What is this about?\\n\\nThe `TOKEN_API_NETWORKS` array in `website/src/supportedNetworks/utils.ts` has been updated.\\n\\n## Why is this important?\\n\\nThis change indicates the addition of `unichain` to the list of supported networks for a token API within the graphprotocol/docs repository.\\n\\n## How does it work?\\n\\nThe update involves directly adding `unichain` to the `TOKEN_API_NETWORKS` array.\\n\\n## What should developers know?\\n\\n* `TOKEN_API_NETWORKS`: This is an array that lists the supported networks for a token API.\\n* `unichain`: This has been added to the `TOKEN_API_NETWORKS` array.\\n","tldr":"The `unichain` network has been added to the `TOKEN_API_NETWORKS` array in the graphprotocol/docs repository, expanding the supported networks for the token API. This update benefits developers by enabling token API functionality on `unichain` with no mentioned costs or community feedback.","created":"2025-04-23T21:14:12Z","updated":"2025-04-23T21:14:13Z","merged":null,"sha":"282006eecaeaa9f8be742e14ee9c1c13f5956e4d","link":"https://github.com/graphprotocol/docs/pull/935","state":"open","commits":1,"additions":1,"deletions":1,"changedFiles":1,"score":0.27,"owner":"graphprotocol","repo":"docs","protocol":"thegraph","headline":"The Graph Adds Unichain Support to Token API in docs Repository","type":"pr"},{"id":6483,"title":"Governance Call - Wednesday, April 23, 16:00 UTC","summary":"$8e","tldr":"A governance call was scheduled for April 23, 14:00 UTC to discuss the \\\"Support EDS development for Safe\\\" proposal, but concerns were raised by @peersky about missing calendar entries and the short notice, potentially impacting participation and transparency. Community reaction has been minimal, with only one reply highlighting these organizational issues.","lastPost":"2025-04-23T21:09:55.152Z","created":"2025-04-23T13:13:35.936Z","views":12,"slug":"governance-call-wednesday-april-23-16-00-utc","replies":0,"postCount":2,"likes":0,"score":1752.1694180423547,"totalWordsAllPosts":94,"totalWordsSummary":222,"updated":1745446267630,"protocol":"safedao","discussionUrl":"https://forum.safe.global","author":{"username":"amanwithwings","url":"https://forum.safe.global/u/amanwithwings"},"relatedLinks":["https://forum.safe.global/t/support-eds-development-for-safe/6432","https://safe-global.notion.site/Governance-Calendar-4af19f92cd0349a6b175cccea09d6bfa"],"globalTags":["Proposal - Seeking feedback","Event - Online","Newsworthy - Affecting Governance"],"localTags":["Support EDS development for Safe","Organizational issues","Participation","Transparency","Calendar entries","Short notice","@peersky"],"headline":"SafeDAO governance call on EDS development faces concerns over short notice and transparency","type":"discussion"},{"id":"2002","number":"2002","title":"docs(consensus-node): reduce log level","description":"Motivated by https://github.com/celestiaorg/celestia-app/issues/4643\r\n\r\ncc: @tac0turtle \r\n\r\n## Screenshot\r\n\r\n![Screenshot 2025-04-23 at 4 52 34 PM](https://github.com/user-attachments/assets/290d975e-d5e2-4a68-b426-fec6c8729124)\r\n\n\n\n\n## Summary by CodeRabbit\n\n- **Documentation**\n - Improved readability by adding blank lines before lists in reset command sections.\n - Added an optional section explaining how to reduce log verbosity by updating the log level in the configuration file.\n\n","summary":"$8f","tldr":"This update to `consensus-node.md` explains how to reduce log verbosity by adjusting the `log_level` in `config.toml` and clarifies the impact of various reset commands on a consensus node's data and state, helping developers maintain node integrity during troubleshooting or maintenance. The benefits include more manageable logs and clearer understanding of data removal, while the main cost is the risk of data loss if reset commands are used without caution.","created":"2025-04-23T20:53:33Z","updated":"2025-04-23T21:08:29Z","merged":null,"sha":"15f2a6f6cc3a29724257713b4c5306be7a517ee3","link":"https://github.com/celestiaorg/docs/pull/2002","state":"open","commits":1,"additions":13,"deletions":0,"changedFiles":1,"score":7.214428857715431,"owner":"celestiaorg","repo":"docs","protocol":"celestia","headline":"Celestia consensus-node.md updated: configurable log levels and clearer reset command impacts","type":"pr"},{"id":21517,"title":"Native rollups—superpowers from L1 execution","summary":"$90","tldr":"The discussion is about a proposal to introduce the `EXECUTE` precompile, enabling native rollups to leverage the L1 EVM execution engine for enhanced security, simplified development, and improved composability, with suggestions to further support diverse L2 innovations. While the proposal offers significant benefits, community responses are mixed, highlighting technical concerns, potential complexity, and debates over composability and security, with no clear next steps decided as of now.","lastPost":"2025-04-23T20:56:19.132Z","created":"2025-01-20T19:19:08.035Z","views":5555,"slug":"native-rollups-superpowers-from-l1-execution","replies":8,"postCount":30,"likes":165,"score":2667.5395534006193,"totalWordsAllPosts":7348,"totalWordsSummary":472,"updated":1745445820991,"protocol":"ethereum","discussionUrl":"https://ethresear.ch","author":{"username":"JustinDrake","url":"https://ethresear.ch/u/JustinDrake"},"relatedLinks":["https://hackmd.io/@levs57/Hy07LMoDke","https://github.com/rkdud007/awesome-zkvm","https://notes.ethereum.org/@vbuterin/enshrined_zk_evm","https://github.com/ethereum/execution-specs/compare/master...fradamt:execution-specs:builder_pays_upfront","https://github.com/ethereum/EIPs/issues/726","https://github.com/ethereum/EIPs/pull/9241","https://ethresear.ch/t/proposal-delay-stateroot-reference-to-increase-throughput-and-reduce-latency/20490","https://www.reddit.com/r/ethereum/comments/vrx9xe/comment/if7auu7/","https://polynya.medium.com/updated-thoughts-on-modular-blockchains-ce1b159fa1b3","https://www.reddit.com/r/ethereum/comments/191kke6/comment/kh7myl5/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1","https://www.youtube.com/watch?v=BWsz_ulng6Y","https://www.youtube.com/watch?v=URCH2d1cdyg","https://arbitrum.io/stylus","https://github.com/attestantio/vouch","https://forum.polkadot.network/t/announcing-polkavm-a-new-risc-v-based-vm-for-smart-contracts-and-possibly-more/3811","https://www.rollup.codes/","https://www.youtube.com/watch?v=MNtzDe9Ck0c&t=1534s","https://ethresear.ch/t/native-rollup-for-3sf/21632","https://github.com/ethereum/EIPs/pull/9241/files","https://ethresear.ch/t/fee-structure-for-execute-precompile/22096/7","https://hackmd.io/@peter-scroll/rJSKJAFnyx"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Controversial","Changes - Technical Change","Security"],"localTags":["EXECUTE precompile","Native rollups","L1 EVM execution engine","L2 innovations","Composability"],"headline":"Ethereum Proposal: Introducing `EXECUTE` Precompile for Native Rollups Faces Mixed Community Feedback","type":"discussion"},{"id":20643,"title":"Forum Topic Scraper","summary":"## What is this about?\\n\\n@accessor.eth introduced a tool named \\\"ENS Forum Scraper\\\" to help users extract data from the forum, solving the problem that forum content cannot be copied and pasted directly. The tool is available on GitHub (https://github.com/accessor-io/ens-dao-forum-scraper.git). Users can clone the repository, install dependencies using npm, and launch the UI with \\\"npm run ui\\\" to scrape entire conversations from the forum efficiently [1].\\n\\n## What could be the impact of this?\\n\\nThe tool could significantly improve access to forum data for users and developers:\\n- Makes it easier to extract and analyze forum discussions, which could benefit research, archiving, or moderation tasks [1].\\n- Reduces manual effort and time required to collect forum data [1].\\n- May raise concerns about data privacy or misuse if not managed responsibly [1].\\n\\n## How is the community reacting?\\n\\nThere have been no community discussions.\\n\\n## Next actions\\n\\nNo next action has been determined.","tldr":"A new tool called \\\"ENS Forum Scraper\\\" allows users to efficiently extract and analyze data from the ENS forum, reducing manual effort and enabling easier research or moderation. The tool is open-source on GitHub, and while it offers clear benefits for data access, there are potential concerns about data privacy; there has been no community feedback or next steps announced.","lastPost":"2025-04-23T20:49:35.472Z","created":"2025-04-23T20:49:35.421Z","views":15,"slug":"forum-topic-scraper","replies":0,"postCount":1,"likes":0,"score":1425.3005601120224,"totalWordsAllPosts":89,"totalWordsSummary":143,"updated":1745445807495,"protocol":"ens","discussionUrl":"https://discuss.ens.domains","author":{"username":"accessor.eth","url":"https://discuss.ens.domains/u/accessor.eth"},"relatedLinks":[],"globalTags":["Newsworthy - Technical"],"localTags":["ENS Forum Scraper","Data extraction tool","Data privacy","Open-source tool","GitHub"],"headline":"ENS Forum Scraper Released: Open-Source Tool for Extracting and Analyzing ENS Forum Data","type":"discussion"},{"id":"330","number":"330","title":"hotfix: merge develop to master","description":"* chore: also verify with sourcify\r\n\r\n* chore: update example\r\n\r\n* fix: better typing\r\n\r\n* ci: bump action versions\r\n\r\n* test: workaround delay proof\r\n\r\n* format: yarn format\r\n\r\n* ci: fix slither db using new version","summary":"$91","tldr":"This update adds a configurable template (`config.example.ts`) and modifies deployment scripts to streamline and customize Arbitrum rollup creation, allowing developers to define chain parameters and initial state for more flexible deployments. There are no noted costs or community reactions in the summary.","created":"2025-04-23T03:15:52Z","updated":"2025-04-23T20:38:51Z","merged":null,"sha":"701deb3a7217a8790ea8d51464b85635332254b9","link":"https://github.com/OffchainLabs/nitro-contracts/pull/330","state":"open","commits":1,"additions":133,"deletions":80,"changedFiles":7,"score":3.565367060651916,"owner":"OffchainLabs","repo":"nitro-contracts","protocol":"arbitrum","headline":"Arbitrum update introduces configurable templates and streamlined deployment scripts for custom rollup creation","type":"pr"},{"id":923,"title":"Gauntlet Delegate Platform","summary":"$92","tldr":"Gauntlet has introduced the Gauntlet Delegate Platform to provide governance and risk management expertise for Morpho, including launching curated vaults and supporting key proposals, with disclosed conflicts of interest and a suggestion for a stablecoin treasury framework. There have been no community discussions or next actions identified, and the total number of replies is 2.","lastPost":"2025-04-23T20:27:33.124Z","created":"2024-10-21T15:18:58.997Z","views":214,"slug":"gauntlet-delegate-platform","replies":0,"postCount":3,"likes":3,"score":152.21277305319327,"totalWordsAllPosts":425,"totalWordsSummary":320,"updated":1745446121189,"protocol":"morpho","discussionUrl":"https://forum.morpho.org","author":{"username":"Gauntlet","url":"https://forum.morpho.org/u/Gauntlet"},"relatedLinks":["https://app.gauntlet.xyz/protocols/metamorpho","https://aera.finance/","https://x.com/gauntlet_xyz"],"globalTags":["Delegate - Reasoning/Justification","Newsworthy - Affecting Governance"],"localTags":["Gauntlet Delegate Platform","Morpho","Curated vaults","Stablecoin treasury framework","Governance expertise","Risk management expertise","Disclosed conflicts of interest"],"headline":"Gauntlet Launches Delegate Platform for Morpho Governance and Risk Management","type":"discussion"},{"id":"932","number":"932","title":"Graphql revampt","description":null,"summary":"$93","tldr":"This is a documentation update for The Graph's GraphQL API, detailing how to efficiently query and filter subgraph data using features like sorting, pagination, block filtering, nested filtering, logical operators, time-travel queries, and full-text search. The update benefits developers by clarifying best practices and performance considerations, but does not mention any costs or community reactions.","created":"2025-04-22T16:20:05Z","updated":"2025-04-23T20:43:53Z","merged":"2025-04-23T20:23:15Z","sha":"d278384c484553d4a92a64f756fef44b055f062c","link":"https://github.com/graphprotocol/docs/pull/932","state":"closed","commits":9,"additions":46,"deletions":48,"changedFiles":1,"score":521.3742484897138,"owner":"graphprotocol","repo":"docs","protocol":"thegraph","headline":"The Graph updates GraphQL API documentation with advanced querying and filtering features","type":"pr"},{"id":5006,"title":"Proposal to Add Ether.fi’s weETH to Venus Core pool on Unichain","summary":"$94","tldr":"A proposal suggests adding Ether.fi’s weETH as collateral and a borrowable asset on Venus Protocol’s Unichain Core pool to diversify assets and enhance yield opportunities, though there are concerns about liquidity risks if Unichain incentive programs end. With only 5 replies, community reaction is generally supportive but limited, focusing on liquidity and potential user incentives.","lastPost":"2025-04-23T20:18:28.259Z","created":"2025-03-27T21:27:24.852Z","views":315,"slug":"proposal-to-add-ether-fi-s-weeth-to-venus-core-pool-on-unichain","replies":1,"postCount":6,"likes":7,"score":319.01757747860296,"totalWordsAllPosts":617,"totalWordsSummary":315,"updated":1745446344438,"protocol":"venus","discussionUrl":"https://community.venus.io","author":{"username":"Showtime","url":"https://community.venus.io/u/Showtime"},"relatedLinks":["https://dune.com/ether_fi/etherfi"],"globalTags":["Proposal - Seeking feedback"],"localTags":["Ether.fi","weETH","Venus Protocol","Unichain Core pool","Collateral asset","Borrowable asset","Asset diversification","Yield opportunities","Liquidity risk","Unichain incentive programs","User incentives"],"headline":"Proposal to Add weETH as Collateral and Borrowable Asset on Venus Unichain Core Pool Raises Liquidity Concerns","type":"discussion"},{"id":431,"title":"Call Links - 2025","summary":"$95","tldr":"A central repository of videos and transcripts for Scroll DAO’s public calls from January to April 2025 has been created, covering topics like governance, grant programs, local node activities, and protocol upgrades, with all materials easily accessible for reference. This resource enhances strategic planning, transparency, and community engagement, with no reported community feedback or next steps identified.","lastPost":"2025-04-23T20:15:08.381Z","created":"2025-01-16T17:55:20.090Z","views":300,"slug":"call-links-2025","replies":0,"postCount":1,"likes":9,"score":1,"totalWordsAllPosts":1861,"totalWordsSummary":405,"updated":1745446299388,"protocol":"scroll","discussionUrl":"https://forum.scroll.io","author":{"username":"eugene","url":"https://forum.scroll.io/u/eugene"},"relatedLinks":["https://forum.scroll.io/t/recordings-of-ccc-related-calls/293","https://docs.google.com/document/d/1Wbk5PQxfoNLW93475ylkubk913YdkoV3Vfw0yIYpX2M/edit?tab=t.0","https://calendar.google.com/calendar/embed?src=c_5c62db9ba29ec8b39ab7be1bbc750b333c554bb144f5bab28cefa55bfa4a84b3%40group.calendar.google.com&ctz=America%2FNew_York","https://drive.google.com/file/d/1g5VdzZSJ6BWcbX2_Tuyi6hbIxzNX6fV4/view?usp=sharing","https://drive.google.com/file/d/1CTZBrFNk_ErrU2i66-bl4ZDvTlQglFWw/view?usp=sharing","https://drive.google.com/file/d/1_12zcjv6GDHdyTcukA81Ex4ErYVDFlLD/view?usp=sharing","https://docs.google.com/document/d/1fIBWy7NJf0iN1gmTdxiJXD2E5z9SIHXMbQIgKy-n67A/edit?tab=t.0#heading=h.bqlhoofflkax","https://docs.google.com/document/d/1Wbk5PQxfoNLW93475ylkubk913YdkoV3Vfw0yIYpX2M/edit?usp=sharing","https://drive.google.com/file/d/1h1Dy0oBpaYOaN56IdObYOXHIHHQqvFF-/view?usp=sharing","https://drive.google.com/file/d/1OGa6_TEvlM7WSM--xo9d-xA8SYbMcIJE/view?usp=sharing","https://docs.google.com/document/d/1FX2IAjOO0uoopQDGpObU2qoirHmixTcV-HM1uo_c5Ek/edit?usp=sharing","https://docs.google.com/document/d/1H9ketNFFv1bJK5aLDd46exCExFuXB3QRoFI6-DUO3Dk/edit?usp=sharing","https://drive.google.com/file/d/1NN-iaIBn6uOFI6Tk7dcKscAVphOcRpzD/view?usp=sharing","https://docs.google.com/document/d/1I4z8XbB9Kmz0To_R7hGb3kH47K-1OzlbBvYaBLbS8S8/edit?tab=t.0#heading=h.eg8bvtrsxho0","https://docs.google.com/document/d/1XaOJqMhN4npvel9R0t9_dAP78zdxkqwptrRjb6kRii4/edit?usp=sharing","https://docs.google.com/document/d/1nFCnn1lkPobPdVOSkTb9WTtaJ-MUnZsaKbewEkwh-C0/edit?usp=sharing","https://docs.google.com/document/d/1r5BYd4x6bvO3st-5Grh65EclczBVfqrDML8xhwDAsFw/edit?tab=t.0#heading=h.1x2me5y3r1gd","https://drive.google.com/file/d/1QEP_GP6U6ePDDhxXG7sVigmOmxnyU1Wx/view?usp=sharing","https://docs.google.com/document/d/1hvdKKj5WpBSkjq1pf1HneUKwSWZZMPo9zsskQiix0C0/edit?tab=t.pypeg4585p2x","https://drive.google.com/file/d/1JKlHPz5h8HCCg_ABRbNsx7DScWpZFSm5/view?usp=sharing","https://www.campus.scroll.io/","https://docs.google.com/document/d/11CwfKW5JqknmjIFSEtw1KNd7RIbYFg6GGMnhbx2xI50/edit?usp=sharing","https://docs.google.com/document/d/14ouQPfouEX-PgzrEvytYbfqoS9jwkcnBliYXsUmJe3o/edit?usp=sharing","https://docs.google.com/document/d/18qFwa_HHpVZtfAnIc9CgTyKX_IR5UCIqZ6LkQCOKNA0/edit?tab=t.0#heading=h.dsypycxxus9t","https://docs.google.com/document/d/1Bli03ahScbpZFlNbXOSEZwtNz9kdPQEg5FGveIewOGQ/edit?tab=t.0#heading=h.by6lp6g3iz6a","https://docs.google.com/document/d/1bObrwuXhpzNt30-PxYmMt8AghW6secu-a_4XvNH3RJE/edit?usp=sharing","https://docs.google.com/document/d/1ekLpbbK6DFSPlkkFhA67wd4PfXE1D-5faOQxG9mn2jk/edit?tab=t.54s5e0h3cpp9","https://docs.google.com/document/d/1ekLpbbK6DFSPlkkFhA67wd4PfXE1D-5faOQxG9mn2jk/edit?tab=t.e3lkjg89cu69","https://docs.google.com/document/d/1hvdKKj5WpBSkjq1pf1HneUKwSWZZMPo9zsskQiix0C0/edit?usp=sharing","https://docs.google.com/document/d/1RKu9wY8V7wGLoQCHwODH4w22jEPfHmIi4veQM5XoPdE/edit?usp=sharing","https://docs.google.com/document/d/1VETU2kaqngvmo-3Wy2cRiZVoXrTW1Y0bnBLSCJ0HDc8/edit?usp=sharing","https://docs.google.com/document/d/1_vvqP5gIIQx8RaXViW04BfXpkh3PAUqSPUi9k7YAGOI/edit?tab=t.0#heading=h.tlre06rwiat9","https://docs.google.com/document/d/1WuklD8BLLyRdnjTJnXK-oIqgwlIy5ccgtbdzvT77oU8/edit?tab=t.0#heading=h.fsy24zf2k8za","https://docs.google.com/document/d/1xl1ILyF2CcHaCEYKPP0Bxk-FSecyiPnxFXPLCRaaI1Q/edit?tab=t.tibzoful78uf","https://drive.google.com/file/d/16cLyWhsvu3_sd20Zfv3reAxnn5RI28XU/view?usp=sharing","https://drive.google.com/file/d/18d5rjivuz3MZCmYGuqzorvHAnPlllJub/view?usp=sharing","https://drive.google.com/file/d/1A_NoWpCHKx7veWYu82CiNkuyIzZDKLvN/view?usp=sharing","https://drive.google.com/file/d/1efNfZdYCDY1IUoS-4XQxfdAbNwv0a2e-/view?usp=sharing","https://drive.google.com/file/d/1fIGpnXqZGi1aRsrklStZ0t4VzL0_cytA/view?usp=sharing","https://drive.google.com/file/d/1g4FgYvUPvco1HF-RGalwsCSL42oJod_2/view?usp=sharing","https://drive.google.com/file/d/1hTQI9eKCCAidWq3_VbvSINS0BUGqBp0u/view?usp=sharing","https://drive.google.com/file/d/1kZyfLRzdlYmP0TGMzcCByJ-ClM-Hroda/view?usp=sharing","https://drive.google.com/file/d/1qWZXaaOn_iYtvKYBFj4diwta2dFzKjSk/view?usp=sharing","https://drive.google.com/file/d/1rMDPwsqkzF-pPVIwv_XA7_UF9yvSrB9G/view?usp=sharing","https://drive.google.com/file/d/1WiveSP5hUSRAIXbD68cGlhY5pMJszuOg/view?usp=sharing","https://drive.google.com/file/d/1XkppyR4F1DHP452y7cBKKMkVclKm2vuu/view?usp=sharing","https://drive.google.com/file/d/1xTqAkQ2X3UusTLwAKwnyrkjLpxsCzhng/view?usp=sharing","https://forum.scroll.io/t/proposal-dao-defi-grant-program/499","https://forum.scroll.io/t/proposal-scroll-dao-delegate-accelerator-proposal/571/24","https://drive.google.com/file/d/1aiH-RYVpfaL4k5-yhHgne9uFGld7B6TW/view?usp=sharing"],"globalTags":["Grants - Grant Program Update","Changes - Technical Change","Newsworthy - Affecting Governance","Event - Online"],"localTags":["Scroll DAO","Public call repository","Governance resource","Protocol upgrades","Local node activities","Community engagement","Transparency"],"headline":"Scroll DAO Publishes Central Repository of Public Call Videos and Transcripts (Jan–Apr 2025)","type":"discussion"},{"id":"9687","number":"9687","title":"Add EIP: 64-bit mode EVM operations","description":"$96","summary":"$97","tldr":"This proposal introduces new EVM opcodes for 64-bit operations, signaled by the `C0` prefix, aiming to improve computational performance and efficiency with adjusted gas costs. Developers benefit from more granular operations, but must adapt to new opcode behaviors and gas pricing, while some legacy opcodes are excluded due to technical constraints.","created":"2025-04-23T19:43:28Z","updated":"2025-04-23T20:13:42Z","merged":null,"sha":"af1b960ad961fb3f15d990165565342e9e27867f","link":"https://github.com/ethereum/EIPs/pull/9687","state":"open","commits":6,"additions":145,"deletions":0,"changedFiles":1,"score":105.41736739811282,"owner":"ethereum","repo":"EIPs","protocol":"ethereum","headline":"Ethereum Proposal: New 64-bit EVM Opcodes with C0 Prefix to Enhance Performance and Efficiency","type":"pr"},{"id":21893,"title":"Chaos Labs Risk Stewards - Increase Supply and Borrow Caps on Aave V3 - 04.23.25","summary":"$98","tldr":"@ChaosLabs proposes increasing supply and borrow caps for RLUSD on Ethereum Core, EURe on Gnosis, and GHO on Base in Aave V3 to meet growing demand without adding risk, based on risk simulations. There are no costs or community reactions noted, and no next actions have been determined.","lastPost":"2025-04-23T20:11:17.977Z","created":"2025-04-23T20:11:17.884Z","views":12,"slug":"chaos-labs-risk-stewards-increase-supply-and-borrow-caps-on-aave-v3-04-23-25","replies":0,"postCount":1,"likes":0,"score":1404.7004400880176,"totalWordsAllPosts":504,"totalWordsSummary":222,"updated":1745445688642,"protocol":"aave","discussionUrl":"https://governance.aave.com","author":{"username":"ChaosLabs","url":"https://governance.aave.com/u/ChaosLabs"},"relatedLinks":[],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change"],"localTags":["ChaosLabs","Supply cap increase","Borrow cap increase","RLUSD","EURe","GHO","Aave V3","Ethereum Core","Gnosis","Base","Risk simulations"],"headline":"ChaosLabs Proposes Raising RLUSD, EURe, and GHO Caps in Aave V3 Following Risk Simulations","type":"discussion"},{"id":"2787","number":"2787","title":"[CT-1358] Support Limit Price for TWAP","description":"$99","summary":"$9a","tldr":"This update adds support for TWAP orders to the dydx protocol, enabling large trades to be executed over time to minimize market impact and attract advanced traders. The implementation involves new functions and state management for order placement, suborder generation, and price calculation, with no costs or community reactions mentioned.","created":"2025-04-15T21:57:09Z","updated":"2025-04-23T20:09:30Z","merged":null,"sha":"ad25660c3e110f370bb68ed760495cfbf0b50451","link":"https://github.com/dydxprotocol/v4-chain/pull/2787","state":"open","commits":6,"additions":1828,"deletions":93,"changedFiles":24,"score":549.155085267569,"owner":"dydxprotocol","repo":"v4-chain","protocol":"dydx","headline":"dydx Protocol Adds TWAP Order Support for Efficient Large Trade Execution","type":"pr"},{"id":23794,"title":"EIP-9687: 64-bit mode EVM operations","summary":"## What is this about?\\n\\nEIP-9687 is a proposal by @sorpaas to add 64-bit mode EVM operations. The initial draft of this EIP was published on 2025-04-23. The discussion references the related pull request: https://github.com/ethereum/EIPs/pull/9687. As of the draft date, there are no external reviews or outstanding issues reported for this EIP [1].\\n\\n## What could be the impact of this?\\n\\nThe potential impacts of EIP-9687 are not detailed in the available information, but the introduction of 64-bit mode EVM operations could have significant technical implications, such as:\\n- Enabling new types of operations or optimizations within the EVM.\\n- Potentially improving performance or compatibility for certain applications.\\n- Introducing new considerations for EVM implementers and developers [1].\\n\\n## How is the community reacting?\\n\\nThere have been no community discussions.\\n\\n## Next actions\\n\\nNo next action has been determined.","tldr":"EIP-9687, proposed by @sorpaas on 2025-04-23, aims to add 64-bit mode EVM operations, which could enable new operations or optimizations and potentially improve performance or compatibility. There are no reported costs, community discussions, or next actions as of now.","lastPost":"2025-04-23T19:57:50.477Z","created":"2025-04-23T19:57:50.406Z","views":11,"slug":"eip-9687-64-bit-mode-evm-operations","replies":0,"postCount":1,"likes":0,"score":1030.001111481605,"totalWordsAllPosts":31,"totalWordsSummary":129,"updated":1745446048300,"protocol":"ethereum","discussionUrl":"https://ethereum-magicians.org","author":{"username":"sorpaas","url":"https://ethereum-magicians.org/u/sorpaas"},"relatedLinks":["https://github.com/ethereum/EIPs/pull/9687"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change","Newsworthy - Technical"],"localTags":["EIP-9687","64-bit mode EVM operations","EVM optimizations","Performance improvement","Compatibility improvement","@sorpaas"],"headline":"EIP-9687 Proposes 64-bit Mode EVM Operations for Potential Performance and Compatibility Improvements","type":"discussion"},{"id":"685","number":"685","title":"Lower stkBPT Emissions","description":"# Changelog\r\n\r\nKeep allowance not withdrawn and enable allowance at 240 per day rate.","summary":"$9b","tldr":"This pull request proposes and implements a contract to reduce AAVE emissions to the `stkABPT` Safety Module category, aiming to optimize token distribution and resource allocation in the Aave protocol. The main change is a lower emission rate, with no explicit costs mentioned, and the update is handled via a new contract and configuration process.","created":"2025-04-23T19:44:49Z","updated":"2025-04-23T19:44:49Z","merged":null,"sha":"4801479c02ef14e5bf99c99d45395c401822abc9","link":"https://github.com/bgd-labs/aave-proposals-v3/pull/685","state":"open","commits":2,"additions":292,"deletions":0,"changedFiles":5,"score":226.0424500989089,"owner":"bgd-labs","repo":"aave-proposals-v3","protocol":"aave","headline":"Aave Pull Request Proposes Lower Emissions to stkABPT Safety Module via New Contract","type":"pr"},{"id":628,"title":"Votable Supply Adjustment Proposal","summary":"$9c","tldr":"This is about a proposal to temporarily delegate 1.5 million SCR from the Scroll DAO treasury to 46 active delegates until October 2025 to boost votable supply and reduce quorum risk, with quarterly reviews and no direct costs to the DAO. Community reaction is mixed, with some supporting the increased decentralisation and operational safety, while others criticize the delegation curve and see the proposal as a temporary \\\"bandaid\\\" rather than a long-term solution; there are only 5 replies, so feedback is limited.","lastPost":"2025-04-23T19:40:59.656Z","created":"2025-04-22T19:03:17.196Z","views":39,"slug":"votable-supply-adjustment-proposal","replies":0,"postCount":7,"likes":9,"score":2509.8122950195902,"totalWordsAllPosts":1619,"totalWordsSummary":488,"updated":1745446296176,"protocol":"scroll","discussionUrl":"https://forum.scroll.io","author":{"username":"eugene","url":"https://forum.scroll.io/u/eugene"},"relatedLinks":["https://docs.google.com/spreadsheets/d/17s11ZL3yf6oKYJy7L2A6QOHHUzQsXsH3qprtfOddEgQ/edit?usp=sharing"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Controversial","Newsworthy - Affecting Governance"],"localTags":["Scroll DAO","SCR delegation","Votable supply","Quorum risk","Delegation curve","Quarterly reviews"],"headline":"Scroll DAO Considers Temporarily Delegating 1.5M SCR to Boost Votable Supply and Reduce Quorum Risk","type":"discussion"},{"id":6677,"title":"Compound Growth Program - Interim Extension","summary":"$9d","tldr":"The discussion is about extending the Compound Growth Program from May 1st to July 1st, 2025, with a $340,000 USDC budget and additional incentives, aiming to support chain success and asset deployment across several blockchains, while pausing some projects and discontinuing StakedCOMP. Community reaction is generally supportive with minor concerns about compensation overlap, and no next steps have been decided.","lastPost":"2025-04-23T19:36:08.416Z","created":"2025-04-11T17:19:42.049Z","views":244,"slug":"compound-growth-program-interim-extension","replies":0,"postCount":4,"likes":5,"score":1813.8405381004177,"totalWordsAllPosts":917,"totalWordsSummary":281,"updated":1745445759374,"protocol":"compound","discussionUrl":"https://www.comp.xyz","author":{"username":"AlphaGrowth","url":"https://www.comp.xyz/u/AlphaGrowth"},"relatedLinks":["https://www.comp.xyz/t/compound-growth-program-2025-renewal-alphagrowth-v4/6563/78"],"globalTags":["Grants - Grant Program Update"],"localTags":["Compound Growth Program","StakedCOMP","USDC incentives","Asset deployment","Compensation overlap"],"headline":"Proposal to Extend Compound Growth Program to July 2025 with $340K USDC Budget and Incentive Changes","type":"discussion"},{"id":"682","number":"682","title":"[Aavechan] onboard stS on Sonic Instance","description":"Forum: https://governance.aave.com/t/arfc-add-sts-to-aave-v3-sonic-instance/21445","summary":"$9e","tldr":"This pull request proposes adding support for the stS token to the Aave V3 Sonic instance, enabling users to supply and borrow stS and introducing a new \\\"stS/wS\\\" eMode category with specific risk parameters. The main benefit is increased utility and flexibility for stS holders, with no explicit costs or community reactions mentioned.","created":"2025-04-18T13:20:33Z","updated":"2025-04-23T19:11:53Z","merged":null,"sha":"ff71f08bfd8d2e11649d8d255f6517621ed992bd","link":"https://github.com/bgd-labs/aave-proposals-v3/pull/682","state":"open","commits":5,"additions":823,"deletions":0,"changedFiles":6,"score":399.8702700899275,"owner":"bgd-labs","repo":"aave-proposals-v3","protocol":"aave","headline":"Aave V3 Sonic Proposes stS Token Support and New eMode Category","type":"pr"},{"id":"553","number":"553","title":"Increase Unichain target block buffer","description":"Increase Unichain target block delta to handle measured latency","summary":"$9f","tldr":"This update to UniswapX introduces chain-specific target block buffers for priority orders, allowing more precise timing and potentially better execution across different blockchain networks. Developers must update their code to use the new chain-specific configuration, but there are no direct costs or noted community reactions mentioned.","created":"2025-04-23T18:56:42Z","updated":"2025-04-23T19:08:32Z","merged":"2025-04-23T19:08:30Z","sha":"4a2d57cb645aa6c77b9c1a5e4c6b3dbfd1354f89","link":"https://github.com/Uniswap/uniswapx-service/pull/553","state":"closed","commits":1,"additions":16,"deletions":3,"changedFiles":3,"score":42.4280745163797,"owner":"Uniswap","repo":"uniswapx-service","protocol":"uniswap","headline":"UniswapX Update Adds Chain-Specific Target Block Buffers for Priority Orders","type":"pr"},{"id":"679","number":"679","title":"[Aavechan] tbtc listing","description":null,"summary":"$a0","tldr":"This pull request adds tBTC as a new asset on Aave V3 on Arbitrum by deploying a contract that handles its setup, allowing users to supply and borrow tBTC with specific risk and usage parameters. The main benefit is increased asset diversity on Aave V3, with no explicit costs mentioned and no community reaction provided.","created":"2025-04-16T19:47:59Z","updated":"2025-04-23T19:05:04Z","merged":null,"sha":"dfec8d49afa72afd310549bf7bbe5812c3aafcec","link":"https://github.com/bgd-labs/aave-proposals-v3/pull/679","state":"open","commits":8,"additions":709,"deletions":0,"changedFiles":6,"score":473.23738910244003,"owner":"bgd-labs","repo":"aave-proposals-v3","protocol":"aave","headline":"tBTC Added as New Asset on Aave V3 Arbitrum Deployment","type":"pr"},{"id":"680","number":"680","title":"[Aavechan] llamarisk renew","description":null,"summary":"$a1","tldr":"This proposal seeks to renew LlamaRisk as the Risk Service Provider for the Aave v3 Ethereum Lido pool by streaming 1,000,000 aEthLidoGho tokens to LlamaRisk over 365 days, ensuring ongoing risk assessment services for protocol safety. The implementation involves a smart contract that automates the funding stream, with no mention of community reaction or additional costs beyond the token allocation.","created":"2025-04-16T19:49:36Z","updated":"2025-04-23T18:59:12Z","merged":"2025-04-23T18:59:11Z","sha":"cf0dfb79aeacfb15a3eb42a534f6f655e4c09a74","link":"https://github.com/bgd-labs/aave-proposals-v3/pull/680","state":"closed","commits":6,"additions":420,"deletions":0,"changedFiles":6,"score":627.6916339756682,"owner":"bgd-labs","repo":"aave-proposals-v3","protocol":"aave","headline":"Proposal to Renew LlamaRisk as Risk Service Provider for Aave v3 Ethereum Lido Pool with Automated Token Streaming","type":"pr"},{"id":"778","number":"778","title":"Fix parsing of custom genesis time","description":"## 📝 Summary\r\n\r\nI made an incorrect change when updating `urfave/cli` here:\r\n* #771\r\n\r\nApparently, `cmd.Uint64` thinks the value isn't found and returns 0.\r\n\r\nNote that this fix is not urgent. It only affects logs when testing with a devnet. Eg this:\r\n\r\nhttps://github.com/flashbots/mev-boost/blob/ee0c91c42fc0d49254498e4d016159fb828c8d8c/server/get_payload.go#L100-L106\r\n\r\n---\r\n\r\n## ✅ I have run these commands\r\n\r\n* [x] `make lint`\r\n* [x] `make test-race`\r\n* [x] `go mod tidy`\r\n","summary":"## What is this about?\\n\\nThis change fixes how the `genesisTime` is parsed from the command line interface (CLI).\\n\\n## Why is this important?\\n\\nCorrectly parsing the `genesisTime` is crucial for the program to function as expected, especially when a custom genesis time is specified.\\n\\n## How does it work?\\n\\nThe `cmd.Uint` function is used to parse the `genesisTime` from the CLI, and the result is then converted to a `uint64`.\\n\\n## What should developers know?\\n\\n* The `genesisTime` variable is now correctly parsed as a `uint64` from the CLI.\\n* The entry point for this change is within the CLI argument parsing section of `main.go`.\\n","tldr":"This update ensures that the `genesisTime` argument is accurately parsed as a `uint64` from the CLI in `main.go`, which is essential for correct program operation when a custom genesis time is set. The main benefit is improved reliability in handling the `genesisTime` parameter, with no additional costs mentioned.","created":"2025-04-23T14:21:08Z","updated":"2025-04-23T18:56:59Z","merged":"2025-04-23T18:56:59Z","sha":"28d3a55a18d735d96605cdfc22bb1d2b55e2abdf","link":"https://github.com/flashbots/mev-boost/pull/778","state":"closed","commits":1,"additions":1,"deletions":1,"changedFiles":1,"score":0.011250000000000001,"owner":"flashbots","repo":"mev-boost","protocol":"flashbots","headline":"Flashbots updates CLI to reliably parse genesisTime as uint64 for custom configurations","type":"pr"},{"id":25489,"title":"[RFC] Deploy Uniswap V3 on XDC Network","summary":"$a2","tldr":"Uniswap V3 has been fully deployed on the XDC Network, an EVM-compatible blockchain optimized for institutional finance and RWAs, with no further DAO action required. This integration offers low fees and new DeFi opportunities for enterprises, but there has been no community discussion or next steps identified.","lastPost":"2025-04-23T18:45:34.877Z","created":"2025-04-23T18:42:47.659Z","views":13,"slug":"rfc-deploy-uniswap-v3-on-xdc-network","replies":0,"postCount":1,"likes":0,"score":171.46858743497398,"totalWordsAllPosts":696,"totalWordsSummary":224,"updated":1745446336332,"protocol":"uniswap","discussionUrl":"https://gov.uniswap.org","author":{"username":"0xbeny","url":"https://gov.uniswap.org/u/0xbeny"},"relatedLinks":[],"globalTags":["Changes - New deployment","Newsworthy - Technical"],"localTags":["Uniswap V3","XDC Network","EVM-compatible","Institutional finance","RWAs","DeFi opportunities","Enterprise DeFi"],"headline":"Uniswap V3 Fully Deployed on XDC Network, Enabling Low-Fee DeFi for Enterprises","type":"discussion"},{"id":"684","number":"684","title":"feat: onboard pendle pt assets","description":null,"summary":"$a3","tldr":"This pull request adds two new assets, PT-sUSDe-31JUL2025 and PT-eUSDe-29MAY2025, to Aave V3 and activates the Edge Automated Governance Risk System (AGRS) for automated risk management, expanding user options and improving protocol safety. The update involves new contracts for asset onboarding, eMode configuration, and risk admin changes, with no mentioned costs or community feedback.","created":"2025-04-23T12:08:26Z","updated":"2025-04-23T18:41:06Z","merged":null,"sha":"1e75878494001a3fd21531a54133dca9284c9a87","link":"https://github.com/bgd-labs/aave-proposals-v3/pull/684","state":"open","commits":2,"additions":1815,"deletions":0,"changedFiles":13,"score":404.70998925886147,"owner":"bgd-labs","repo":"aave-proposals-v3","protocol":"aave","headline":"Aave V3 Adds PT-sUSDe-31JUL2025 and PT-eUSDe-29MAY2025 Assets, Activates Automated Governance Risk System","type":"pr"},{"id":9959,"title":"Lido × Giveth QF Round to Fund Public Goods","summary":"$a4","tldr":"This is a proposal for Lido to partner with Giveth on a Quadratic Funding round, allocating around $53.5K to support public goods and boost Lido’s visibility in the Ethereum ecosystem, with benefits including increased funding for projects and broader community engagement. There have been no community discussions or next steps decided.","lastPost":"2025-04-23T18:41:02.021Z","created":"2025-04-23T18:41:01.948Z","views":6,"slug":"lido-x-giveth-qf-round-to-fund-public-goods","replies":0,"postCount":1,"likes":0,"score":63.500200040008004,"totalWordsAllPosts":638,"totalWordsSummary":250,"updated":1745445948544,"protocol":"lido","discussionUrl":"https://research.lido.fi","author":{"username":"kechy","url":"https://research.lido.fi/u/kechy"},"relatedLinks":[],"globalTags":["Proposal - Seeking feedback","Grants - Grant Proposal / Application"],"localTags":["Lido","Giveth","Quadratic Funding","Public Goods Funding"],"headline":"Lido Proposal: $53.5K Quadratic Funding Partnership with Giveth to Support Public Goods","type":"discussion"},{"id":6528,"title":"Request for Information on Disputes #GDR-33","summary":"$a5","tldr":"This discussion is about a dispute regarding whether an indexer closed allocations on the Graph Network Arbitrum subgraph while unsynced, with both parties providing technical evidence and requesting further data to clarify the timeline and state of the subgraph. With only 5 replies, community reaction is limited, focusing mainly on evidence exchange and clarification, and no next actions have been decided.","lastPost":"2025-04-23T18:33:25.601Z","created":"2025-04-18T15:11:50.868Z","views":44,"slug":"request-for-information-on-disputes-gdr-33","replies":3,"postCount":6,"likes":0,"score":2371.3838719314845,"totalWordsAllPosts":968,"totalWordsSummary":639,"updated":1745446325391,"protocol":"thegraph","discussionUrl":"https://forum.thegraph.com","author":{"username":"absolutelyNot","url":"https://forum.thegraph.com/u/absolutelyNot"},"relatedLinks":[],"globalTags":[],"localTags":["Dispute","Indexer","Graph Network","Arbitrum subgraph","Allocation closure","Unsynced state","Technical evidence","Timeline clarification","Community reaction"],"headline":"Dispute Over Indexer Allocation Timing on The Graph Arbitrum Subgraph Spurs Evidence Exchange","type":"discussion"},{"id":"2804","number":"2804","title":"[ENG-4] Add cross-margin launch for listings","description":"$a6","summary":"$a7","tldr":"This update to the `CreatePerpetual` function in `listing.go` introduces a `CrossLaunch` flag that dynamically sets the `marketType` for new perpetual markets, enabling support for both cross and isolated market types. The main benefit is increased flexibility in market creation, with no costs or community reactions mentioned.","created":"2025-04-23T17:40:52Z","updated":"2025-04-23T18:33:20Z","merged":"2025-04-23T18:33:19Z","sha":"656601fce0941780fec9de398e129dbb2e00bdac","link":"https://github.com/dydxprotocol/v4-chain/pull/2804","state":"closed","commits":3,"additions":20,"deletions":5,"changedFiles":2,"score":151.5808313727347,"owner":"dydxprotocol","repo":"v4-chain","protocol":"dydx","headline":"dydx Adds CrossLaunch Flag to CreatePerpetual for Flexible Market Type Support","type":"pr"}]},"allProposals":[{"currentStatus":"created","currentStatusSinceTx":"0x07c9b6898966765816e7b0ab830dcb3a60ef6e3474bf6046bf2ed8a36e3e7db9","votingStartBlock":22344227,"proposer":"0x393BC37ea5493233D2bDC68FD59Dd97Ee01B18Cf","quorum":2.5e+24,"description":"\"This proposal will execute the revoke function on Wonderland's vesting contract, following the successful completion of their work with Grants Lab as outlined in the original July 2023 proposal.\\n\\nAs agreed with Wonderland, this action will:\\n\\n* Stop the remaining vesting schedule\\n* Transfer already vested tokens to Wonderland\\n* Return any unvested tokens to the Gitcoin treasury\\n\\nWonderland has successfully delivered their technical and product management support for Grants Lab over the contracted period. This cancellation represents the planned conclusion of our engagement.\\n\\nIt's been a valuable partnership with the Wonderland team, and we look forward to potential future collaborations.\\n\\nOriginal proposal below.\"","votingEndTime":1746045467,"votingStartTime":1745561627,"id":"17479554285430824235935339015686957231675135320692618616781702573982249581366","title":"# [REPOST] Revoke Wonderland Vesting Contract - Contract Termination","votingEndBlock":22384547,"summary":"## What is this about?\n\nThis proposal seeks to execute the revoke function on Wonderland's vesting contract, marking the official termination of their agreement with Gitcoin after Wonderland completed its technical and product management support for Grants Lab as per the July 2023 arrangement. The action will halt the remaining vesting schedule, transfer vested tokens to Wonderland, and return any unvested tokens to the Gitcoin treasury. The proposal notes the successful partnership and concludes the engagement as planned.\n\n## What could be the impact of this?\n\nThe immediate impact will be the cessation of further token vesting to Wonderland, ensuring only earned tokens are transferred while unvested tokens are reclaimed by the Gitcoin treasury. This maintains financial accountability and aligns with the original agreement terms. It also sets a precedent for clear contract closure processes and preserves the possibility of future collaborations between Gitcoin and Wonderland.","tldr":"This proposal is about formally ending the agreement between Wonderland and Gitcoin by revoking Wonderland's vesting contract, transferring only the vested tokens to Wonderland and returning unvested tokens to the Gitcoin treasury. The benefits include financial accountability, adherence to the original agreement, and establishing a clear process for contract closure, with no additional costs mentioned.","searchKeywords":["Wonderland","Gitcoin","Vesting contract","Revoke function","Termination","Agreement","Grants Lab","July 2023","Technical support","Product management","Token vesting","Transfer vested tokens","Return unvested tokens","Gitcoin treasury","Financial accountability","Contract closure","Future collaboration","Partnership","Proposal"],"globalTags":["Proposal - Seeking feedback"],"localTags":["Vesting contract","Contract termination","Gitcoin treasury","Wonderland","Grants Lab","Token vesting","Partnership conclusion"],"headline":"Gitcoin Proposes Termination of Wonderland Vesting Contract, Returning Unvested Tokens to Treasury","updated":1745415999,"timestamp":{"_seconds":1745416018,"_nanoseconds":360000000},"type":"onchain","governor":"v2","protocol":"gitcoin"},{"currentStatus":"created","currentStatusSinceTx":"0x020b82b4167769f6d970b692bc9148804e1c4781478bb0e9ad560dffc3120811","votingStartBlock":22339849,"proposer":"0x8787FC2De4De95c53e5E3a4e5459247D9773ea52","quorum":4e+25,"description":"$a8","votingEndTime":1745992475,"votingStartTime":1745508635,"id":"85","title":"# Establish Uniswap v4 Licensing Process","votingEndBlock":22380169,"summary":"$a9","tldr":"This proposal establishes a formal, transparent process for licensing and deploying Uniswap v4 under the BSL, including onchain registries and a blanket exemption for the Uniswap Foundation to deploy on DAO-approved chains, with the BSL in effect until June 15, 2027. The benefits include faster v4 adoption, a stronger competitive position, improved developer and LP incentives, and enhanced transparency, with no explicit costs or community reactions mentioned.","searchKeywords":["Uniswap","Uniswap v4","Accountability Committee","abdullahumar","juanbug","alicecorsini","Business Source License","BSL","Formal licensing","Deployment process","ENS subdomain","v4-core-license-grants.uniswap.eth","BSL license exemptions","Uniswap Foundation","Blanket license exemption","DAO-approved chain","Expansion","v4deployments.uniswap.eth","Onchain registry","Official v4 deployments","Base","Governance process","Single-chain exemption","Blanket exemption","Funding requests","MIT license","June 15, 2027","Accelerated adoption","Competitive moat","Unauthorized forks","Ecosystem partners","Developer incentives","LP incentives","Hooks","Liquidity providers","Transparency","Governance","Authoritative records","Trust","Coordination","Scalable expansion","Deployers","Front-end providers","RFP","Growth"],"globalTags":["Proposal - Seeking feedback","Changes - Legal","Changes - New deployment","Newsworthy - Affecting Governance"],"localTags":["Uniswap v4","Business Source License","BSL license exemptions","ENS subdomain","v4-core-license-grants.uniswap.eth","Uniswap Foundation","DAO-approved chain","v4deployments.uniswap.eth","onchain registry","Accountability Committee","Base","MIT license","RFP process"],"headline":"Uniswap Proposal Seeks Formalized v4 Licensing, Onchain Deployment Registry, and Streamlined Expansion","updated":1745354727,"timestamp":{"_seconds":1745354736,"_nanoseconds":425000000},"type":"onchain","governor":"governance","protocol":"uniswap"},{"currentStatus":"created","currentStatusSinceTx":"0x512cb111adc657679464cfbe315f42f1d3f7b0a01a9470fd781790b73226ec98","votingStartBlock":10585559,"proposer":"0x84165355AFbFB553f3a58f1C6f3b5e2E7d7C244d","quorum":1e+26,"description":"$aa","votingEndTime":1745708064,"votingStartTime":1745448864,"id":"94","title":"# MIP-X20: Gauntlet's Monthly Recommendations (04/17/2025)","totalWeightFor":10000000000000000000,"totalWeight":10000000000000000000,"score":0,"decayedScore":0,"proposalResults":"## How is the community reacting?\n\n- The proposal has a total voting weight of 10.00.\n- The quorum required is 100,000,000.00, meaning the current participation is extremely low (0.00% of quorum reached).\n- Only 10.00 weight has voted \"For\" so far.\n- The community appears to be largely disengaged or unaware of this proposal at this stage, with almost no participation relative to the quorum requirement.","summary":"$ab","tldr":"MIP-X20 proposes Gauntlet's monthly risk parameter updates for Moonwell on Base, Optimism, and Moonbeam, aiming to optimize risk and capital efficiency by adjusting collateral factors, reserve factors, caps, and interest rates for multiple assets. While these changes could improve protocol safety and efficiency, community engagement is currently extremely low, with almost no votes cast relative to the required quorum.","globalTags":["Proposal - Seeking feedback","Changes - Technical Change"],"localTags":["MIP-X20","Gauntlet","Risk parameter recommendations","Moonwell","Base","Optimism","Moonbeam","Collateral factors","Reserve factors","Supply caps","Borrow caps","Interest rate parameters","Guardian","USDC","EURC","cbBTC","LBTC","tBTC","USDT","DAI","WETH","WGLMR","xcUSDC","USDC.wh","FRAX","WBTC.wh"],"headline":"Gauntlet Proposes Risk Parameter Updates for Moonwell on Base, Optimism, and Moonbeam","updated":1745462247,"searchKeywords":["MIP-X20","Gauntlet","Risk parameter recommendations","Moonwell","Base","Optimism","Moonbeam","Collateral factors","Reserve factors","Supply caps","Borrow caps","Interest rate parameters","Guardian","USDC","EURC","cbBTC","LBTC","tBTC","USDT","DAI","WETH","WGLMR","xcUSDC","USDC.wh","FRAX","WBTC.wh","Protocol safety","Capital efficiency","Market conditions","Lending","Borrowing","Forum post","Terms of service"],"timestamp":{"_seconds":1745462252,"_nanoseconds":875000000},"type":"onchain","governor":"govMultichain","protocol":"moonwell"},{"currentStatus":"created","currentStatusSinceTx":"0x5299aea1c032ac9d06c38effc2ce990778d98d3c5072d2538a8cb12f6a62eefa","votingStartBlock":22332664,"countingMode":"support=bravo&quorum=for,abstain","proposer":"0xb8c2C29ee19D8307cb7255e1Cd9CbDE883A267d5","quorum":1e+24,"description":"$ac","votingEndTime":1745972735,"votingStartTime":1745422883,"id":"51329136884099251878034959419745117799040381230875971532699817044496491926852","title":"# [6.7] [Executable] Transfer .ceo TLD to the DNSSEC registrar","votingEndBlock":22378482,"score":0,"decayedScore":0,"summary":"## What is this about?\n\nThis proposal seeks to transfer the .ceo TLD from its current custom address (set by the previous owner for bespoke DNS integration) back to the DNSSEC registrar. The new owner, XYZ, has requested this change so that .ceo TLD holders can use the standard DNSSEC integration to claim their names on ENS. Ownership verification was demonstrated by setting a TXT record on `_ens.nic.ceo` pointing to the DNSSEC registrar's address. The technical action involves calling `setSubnodeOwner` on the ENS Root contract with the appropriate parameters.\n\n## What could be the impact of this?\n\nIf approved, the .ceo TLD will be managed by the DNSSEC registrar, enabling standard DNSSEC-based name claiming for .ceo domains on ENS. This would simplify integration for .ceo domain holders and align .ceo with the standard ENS DNSSEC workflow, potentially increasing usability and adoption.","searchKeywords":[".ceo","TLD","transfer","custom address","previous owner","bespoke DNS integration","DNSSEC registrar","XYZ","TLD holders","standard DNSSEC integration","claim names","ENS","ownership verification","TXT record","_ens.nic.ceo","technical action","setSubnodeOwner","ENS Root contract","parameters","impact","managed by DNSSEC registrar","DNSSEC-based name claiming","simplify integration","usability","adoption"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change"],"localTags":[".ceo TLD","DNSSEC registrar","ENS Root contract","setSubnodeOwner","XYZ (owner)","DNSSEC integration","ENS DNSSEC workflow"],"totalVotersFor":16,"totalVoters":16,"totalWeightFor":4.4106194332162e+23,"totalWeight":4.4106194332162e+23,"proposalVoteReasons":"No proposal results or reasoning were provided to summarize.","proposalResults":"## How is the community reacting?\n\n- Total of 16 voters participated, all voting \"for\" the proposal.\n- The total voting weight in favor is 441,061.94.\n- The required quorum is 1,000,000.00, which only counts \"for\" and \"abstain\" votes.\n- The quorum has not been met; 558,938.06 more voting weight is needed.\n- Community participation is low relative to the quorum requirement, indicating limited engagement or support at this stage.","tldr":"This proposal aims to transfer the .ceo TLD to the DNSSEC registrar, allowing .ceo domain holders to use standard DNSSEC-based claiming on ENS, which would improve usability and integration. While all 16 voters supported the proposal with a total voting weight of 441,061.94, the required quorum of 1,000,000.00 was not met, indicating low community participation.","headline":"Proposal to Transfer .ceo TLD Back to DNSSEC Registrar for Standard ENS Integration","updated":1745462216,"timestamp":{"_seconds":1745462218,"_nanoseconds":209000000},"type":"onchain","governor":"governance","protocol":"ens"},{"currentStatus":"started","currentStatusSinceTx":"0x1ddd4e8b4965c0cf59d167751924d114ef53ed43d20ea25bccba3ccff445e71b","metadata":"$ad","votingStartBlock":22332246,"ipfsData":"$ae","proposer":"0xf73a1260d222f447210581DDf212D915c09a3249","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreifxv3nmowbp3trdwzb3ybyrlhbjccchesmweaoicmua25lqto2xte","votingEndTime":1745849855,"votingStartTime":1745417855,"id":"185","cid":"bafkreifxv3nmowbp3trdwzb3ybyrlhbjccchesmweaoicmua25lqto2xte","score":0,"decayedScore":0,"summary":"$af","searchKeywords":["Lido","Ethereum","Pectra Fork","Oracle contracts","CS Verifier contract","Community Staking Module","Accounting Oracle","Validator Exit Bus Oracle","CS Fee Oracle","Consensus version upgrade","Slashing report removal","gIndexes structure","Aragon Agent","Role management","Composable Security","MixBytes","Ackee Blockchain","Audit","Protocol stability","Security","Governance","Stakers","Technical compatibility","Disruption risk","Operational safety"],"globalTags":["Security - Audit","Changes - Technical Change","Proposal - Seeking feedback","Newsworthy - Technical","Newsworthy - Affecting Governance"],"localTags":["Lido","Ethereum Pectra Fork","Oracle contract upgrade","CS Verifier contract","Community Staking Module","Aragon Agent","Composable Security","MixBytes","Ackee Blockchain"],"totalVotersFor":11,"totalVoters":11,"totalWeightFor":4.175771922617099e+24,"totalWeight":4.175771922617099e+24,"proposalResults":"## How is the community reacting?\n\n- All 11 voters (100%) supported the proposal.\n- The total voting weight was 4,175,771.92, with 100% of this weight in favor.\n- No votes were cast against the proposal.\n- Community reaction is unanimously positive, indicating strong consensus and support for the proposal.","tldr":"This proposal updates key Lido oracle and verifier contracts to ensure compatibility and stability with the Ethereum Pectra Fork, with all changes audited and specific role management included. The community unanimously supports the proposal, with no opposition and full voting weight in favor.","headline":"Lido Proposes Oracle and Verifier Contract Upgrades for Ethereum Pectra Fork Compatibility","updated":1745462226,"timestamp":{"_seconds":1745462228,"_nanoseconds":30000000},"type":"onchain","governor":"voting","protocol":"lido"},{"currentStatus":"started","currentStatusSinceTx":"0x84bd58dc1d9b6692339c63b38765a241ba72288adedac98826c64bdcb0e7f1fb","metadata":"ipfs:bafkreihwwyefxfb45gwwewzyh47shlppcymlu2zck6yw4cwarou5dzs7ki","votingStartBlock":22328018,"ipfsData":"Add a gauge for the following Stableswap NG pool: msETH/OETH","proposer":"0xD4f9FE0039Da59e6DDb21bbb6E84e0C9e83D73eD","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreihwwyefxfb45gwwewzyh47shlppcymlu2zck6yw4cwarou5dzs7ki","votingEndTime":1745971547,"votingStartTime":1745366747,"id":"1039","cid":"bafkreihwwyefxfb45gwwewzyh47shlppcymlu2zck6yw4cwarou5dzs7ki","summary":"## What is this about?\n\nThis proposal suggests adding a gauge for the Stableswap NG pool consisting of msETH and OETH. The gauge would enable liquidity providers in this pool to receive CRV rewards. The proposal includes a reference to additional metadata stored on IPFS.\n\n## What could be the impact of this?\n\nIf approved, the msETH/OETH pool would become eligible for CRV emissions, potentially increasing liquidity and trading activity in the pool. This could enhance the utility and attractiveness of both msETH and OETH on Curve, and may incentivize more users to provide liquidity to this specific pool.","tldr":"This proposal aims to add a gauge for the msETH/OETH Stableswap NG pool, allowing liquidity providers to earn CRV rewards and potentially increasing liquidity and trading activity. If approved, it could make msETH and OETH more attractive on Curve, with no costs or community reactions mentioned.","searchKeywords":["Stableswap NG","msETH","OETH","Gauge","CRV rewards","Curve","Liquidity providers","Liquidity","Trading activity","CRV emissions","Pool","Utility","Attractiveness","Incentivize","IPFS metadata"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Token Distribution"],"localTags":["Stableswap NG","msETH","OETH","CRV rewards","Curve","Gauge","IPFS metadata"],"headline":"Proposal to Add Gauge for msETH/OETH Stableswap NG Pool on Curve","updated":1745370050,"timestamp":{"_seconds":1745370053,"_nanoseconds":435000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"id":"0x13c7ed7662af458af664ce60553606ac4539ca2535e1f61a1ac62aa3d9aeca41","title":"GMX V2 Deployment on Spiderchain","summary":"$b0","tldr":"This proposal is about deploying GMX V2 on Botanix Labs’ Spiderchain to enable BTC-collateralized perpetual markets with Bitcoin security, EVM compatibility, and cross-chain integrations, offering expanded access and fee flows for GMX stakers. The community is showing near-unanimous support, and if approved, the next steps include finalizing partnership terms, implementation, audits, and launching incentives and marketing.","protocol":"gmx","slug":"gmx-v2-deployment-on-spiderchain","snapshotUrl":"https://snapshot.box/#/s:gmx.eth/proposal/0x13c7ed7662af458af664ce60553606ac4539ca2535e1f61a1ac62aa3d9aeca41","startDate":1745346420,"endDate":1745836200,"updated":1745460053,"relatedLinks":["https://snapshot.box/#/s:gmx.eth/proposal/0x13c7ed7662af458af664ce60553606ac4539ca2535e1f61a1ac62aa3d9aeca41","https://gov.gmx.io/t/gmx-v2-hybrid-deployment-on-botanix/4500"],"state":"active","results":{"quorum":0,"totalScores":"31325.74","totalVotes":170,"choices":[{"id":0,"name":"For","scores":"31230.80"},{"id":1,"name":"Against","scores":"94.92"},{"id":2,"name":"Abstain","scores":"0.03"}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Seeking feedback","Changes - New deployment","Security - Audit"],"localTags":["GMX V2","Botanix Labs","Spiderchain","BTC-collateralized perpetual markets","Bitcoin security","EVM compatibility","Cross-chain integrations","GMX stakers","Partnership terms","Incentives","Marketing"],"headline":"Proposal to Deploy GMX V2 on Botanix Spiderchain for BTC-Collateralized Perpetual Markets","type":"snapshot"},{"id":"0x911e9b447bf0aa21efd1594aea23b2cbc8397dc374ebe417a5cb60c65e14beec","title":"SIP #3 - Community Bounty Pool","summary":"## What is this about?\n\nThis proposal (SIP #3) asks the community to advise the Superfluid Foundation on which provider—SHERLOCK or IMMUNEFI—should be chosen to implement a \"Community Bounty Pool.\" The bounty pool is intended to incentivize community contributions, with the provider managing the process.\n\n## What could be the impact of this?\n\nSelecting a provider will determine how the Community Bounty Pool is managed, potentially affecting the effectiveness, security, and engagement of community-driven initiatives. The chosen provider will play a key role in how bounties are distributed and how contributions are rewarded.\n\n## How is the community reacting?\n\nThe vote is ongoing, with strong participation (over 12.8 million votes cast, well above the 1 million quorum). SHERLOCK is currently leading with a significant majority of the votes (over 11.5 million), while IMMUNEFI has about 1.25 million votes. This indicates a clear community preference for SHERLOCK at this stage.","tldr":"This is about the Superfluid Foundation seeking community input on whether SHERLOCK or IMMUNEFI should manage its Community Bounty Pool, which will impact how bounties are distributed and community contributions are rewarded. The community is actively participating in the vote, with SHERLOCK currently favored by a large majority.","protocol":"superfluid","slug":"sip-3-community-bounty-pool","snapshotUrl":"https://snapshot.box/#/s:superfluid.eth/proposal/0x911e9b447bf0aa21efd1594aea23b2cbc8397dc374ebe417a5cb60c65e14beec","startDate":1745334343,"endDate":1745791543,"updated":1745460638,"relatedLinks":["https://snapshot.box/#/s:superfluid.eth/proposal/0x911e9b447bf0aa21efd1594aea23b2cbc8397dc374ebe417a5cb60c65e14beec","https://forum.superfluid.org/t/sip-community-bounty-pool/162"],"state":"active","results":{"quorum":1000000,"totalScores":"12847180.66","totalVotes":19,"choices":[{"id":0,"name":"SHERLOCK","scores":"11594911.15"},{"id":1,"name":"IMMUNEFI","scores":"1252269.52"}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Currently voting"],"localTags":["Superfluid Foundation","Community Bounty Pool","SHERLOCK","IMMUNEFI","Bounty management","Community vote"],"headline":"Superfluid Foundation Seeks Community Vote on SHERLOCK vs IMMUNEFI for Bounty Pool Management","type":"snapshot"},{"currentStatus":"started","currentStatusSinceTx":"0xe54466d2d4d0712298f6c52a13810b62da90f01c53227a8f6c2039f7c43b2a33","metadata":"ipfs:bafkreiff4l6wx3eaia7jfxsvoy3cg6llnnievct2iyn4rbq23e6anjrkjm","votingStartBlock":22325139,"ipfsData":"Add gauges for the following CrossCurve pools on Sonic: Ethereum Pools (xE-series), https://gov.curve.fi/t/proposal-to-add-crosscurve-pools-on-sonic-to-the-gauge-controller/10589#ethereum-pools-xe-series-6","proposer":"0x5802ad5D5B1c63b3FC7DE97B55e6db19e5d36462","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreiff4l6wx3eaia7jfxsvoy3cg6llnnievct2iyn4rbq23e6anjrkjm","votingEndTime":1745936855,"votingStartTime":1745332055,"id":"1038","cid":"bafkreiff4l6wx3eaia7jfxsvoy3cg6llnnievct2iyn4rbq23e6anjrkjm","summary":"## What is this about?\n\nThis proposal seeks to add gauges for the CrossCurve pools on Sonic, specifically targeting the Ethereum Pools (xE-series). The proposal references further details and discussion on the Curve governance forum and provides an IPFS link for metadata.\n\n## What could be the impact of this?\n\nIf approved, these CrossCurve pools on Sonic would become eligible for CRV emissions via the gauge controller, potentially increasing liquidity and usage of these pools. This could enhance yield opportunities for liquidity providers and further integrate Sonic-based pools into the Curve ecosystem.","tldr":"This proposal aims to add gauges for CrossCurve pools on Sonic (xE-series Ethereum Pools), making them eligible for CRV emissions and potentially increasing liquidity and yield for providers. If approved, it would further integrate Sonic-based pools into the Curve ecosystem.","searchKeywords":["CrossCurve pools","Sonic","Ethereum Pools","xE-series","Curve governance forum","IPFS","Metadata","CRV emissions","Gauge controller","Liquidity","Usage","Yield opportunities","Liquidity providers","Integration","Curve ecosystem"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Technical"],"localTags":["CrossCurve pools","Sonic","Ethereum Pools","xE-series","Curve governance forum","IPFS metadata","CRV emissions","Gauge controller","Liquidity providers","Sonic-based pools","Curve ecosystem"],"headline":"Proposal to Add Gauges for CrossCurve Pools on Sonic to Enable CRV Emissions","updated":1745339398,"timestamp":{"_seconds":1745339407,"_nanoseconds":150000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"currentStatus":"started","currentStatusSinceTx":"0x0721cdf8a7cc29cabfab47dd9c7fb63ec38975147800d3793f41209c5c674670","metadata":"ipfs:bafkreicllepsogm4silhfsu5qkjjhdyddsfybcco43gfzpwguumfs4by2m","votingStartBlock":22324956,"ipfsData":"Add gauges for the following CrossCurve pools on Sonic: Stablecoin Pools (xS-series), https://gov.curve.fi/t/proposal-to-add-crosscurve-pools-on-sonic-to-the-gauge-controller/10589#stablecoin-pools-xs-series-5","proposer":"0x7ebA24233f7b5966047F637aec558dfF3344883f","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreicllepsogm4silhfsu5qkjjhdyddsfybcco43gfzpwguumfs4by2m","votingEndTime":1745934659,"votingStartTime":1745329859,"id":"1037","cid":"bafkreicllepsogm4silhfsu5qkjjhdyddsfybcco43gfzpwguumfs4by2m","summary":"## What is this about?\n\nThis proposal suggests adding gauges for CrossCurve pools on Sonic, specifically targeting the Stablecoin Pools (xS-series). The proposal references further details and discussion in the Curve governance forum and provides an IPFS link for metadata. The voting period is set from April 22, 2025, to April 29, 2025.\n\n## What could be the impact of this?\n\nIf approved, the addition of gauges for these CrossCurve pools on Sonic would enable liquidity providers in the xS-series stablecoin pools to earn CRV rewards. This could incentivize deeper liquidity, potentially increasing the utility and adoption of these pools within the Curve ecosystem.","tldr":"This proposal seeks to add gauges for CrossCurve xS-series stablecoin pools on Sonic, allowing liquidity providers to earn CRV rewards and potentially boosting liquidity and adoption in the Curve ecosystem. The voting period is from April 22, 2025, to April 29, 2025.","searchKeywords":["CrossCurve pools","Sonic","Stablecoin Pools","xS-series","Curve","Gauges","Proposal","Curve governance forum","IPFS","Metadata","Voting period","April 22, 2025","April 29, 2025","CRV rewards","Liquidity providers","Incentivize","Deeper liquidity","Utility","Adoption","Curve ecosystem"],"globalTags":["Proposal - Currently voting"],"localTags":["CrossCurve pools","Sonic","Stablecoin Pools","xS-series","Curve governance forum","IPFS metadata","CRV rewards","Liquidity providers","Deeper liquidity","Curve ecosystem"],"headline":"Proposal to Add Gauges for CrossCurve xS-Series Pools on Sonic for CRV Rewards","updated":1745339398,"timestamp":{"_seconds":1745339402,"_nanoseconds":551000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"currentStatus":"started","currentStatusSinceTx":"0x3257ff4dec1638f44303062677ee5d2888475e847da4c3767377d7aa7822419c","metadata":"ipfs:bafkreic5gzob3bhol57y2vgynvluzkbugg35r7vtpdt4bbff7gwa5bnspa","votingStartBlock":22324807,"ipfsData":"Add gauges for the following CrossCurve pools on Sonic: Bitcoin Pools (xB-series), https://gov.curve.fi/t/proposal-to-add-crosscurve-pools-on-sonic-to-the-gauge-controller/10589#bitcoin-pools-xb-series-7","proposer":"0xf7Bd34Dd44B92fB2f9C3D2e31aAAd06570a853A6","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreic5gzob3bhol57y2vgynvluzkbugg35r7vtpdt4bbff7gwa5bnspa","votingEndTime":1745932859,"votingStartTime":1745328059,"id":"1036","cid":"bafkreic5gzob3bhol57y2vgynvluzkbugg35r7vtpdt4bbff7gwa5bnspa","summary":"## What is this about?\n\nThis proposal seeks to add gauges for the CrossCurve Bitcoin Pools (xB-series) on Sonic to the Curve gauge controller. The proposal references a detailed discussion on the Curve governance forum and provides metadata via IPFS.\n\n## What could be the impact of this?\n\nIf approved, the addition of these gauges would enable liquidity providers in the specified CrossCurve pools on Sonic to earn CRV rewards, potentially increasing liquidity and activity in these pools. This could further incentivize participation and growth within the Curve ecosystem, particularly for Bitcoin-related assets on Sonic.","tldr":"This proposal aims to add gauges for CrossCurve Bitcoin Pools (xB-series) on Sonic to the Curve gauge controller, allowing liquidity providers in these pools to earn CRV rewards. The main benefit is increased liquidity and participation in Bitcoin-related pools on Sonic, with no costs or community reactions mentioned.","searchKeywords":["CrossCurve","Bitcoin Pools","xB-series","Sonic","Curve","Gauge controller","Proposal","Governance forum","IPFS","Liquidity providers","CRV rewards","Increase liquidity","Curve ecosystem","Bitcoin assets","Incentivize participation","Growth","Technical change"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Technical"],"localTags":["CrossCurve Bitcoin Pools","xB-series","Sonic","Curve gauge controller","CRV rewards","Liquidity providers","Bitcoin-related assets"],"headline":"Proposal to Add CrossCurve Bitcoin Pool Gauges on Sonic to Curve Gauge Controller","updated":1745339399,"timestamp":{"_seconds":1745339403,"_nanoseconds":21000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"currentStatus":"created","currentStatusSinceTx":"0x2965f88e37c4776e4ecc89d67c494ddfa58280833a0818616ca9d5aca5723770","votingStartBlock":1745325911,"countingMode":"support=bravo&quorum=for,abstain","proposer":"0xc164411CCb8468E0c9F6a0Fc0B06E69f5845AC30","description":"$b1","votingEndTime":1745585111,"votingStartTime":1745325911,"id":"5967615389223014639863581541879335769946644973373342901142143540229222064268","title":"# [IP] eUSD Revenue Share Update 2025-04-15 ","votingEndBlock":1745585111,"summary":"$b2","searchKeywords":["eUSD","revenue share","distribution","Ugly Cash","Sentz","stRSR holders","RToken Champion","Sentz share reduction","stRSR share increase","fintech partners","eUSD holdings","market cap","bi-weekly update","onchain data","fintech wallet holdings","fair distribution","transparency","responsiveness","revenue allocation","stakeholders"],"globalTags":["Proposal - Seeking feedback","Newsworthy - Token Distribution"],"localTags":["eUSD","Ugly Cash","Sentz","stRSR","RToken Champion","Revenue share","Fintech partners","Bi-weekly update","Revenue allocation"],"score":0,"decayedScore":0,"quorum":-4217248528871107600,"totalVotersFor":4,"totalVoters":4,"totalWeightFor":5.658270654068476e+26,"totalWeight":5.658270654068476e+26,"proposalResults":"## How is the community reacting?\n\n- There were 4 voters in total, all of whom voted \"for\" the proposal.\n- The total voting weight \"for\" the proposal is 565,827,065.41.\n- No votes were cast as \"against\" or \"abstain.\"\n- The quorum is listed as -4.22, which is an unusual negative value.\n- The proposal has unanimous support from participating voters, but the negative quorum value may indicate a configuration or reporting issue.","tldr":"The proposal adjusts eUSD revenue shares by slightly decreasing Sentz's portion and increasing stRSR's, with updates now occurring bi-weekly for more accurate and transparent distribution. All participating voters supported the change, though a negative quorum value suggests a possible reporting issue.","headline":"Reserve updates eUSD revenue share: Sentz share reduced, stRSR increased, bi-weekly distribution introduced","updated":1745370073,"timestamp":{"_seconds":1745370075,"_nanoseconds":272000000},"type":"onchain","governor":"v2","protocol":"reserve"},{"currentStatus":"created","currentStatusSinceTx":"0x7f07d14b76c4ba8f326ac5986eeec848a9c6ff99e7708ff54473cd7f6e309f92","motionData":[{"tuple[]":"42"},{"tuple[]":"874"}],"votingStartBlock":22323717,"proposer":"0x08637515E85A4633E23dfc7861e2A9f53af640f7","description":"Set SDVT vetted validators limits","votingEndTime":1745574143,"motionTargets":["0xae7b191a31f627b4eb1d4dac64eab9976995b433"],"votingStartTime":1745314943,"id":"825","objectionsThreshold":5e+24,"summary":"## What is this about?\n\nThis proposal suggests setting limits for SDVT vetted validators within the Lido protocol. The voting period is from April 22, 2025, 9:42 AM to April 25, 2025, 9:42 AM. The proposal will pass unless it receives 5,000,000 or more weighted 'no' votes (objections).\n\n## What could be the impact of this?\n\nImplementing limits on SDVT vetted validators could affect the composition and decentralization of the validator set in Lido. It may influence validator participation, overall protocol security, and governance dynamics by controlling how many SDVT vetted validators can operate within the system.","tldr":"This proposal aims to set limits on SDVT vetted validators in the Lido protocol, with voting scheduled from April 22, 2025, 9:42 AM to April 25, 2025, 9:42 AM. The main benefit is potentially improved decentralization and governance control, while the cost could be reduced participation from SDVT vetted validators.","searchKeywords":["Lido","SDVT","vetted validators","validator limits","proposal","voting period","April 22, 2025","April 25, 2025","weighted no votes","objections","validator participation","protocol security","governance dynamics","decentralization","validator set","protocol","governance"],"globalTags":["Proposal - Currently voting","Newsworthy - Affecting Governance","Security"],"localTags":["Lido","SDVT vetted validators","Validator limits","Validator set composition","Protocol decentralization"],"headline":"Lido Proposal Seeks to Set Limits on SDVT Vetted Validators, Affecting Validator Composition and Decentralization","updated":1745323949,"timestamp":{"_seconds":1745323954,"_nanoseconds":825000000},"type":"onchain","governor":"easyTrack","protocol":"lido"},{"currentStatus":"created","currentStatusSinceTx":"0xaff32e118717093614ad4a30ec11cf2c15e69a47a7bf2fbd11b09a12b665a83d","motionData":[{"token":"0x6B175474E89094C44Da98b954EedeAC495271d0F","recipients":"0x12a43b049A7D330cB8aEAB5113032D18AE9a9030"},{"recipients":"209196530000000000000000"}],"votingStartBlock":22323277,"proposer":"0x12a43b049A7D330cB8aEAB5113032D18AE9a9030","description":"Top up LEGO stables","votingEndTime":1745568839,"motionTargets":["0xb0fe4d300334461523d9d61aad90d0494e1abb43","0xb9e5cbb9ca5b0d659238807e84d0176930753d86"],"votingStartTime":1745309639,"id":"824","objectionsThreshold":5e+24,"summary":"## What is this about?\n\nThis proposal suggests topping up the LEGO stables, likely referring to replenishing stablecoin reserves or a specific fund within the Lido protocol. The proposal outlines a voting period from April 22 to April 25, 2025, and specifies that it will pass unless there are 5,000,000 or more weighted 'no' votes.\n\n## What could be the impact of this?\n\nIf approved, the LEGO stables will receive additional funds, which could enhance the protocol's liquidity, stability, or operational capacity. This may support ongoing or future initiatives managed by the LEGO group within Lido, depending on the intended use of the stables. The proposal's passing threshold ensures that only significant opposition can block the top-up.","tldr":"This proposal seeks to add funds to the LEGO stables within the Lido protocol, with voting scheduled from April 22 to April 25, 2025, and will pass unless 5,000,000 or more weighted 'no' votes are cast. If approved, it could improve liquidity, stability, or operational capacity for Lido initiatives managed by the LEGO group.","searchKeywords":["LEGO stables","Lido","Proposal","Stablecoin reserves","Fund top-up","Voting period","April 22 to April 25, 2025","Passing threshold","5,000,000 weighted no votes","Liquidity","Stability","Operational capacity","LEGO group","Protocol","Initiatives","Replenishing funds"],"globalTags":["Proposal - Currently voting","Grants - Grant Funding"],"localTags":["LEGO stables","Lido","LEGO group"],"headline":"Lido Proposal Seeks to Top Up LEGO Stables, Voting Set for April 2025","updated":1745323949,"timestamp":{"_seconds":1745323954,"_nanoseconds":272000000},"type":"onchain","governor":"easyTrack","protocol":"lido"},{"currentStatus":"created","currentStatusSinceTx":"0xaff32e118717093614ad4a30ec11cf2c15e69a47a7bf2fbd11b09a12b665a83d","motionData":[{"recipients":"0x12a43b049A7D330cB8aEAB5113032D18AE9a9030","amounts":"52023190000000000000000"}],"votingStartBlock":22323277,"proposer":"0x12a43b049A7D330cB8aEAB5113032D18AE9a9030","description":"Top up LEGO LDO","votingEndTime":1745568839,"motionTargets":["0x97615f72c3428a393d65a84a3ea6bbd9ad6c0d74","0xb9e5cbb9ca5b0d659238807e84d0176930753d86"],"votingStartTime":1745309639,"id":"823","objectionsThreshold":5e+24,"summary":"## What is this about?\n\nThis proposal seeks to top up the LEGO LDO allocation. Voting on the proposal is open from April 22, 2025, to April 25, 2025. The proposal will pass unless it receives 5,000,000 or more weighted 'no' votes (objections).\n\n## What could be the impact of this?\n\nIf approved, the LEGO LDO allocation will be increased, potentially providing more resources for the LEGO initiative within the protocol. This could enable further development, incentives, or operations tied to LEGO, depending on its current objectives and needs. If the threshold of objections is met, the proposal will not pass, and the allocation will remain unchanged.","tldr":"This proposal is about increasing the LEGO LDO allocation, with voting open from April 22, 2025, to April 25, 2025; if approved, it would provide more resources for the LEGO initiative, but if 5,000,000 or more weighted 'no' votes are cast, the allocation will not change. The main benefit is additional support for LEGO-related activities, with no explicit costs mentioned.","searchKeywords":["LEGO","LDO","allocation","proposal","voting","April 22, 2025","April 25, 2025","weighted 'no' votes","objections","resources","initiative","protocol","development","incentives","operations","threshold","pass","fail"],"globalTags":["Proposal - Currently voting","Grants - Grant Funding"],"localTags":["LEGO","LDO allocation"],"headline":"Lido Proposal Seeks to Increase LEGO LDO Allocation; Voting Open April 22–25, 2025","updated":1745323949,"timestamp":{"_seconds":1745323954,"_nanoseconds":825000000},"type":"onchain","governor":"easyTrack","protocol":"lido"},{"id":"0x19336684bc65be5d580da43c09ca74900e2952e6cb21d2081a74fb9ebdb7d07f","title":"SGR 69: inwstETHs","summary":"$b3","tldr":"This is about approving a gauge for the LP-inwstETHs pair on Ethereum mainnet, enabling users to earn both restaking and staking rewards, which is expected to increase TVL, yield options, and visibility for InceptionLRT and Spectra. The proposal passed unanimously with strong community support, and implementation will proceed as planned; no costs or opposition were mentioned.","protocol":"spectra","slug":"sgr-69-inwsteths","snapshotUrl":"https://snapshot.box/#/s:spectradao.eth/proposal/0x19336684bc65be5d580da43c09ca74900e2952e6cb21d2081a74fb9ebdb7d07f","startDate":1745266908,"endDate":1745413200,"updated":1745413217,"relatedLinks":["https://x.com/InceptionLRT","https://discord.gg/WuMSynCbxn","https://snapshot.box/#/s:spectradao.eth/proposal/0x19336684bc65be5d580da43c09ca74900e2952e6cb21d2081a74fb9ebdb7d07f","https://gov.spectra.finance/t/sgr-inwsteth-september25-gauge-listing-request/699"],"state":"closed","results":{"quorum":1,"totalScores":"38543855.50","totalVotes":3,"choices":[{"id":0,"name":"For","scores":"38543855.50"},{"id":1,"name":"Against","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["Gauge approval","LP-inwstETHs","Ethereum mainnet","Restaking rewards","Staking rewards","TVL increase","Yield options","InceptionLRT","Spectra"],"headline":"Gauge Approved for LP-inwstETHs Pair on Ethereum, Expanding Rewards and Visibility for InceptionLRT and Spectra","type":"snapshot"},{"currentStatus":"created","currentStatusSinceTx":"0xb3e324b8f3c5e0063a2c1c8bfe2ca234b2cbab924baa7e23efeb2c0085a45c05","motionData":[{"token":"0x6B175474E89094C44Da98b954EedeAC495271d0F","recipients":"0x79f5E20996abE9f6a48AF6f9b13f1E55AED6f06D"},{"recipients":"2000000000000000000000000"}],"votingStartBlock":22319166,"proposer":"0xa02FC823cCE0D016bD7e17ac684c9abAb2d6D647","description":"Top up Stonks stables","votingEndTime":1745519243,"motionTargets":["0x3f0534cccfb952470775c516dc2eff8396b8a368","0xb9e5cbb9ca5b0d659238807e84d0176930753d86"],"votingStartTime":1745260043,"id":"822","objectionsThreshold":5e+24,"summary":"## What is this about?\n\nThis proposal suggests topping up the Stonks stables. The voting period is from April 21, 2025, 6:27 PM to April 24, 2025, 6:27 PM. The proposal will pass unless there are 5,000,000 or more weighted 'no' votes (objections).\n\n## What could be the impact of this?\n\nIf approved, the Stonks stables will receive additional funds or resources. This could help maintain or improve their operations, liquidity, or stability, depending on the specific function of the Stonks stables within the protocol. The outcome depends on the level of community objection during the voting period.","tldr":"A proposal is open from April 21, 2025, 18:27 to April 24, 2025, 18:27 to allocate more resources to the Stonks stables, aiming to support their operations or stability. The proposal will be approved unless it receives 5,000,000 or more weighted 'no' votes from the community.","searchKeywords":["Stonks stables","Proposal","Top up","Voting period","April 21, 2025","April 24, 2025","Weighted 'no' votes","Objections","Additional funds","Resources","Operations","Liquidity","Stability","Protocol","Community objection"],"globalTags":["Proposal - Currently voting","Grants - Grant Funding"],"localTags":["Stonks stables"],"headline":"Lido Proposal Seeks to Top Up Stonks Stables Pending Community Vote","updated":1745276227,"timestamp":{"_seconds":1745276230,"_nanoseconds":988000000},"type":"onchain","governor":"easyTrack","protocol":"lido"},{"id":"0x055da94c7507029862af753d0281ddeadf35af4b5a77f15f7e249bd79df67783","title":"[AGIP 145] Adjusting Quorum Requirements and Increasing Voter XP","summary":"$b4","tldr":"This proposal aims to lower the Aavegotchi DAO quorum by excluding DAO-owned GHST and to double XP rewards for voters, making it easier to pass proposals and incentivizing participation. The community shows strong support, but current voter turnout remains below the existing quorum threshold, underscoring the need for these changes.","protocol":"aavegotchi","slug":"agip-145-adjusting-quorum-requirements-and-increasing-voter-xp","snapshotUrl":"https://snapshot.box/#/s:aavegotchi.eth/proposal/0x055da94c7507029862af753d0281ddeadf35af4b5a77f15f7e249bd79df67783","startDate":1745251755,"endDate":1747066080,"updated":1745459939,"relatedLinks":["https://discord.com/channels/732491344970383370/1351529648424615966","https://snapshot.box/#/s:aavegotchi.eth/proposal/0x055da94c7507029862af753d0281ddeadf35af4b5a77f15f7e249bd79df67783"],"state":"active","results":{"quorum":9000000,"totalScores":"2915174.65","totalVotes":101,"choices":[{"id":0,"name":"Make proposed adjustments","scores":"2835459.83"},{"id":1,"name":"Reject proposal","scores":"79714.82"}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Seeking feedback","Changes - Community Improvement","Newsworthy - Affecting Governance"],"localTags":["Aavegotchi DAO","GHST","Quorum reduction","XP rewards","Voter participation"],"headline":"Aavegotchi DAO Proposal Seeks to Lower Quorum and Double Voter XP Rewards to Boost Participation","type":"snapshot"},{"id":"0xcd1c1a051888efd495d97458ae9fa4fe5198616eb3d92a71d3352d9f25e79c4e","title":"CSM: stakeShareLimit and keyRemovalCharge parameters adjustment","summary":"$b5","tldr":"This proposal aims to increase the CSM `stakeShareLimit` to 3% under specific conditions and reduce the `keyRemovalCharge` to 0.02 ETH, enabling more validators and lowering Node Operator costs. The community is overwhelmingly supportive, and if passed, these changes will be implemented via on-chain votes once the outlined conditions are met or with the release of CSM v2.","protocol":"lido","slug":"csm-stakesharelimit-and-keyremovalcharge-parameters-adjustment","snapshotUrl":"https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xcd1c1a051888efd495d97458ae9fa4fe5198616eb3d92a71d3352d9f25e79c4e","startDate":1745251200,"endDate":1745856000,"updated":1745432449,"relatedLinks":["https://research.lido.fi/t/community-staking-module/5917/90","https://operators.lido.fi/module/3","https://research.lido.fi/t/community-staking-module/5917/86","https://operators.lido.fi/module/2","https://operators.lido.fi/module/1/36","https://research.lido.fi/t/lido-on-ethereum-node-operator-numic-security-incident-disclosure-may-21-2024/7536","https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7fd7879a945ebf95709bb0f5d0679370a06d6d0289b832ef8a100f983373e242","https://research.lido.fi/t/community-staking-module/5917/55#p-17771-keyremovalcharge-25","https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xcd1c1a051888efd495d97458ae9fa4fe5198616eb3d92a71d3352d9f25e79c4e","https://research.lido.fi/t/community-staking-module/5917/104"],"state":"active","results":{"quorum":0,"totalScores":"22546826.71","totalVotes":36,"choices":[{"id":0,"name":"For","scores":"22546825.61"},{"id":1,"name":"Against","scores":"1.10"}]},"decayedScore":0,"score":0.005398122268201353,"isFlagged":false,"globalTags":["Proposal - Seeking feedback","Changes - Technical Change"],"localTags":["CSM","stakeShareLimit","keyRemovalCharge","Node Operator","CSM v2"],"headline":"Lido Proposal Seeks to Raise CSM stakeShareLimit and Lower keyRemovalCharge to 0.02 ETH","type":"snapshot"},{"id":"0xc67103e65d8bb4e088ddb89e0a7654fa56db5f0162f5870fca41c5dabd937f11","title":"Lido Alliance application: Twyne","summary":"$b6","tldr":"This proposal is about onboarding Twyne, a credit delegation protocol, to the Lido Alliance to expand stETH use cases, increase capital efficiency, and support Ethereum decentralization, with Twyne offering a 10% token allocation and 50% revenue share on stETH pools in exchange for Lido DAO’s endorsement and collaboration. The community is strongly supportive, with almost unanimous votes in favor and the proposal surpassing quorum requirements.","protocol":"lido","slug":"lido-alliance-application-twyne","snapshotUrl":"https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xc67103e65d8bb4e088ddb89e0a7654fa56db5f0162f5870fca41c5dabd937f11","startDate":1745251200,"endDate":1745856000,"updated":1745443219,"relatedLinks":["https://x.com/twynexyz","https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xc67103e65d8bb4e088ddb89e0a7654fa56db5f0162f5870fca41c5dabd937f11","https://research.lido.fi/t/twyne-lido-alliance-proposal/9901"],"state":"active","results":{"quorum":0,"totalScores":"22265880.86","totalVotes":35,"choices":[{"id":0,"name":"For","scores":"22265879.76"},{"id":1,"name":"Against","scores":"1.10"}]},"decayedScore":0,"score":0.0054623917081879,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["Lido Alliance","Twyne","Credit Delegation Protocol","stETH use cases","Token allocation","Revenue share","Lido DAO endorsement","Ethereum decentralization"],"headline":"Lido Alliance Proposal: Onboarding Twyne to Expand stETH Use Cases and Share Revenue","type":"snapshot"},{"id":"0x3ecd09e4c0f22d25c711ca5777c49c22d144385b85dd7f696ca6cc66cc0ca157","title":"Increasing LOL Easy Track Limits to align with Grant Requests","summary":"$b7","tldr":"This proposal seeks to raise the Easy Track transfer limit for the Liquidity Observation Lab multisig to 6,000 stETH every 6 months, enabling the Lido Ecosystem BORG Foundation to access grant funds more efficiently and streamline treasury operations. The community response is highly positive, with all votes so far in favor, and the proposal will proceed to an Aragon vote for on-chain implementation if support continues.","protocol":"lido","slug":"increasing-lol-easy-track-limits-to-align-with-grant-requests","snapshotUrl":"https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x3ecd09e4c0f22d25c711ca5777c49c22d144385b85dd7f696ca6cc66cc0ca157","startDate":1745251200,"endDate":1745856000,"updated":1745443197,"relatedLinks":["https://docs.lido.fi/multisigs/committees#281-liquidity-observation-lab-committee-ethereum","https://docs.lido.fi/deployed-contracts/#easy-track-factories-for-token-transfers","https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x8736420fd3ebecc1aae603c3a49d6805899c38b142c92525169e5bfa95f53b26","https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x90e2f9926e37867d2ef319a8ef7a0257bb5695086b64b88b43b43f00959a0047","https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x3ecd09e4c0f22d25c711ca5777c49c22d144385b85dd7f696ca6cc66cc0ca157","https://research.lido.fi/t/increasing-lol-et-limits-to-align-with-egg-lido-ecosystem-borg-foundation-grant-funding-request/9881"],"state":"active","results":{"quorum":0,"totalScores":"21306421.04","totalVotes":38,"choices":[{"id":0,"name":"For","scores":"21306421.04"},{"id":1,"name":"Against","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Grants - Grant Funding","Proposal - Currently voting"],"localTags":["Easy Track","Liquidity Observation Lab","Lido Ecosystem BORG Foundation","Aragon vote","stETH transfer limit","Treasury operations"],"headline":"Lido Proposal to Increase Easy Track Transfer Limit for Liquidity Observation Lab Multisig to 6,000 stETH Every 6 Months","type":"snapshot"},{"id":"0x2533d8d3903d94daa4de16ef7abf957441439e7867962ce8709a375479f417de","title":"Extend Delegate Incentivization Program through 2025","summary":"$b8","tldr":"This proposal is to extend the Lido DAO Delegate Incentivization Program through Q2–Q4 2025 with a $225,000 LDO budget, lowering the eligibility threshold and updating committee members to broaden participation and improve oversight. The community response is overwhelmingly positive, with all votes so far in favor and no opposition.","protocol":"lido","slug":"extend-delegate-incentivization-program-through-2025","snapshotUrl":"https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x2533d8d3903d94daa4de16ef7abf957441439e7867962ce8709a375479f417de","startDate":1745251200,"endDate":1745856000,"updated":1745432607,"relatedLinks":["https://www.agora.xyz","https://docs.lido.fi/multisigs/committees#210-delegate-oversight-committee","https://docs.lido.fi/multisigs/committees#21-lego-committee","https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x2533d8d3903d94daa4de16ef7abf957441439e7867962ce8709a375479f417de","https://research.lido.fi/t/establish-a-public-delegate-platform-and-delegate-incentivization-program/7858/49"],"state":"active","results":{"quorum":0,"totalScores":"21274263.68","totalVotes":36,"choices":[{"id":0,"name":"For","scores":"21274263.68"},{"id":1,"name":"Against","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Currently voting","Grants - Grant Program Update"],"localTags":["Lido DAO Delegate Incentivization Program","LDO budget","Eligibility threshold","Committee members","Broaden participation","Improve oversight"],"headline":"Lido DAO Proposes Extension of Delegate Incentivization Program Through 2025 with Updated Eligibility and Oversight","type":"snapshot"},{"currentStatus":"created","currentStatusSinceTx":"0x4c2220184a2f08a9918e05f245fc0436cb9eda86a1aad9a9c3d6dad85ef6e617","motionData":[{"recipients":"0xe7B6109E3907e362195E214505383001BdAe8a40","amounts":"58580000000000000000"},{"recipients":"0x7bad1B0fC06EEC11EaE08Ce0D3f143Bf52955066"},{"recipients":"0xed96e247655361031aEE6514cD1b89C7141b59D5"},{"recipients":"0x4550b615Bdd735429aF593a54D9C691368168d99"},{"recipients":"0x19f58BA5ffdc8e556A9b97e5866f08425689b9a1"},{"recipients":"0xf40bcc0845528873784F36e5C105E62a93ff7021"}],"votingStartBlock":22318223,"proposer":"0xe2A682A9722354D825d1BbDF372cC86B2ea82c8C","description":"Top up rewards share program","votingEndTime":1745507891,"motionTargets":["0xdc7300622948a7adaf339783f6991f9cddd79776","0xb9e5cbb9ca5b0d659238807e84d0176930753d86"],"votingStartTime":1745248691,"id":"821","objectionsThreshold":5e+24,"summary":"## What is this about?\n\nThis proposal suggests topping up the rewards share program for the Lido protocol. The voting period runs from April 21, 2025, to April 24, 2025. The proposal will pass unless it receives 5,000,000 or more weighted 'no' votes (objections).\n\n## What could be the impact of this?\n\nIf approved, the rewards share program will receive additional funding, potentially increasing incentives for participants. This could encourage greater engagement or participation in the protocol, but may also affect the protocol's treasury or reward distribution dynamics.","tldr":"This proposal seeks to add more funds to the Lido protocol's rewards share program, with voting scheduled from April 21, 2025, to April 24, 2025. If passed, it could boost participant incentives but may impact the protocol's treasury or how rewards are distributed.","searchKeywords":["Lido","Proposal","Rewards share program","Voting period","April 21 2025","April 24 2025","5,000,000 weighted no votes","Objections","Additional funding","Incentives","Participants","Engagement","Participation","Protocol","Treasury","Reward distribution dynamics"],"globalTags":["Proposal - Currently voting","Grants - Grant Funding"],"localTags":["Lido","Rewards Share Program"],"headline":"Lido Proposal Seeks to Top Up Rewards Share Program; Voting Set for April 2025","updated":1745260221,"timestamp":{"_seconds":1745260225,"_nanoseconds":142000000},"type":"onchain","governor":"easyTrack","protocol":"lido"},{"id":"0x2c14dd45e22b2c85f825b50facb9a494103add2ffa58fbcf9ca8699e524ec567","title":"MIP 101 - Plume - Morpho Coincentives","summary":"$b9","tldr":"This proposal is about allocating $500,000 in MORPHO tokens as incentives on the Plume network, contingent on Plume providing $1.5 million in incentives to Morpho and Morpho Protocol reaching specific loan activity thresholds, with distribution over eight months if conditions are met. The community is strongly supportive, and the main benefit is increased activity and liquidity for Morpho on Plume, with no direct costs beyond the token allocation.","protocol":"morpho","slug":"mip-101-plume-morpho-coincentives","snapshotUrl":"https://snapshot.box/#/s:morpho.eth/proposal/0x2c14dd45e22b2c85f825b50facb9a494103add2ffa58fbcf9ca8699e524ec567","startDate":1745247517,"endDate":1745506717,"updated":1745440771,"relatedLinks":["https://snapshot.box/#/s:morpho.eth/proposal/0x2c14dd45e22b2c85f825b50facb9a494103add2ffa58fbcf9ca8699e524ec567","https://forum.morpho.org/t/plume-morpho-coincentives-proposal/1704"],"state":"active","results":{"quorum":500000,"totalScores":"3937695.15","totalVotes":14,"choices":[{"id":0,"name":"For","scores":"3937695.15"},{"id":1,"name":"Against","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Grants - Grant Proposal / Application","Grants - Grant Funding"],"localTags":["MORPHO","Plume network","Incentive program","Loan activity thresholds","Token allocation"],"headline":"Morpho Proposes $500K Token Incentives on Plume, Conditional on $1.5M Plume Incentives and Loan Activity Targets","type":"snapshot"},{"id":"0x3f194a24787634a92bdcfe4f138e38dfe2e608448dd60a1268ffc5b0e1621535","title":"MIP 100 - Approve Review of 2024 Contributor Grants","summary":"## What is this about?\n\nThis proposal seeks DAO approval for the 2024 contributor grants, as part of an annual process established by a previous Morpho DAO vote. The Morpho Association has presented the proposed grant allocations for contributors, and the DAO is now voting to ratify and distribute these grants.\n\n## What could be the impact of this?\n\nIf approved, the proposal will authorize the distribution of contributor grants for 2024, supporting ongoing work and incentivizing contributors within the Morpho ecosystem. This process helps ensure transparency and community oversight of resource allocation.\n\n## How is the community reacting?\n\nThe community response is strongly positive so far, with all 15 voters (totaling 3,937,797.45 votes) in favor and no votes against or abstaining. The quorum has been significantly surpassed.\n\n## Next actions\n\nThe vote is still ongoing. If the current trend continues, the grants will be ratified and distributed as proposed.","tldr":"This is a Morpho DAO proposal to approve and distribute 2024 contributor grants, aiming to support ongoing work and maintain transparency in resource allocation. The community response is overwhelmingly positive, with all votes so far in favor and the quorum exceeded.","protocol":"morpho","slug":"mip-100-approve-review-of-2024-contributor-grants","snapshotUrl":"https://snapshot.box/#/s:morpho.eth/proposal/0x3f194a24787634a92bdcfe4f138e38dfe2e608448dd60a1268ffc5b0e1621535","startDate":1745247284,"endDate":1745506484,"updated":1745440737,"relatedLinks":["https://snapshot.box/#/s:morpho.eth/proposal/0x3f194a24787634a92bdcfe4f138e38dfe2e608448dd60a1268ffc5b0e1621535","https://forum.morpho.org/t/mip-100-approve-review-of-2024-contributor-grants/1701"],"state":"active","results":{"quorum":500000,"totalScores":"3937797.45","totalVotes":15,"choices":[{"id":0,"name":"For","scores":"3937797.45"},{"id":1,"name":"Against","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Grants - Grant Funding","Proposal - Currently voting"],"localTags":["Morpho DAO","2024 contributor grants","Resource allocation","Community response","Quorum exceeded"],"headline":"Morpho DAO Proposes 2024 Contributor Grants to Support Ongoing Work and Transparency","type":"snapshot"},{"currentStatus":"started","currentStatusSinceTx":"0xbe1cefe0ef4bfa0cf4292c063c00fd404d137d3a749267b37ff5f391be30d830","metadata":"ipfs:QmbyeSj8ceD4peNS6rtKKD3TgjC6ZEJyXeGZThNHa1vY2e","votingStartBlock":22314582,"ipfsData":"Unable to fetch data from IPFS","proposer":"0x34d6Dbd097f6b739C59D7467779549Aea60e1F84","quorum":0,"yesThreshold":0,"ipfsHash":"QmbyeSj8ceD4peNS6rtKKD3TgjC6ZEJyXeGZThNHa1vY2e","votingEndTime":1745809643,"votingStartTime":1745204843,"id":"1035","cid":"QmbyeSj8ceD4peNS6rtKKD3TgjC6ZEJyXeGZThNHa1vY2e","summary":"## What is this about?\n\nThis proposal appears to be a placeholder or an incomplete submission for the Curve protocol. It provides only the voting start and end times, along with an IPFS link to metadata, but does not include any substantive details or description of the proposal’s content or objectives.\n\n## What could be the impact of this?\n\nWithout further information or a summary of the proposal’s intent, it is not possible to determine the potential impact on the protocol, its users, or governance. The lack of detail may hinder informed voting and decision-making by the community.","searchKeywords":["Curve","Proposal","Placeholder","Incomplete submission","Voting start time","Voting end time","IPFS link","Metadata","No details","No description","Impact unknown","Governance","Community","Informed voting","Decision-making"],"globalTags":["Proposal - Currently voting"],"localTags":["Curve","Incomplete proposal","IPFS metadata"],"totalVotersAgainst":1,"totalWeightAgainst":1346849961699507000,"totalVotersFor":4,"totalVoters":5,"totalWeightFor":29737781292994890000,"totalWeight":31084631254694396000,"score":1108.4073884199222,"proposalResults":"## How is the community reacting?\n\n- The proposal has attracted participation from 5 voters, with a total voting weight of 31.08.\n- 4 voters, representing 29.74 in weight (95.69% of total weight), support the proposal.\n- 1 voter, with a weight of 1.35 (4.34% of total weight), is against the proposal.\n- The community reaction is strongly in favor, with the vast majority of voting weight supporting the proposal.","tldr":"This is an incomplete or placeholder proposal for the Curve protocol, lacking substantive details or objectives, which limits informed community decision-making. Despite the lack of information, the majority of voting weight from 5 participants supports the proposal.","headline":"Curve proposal submitted with only metadata and voting times, lacking substantive details","updated":1745385315,"timestamp":{"_seconds":1745385316,"_nanoseconds":768000000},"decayedScore":1267.8567036299007,"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"id":"0xe04a281294cc6aff175463cd8c61838512f1d55fd7b95efa323e71c74125d818","title":"PizzaDAO x Aavegotchi 2025 (UPDATED)","summary":"$ba","tldr":"Aavegotchi DAO is considering sponsoring PizzaDAO’s Global Pizza Party on May 22, 2025, for either $6,000 or $10,000, in exchange for brand integration and onboarding at global events to boost visibility and community growth. Most voters so far support the $10,000 option, but the proposal has not yet reached the required quorum.","protocol":"aavegotchi","slug":"pizzadao-x-aavegotchi-2025-updated","snapshotUrl":"https://snapshot.box/#/s:aavegotchi.eth/proposal/0xe04a281294cc6aff175463cd8c61838512f1d55fd7b95efa323e71c74125d818","startDate":1745151926,"endDate":1745756640,"updated":1745441719,"relatedLinks":["https://app.ens.domains/dreadpizzaroberts.eth","https://opensea.io/item/matic/0x86935f11c86623dec8a25696e1c19a8659cbf95d/542","https://discord.com/channels/732491344970383370/1307288564458852384","https://opensea.io/item/matic/0x86935f11c86623dec8a25696e1c19a8659cbf95d/5421","https://docs.google.com/presentation/d/1Oycsq4YBOmyursmVCkr-6auI5bMnXOnb-KumDjWBWiU/edit?slide=id.g346aa5b3e98_0_105#slide=id.g346aa5b3e98_0_105","https://s3.amazonaws.com/charm.public/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/bfceae58-3fc9-4518-8c1a-9fdde90d8518/77e4fb7e-9d54-4102-97dd-97b1fbddff20.png","https://s3.amazonaws.com/charm.public/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/b473ab94-93f4-4dbe-a5ac-3bd4779d87a2/8b4e99f1-1af7-4423-a4e1-98c3d88ee6ad.png","https://stream.mux.com/r0102rWWVYRmMSApW7pMRzWOwFXM1xKljs401iaxyOCIts","https://x.com/GoobzGG/status/1806837269359403117","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/8fbac2a5-e0a1-4477-9e43-3b4d5dd584f5/pizzaavegotchi.webp","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/4d49a009-661e-49c4-9c11-3e988550b63f/merch.jpeg","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/1949954d-38b5-4cca-8292-06bcf54b8fbc/pizzaday2024.jpeg","https://x.com/Pizza_DAO/status/1869133689818619981","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/6e54ec34-4346-4f1e-9873-d2adf8d36385/art_basel_pizzadao.webp","https://x.com/Pizza_DAO/status/1778891140877434962","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/ad2dc1c9-65ac-4eb2-a461-51bfbfb363bb/pizza_bazaar_nyc.webp","https://x.com/Pizza_DAO/status/1902085732875039074","https://cdn.charmverse.io/user-content/5d8d6b7e-1aff-44a3-a5b4-50f391c8c34a/17f86e13-8573-435f-b911-e05e035822e2/GkRIY6PW0AAO26E.webp","https://www.globalpizzaparty.xyz/","https://www.instagram.com/pizza_dao/","https://x.com/Pizza_DAO","https://discord.com/invite/Bqv4AaVebK","https://www.facebook.com/thepizzadao","https://www.rarepizzas.com/mint","https://opensea.io/collection/rare-pizzas-box","https://oncyber.io/pizzadao","https://pizzadao.github.io/moltobennydelivery/","https://treasury.pizzadao.xyz","https://docs.google.com/spreadsheets/d/1vBdETWF_PjdVZioOuXXjKxz4kQK0rv5OXHIrG3Ple7o/edit?gid=0#gid=0","https://snapshot.box/#/s:aavegotchi.eth/proposal/0xe04a281294cc6aff175463cd8c61838512f1d55fd7b95efa323e71c74125d818"],"state":"active","results":{"quorum":9000000,"totalScores":"2785443.39","totalVotes":143,"choices":[{"id":0,"name":"Huumble Pizza Party","scores":"461426.09"},{"id":1,"name":"Spaacious Pizza Party","scores":"1517574.28"},{"id":2,"name":"No Partnership","scores":"251124.78"},{"id":3,"name":"Abstain","scores":"555318.25"}]},"decayedScore":0,"score":3620.1826700477327,"isFlagged":false,"globalTags":["Proposal - Currently voting","Grants - Grant Funding","Event - IRL"],"localTags":["PizzaDAO","Global Pizza Party","Brand integration","Onboarding","Community growth","Quorum"],"headline":"Aavegotchi DAO Weighs $10K Sponsorship of PizzaDAO’s 2025 Global Pizza Party for Brand Integration","type":"snapshot"},{"votingStartBlock":22292502,"proposer":"0x5C43AAC965ff230AC1cF63e924D0153291D78BaD","quorum":4e+24,"description":"$bb","votingEndTime":1745110967,"votingStartTime":1744938167,"id":"92","title":"# Set Launch Allowance for sUSDS<>USDT DEX, Update Multisig Authorization, Launch LBTC-Stable Vaults, Set Rebalancer for sUSDS<>USDT Smart Lending, Update LBTC-cbBTC DEX Shares, and Update GHO-USDC Limits & Parameters","votingEndBlock":22306902,"searchKeywords":["Instadapp","protocol updates","sUSDS<>USDT DEX pool","T4 vault","Team Multisig","governance","LBTC-stable vaults","LBTC/USDC","LBTC/USDT","LBTC/GHO","FLUID_RESERVE contract","rebalancer","sUSDS-USDT smart lending","supply limits","borrow share limits","LBTC-cbBTC DEX","GHO-USDC DEX","caps","user configurations","risk parameters","collateral factor","liquidation thresholds","withdrawal limits","borrow limits","security","decentralization","liquidity management","protocol efficiency","growth","governance-driven oversight","risk controls"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change"],"localTags":["Instadapp","sUSDS<>USDT DEX pool","T4 vault","Team Multisig","LBTC-stable vaults","LBTC/USDC","LBTC/USDT","LBTC/GHO","FLUID_RESERVE contract","sUSDS-USDT smart lending","LBTC-cbBTC DEX","GHO-USDC DEX","Governance-driven oversight","Rebalancer contract","Risk parameters update"],"score":0,"decayedScore":0,"totalVotersFor":7,"totalVoters":7,"totalWeightFor":4.1212450172088003e+24,"totalWeight":4.1212450172088003e+24,"proposalResults":"## How is the community reacting?\n\n- The proposal received participation from 7 voters, with a total voting weight of 4,121,245.02.\n- All 7 voters supported the proposal, resulting in 100% approval by both voter count and weight.\n- The quorum requirement was 4,000,000.00, and the total weight for the proposal surpassed this threshold by 121,245.02.\n- Community engagement was limited in terms of voter count but strong in terms of voting weight, indicating that large stakeholders participated and unanimously supported the proposal.","currentStatus":"queued","currentStatusSinceTx":"0x6a51b55e62c1edf063aa3989b8e2ffbab03d8ee83819a8a1e02c263fe44709b6","summary":"$bc","tldr":"This proposal implements protocol updates for Instadapp, including new launch and risk limits, governance control over pools and vaults, and improved risk and liquidity management, aiming to enhance security, flexibility, and scalability. All 7 participating voters, representing a total voting weight of 4,121,245.02, unanimously approved the changes, with no noted costs.","headline":"Instadapp Proposes Protocol Updates: Governance Control, New Vault Limits, and Risk Parameter Adjustments","updated":1745136945,"timestamp":{"_seconds":1745136947,"_nanoseconds":34000000},"type":"onchain","governor":"governance","protocol":"instadapp"},{"accessLevel":"1","creationTime":1744833227,"ipfsData":"$bd","proposer":"0x57ab7ee15cE5ECacB1aB84EE42D5A9d0d8112922","coolDownBeforeVotingStart":86400,"yesThreshold":3.2e+23,"description":"$be","minPropositionPower":80000,"yesNoDifferential":8e+22,"title":"Aave Liquidity Committee Funding Phase VI","votingPortal":"0xFe4683C18aaad791B6AFDF0a8e1Ed5C6e2c9ecD6","votingDuration":259200,"ipfsHash":"0x22262761d78b56bc43694c7a928aec29b984dd41f4e3ee3ed767e4af4b248e5c","queuingTime":0,"id":"296","cid":"QmQdxKCw1ncwGCJbF8gTCWuNgNcz32mKu2qWNxDbtdkEmy","searchKeywords":["Aave Liquidity Committee","ALC","Phase VI","Funding request","3,500,000 aEthLidoGHO","Ethereum collector","ALC Ethereum SAFE","Phase V progress","GHO liquidity","Balancer v3","Fluid","Rings","Resolv","GHO expansion","Ethereum","Arbitrum","Base","Strategic focus","Multichain expansion","Sonic","Avalanche","Gnosis","Capital efficiency","Bridging","GSM mechanisms","DeFi protocols","Performance metrics","Liquidity targets","Price stability","Adoption","User experience","Stablecoin","DAO capital management","Yield generation","Operational flexibility","GHO peg","Market presence","Surge pricing","Native swaps","TVL","Trading volume","Ecosystem growth","Aave","GHO","DeFi"],"globalTags":["Grants - Grant Proposal / Application","Grants - Grantee Update"],"localTags":["Aave Liquidity Committee","ALC Phase VI","aEthLidoGHO","Ethereum collector","ALC Ethereum SAFE","GHO liquidity","Balancer v3","Fluid","Rings","Resolv","Sonic","Avalanche","Gnosis","GSM mechanisms","Multichain expansion","DeFi integrations","Surge pricing","Native swaps","TVL growth"],"votingStartBlock":22290933,"votingEndTime":1745178851,"votingStartTime":1744919651,"score":0,"decayedScore":0,"totalVotersFor":51,"totalVoters":51,"proposalResults":"## How is the community reacting?\n\n- The proposal received participation from 51 voters, all of whom voted in favor.\n- The total voting weight in support was 560,292.51.\n- Both the required vote differential (80,000) and the yes weighted threshold (320,000) were surpassed by a significant margin.\n- There was unanimous support, with 100% of the votes cast in favor and no opposition.\n- Community sentiment appears strongly positive, indicating broad consensus for the proposal.","totalWeightFor":5.6029250751945816e+23,"totalWeight":5.6029250751945816e+23,"totalWeightAgainst":0,"currentStatus":"executed","currentStatusSinceTx":"0x880a0d21555e21081557afd6dc4d884e43fd6ad3206dc8327c632505c3a740fe","summary":"$bf","tldr":"This proposal seeks approval for the Aave Liquidity Committee to withdraw 3,500,000 aEthLidoGHO from the Ethereum collector to fund Phase VI initiatives aimed at expanding and improving GHO liquidity, utility, and integrations across multiple chains, including new deployments and advanced bridging. The community unanimously supports the proposal, with all 51 voters in favor and both voting thresholds exceeded.","headline":"Aave Proposes Phase VI Funding to Expand GHO Liquidity and Utility Across Multiple Chains","updated":1745182975,"timestamp":{"_seconds":1745182976,"_nanoseconds":788000000},"type":"onchain","governor":"v3","protocol":"aave"},{"accessLevel":"1","creationTime":1744827755,"ipfsData":"$c0","proposer":"0x57ab7ee15cE5ECacB1aB84EE42D5A9d0d8112922","coolDownBeforeVotingStart":86400,"yesThreshold":3.2e+23,"description":"$c1","minPropositionPower":80000,"yesNoDifferential":8e+22,"title":"Add rlUSD to Core Instance","votingPortal":"0xFe4683C18aaad791B6AFDF0a8e1Ed5C6e2c9ecD6","votingDuration":259200,"ipfsHash":"0x7bf5753a0e909b4256fc406e6e6897cafebfcb8e0179e2e9696650ac0c6f7226","queuingTime":0,"id":"295","cid":"QmWgXwWPnf4aCuGA2S8Kuz3wCUVwTGZqubYQCb1k6aasTb","searchKeywords":["Ripple","rlUSD","Aave v3","Ethereum","Stablecoin","Governance approval","Onboarding","Borrowable asset","Collateral asset","Risk parameters","Supply cap","Borrow cap","Reserve factor","Emission admin","Implementation","Tests","Snapshot","Discussion","Protocol usage","Liquidity","LTV","LT","Strategic growth","Integration","Communities","Products"],"globalTags":["Proposal - Seeking feedback","Changes - Technical Change"],"localTags":["rlUSD","Ripple","Aave v3 Core","Stablecoin onboarding","Risk parameters","Emission admin"],"votingStartBlock":22290480,"votingEndTime":1745173379,"votingStartTime":1744914179,"totalVotersAgainst":6,"totalWeightAgainst":4516848255615239700,"totalVotersFor":110,"totalVoters":116,"score":0.6369507630506431,"decayedScore":0.6384214887619104,"proposalResults":"## How is the community reacting?\n\n- The proposal received strong community engagement, with 116 total voters and a combined voting weight of 560,307.38.\n- Support for the proposal is overwhelmingly positive: 110 voters (560,302.86 weight) voted \"For,\" while only 6 voters (4.52 weight) voted \"Against.\"\n- The \"Yes\" votes exceed both the required vote differential (560,302.86 - 4.52 = 560,298.34, which is much greater than the required 80,000) and the \"Yes\" weighted threshold (560,302.86 > 320,000).\n- The community is highly supportive of this proposal, with almost unanimous weighted approval.","totalWeightFor":5.603028591383127e+23,"totalWeight":5.603073759865683e+23,"currentStatus":"executed","currentStatusSinceTx":"0x02a8156d64af7445b4ac2cfe233caa53d8a0680ec34a6cda1a4057eac92a74e7","summary":"$c2","tldr":"This proposal is about adding Ripple’s rlUSD stablecoin to Aave v3 on Ethereum with strict risk controls (no collateral use, low supply and borrow caps), aiming to expand Aave’s stablecoin offerings and attract Ripple users. The community response is overwhelmingly positive, with nearly unanimous approval and minimal risk due to the conservative parameters.","headline":"Proposal to onboard Ripple’s rlUSD stablecoin to Aave v3 Core on Ethereum with conservative risk parameters","updated":1745182975,"timestamp":{"_seconds":1745182976,"_nanoseconds":770000000},"type":"onchain","governor":"v3","protocol":"aave"},{"id":"0x9bdcd0a1cf23893ecf501acd68ca14a958902c73ff8b6dfe45e31aeabe0022f7","title":"[BIP-815] Enable Gauge for inwstETHs/wstETH [Ethereum]","summary":"$c3","tldr":"This proposal enables a gauge for the inwstETHs/wstETH pool on Ethereum via Balancer, aiming to increase liquidity and utility for inwstETHs in DeFi protocols, with no mentioned costs. The community showed unanimous support, and technical implementation will proceed as specified.","protocol":"balancer","slug":"bip815-enable-gauge-for-inwstethswsteth-ethereum","snapshotUrl":"https://snapshot.box/#/s:balancer.eth/proposal/0x9bdcd0a1cf23893ecf501acd68ca14a958902c73ff8b6dfe45e31aeabe0022f7","startDate":1744912800,"endDate":1745258400,"updated":1745258414,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1934","https://www.inceptionlrt.com/","https://docs.inceptionlrt.com/","https://github.com/inceptionlrt/smart-contracts","https://discord.com/invite/RSAtmyXcSk","https://x.com/InceptionLRT","https://etherscan.io/address/0xae48B92CBc0882a7D70D878e42cc121a62ceB632","https://docs.inceptionlrt.com/security/audit-reports","https://www.coingecko.com/en/coins/inception-restaked-steth-symbiotic","https://etherscan.io/address/0x6D0216CF4B6741B23B4beeda42b7100EB8A7CA0C","https://snapshot.box/#/s:balancer.eth/proposal/0x9bdcd0a1cf23893ecf501acd68ca14a958902c73ff8b6dfe45e31aeabe0022f7","https://forum.balancer.fi/t/bip-815-enable-gauge-for-inwsteths-wsteth-ethereum/6481"],"state":"closed","results":{"quorum":2000000,"totalScores":"2659692.60","totalVotes":3,"choices":[{"id":0,"name":"Yes, let's do it","scores":"2659692.60"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed","Newsworthy - Technical"],"localTags":["inwstETHs/wstETH pool","Balancer","Liquidity","DeFi protocols"],"headline":"Balancer to Enable Gauge for inwstETHs/wstETH Pool on Ethereum to Boost Liquidity and Utility","type":"snapshot"},{"id":"0x9b30b21e4a0a658cda58b51076239503cbbcadd5e199d76d6f8f566b369e3861","title":"[BIP-816] Enable PRL/wETH 80/20 Gauges with a 2% cap (Ethereum & Base)","summary":"$c4","tldr":"The proposal to enable Balancer gauges for 80-PRL/20-wETH pools on Ethereum and Base with a 2% cap was unanimously approved, aiming to boost PRL liquidity and trading activity while managing risk. There are no noted costs, and the community showed strong support, with all votes in favor and quorum met.","protocol":"balancer","slug":"bip816-enable-prlweth-8020-gauges-with-a-2-cap-ethereum-base","snapshotUrl":"https://snapshot.box/#/s:balancer.eth/proposal/0x9b30b21e4a0a658cda58b51076239503cbbcadd5e199d76d6f8f566b369e3861","startDate":1744912800,"endDate":1745258400,"updated":1745258413,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1935","https://app.parallel.best/","https://docs.mimo.capital/parallel-protocol/","https://github.com/parallel-protocol","https://twitter.com/ParallelMoney","https://docs.mimo.capital/parallel-protocol/resources/security-audits","https://gov.mimo.capital/t/pip-45-l-introducing-prl-the-mimo-token-upgrade/458","https://debank.com/profile/0x4a266739E40664e80470CC335120a2A1fA0B3F3f","https://pro.octav.fi/parallelprotocol/treasury","https://app.balancer.fi/#/ethereum/pool/0x5b1c06c4923dbba4b27cfa270ffb2e60aa28615900020000000000000000004a","https://app.balancer.fi/#/ethereum/pool/0xa5533a44d06800eaf2daad5aad3f9aa9e1dc36140002000000000000000001b8","https://app.balancer.fi/#/polygon/pool/0x77952e11e1ba727ffcea95a0f38ed7da586eebc7000200000000000000000072","https://app.balancer.fi/#/polygon/pool/0x82d7f08026e21c7713cfad1071df7c8271b17eae0002000000000000000004b6","https://snapshot.org/#/mimo.eth","https://docs.mimo.capital/parallel-protocol/governance/dao-multisig","https://balancer.fi/pools/ethereum/v3/0x1846c6cbe0d433e152fa358e5ff27968e18bce7c","https://etherscan.io/address/0x1846c6cbe0d433e152fa358e5ff27968e18bce7c","https://etherscan.io/token/0x6c0aeceedc55c9d55d8b99216a670d85330941c3","https://etherscan.io/token/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2","https://etherscan.io/address/0x30fb447441195a5b72a382ef14c5865c0fc1a9aa","https://balancer.fi/pools/base/v3/0x19e3e19945e7fd2a7856824c595981c7fe450bb5","https://basescan.org/address/0x19e3e19945e7fd2a7856824c595981c7fe450bb5","https://basescan.org/token/0xfd28f108e95f4d41daae9dbfff707d677985998e","https://basescan.org/token/0x4200000000000000000000000000000000000006","https://basescan.org/address/0xca66072ca2d7c3af6f44f4d4d29eb9e088a2df79","https://etherscan.io/address/0xfcce9b5c1e8d56d9fc6dcbb706acc51dd03fe9f1","https://snapshot.box/#/s:balancer.eth/proposal/0x9b30b21e4a0a658cda58b51076239503cbbcadd5e199d76d6f8f566b369e3861","https://forum.balancer.fi/t/bip-816-enable-prl-weth-80-20-gauges-with-a-2-cap-ethereum-base/6483"],"state":"closed","results":{"quorum":2000000,"totalScores":"2659692.29","totalVotes":3,"choices":[{"id":0,"name":"Yes, let's do it","scores":"2659692.29"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["Balancer gauges","80-PRL/20-wETH pool","Ethereum","Base","2% cap","PRL liquidity","Trading activity","Risk management","Unanimous approval","Quorum met"],"headline":"Balancer Approves Gauges for 80-PRL/20-wETH Pools on Ethereum and Base with 2% Cap","type":"snapshot"},{"id":"0xc5ee84def8770d26315f8804af4d1433f5ea707c32f457900ecb5cd645e7f008","title":"[BIP-816] Enable PRL/wETH 80/20 Gauges with a 2% cap (Ethereum & Base)","summary":"$c5","tldr":"The proposal to enable Balancer gauges for 80-PRL/20-wETH pools with a 2% cap on Ethereum and Base was unanimously approved, aiming to boost PRL liquidity and trading activity while managing risk. There are no noted costs, and the community showed strong support, with all votes in favor.","protocol":"aura","slug":"bip816-enable-prlweth-8020-gauges-with-a-2-cap-ethereum-base","snapshotUrl":"https://snapshot.box/#/s:aurafinance.eth/proposal/0xc5ee84def8770d26315f8804af4d1433f5ea707c32f457900ecb5cd645e7f008","startDate":1744912800,"endDate":1745200800,"updated":1745200822,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1935","https://app.parallel.best/","https://docs.mimo.capital/parallel-protocol/","https://github.com/parallel-protocol","https://twitter.com/ParallelMoney","https://docs.mimo.capital/parallel-protocol/resources/security-audits","https://gov.mimo.capital/t/pip-45-l-introducing-prl-the-mimo-token-upgrade/458","https://debank.com/profile/0x4a266739E40664e80470CC335120a2A1fA0B3F3f","https://pro.octav.fi/parallelprotocol/treasury","https://app.balancer.fi/#/ethereum/pool/0x5b1c06c4923dbba4b27cfa270ffb2e60aa28615900020000000000000000004a","https://app.balancer.fi/#/ethereum/pool/0xa5533a44d06800eaf2daad5aad3f9aa9e1dc36140002000000000000000001b8","https://app.balancer.fi/#/polygon/pool/0x77952e11e1ba727ffcea95a0f38ed7da586eebc7000200000000000000000072","https://app.balancer.fi/#/polygon/pool/0x82d7f08026e21c7713cfad1071df7c8271b17eae0002000000000000000004b6","https://snapshot.org/#/mimo.eth","https://docs.mimo.capital/parallel-protocol/governance/dao-multisig","https://balancer.fi/pools/ethereum/v3/0x1846c6cbe0d433e152fa358e5ff27968e18bce7c","https://etherscan.io/address/0x1846c6cbe0d433e152fa358e5ff27968e18bce7c","https://etherscan.io/token/0x6c0aeceedc55c9d55d8b99216a670d85330941c3","https://etherscan.io/token/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2","https://etherscan.io/address/0x30fb447441195a5b72a382ef14c5865c0fc1a9aa","https://balancer.fi/pools/base/v3/0x19e3e19945e7fd2a7856824c595981c7fe450bb5","https://basescan.org/address/0x19e3e19945e7fd2a7856824c595981c7fe450bb5","https://basescan.org/token/0xfd28f108e95f4d41daae9dbfff707d677985998e","https://basescan.org/token/0x4200000000000000000000000000000000000006","https://basescan.org/address/0xca66072ca2d7c3af6f44f4d4d29eb9e088a2df79","https://etherscan.io/address/0xfcce9b5c1e8d56d9fc6dcbb706acc51dd03fe9f1","https://etherscan.io/address/0x5DbAd78818D4c8958EfF2d5b95b28385A22113Cd","https://snapshot.box/#/s:aurafinance.eth/proposal/0xc5ee84def8770d26315f8804af4d1433f5ea707c32f457900ecb5cd645e7f008","https://forum.balancer.fi/t/bip-816-enable-prl-weth-80-20-gauges-with-a-2-cap-ethereum-base/6483"],"state":"closed","results":{"quorum":0,"totalScores":"16624791.15","totalVotes":4,"choices":[{"id":0,"name":"Yes, let's do it","scores":"16624791.15"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["Balancer gauges","80-PRL/20-wETH pool","2% cap","Ethereum","Base","PRL liquidity","Trading activity"],"headline":"Balancer gauges enabled for 80-PRL/20-wETH pools with 2% cap on Ethereum and Base to boost PRL liquidity","type":"snapshot"},{"id":"0x1ce449f51e9fd2a27fd3a112f1c5340ac2cfd454b6195ca3aff8a90de5686163","title":"[BIP-815] Enable Gauge for inwstETHs/wstETH [Ethereum]","summary":"$c6","tldr":"This proposal enables a gauge for the inwstETHs/wstETH pool on Ethereum via Balancer, allowing veING holders to direct incentives to increase liquidity and utility for inwstETHs across DeFi protocols, with no noted costs. The community unanimously supported the proposal, and technical implementation by the Balancer Maxi LM Multisig is the next step.","protocol":"aura","slug":"bip815-enable-gauge-for-inwstethswsteth-ethereum","snapshotUrl":"https://snapshot.box/#/s:aurafinance.eth/proposal/0x1ce449f51e9fd2a27fd3a112f1c5340ac2cfd454b6195ca3aff8a90de5686163","startDate":1744912800,"endDate":1745200800,"updated":1745200820,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1934","https://www.inceptionlrt.com/","https://docs.inceptionlrt.com/","https://github.com/inceptionlrt/smart-contracts","https://discord.com/invite/RSAtmyXcSk","https://x.com/InceptionLRT","https://etherscan.io/address/0xae48B92CBc0882a7D70D878e42cc121a62ceB632","https://docs.inceptionlrt.com/security/audit-reports","https://www.coingecko.com/en/coins/inception-restaked-steth-symbiotic","https://etherscan.io/address/0x6D0216CF4B6741B23B4beeda42b7100EB8A7CA0C","https://snapshot.box/#/s:aurafinance.eth/proposal/0x1ce449f51e9fd2a27fd3a112f1c5340ac2cfd454b6195ca3aff8a90de5686163","https://forum.balancer.fi/t/bip-815-enable-gauge-for-inwsteths-wsteth-ethereum/6481"],"state":"closed","results":{"quorum":0,"totalScores":"16624791.15","totalVotes":4,"choices":[{"id":0,"name":"Yes, let's do it","scores":"16624791.15"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["inwstETHs/wstETH pool","veING","Balancer Maxi LM Multisig","Gauge enablement","Liquidity incentives","DeFi utility"],"headline":"Proposal to Enable Gauge for inwstETHs/wstETH Pool on Balancer Advances to Implementation","type":"snapshot"},{"motionData":[{"tuple[]":"48"},{"tuple[]":"80"},{"tuple[]":"49"},{"tuple[]":"80"},{"tuple[]":"50"},{"tuple[]":"80"},{"tuple[]":"51"},{"tuple[]":"80"},{"tuple[]":"52"},{"tuple[]":"80"},{"tuple[]":"53"},{"tuple[]":"80"},{"tuple[]":"54"},{"tuple[]":"80"},{"tuple[]":"55"},{"tuple[]":"80"},{"tuple[]":"56"},{"tuple[]":"80"},{"tuple[]":"74"},{"tuple[]":"5"},{"tuple[]":"79"},{"tuple[]":"5"},{"tuple[]":"81"},{"tuple[]":"5"}],"votingStartBlock":22289534,"proposer":"0x08637515E85A4633E23dfc7861e2A9f53af640f7","description":"Set SDVT vetted validators limits","votingEndTime":1745161967,"motionTargets":["0xae7b191a31f627b4eb1d4dac64eab9976995b433"],"votingStartTime":1744902767,"id":"820","objectionsThreshold":5e+24,"searchKeywords":["SDVT","vetted validators","Lido","Lido protocol","Proposal","Validator set","Voting period","April 17 2025","April 20 2025","Weighted no votes","Objections","Composition","Scalability","Decentralization","Security","Performance","Governance","Operation","Validator participation","Validator limits"],"globalTags":["Proposal - Currently voting","Newsworthy - Affecting Governance","Security"],"localTags":["SDVT vetted validators","Lido protocol","Validator limits"],"currentStatus":"executed","currentStatusSinceTx":"0xfc4d82ec49888d671607ac876283606b5b036bd68d6c7ccece995ad5a3b9b352","summary":"## What is this about?\n\nThis proposal suggests setting limits on SDVT vetted validators within the Lido protocol. The voting period ran from April 17 to April 20, 2025. The proposal would pass if there were fewer than 5,000,000 weighted 'no' votes (objections).\n\n## What could be the impact of this?\n\nImplementing limits on SDVT vetted validators could affect the composition and decentralization of the validator set, potentially improving security or governance oversight. It may also influence how new validators are onboarded and the overall trust in the protocol’s validator selection process.","tldr":"This proposal aims to set limits on SDVT vetted validators in the Lido protocol, with voting held from April 17 to April 20, 2025. The intended benefits include potential improvements in security and governance oversight, while the main cost could be changes to validator onboarding and protocol decentralization.","headline":"Lido Proposal Seeks to Limit SDVT Vetted Validators to Influence Decentralization and Security","updated":1745229288,"timestamp":{"_seconds":1745229290,"_nanoseconds":544000000},"type":"onchain","governor":"easyTrack","protocol":"lido"},{"currentStatus":"started","currentStatusSinceTx":"0x6e616107790f24a12c9ec617f470588c36cc55f9623147e0327165605359c47e","metadata":"ipfs:bafkreiajh3gxitdp62xrx7lasezkjlo55wuv3wkhlmssoiyqgpzd6dsrca","votingStartBlock":22289295,"ipfsData":"Add a gauge for the following Stableswap NG pool: sdSPECTRA/SPECTRA on Base ","proposer":"0xD4f9FE0039Da59e6DDb21bbb6E84e0C9e83D73eD","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreiajh3gxitdp62xrx7lasezkjlo55wuv3wkhlmssoiyqgpzd6dsrca","votingEndTime":1745504699,"votingStartTime":1744899899,"id":"1034","cid":"bafkreiajh3gxitdp62xrx7lasezkjlo55wuv3wkhlmssoiyqgpzd6dsrca","summary":"## What is this about?\n\nThis proposal suggests adding a gauge for the Stableswap NG pool consisting of sdSPECTRA and SPECTRA tokens on the Base network. The gauge would enable liquidity providers in this pool to receive CRV emissions as rewards.\n\n## What could be the impact of this?\n\nIf approved, this would incentivize liquidity provision for the sdSPECTRA/SPECTRA pool on Base, potentially increasing the pool's liquidity and trading volume. It would also expand Curve's presence and utility on the Base network, and provide additional yield opportunities for users holding sdSPECTRA and SPECTRA.","searchKeywords":["Gauge","Stableswap NG pool","sdSPECTRA","SPECTRA","Base network","CRV emissions","Liquidity providers","Rewards","Liquidity provision","Trading volume","Curve","Yield opportunities","Token incentives","Pool liquidity","Curve presence","Curve utility"],"globalTags":["Proposal - Seeking feedback"],"localTags":["Gauge Addition","Stableswap NG","sdSPECTRA","SPECTRA","Base network","CRV emissions","Liquidity incentives","Curve expansion"],"totalVotersAgainst":1,"totalWeightAgainst":1845453294738182400,"totalVotersFor":4,"totalVoters":5,"totalWeightFor":4.3023296452698166e+26,"totalWeight":4.3023296637243496e+26,"score":0.0005405678130245474,"decayedScore":0.0005869150531431513,"proposalResults":"## How is the community reacting?\n\n- The proposal has received participation from 5 voters, with a total voting weight of 430,232,966.37.\n- 4 voters (99.99% of the total weight) are in favor, representing 430,232,964.53.\n- 1 voter (effectively 0.00% of the total weight) is against, representing 1.85.\n- The overwhelming majority of voting weight supports the proposal, indicating strong community approval.","tldr":"A proposal to add a gauge for the sdSPECTRA/SPECTRA Stableswap NG pool on Base would allow liquidity providers to earn CRV rewards, increasing incentives and potentially boosting liquidity and trading volume. The community response is overwhelmingly positive, with nearly all voting weight in favor and minimal opposition.","headline":"Proposal to Add Gauge for sdSPECTRA/SPECTRA Pool on Curve Base Network to Enable CRV Rewards","updated":1745291672,"timestamp":{"_seconds":1745291674,"_nanoseconds":50000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"votingStartBlock":22288929,"proposer":"0x3FB19771947072629C8EEE7995a2eF23B72d4C8A","quorum":4e+25,"description":"$c7","votingEndTime":1745378615,"votingStartTime":1744894775,"id":"84","title":"# BoB Uniswap v3 Incentives Package","votingEndBlock":22329249,"searchKeywords":["Uniswap","BOB Network","Hybrid Layer 2","Bitcoin security","EVM compatibility","UNI incentives","Uniswap v3 pools","Liquidity mining","Angle Merkl","Oku deployment","Incentive package","$$375k UNI","$$250k liquidity mining","$$20k Angle Merkl","$$105k Oku rebate","BOB incentives","$$500k BOB","Six months","75% match","Canonical DEX","BTC","BTC LSTs","DeFi ecosystem","BOB Rise","Fusion","TVL","User growth","BTC-native users","EVM users","Trading volume","Cross-chain liquidity","Collaborative incentive programs","Retroactive funding","Ecosystem growth","Incentive campaigns"],"globalTags":["Grants - Grant Proposal / Application","Grants - Grant Funding"],"localTags":["Uniswap","BOB Network","Hybrid Layer 2","Bitcoin security","EVM compatibility","UNI incentives","Liquidity mining","Angle Merkl integration","Oku deployment","BOB Rise","Fusion","BTC LSTs","Canonical DEX","Cross-chain BTC liquidity","DeFi ecosystem","TVL growth"],"totalVotersAbstain":10,"totalWeightAbstain":2.500660120973113e+24,"totalVotersAgainst":20,"totalWeightAgainst":9051128927486897000,"totalVotersFor":251,"totalVoters":281,"totalWeightFor":4.714069342429723e+25,"totalWeight":4.964136259639927e+25,"currentStatus":"queued","currentStatusSinceTx":"0x3ceb44cf2d0aeaa3bf3abfbf1e8b48507cec46a7d793e33750506f39c01329bd","score":781.3166101072889,"summary":"$c8","proposalResults":"## How is the community reacting?\n\n- Voter turnout was 281, with a total voting weight of 49,641,362.60.\n- The quorum of 40,000,000.00 was surpassed, indicating strong participation.\n- 251 voters (weight: 47,140,693.42) supported the proposal.\n- 20 voters (weight: 9.05) voted against.\n- 10 voters (weight: 2,500,660.12) abstained.\n- The overwhelming majority of voting weight (94.96%) was in favor, with negligible opposition (0.00% by weight).\n- Community sentiment is highly supportive of the proposal.","proposalVoteReasons":"- Broad support for onboarding and empowering new delegates and communities, as seen in backing for she256, Curia, and Proxy (Prev Boardroom) delegate platforms.\n- Positive sentiment towards initiatives that improve delegate diversity, education, and participation, aligning with Uniswap’s decentralised governance values.\n- Approval for proposals that provide clear onboarding processes and resources, such as the Uniswap onboarding package for BOB, to enhance effective governance.\n- General agreement that these proposals strengthen the protocol’s governance infrastructure and community engagement.","tldr":"This proposal seeks $375K in UNI from Uniswap to match BOB Network’s $500K incentive package, aiming to make Uniswap v3 the main DEX on BOB by boosting liquidity and user activity, especially for BTC-related pairs, and covering integration costs. The community response is overwhelmingly positive, with strong voter turnout and nearly unanimous support for the initiative.","headline":"Uniswap Proposal Seeks $375K UNI Match to Bootstrap v3 Pools on BOB Hybrid Layer 2","updated":1745385347,"timestamp":{"_seconds":1745385349,"_nanoseconds":354000000},"decayedScore":756.6312363831976,"type":"onchain","governor":"governance","protocol":"uniswap"},{"currentStatus":"started","currentStatusSinceTx":"0x7ff8ee97cfb12f25c8517afb5a356ffbc6b3b4e97f1567ac498a5f0242a026e5","metadata":"ipfs:QmRTjNw9D1B16RmYeRWUVfEjm4JqFGNDvocNPaWi1DcgKG","votingStartBlock":22288794,"ipfsData":"Add a gauge for the following twocrypto-NG pool: ION/SuperOETHb on Base","proposer":"0xf7Bd34Dd44B92fB2f9C3D2e31aAAd06570a853A6","quorum":0,"yesThreshold":0,"ipfsHash":"QmRTjNw9D1B16RmYeRWUVfEjm4JqFGNDvocNPaWi1DcgKG","votingEndTime":1745498639,"votingStartTime":1744893839,"id":"1033","cid":"QmRTjNw9D1B16RmYeRWUVfEjm4JqFGNDvocNPaWi1DcgKG","summary":"## What is this about?\n\nThis proposal suggests adding a gauge for the twocrypto-NG pool, specifically the ION/SuperOETHb pair, on the Base network. The gauge would enable liquidity providers in this pool to receive CRV rewards.\n\n## What could be the impact of this?\n\nIf approved, the new gauge would incentivize liquidity provision for the ION/SuperOETHb pool on Base, potentially increasing the pool's liquidity and trading volume. This could also expand Curve’s presence and utility on the Base network.","searchKeywords":["Gauge","twocrypto-NG pool","ION/SuperOETHb","Base network","CRV rewards","Curve","Liquidity providers","Liquidity provision","Trading volume","Curve presence","Curve utility","Incentivize","Pool liquidity"],"globalTags":["Proposal - Seeking feedback","Changes - New deployment"],"localTags":["Gauge","twocrypto-NG pool","ION/SuperOETHb","Base network","CRV rewards","Curve"],"score":0,"decayedScore":0,"totalVotersFor":5,"totalVoters":5,"totalWeightFor":3.0323821031364484e+26,"totalWeight":3.0323821031364484e+26,"proposalResults":"## How is the community reacting?\n\n- All 5 voters participated in favor of the proposal, with 100% support.\n- The total voting weight for the proposal is 303,238,210.31.\n- No votes were cast against the proposal.\n- Community engagement is low in terms of voter count, but unanimous among those who participated.","tldr":"This proposal aims to add a gauge for the ION/SuperOETHb pool on the Base network, allowing liquidity providers to earn CRV rewards and potentially boosting liquidity and Curve’s presence on Base. All 5 participating voters supported the proposal with a total voting weight of 303,238,210.31, though overall community engagement was low.","headline":"Proposal to Add Gauge for ION/SuperOETHb Pool on Curve Base Network Aims to Boost Liquidity","updated":1745385315,"timestamp":{"_seconds":1745385317,"_nanoseconds":221000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"id":"0xa2b2075bb373f833112e1b26efbafdd66c404ea0df17822820f5dd4bd21be6d9","title":"SIP #2 - DAO Voting","summary":"## What is this about?\n\nThis proposal, SIP #2, concerns the implementation or approval of DAO Voting within the Superfluid ecosystem. Community members were asked to vote FOR or AGAINST the proposal, with further details and discussion available on the project’s forum.\n\n## What could be the impact of this?\n\nIf enacted, this proposal would establish or formalize DAO Voting, potentially enabling decentralized governance and decision-making for the Superfluid community. This could increase transparency, community participation, and decentralized control over protocol changes or resource allocation.\n\n## How is the community reacting?\n\nThe proposal received unanimous support, with all 5 voters casting their votes FOR and none AGAINST. The quorum was easily met, indicating strong consensus and engagement from the participating community members.","tldr":"This is about SIP #2, a proposal to implement DAO Voting in the Superfluid ecosystem, aiming to enable decentralized governance and increase transparency and community participation. The proposal received unanimous support from the community, with all 5 voters in favor and quorum met.","protocol":"superfluid","slug":"sip-2-dao-voting","snapshotUrl":"https://snapshot.box/#/s:superfluid.eth/proposal/0xa2b2075bb373f833112e1b26efbafdd66c404ea0df17822820f5dd4bd21be6d9","startDate":1744874128,"endDate":1745270128,"updated":1745270146,"relatedLinks":["https://snapshot.box/#/s:superfluid.eth/proposal/0xa2b2075bb373f833112e1b26efbafdd66c404ea0df17822820f5dd4bd21be6d9","https://forum.superfluid.org/t/sip-dao-voting/391"],"state":"closed","results":{"quorum":1,"totalScores":"5.00","totalVotes":5,"choices":[{"id":0,"name":"FOR","scores":"5.00"},{"id":1,"name":"AGAINST","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed","Newsworthy - Affecting Governance"],"localTags":["SIP #2","Superfluid","DAO Voting","Decentralized governance"],"headline":"Superfluid SIP #2: DAO Voting Proposal Passes with Unanimous Support","type":"snapshot"},{"id":"0x2c07add832383dc6900077406b4241a34dc4923ba209e2d07d1a4243a18fcdef","title":"[6.6.2] [Social] April Funding Request - ENS Public Goods Working Group Term 6","summary":"$c9","tldr":"The ENS DAO approved transferring 356,000 USDC from its treasury to the Public Goods Working Group multisig to fund grants and initiatives through October 2025, aiming to support public goods, builders, and emergent opportunities in the ENS ecosystem. The proposal saw overwhelming community support with no opposition, and the funds will be disbursed as part of a collective executable proposal.","protocol":"ens","slug":"662-social-april-funding-request-ens-public-goods-working-group-term-6","snapshotUrl":"https://snapshot.box/#/s:ens.eth/proposal/0x2c07add832383dc6900077406b4241a34dc4923ba209e2d07d1a4243a18fcdef","startDate":1744841373,"endDate":1745273373,"updated":1745273388,"relatedLinks":["https://enswallets.xyz","https://snapshot.box/#/s:ens.eth/proposal/0x2c07add832383dc6900077406b4241a34dc4923ba209e2d07d1a4243a18fcdef","https://discuss.ens.domains/t/6-6-2-social-april-funding-request-ens-public-goods-working-group-term-6/20532"],"state":"closed","results":{"quorum":0,"totalScores":"1492561.87","totalVotes":173,"choices":[{"id":0,"name":"For","scores":"1492560.84"},{"id":1,"name":"Against","scores":0},{"id":2,"name":"Abstain","scores":"1.03"}]},"decayedScore":0,"score":0.04101899532173718,"isFlagged":false,"globalTags":["Grants - Grant Funding","Proposal - Result: Passed"],"localTags":["ENS DAO","Public Goods Working Group","Public goods funding","ENS ecosystem"],"headline":"ENS DAO Approves 356,000 USDC Transfer to Fund Public Goods Through 2025","type":"snapshot"},{"id":"0x2c56d8776c8be3a824d010f94f00108716acaa31ede92cd03692e779af8a051d","title":"[6.6.1] [Social] April Funding Request - ENS Meta-Governance Working Group Term 6","summary":"$ca","tldr":"This is a funding proposal for the ENS Meta-Governance Working Group for Term 6, requesting 589k USDC and 100k $ENS to support governance, DAO tooling, and contributor compensation through October 2025. The proposal received near-unanimous community support and will proceed to fund disbursement as part of a collective executable proposal.","protocol":"ens","slug":"661-social-april-funding-request-ens-metagovernance-working-group-term-6","snapshotUrl":"https://snapshot.box/#/s:ens.eth/proposal/0x2c56d8776c8be3a824d010f94f00108716acaa31ede92cd03692e779af8a051d","startDate":1744808571,"endDate":1745240571,"updated":1745240591,"relatedLinks":["https://docs.ens.domains/v/governance/governance-proposals/term-1/ep12-working-group-rules","https://enswallets.xyz","https://snapshot.box/#/s:ens.eth/proposal/0x88de13f2f088390262d1d5e7db9ddff5a74d0b878fedf590a0448c32692078ba","https://snapshot.box/#/s:ens.eth/proposal/0x2c56d8776c8be3a824d010f94f00108716acaa31ede92cd03692e779af8a051d","https://discuss.ens.domains/t/6-6-1-social-april-funding-request-ens-meta-governance-working-group-term-6/20536"],"state":"closed","results":{"quorum":0,"totalScores":"1602312.83","totalVotes":170,"choices":[{"id":0,"name":"For","scores":"1602311.60"},{"id":1,"name":"Against","scores":"0.19"},{"id":2,"name":"Abstain","scores":"1.03"}]},"decayedScore":0,"score":0.04625366918081876,"isFlagged":false,"globalTags":["Grants - Grant Proposal / Application","Grants - Grant Funding","Proposal - Result: Passed"],"localTags":["ENS Meta-Governance Working Group","Term 6","DAO tooling","Contributor compensation","Collective executable proposal"],"headline":"ENS Meta-Governance Working Group Secures Funding for Term 6 with 589k USDC and 100k $ENS","type":"snapshot"},{"accessLevel":"1","creationTime":1744720511,"ipfsData":"$cb","proposer":"0xf71fc92e2949ccF6A5Fd369a0b402ba80Bc61E02","coolDownBeforeVotingStart":86400,"yesThreshold":3.2e+23,"description":"$cc","minPropositionPower":80000,"yesNoDifferential":8e+22,"title":"Mantle a.DI path activation","votingPortal":"0xFe4683C18aaad791B6AFDF0a8e1Ed5C6e2c9ecD6","votingDuration":259200,"ipfsHash":"0x843f8e79d8b8a8d16f67b3b612386459ec256ed0118f0452c9f8f75b39c929c0","queuingTime":0,"id":"294","cid":"QmXEtjc42MzV5ekr3atou6JBAnjTS5YbktUM5aAUNqDGiT","searchKeywords":["Aave","bgdlabs","a.DI","Aave Delivery Infrastructure","governance infrastructure","Mantle network","activation vote","Aave v3 deployment","register pre-deployed Mantle adapters","Ethereum a.DI instance","enableBridgeAdapters","Ethereum Cross-chain Controller contract","message passing","Ethereum","Mantle","ZkSync","Linea","addresses","new a.DI contracts","governance contracts","cross-chain governance","technical operations","protocol usage","liquidity","multi-chain capabilities","future cross-chain operations","governance actions"],"globalTags":["Changes - Technical Change","Changes - New deployment","Proposal - Seeking feedback","Newsworthy - Technical"],"localTags":["Aave Delivery Infrastructure","a.DI","Mantle network","enableBridgeAdapters","Ethereum Cross-chain Controller","Cross-chain governance","Mantle adapters","Aave v3 deployment","Multi-chain capabilities"],"votingStartBlock":22281593,"votingEndTime":1745066135,"votingStartTime":1744806935,"totalVotersAgainst":6,"totalWeightAgainst":12703547019011930000,"totalVotersFor":89,"totalVoters":95,"totalWeightFor":5.6100643598842716e+23,"totalWeight":5.610191395354462e+23,"currentStatus":"executed","currentStatusSinceTx":"0x05bfb4b955865126693a04ebd8a6036ba421d35ecd64e587c0c242bdef83ab76","score":1.6424893868704147,"decayedScore":1.6367003136644465,"summary":"$cd","proposalResults":"## How is the community reacting?\n\n- The proposal received strong participation, with 95 total voters and a combined voting weight of 561,019.14.\n- Support for the proposal is overwhelmingly positive: 89 voters (561,006.44 weight) voted For, while only 6 voters (12.70 weight) voted Against.\n- The Yes Weighted Threshold (320,000) and Vote Differential (80,000) requirements were both significantly exceeded, with the For votes surpassing the threshold by 241,006.44 and the differential by 560,993.74.\n- The community reaction indicates near-unanimous support for the proposal, with negligible opposition.","tldr":"This proposal enables the technical and governance setup required for Aave v3 deployment on Mantle by registering Mantle adapters on Ethereum’s a.DI, allowing secure cross-chain communication. The community overwhelmingly supports the proposal, with minimal opposition and no significant costs mentioned.","updated":1745075477,"headline":"Aave Proposal Seeks to Enable Governance and v3 Deployment on Mantle via Cross-Chain Infrastructure","timestamp":{"_seconds":1745075478,"_nanoseconds":759000000},"type":"onchain","governor":"v3","protocol":"aave"},{"id":"0x62532df111b2b5f50353f8441ff0040e41fbaa903ea454a3f1fbd6faa389e705","title":"[BNB Chain] Add Support USD1 on Venus Core Pool","summary":"$ce","tldr":"The proposal to add the USD1 stablecoin to the Venus Core Pool on BNB Chain aims to diversify collateral and attract institutional liquidity, with unanimous community support (770,075.47 votes in favor from two voters). Integration will proceed as recommended, with no mentioned costs or opposition.","protocol":"venus","slug":"bnb-chain-add-support-usd1-on-venus-core-pool","snapshotUrl":"https://snapshot.box/#/s:venus-xvs.eth/proposal/0x62532df111b2b5f50353f8441ff0040e41fbaa903ea454a3f1fbd6faa389e705","startDate":1744805480,"endDate":1744891880,"updated":1744891892,"relatedLinks":["https://snapshot.box/#/s:venus-xvs.eth/proposal/0x62532df111b2b5f50353f8441ff0040e41fbaa903ea454a3f1fbd6faa389e705","https://community.venus.io/t/idea-add-support-usd1-on-venus/5039"],"state":"closed","results":{"quorum":50000,"totalScores":"770075.47","totalVotes":2,"choices":[{"id":0,"name":"For, please proceed.","scores":"770075.47"},{"id":1,"name":"Against, do not proceed.","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["Venus Core Pool","USD1 stablecoin","BNB Chain","Institutional liquidity"],"headline":"USD1 Stablecoin Approved for Addition to Venus Core Pool on BNB Chain","type":"snapshot"},{"id":"0xc8cc5b27f566f18e7030a26bfdc57cf27b326120b66c733ca91f369cb92aee70","title":"0x48..9BEC Account remediation: Concluding steps","summary":"$cf","tldr":"This proposal aims to fully resolve the over-collateralized debt of account 0x48…9BEC on Venus by force liquidating its remaining debts, withdrawing the BNB (with a 10% bounty to the risk fund), and burning the withdrawn BNB. The community unanimously supports these actions, which will eliminate remaining risk and protect the protocol.","protocol":"venus","slug":"0x489bec-account-remediation-concluding-steps","snapshotUrl":"https://snapshot.box/#/s:venus-xvs.eth/proposal/0xc8cc5b27f566f18e7030a26bfdc57cf27b326120b66c733ca91f369cb92aee70","startDate":1744802713,"endDate":1744889113,"updated":1744889127,"relatedLinks":["https://snapshot.box/#/s:venus-xvs.eth/proposal/0xc8cc5b27f566f18e7030a26bfdc57cf27b326120b66c733ca91f369cb92aee70","https://community.venus.io/t/0x48-9bec-account-remediation-concluding-steps/5034"],"state":"closed","results":{"totalScores":"770075.47","totalVotes":2,"quorum":50000,"choices":[{"id":0,"name":"For, please proceed.","scores":"770075.47"},{"id":1,"name":"Against, do not proceed.","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed","Security - Incident"],"localTags":["Venus","Force liquidation","Over-collateralized debt","BNB burn","Risk fund","Protocol protection"],"headline":"Proposal to Force Liquidate and Burn BNB from Over-Collateralized Venus Account to Eliminate Risk","type":"snapshot"},{"metadata":"ipfs:bafkreie3akw2obr7ykjdtsk5esmxcn47glthe3tndbg4and7m6fnflnp6m","votingStartBlock":22275557,"ipfsData":"Add a gauge for the following Stableswap NG pool: USDC/USDf","proposer":"0xD4f9FE0039Da59e6DDb21bbb6E84e0C9e83D73eD","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreie3akw2obr7ykjdtsk5esmxcn47glthe3tndbg4and7m6fnflnp6m","votingEndTime":1745339075,"votingStartTime":1744734275,"id":"1032","cid":"bafkreie3akw2obr7ykjdtsk5esmxcn47glthe3tndbg4and7m6fnflnp6m","searchKeywords":["Gauge","Stableswap NG","USDC","USDf","CRV emissions","Liquidity provision","CRV rewards","Trading volume","Curve","Pool utility","Incentivizing liquidity","IPFS metadata","Curve ecosystem","Liquidity incentives"],"globalTags":["Proposal - Seeking feedback"],"localTags":["Gauge","Stableswap NG","USDC/USDf pool","CRV emissions","Liquidity incentives","Curve ecosystem"],"score":0,"decayedScore":0,"totalVotersFor":7,"totalVoters":7,"totalWeightFor":4.1821201374657714e+26,"totalWeight":4.1821201374657714e+26,"proposalResults":"## How is the community reacting?\n\n- All 7 voters participated in favor of the proposal, resulting in 100% support.\n- The total voting weight for the proposal is 418,212,013.75, with no opposition or abstentions.\n- Community engagement is low in terms of voter count, but unanimous among participants.","currentStatus":"executed","currentStatusSinceTx":"0x4ce04eeaaa0d740f52471915658de499eae8d5f9c4da04abb8b95ae3fa49ea84","summary":"## What is this about?\n\nThis proposal seeks to add a gauge for the Stableswap NG pool consisting of USDC and USDf. The gauge would enable liquidity providers in this pool to receive CRV rewards. The proposal includes a reference to additional metadata hosted on IPFS.\n\n## What could be the impact of this?\n\nIf approved, the USDC/USDf pool would become eligible for CRV emissions, incentivizing liquidity provision and potentially increasing the pool's depth and trading volume. This could enhance stablecoin swap efficiency and attract more users to the Curve protocol.","tldr":"This proposal aims to add a gauge for the USDC/USDf Stableswap NG pool, allowing liquidity providers to earn CRV rewards and potentially increasing pool depth and trading volume. The community response shows unanimous support among a small number of voters, with no opposition or abstentions.","headline":"Proposal to Add Gauge for USDC/USDf Stableswap NG Pool on Curve, Enabling CRV Rewards","updated":1745431352,"timestamp":{"_seconds":1745431353,"_nanoseconds":890000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"id":"0xea449c23b12d6c29a11fe5d314c27018ced24dcce44f8375276fbdd90d8cd479","title":"SGR 68: yvBal-GHO-USR","summary":"$d0","tldr":"This is about the approval and upcoming implementation of a gauge to incentivize liquidity for the GHO/USR pair on Balancer v3 (Base Network), offering LPs multiple yield opportunities and supporting ecosystem growth for Aave and Resolv. The proposal received unanimous community support, with no noted costs mentioned.","protocol":"spectra","slug":"sgr-68-yvbalghousr","snapshotUrl":"https://snapshot.box/#/s:spectradao.eth/proposal/0xea449c23b12d6c29a11fe5d314c27018ced24dcce44f8375276fbdd90d8cd479","startDate":1744706746,"endDate":1744808400,"updated":1744808426,"relatedLinks":["https://app.spectra.finance/pools/base:0xd1f6dbd971e2cd6f486f2c42ea1accc8667447c9","https://x.com/aave","https://balancer.fi/pools/base/v3/0x5b14ce8de84448e9a6f6af652af318472aa4fcaf","https://app.aave.com/reserve-overview/?underlyingAsset=0x40d16fc0246ad3160ccc09b8d0d3a2cd28ae6c2f&marketName=proto_mainnet_v3","https://docs.gho.xyz/concepts/overview","https://github.com/aave/gho-core/tree/main","https://twitter.com/aave","https://aave.tokenlogic.xyz/gho","https://resolv.xyz/","https://app.resolv.xyz/overview","https://docs.resolv.xyz/litepaper","https://github.com/resolv-im/resolv-contracts-public","https://defillama.com/protocol/resolv#information","https://x.com/ResolvLabs","https://creativecommons.org/publicdomain/zero/1.0/","https://snapshot.box/#/s:spectradao.eth/proposal/0xea449c23b12d6c29a11fe5d314c27018ced24dcce44f8375276fbdd90d8cd479","https://gov.spectra.finance/t/sgr-create-balancer-lp-sw-gho-usr-gauge-base-network/713"],"state":"closed","results":{"quorum":1,"totalScores":"6938.28","totalVotes":4,"choices":[{"id":0,"name":"For","scores":"6938.28"},{"id":1,"name":"Against","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed","Newsworthy - Token Distribution"],"localTags":["Gauge","GHO/USR pair","Balancer v3","Base Network","Liquidity incentives","Aave","Resolv","LP yield opportunities","Ecosystem growth"],"headline":"Gauge Approved to Incentivize GHO/USR Liquidity on Balancer v3 (Base Network)","type":"snapshot"},{"votingStartBlock":22270771,"proposer":"0x059A94A72951c0ae1cc1CE3BF0dB52421bbE8210","quorum":4e+24,"description":"$d1","votingEndTime":1744848887,"votingStartTime":1744676087,"id":"91","title":"# Set Initial Allowance for sUSDS<>USDT DEX & T4 Vault and Update Range and Fee for GHO-USDC","votingEndBlock":22285171,"searchKeywords":["Proposal","Dust allowance limits","sUSDS<>USDT DEX pool","T4 vault","Conservative supply limits","Borrow limits","Scalability","Range percentages","Trading fees","GHO-USDC pool","Team Multisig","Authorized entity","Liquidity pools","Safe operations","Efficient operation","Controlled growth","Oversight","Governance"],"globalTags":["Proposal - Seeking feedback"],"localTags":["sUSDS<>USDT DEX pool","T4 vault","GHO-USDC pool","Team Multisig"],"score":0,"decayedScore":0,"totalVotersFor":20,"totalVoters":20,"totalWeightFor":5.058889671710531e+24,"totalWeight":5.058889671710531e+24,"proposalResults":"## How is the community reacting?\n\n- All 20 voters supported the proposal, resulting in 100% approval.\n- The total voting weight in favor is 5,058,889.67, which exceeds the quorum requirement of 4,000,000.00 by 1,058,889.67.\n- The proposal has strong community backing with full participation from all voters and a significant margin above the quorum.","currentStatus":"executed","currentStatusSinceTx":"0x8b7b045e74734b2d2841fb0314b917fa9016a8d1c5af173bf73abe27d0e12c87","summary":"## What is this about?\n\nThis proposal sets initial dust allowance limits for the sUSDS<>USDT DEX pool (DEX Pool 31) and its associated T4 vault (Vault ID 116). It introduces conservative supply and borrow limits for the DEX pool, adds the Team Multisig as an authorized manager for both the DEX and the vault, and updates the lower and upper range percentages and trading fees for the GHO-USDC DEX pool (DEX Pool 4).\n\n## What could be the impact of this?\n\nThe proposal aims to ensure safe and controlled operation of the new sUSDS<>USDT DEX pool and T4 vault by imposing conservative limits, which can be expanded later if needed. Adding Team Multisig as an authorized address enhances management and oversight. Updating the GHO-USDC pool parameters may improve trading efficiency and fee structure, potentially benefiting liquidity providers and traders.","tldr":"This proposal establishes initial conservative limits for the sUSDS<>USDT DEX pool and its T4 vault, authorizes the Team Multisig for management, and updates parameters for the GHO-USDC DEX pool to potentially improve trading efficiency and fees. It received unanimous community approval, with all 20 voters in favor and voting weight significantly exceeding the quorum requirement.","headline":"Instadapp Proposal Sets Limits for sUSDS<>USDT DEX Pool, Updates GHO-USDC Parameters","updated":1744983265,"timestamp":{"_seconds":1744983267,"_nanoseconds":247000000},"type":"onchain","governor":"governance","protocol":"instadapp"},{"metadata":"ipfs:QmWwbYUhgcxUPfYQh5TNCAPLUuWtUKBzoRGtPjCNFzHoyp","votingStartBlock":22270516,"ipfsData":"Set LlamaLend market rates on Optimism to min/max 0.1%/70%. ","proposer":"0x34d6Dbd097f6b739C59D7467779549Aea60e1F84","quorum":0,"yesThreshold":0,"ipfsHash":"QmWwbYUhgcxUPfYQh5TNCAPLUuWtUKBzoRGtPjCNFzHoyp","votingEndTime":1745278175,"votingStartTime":1744673375,"id":"1031","cid":"QmWwbYUhgcxUPfYQh5TNCAPLUuWtUKBzoRGtPjCNFzHoyp","searchKeywords":["LlamaLend","Market rates","Optimism network","Minimum rate","Maximum rate","Voting phase","April 14, 2025","April 21, 2025","IPFS","Identifier","QmWwbYUhgcxUPfYQh5TNCAPLUuWtUKBzoRGtPjCNFzHoyp","Borrowing","Lending","Liquidity provision","User participation","Liquidity dynamics"],"globalTags":["Proposal - Currently voting"],"localTags":["LlamaLend","Optimism","IPFS"],"score":0,"decayedScore":0,"totalVotersFor":5,"totalVoters":5,"totalWeightFor":2.979354271120398e+26,"totalWeight":2.979354271120398e+26,"proposalResults":"## How is the community reacting?\n\n- All 5 voters supported the proposal, resulting in 100% approval.\n- The total voting weight was 297,935,427.11, with the entire weight cast in favor.\n- No votes were cast against or abstained.\n- Participation was limited, with only 5 voters, but those who participated showed unanimous support.","currentStatus":"executed","currentStatusSinceTx":"0x311e7d24cd1a1ef4e08ce7d8437de34a267a6989707984e6c10736455a8ece70","summary":"## What is this about?\n\nThis proposal suggests setting the minimum and maximum market rates for LlamaLend on Optimism to 0.1% and 70%, respectively. The proposal includes a reference to additional metadata stored on IPFS and outlines the voting period.\n\n## What could be the impact of this?\n\nAdjusting the min/max rates for LlamaLend on Optimism could directly affect lending and borrowing dynamics, influencing user participation, risk management, and overall protocol utilization on the Optimism network. This change may also impact yield opportunities and the competitiveness of LlamaLend compared to other lending platforms.","tldr":"A proposal to set LlamaLend's minimum and maximum market rates on Optimism to 0.1% and 70% aims to influence lending dynamics, risk, and competitiveness on the platform. The proposal received unanimous support from all 5 participating voters, with no opposition or abstentions.","headline":"Proposal to Set LlamaLend Min/Max Market Rates on Curve Optimism to 0.1%/70%","updated":1745291671,"timestamp":{"_seconds":1745291672,"_nanoseconds":709000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"votingStartBlock":10456301,"proposer":"0xf57B7C0025444c069dBfE12417729f22A13a399b","quorum":1e+26,"description":"$d2","votingEndTime":1744919478,"votingStartTime":1744660278,"id":"93","title":"\\# \\*\\*MIP-M43 Switching Moonwell's GLMR Market to using API3's OEV Enabled Data","globalTags":["Changes - Technical Change","Proposal - Seeking feedback"],"localTags":["Moonwell","Moonbeam","API3","OEV-enabled data feeds","dAPIs","GLMR core market","Dune dashboard"],"searchKeywords":["Moonwell","Moonbeam network","Chainlink","API3","OEV-enabled data feeds","Yield improvement","dAPIs","Liquidations","addReserves function","GLMR core market","Technical support","Dune dashboard","Revenue enhancement","Proof of concept","Oracle infrastructure","Competitive bidding","Liquidation incentives","DeFi protocol","Financial outcomes"],"totalWeightAgainst":2.047005113308567e+24,"totalWeightAbstain":4.418043705072757e+25,"totalWeight":1.5399547163629189e+26,"totalWeightFor":1.0776802947225574e+26,"score":2604.599389112969,"proposalResults":"## How is the community reacting?\n\n- The proposal met quorum, with a total voting weight of 153,995,471.64, exceeding the required 100,000,000.00.\n- The majority of votes were in favor, with 107,768,029.47 (70.00%) voting \"For\".\n- 2,047,005.11 (1.33%) voted \"Against\".\n- 44,180,437.05 (28.67%) abstained.\n- The community reaction is strongly supportive, with minimal opposition and a significant portion abstaining.","currentStatus":"executed","currentStatusSinceTx":"0xea4f1f3aef7242862e4ad9eb76b17a68bbef908be61b4ac932d9fce392935e47","summary":"$d3","tldr":"Moonwell is proposing to switch its GLMR market oracle on Moonbeam from Chainlink to API3's OEV-enabled dAPIs to increase protocol revenue and transparency, with API3 covering all integration costs and no code changes required. The community is largely supportive, as shown by the voting results, and the change is expected to provide new revenue streams and operational benefits without additional costs to Moonwell.","headline":"Moonwell Proposes Switching GLMR Market Oracle from Chainlink to API3’s OEV-Enabled dAPIs for Increased Revenue and Transparency","updated":1745013993,"timestamp":{"_seconds":1745013995,"_nanoseconds":184000000},"decayedScore":2412.5212586069183,"type":"onchain","governor":"govMultichain","protocol":"moonwell"},{"id":"0x8b2180dadff3768ddafcbb650568e9c6f9daca6e589b6f0f8ae4bab5f52ae042","title":"SGR 67: fxSAVE","summary":"$d4","tldr":"This is about integrating the fxSAVE pool from the f(x) Protocol 2.0 into the Spectra gauge system on Ethereum Mainnet to boost liquidity, TVL, and yield opportunities for users and both protocols. The proposal passed with unanimous community support and no reported costs.","protocol":"spectra","slug":"sgr-67-fxsave","snapshotUrl":"https://snapshot.box/#/s:spectradao.eth/proposal/0x8b2180dadff3768ddafcbb650568e9c6f9daca6e589b6f0f8ae4bab5f52ae042","startDate":1744615711,"endDate":1744804800,"updated":1744804815,"relatedLinks":["https://app.spectra.finance/pools/eth:0xb4dde9015c766f09043247e0687e406049947373","https://snapshot.box/#/s:spectradao.eth/proposal/0x8b2180dadff3768ddafcbb650568e9c6f9daca6e589b6f0f8ae4bab5f52ae042","https://gov.spectra.finance/t/create-fxsave-gauge-on-ethereum-mainnet/712"],"state":"closed","results":{"quorum":1,"totalScores":"423186.90","totalVotes":5,"choices":[{"id":0,"name":"For","scores":"423186.90"},{"id":1,"name":"Against","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["fxSAVE pool","f(x) Protocol 2.0","Spectra gauge system","Ethereum Mainnet","Liquidity boost","TVL increase","Yield opportunities"],"headline":"Spectra Integrates fxSAVE Pool from f(x) Protocol 2.0 to Enhance Liquidity and Yield on Ethereum Mainnet","type":"snapshot"},{"metadata":"ipfs:bafkreieco34tsbeybneuf37g5jywckxmgbvrdsojwz5hamc3gs53alrbiy","votingStartBlock":22260642,"ipfsData":"{\"text\":[\"Update StableswapNG parameters for pool 0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F with: amplification factor from 500 -> 350 ramped over 1 weeks starting on 2025-04-20 14:26:35+0000 and ending on 2025-04-27 14:26:35+0000. THIS IS A CORRECTION OF PROPOSAL 1026.\"]}","proposer":"0xDAa094A0Ed166FeDF8a0a4310f3F74a1e96F9195","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreieco34tsbeybneuf37g5jywckxmgbvrdsojwz5hamc3gs53alrbiy","votingEndTime":1745159231,"votingStartTime":1744554431,"id":"1030","cid":"bafkreieco34tsbeybneuf37g5jywckxmgbvrdsojwz5hamc3gs53alrbiy","score":0,"decayedScore":0,"searchKeywords":["Proposal","StableswapNG","Pool","Address","0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F","Amplification factor","500 to 350","April 20, 2025","April 27, 2025","Correction","Previous proposal","Proposal 1026","Liquidity","Trading efficiency","Stable pricing","Large volumes","Optimize performance","Parameter settings"],"globalTags":["Changes - Technical Change","Proposal - Seeking feedback"],"localTags":["StableswapNG","Amplification factor","Proposal 1026"],"totalVotersFor":4,"totalVoters":4,"totalWeightFor":5.178305800881332e+26,"totalWeight":5.178305800881332e+26,"proposalResults":"## How is the community reacting?\n\n- All 4 voters participated in favor of the proposal, with 100% of both voter count and voting weight (517,830,580.09) supporting it.\n- There is no opposition or abstention recorded.\n- Voter turnout is very low, with only 4 participants, but these voters represent a significant total voting weight.\n- The community reaction is unanimously positive among those who voted, but overall engagement appears limited.","currentStatus":"executed","currentStatusSinceTx":"0x4d573f53a6fd6c36879034d8a14dd333ff56bd9becf4eed9462e02ac49a4bca9","summary":"## What is this about?\n\nThis proposal seeks to update the StableswapNG parameters for the pool at address 0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F. Specifically, it proposes to change the amplification factor from 500 to 350, with the adjustment ramped over one week, starting on April 20, 2025, and ending on April 27, 2025. The proposal is a correction of a previous proposal (1026).\n\n## What could be the impact of this?\n\nLowering the amplification factor will affect the pool's pricing curve, potentially reducing slippage for trades near the equilibrium but increasing it for larger trades. This change may impact liquidity provider returns and the trading experience in the affected pool. As it corrects a previous proposal, it also ensures protocol parameters are accurately aligned with intended governance outcomes.","tldr":"This proposal aims to lower the amplification factor for the StableswapNG pool at 0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F from 500 to 350, ramping the change between April 20, 2025, and April 27, 2025, to better align protocol parameters and potentially adjust slippage and liquidity provider returns. All four voters, representing the full voting weight, supported the proposal, though overall participation was low.","headline":"Curve Proposal Seeks to Lower StableswapNG Pool Amplification Factor from 500 to 350 Over One Week","updated":1745198382,"timestamp":{"_seconds":1745198385,"_nanoseconds":140000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"id":"0x60c95ab69a427ce263f4c3c950df8da1134e96a3e76d139c8dac366271009530","title":"[EP 6.5] [Social] Service Provider Season 2 Vote Amendment Proposal II","summary":"$d5","tldr":"EP 6.5 amends the Service Provider Program's $4.5M Season 2 voting process to let voters rank both basic and extended budget requests for each team, increasing flexibility and precision in funding decisions. The proposal passed with strong community support, and its more nuanced voting system will now be implemented.","protocol":"ens","slug":"ep-65-social-service-provider-season-2-vote-amendment-proposal-ii","snapshotUrl":"https://snapshot.box/#/s:ens.eth/proposal/0x60c95ab69a427ce263f4c3c950df8da1134e96a3e76d139c8dac366271009530","startDate":1744547479,"endDate":1744979479,"updated":1744979494,"relatedLinks":["https://snapshot.box/#/s:ens.eth/proposal/0x60c95ab69a427ce263f4c3c950df8da1134e96a3e76d139c8dac366271009530","https://discuss.ens.domains/t/temp-check-social-service-provider-season-2-vote-amendment-proposal/20526/42?u=avsa"],"state":"closed","results":{"quorum":0,"totalScores":"1474982.79","totalVotes":161,"choices":[{"id":0,"name":"For","scores":"1157128.24"},{"id":1,"name":"Against","scores":"307248.71"},{"id":2,"name":"Abstain","scores":"10605.84"}]},"decayedScore":0,"score":2163.156917290685,"isFlagged":false,"globalTags":["Proposal - Result: Passed","Grants - Grant Program Update"],"localTags":["EP 6.5","Service Provider Program","Season 2","Ranked voting","Basic and extended budget requests","Nuanced voting system"],"headline":"ENS EP 6.5 Introduces Ranked Voting for Service Provider Program Season 2 Budget Requests","type":"snapshot"},{"id":"0xf0c3a2fe4bd085ea74a072cafb830aaadb4830b557a3d122eab36058a17c1860","title":"[EP 6.4] [Social] Service Provider Season 2 Vote Amendment Proposal","summary":"$d6","tldr":"This proposal changes the Service Provider Season 2 voting process by letting delegates rank both service providers and their budget options using Copeland pairwise comparison, aiming for more precise and efficient budget allocation of the $4.5M 2025 budget. The amendment passed with strong but not unanimous support, and implementation steps are underway, including updates to the voting UI and a window for proposal adjustments.","protocol":"ens","slug":"ep-64-social-service-provider-season-2-vote-amendment-proposal","snapshotUrl":"https://snapshot.box/#/s:ens.eth/proposal/0xf0c3a2fe4bd085ea74a072cafb830aaadb4830b557a3d122eab36058a17c1860","startDate":1744540200,"endDate":1744972200,"updated":1744972211,"relatedLinks":["https://snapshot.box/#/s:ens.eth/proposal/0xf0c3a2fe4bd085ea74a072cafb830aaadb4830b557a3d122eab36058a17c1860","https://discuss.ens.domains/t/temp-check-social-service-provider-season-2-vote-amendment-proposal/20526/54"],"state":"closed","results":{"quorum":0,"totalScores":"1553205.23","totalVotes":156,"choices":[{"id":0,"name":"For","scores":"916886.84"},{"id":1,"name":"Against","scores":"632185.54"},{"id":2,"name":"Abstain","scores":"4132.86"}]},"decayedScore":0,"score":2711.6249434930123,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["Service Provider Season 2","Copeland pairwise comparison","Budget allocation","Voting process amendment","Voting UI update","Proposal adjustment window","$$4.5M 2025 budget"],"headline":"ENS Adopts Copeland Pairwise Voting for Service Provider Budget Allocation","type":"snapshot"},{"metadata":"ipfs:bafkreiges6vhiziq4ltp4evsy5kdf2j5oy447ddzzzgdubx2hoy5baoekq","votingStartBlock":22257928,"ipfsData":"Add a gauge for the following pool: Resupply reUSD/fxUSD","proposer":"0xDd2f2858964c17486E1b8A7E337a5732170E3320","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreiges6vhiziq4ltp4evsy5kdf2j5oy447ddzzzgdubx2hoy5baoekq","votingEndTime":1745126531,"votingStartTime":1744521731,"id":"1029","cid":"bafkreiges6vhiziq4ltp4evsy5kdf2j5oy447ddzzzgdubx2hoy5baoekq","searchKeywords":["Proposal","Gauge","Liquidity pool","reUSD","fxUSD","Curve platform","CRV token emissions","Incentivizing liquidity providers","Trading efficiency","Slippage","Liquidity providers","Utility","Attractiveness","Curve ecosystem"],"globalTags":["Proposal - Seeking feedback"],"localTags":["Curve","Liquidity Pool","reUSD","fxUSD","CRV token emissions"],"score":0,"decayedScore":0,"totalVotersFor":6,"totalVoters":6,"totalWeightFor":5.02906907527426e+26,"totalWeight":5.02906907527426e+26,"proposalResults":"## How is the community reacting?\n\n- All 6 voters supported the proposal, resulting in 100% approval.\n- The total voting weight in favor is 502,906,907.53.\n- No votes were cast against the proposal.\n- Community participation appears low, with only 6 voters, but all voting power was aligned in support.","currentStatus":"executed","currentStatusSinceTx":"0x6f01ce401f04d59330c823a987742ac1764d013d5ca1d94dc0d2f7426eb3ca33","summary":"## What is this about?\n\nThis proposal seeks to add a gauge for the Resupply reUSD/fxUSD pool on Curve. Gauges are used to allocate CRV emissions to liquidity pools, incentivizing liquidity provision. The proposal includes a reference to additional metadata stored on IPFS.\n\n## What could be the impact of this?\n\nIf approved, the Resupply reUSD/fxUSD pool would become eligible for CRV rewards, likely increasing liquidity and trading activity in this pool. This could enhance the utility and stability of both reUSD and fxUSD within the Curve ecosystem.","tldr":"This proposal aims to add a gauge for the Resupply reUSD/fxUSD pool on Curve, enabling CRV rewards to incentivize liquidity, which could boost liquidity and trading for reUSD and fxUSD. The proposal received unanimous support from all 6 voters, though overall community participation was low.","headline":"Proposal to Add Gauge for Resupply reUSD/fxUSD Pool on Curve Approved Unanimously","updated":1745198382,"timestamp":{"_seconds":1745198383,"_nanoseconds":928000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"metadata":"ipfs:bafkreieqnve3icirq7qjfohtqiq64hscgpby37xuv5cm3xn75fpczp73lm","votingStartBlock":22257912,"ipfsData":"Add a gauge for the following pool: Resuply reUSD/sDOLA","proposer":"0x947B7742C403f20e5FaCcDAc5E092C943E7D0277","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreieqnve3icirq7qjfohtqiq64hscgpby37xuv5cm3xn75fpczp73lm","votingEndTime":1745126339,"votingStartTime":1744521539,"id":"1028","cid":"bafkreieqnve3icirq7qjfohtqiq64hscgpby37xuv5cm3xn75fpczp73lm","searchKeywords":["Proposal","Gauge","Liquidity Pool","reUSD","sDOLA","Curve platform","Liquidity providers","Rewards","IPFS","Metadata","Incentivize","Trading efficiency","Stability","User engagement"],"globalTags":["Proposal - Seeking feedback"],"localTags":["Curve","Liquidity Pool","reUSD","sDOLA","Gauge","IPFS"],"score":0,"decayedScore":0,"totalVotersFor":4,"totalVoters":4,"totalWeightFor":5.027090594371756e+26,"totalWeight":5.027090594371756e+26,"proposalResults":"## How is the community reacting?\n\n- All 4 voters (100%) supported the proposal.\n- The total voting weight was 502,709,059.44, with 100% of the weight in favor.\n- No votes were cast against the proposal.\n- Community participation appears low, with only 4 voters, but those who participated showed unanimous support.","currentStatus":"executed","currentStatusSinceTx":"0x64628e6b405c5d1b4579ac8ef0726fa8c0c0ece720cb80ad3d0e7649db026786","summary":"## What is this about?\n\nThis proposal seeks to add a gauge for the Resuply reUSD/sDOLA pool on Curve. The gauge would enable liquidity providers in this pool to earn CRV rewards. The proposal includes a reference to additional metadata stored on IPFS.\n\n## What could be the impact of this?\n\nIf approved, the addition of the gauge would incentivize greater liquidity in the reUSD/sDOLA pool by distributing CRV rewards to its participants. This could enhance the pool's depth, trading efficiency, and overall utility within the Curve ecosystem. It may also attract new users and increase protocol activity related to these assets.","tldr":"This proposal aims to add a gauge for the reUSD/sDOLA pool on Curve, allowing liquidity providers to earn CRV rewards and potentially increasing liquidity and trading efficiency for the pool. The community response was unanimously positive among the 4 voters, though overall participation was low.","headline":"Proposal to Add Gauge for reUSD/sDOLA Pool on Curve to Enable CRV Rewards","updated":1745198382,"timestamp":{"_seconds":1745198383,"_nanoseconds":508000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"accessLevel":"1","creationTime":1744361855,"ipfsData":"$d7","proposer":"0x57ab7ee15cE5ECacB1aB84EE42D5A9d0d8112922","coolDownBeforeVotingStart":86400,"yesThreshold":3.2e+23,"description":"$d8","minPropositionPower":80000,"yesNoDifferential":8e+22,"title":"April Funding update","votingPortal":"0xFe4683C18aaad791B6AFDF0a8e1Ed5C6e2c9ecD6","votingDuration":259200,"ipfsHash":"0x87a8aaaa34d0fbe1b588b7560fbf28d5bcff95417037e20f3529b79a3ae412ad","queuingTime":0,"id":"293","cid":"QmXUCvDhU8Zri5iv2CF368jksqx2EnSDLstvgUPZgutAbW","searchKeywords":["Aave","April Funding Update","Bridging funds","Polygon","Ethereum","GHO","Operational needs","FLUID","Aave Protocol Embassy","stataUSDT GSM exposure cap","CrossChainController","DAO","Liquidity","Buyback programs","Incentive campaigns","Financial stability","Operational efficiency"],"globalTags":["Grants - Grant Program Update","Proposal - Seeking feedback"],"localTags":["Aave Protocol Embassy","CrossChainController","Sonic incentive campaign","stataUSDT GSM exposure cap"],"votingStartBlock":22251832,"votingEndTime":1744707479,"votingStartTime":1744448279,"totalWeightAgainst":0,"currentStatus":"executed","currentStatusSinceTx":"0xf5451bf83065f7bba83e5b0c62cebf6ec64d24e8317be4970bf298e90678ae1c","summary":"$d9","totalVotersFor":63,"totalVoters":63,"totalWeightFor":1.0860091969774729e+24,"totalWeight":1.0860091969774729e+24,"score":0,"decayedScore":0,"proposalResults":"## How is the community reacting?\n\n- The proposal received unanimous support, with all 63 voters voting \"For\" and none voting \"Against.\"\n- The total voting weight in favor was 1,086,009.20, and the weight against was 0.00.\n- Both the vote differential (1,086,009.20) and the \"Yes\" weighted threshold (1,086,009.20) far exceeded the requirements of 80,000 and 320,000, respectively.\n- The community is strongly supportive of this proposal, with no opposition recorded.","tldr":"This proposal details operational funding and asset management actions for the Aave DAO, including consolidating assets on Ethereum, acquiring GHO, funding incentive campaigns, and adjusting stataUSDT risk parameters to improve efficiency and support DAO initiatives. The community unanimously supports the proposal, with no recorded opposition and all 63 voters in favor.","headline":"Aave DAO Proposal Seeks Asset Consolidation, GHO Acquisition, and Funding for Incentive Campaigns","updated":1744861480,"timestamp":{"_seconds":1744861482,"_nanoseconds":566000000},"type":"onchain","governor":"v3","protocol":"aave"},{"motionData":[{"token":"0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48","recipients":"0x606f77BF3dd6Ed9790D9771C7003f269a385D942"},{"recipients":"250000000000"}],"votingStartBlock":22248988,"proposer":"0x606f77BF3dd6Ed9790D9771C7003f269a385D942","description":"Top up Alliance Ops stables","votingEndTime":1744673303,"motionTargets":["0x3b525f4c059f246ca4aa995d21087204f30c9e2f","0xb9e5cbb9ca5b0d659238807e84d0176930753d86"],"votingStartTime":1744414103,"id":"819","objectionsThreshold":5e+24,"searchKeywords":["Proposal","Stablecoin reserves","Alliance Ops","Voting","April 11, 2025","April 14, 2025","5,000,000 weighted 'no' votes","Financial stability","Operational efficiency","Governance","Resource allocation"],"globalTags":["Proposal - Currently voting"],"localTags":["Alliance Ops","Stablecoin reserves"],"currentStatus":"executed","currentStatusSinceTx":"0xda39d715f6c3eadb15b7778f19c1cc897b83928190d70b447091a2dc9832baf7","summary":"## What is this about?\n\nThis proposal seeks approval to top up the Alliance Ops stablecoins. The voting period was from April 11 to April 14, 2025. The proposal would pass as long as objections (weighted 'no' votes) remain below 5,000,000.\n\n## What could be the impact of this?\n\nIf approved, Alliance Ops will receive additional stablecoins, potentially supporting its operational needs or initiatives. The decision threshold ensures that only significant opposition can block the top-up, streamlining funding for Alliance Ops.","tldr":"This proposal requests approval to provide more stablecoins to Alliance Ops, with the measure passing unless weighted 'no' votes exceed 5,000,000 during the voting period from April 11 to April 14, 2025. If approved, Alliance Ops will gain additional funding for its operations, with a streamlined process that limits the ability of minor opposition to block the top-up.","headline":"Lido Proposal Seeks Approval to Top Up Alliance Ops Stablecoins with Low Objection Threshold","updated":1744830945,"timestamp":{"_seconds":1744830947,"_nanoseconds":900000000},"type":"onchain","governor":"easyTrack","protocol":"lido"},{"votingStartBlock":22248232,"proposer":"0x9efdE135CA4832AbF0408c44c6f5f370eB0f35e8","quorum":4e+24,"description":"$da","votingEndTime":1744577543,"votingStartTime":1744404743,"id":"90","title":"# Update Revenue Percentage for DEX Pools, Add Fee Handler for USDe-USDT DEX, Set Launch Limits for LBTC-cbBTC <> cbBTC, LBTC-WBTC <> WBTC Vaults, Adjust Borrow Limits for LBTC-cbBTC <> WBTC and Update Lower Range Percet of wstETH-ETH Pool","votingEndBlock":22262632,"searchKeywords":["Instadapp protocol","DEX pools","Vaults","Revenue share model","Trading fees","Fee handler","USDe-USDT DEX pool","Launch limits","Borrow limits","wstETH-ETH pool","Avocado team multisig","Efficiency","Consistency","Revenue distribution","Financial sustainability","Fee management","Controlled launch","Over-leveraging","Market conditions","Stable trading outcomes"],"globalTags":["Changes - Technical Change","Proposal - Seeking feedback"],"localTags":["Instadapp","DEX pools","USDe-USDT DEX pool","wstETH-ETH pool","Avocado team multisig"],"score":0,"decayedScore":0,"totalWeightFor":4.7386641692512846e+24,"totalWeight":4.7386641692512846e+24,"totalVotersFor":12,"totalVoters":12,"proposalResults":"## How is the community reacting?\n\nThe community has shown unanimous support for the proposal, with all 12 voters casting their votes in favor. The total voting weight for the proposal is 4,738,664.17, which surpasses the quorum requirement of 4,000,000.00. This indicates strong backing from the community, as the proposal has not only met but exceeded the necessary quorum to pass.","currentStatus":"executed","currentStatusSinceTx":"0x0e87743070aa3cbc9c472cd6d9a13b15273036fafa8c176cae244fa3863c4ff6","summary":"$db","tldr":"This proposal standardizes DEX pool revenue sharing at 25%, introduces a fee handler for the USDe-USDT pool, sets vault limits, removes the Avocado team multisig from certain roles, and updates wstETH-ETH pool parameters, aiming to increase protocol revenue, improve efficiency, manage risk, and enhance decentralization. The community unanimously supports the proposal, with 12 votes and a total voting weight of 4,738,664.17, exceeding the quorum requirement of 4,000,000.00.","headline":"Instadapp Proposes Protocol Updates: Standardized DEX Revenue, Fee Management, Vault Limits, and Decentralization","updated":1744708778,"timestamp":{"_seconds":1744708781,"_nanoseconds":564000000},"type":"onchain","governor":"governance","protocol":"instadapp"},{"metadata":"ipfs:QmYTp7yefp6WiBzXXUwkFhV4PA2SG4qpTXWYdFrjuXZrQH","votingStartBlock":22246612,"ipfsData":"Add a gauge for the following stableswap-NG pool: Better Gold (XAUt-PAXG)","proposer":"0xf7Bd34Dd44B92fB2f9C3D2e31aAAd06570a853A6","quorum":0,"yesThreshold":0,"ipfsHash":"QmYTp7yefp6WiBzXXUwkFhV4PA2SG4qpTXWYdFrjuXZrQH","votingEndTime":1744990295,"votingStartTime":1744385495,"id":"1027","cid":"QmYTp7yefp6WiBzXXUwkFhV4PA2SG4qpTXWYdFrjuXZrQH","searchKeywords":["Proposal","Gauge","Stableswap-NG pool","Better Gold","XAUt-PAXG","Curve platform","Liquidity providers","Rewards","Incentivizing liquidity","Participation","Liquidity","Trading volume","Gold-backed stablecoins","Curve","Users","Trading","Gold-pegged assets","Protocol utility","Attractiveness"],"globalTags":["Proposal - Seeking feedback"],"localTags":["Curve","Gauge","Stableswap-NG","XAUt-PAXG","Gold-backed stablecoins"],"score":0,"decayedScore":0,"totalVotersFor":6,"totalVoters":6,"totalWeightFor":5.33395471608968e+26,"totalWeight":5.33395471608968e+26,"proposalResults":"## How is the community reacting?\n\n- All 6 voters supported the proposal, resulting in 100% approval.\n- The total voting weight in favor is 533,395,471.61.\n- No votes were cast against the proposal.\n- Community response is unanimously positive among participants, but overall voter turnout is low with only 6 voters.","currentStatus":"executed","currentStatusSinceTx":"0x14b175826c3e0d9523c0f313f0e48b3d86e67fe900e173730da5668cae1afb42","summary":"## What is this about?\n\nThis proposal suggests adding a gauge for a stableswap-NG pool containing Better Gold (XAUt-PAXG). The gauge would enable liquidity providers in this pool to receive CRV emissions as rewards. The proposal references additional metadata stored on IPFS.\n\n## What could be the impact of this?\n\nIf approved, the new gauge would incentivize liquidity provision for the XAUt-PAXG stableswap-NG pool, potentially increasing its liquidity and trading volume. This could enhance the utility and adoption of gold-backed tokens on Curve, while also expanding the protocol’s supported asset pools.","tldr":"A proposal to add a gauge for the stableswap-NG pool with XAUt-PAXG would reward liquidity providers with CRV emissions, aiming to boost liquidity and trading volume for gold-backed tokens on Curve. The community response is unanimously positive among the few who voted, with 100% approval and no opposition, but overall voter turnout is low.","headline":"Proposal to Add Gauge for XAUt-PAXG Stableswap-NG Pool on Curve Receives Unanimous Support","updated":1745075493,"timestamp":{"_seconds":1745075495,"_nanoseconds":471000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"currentStatus":"started","currentStatusSinceTx":"0x3e0b1b6082d6d050d8a83b66e0e566579d9100dd7c48b224d55266c5d649417f","metadata":"ipfs:bafkreidyg7mws4tn33ce7klgmge2gcqnvqitt2i5apaxaanu7ah4ucneae","votingStartBlock":22246476,"ipfsData":"Update StableswapNG parameters for pool 0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F with: amplification factor from 500 -> 1000 ramped over 1 weeks starting on 2025-04-18 15:03:59+0000 and ending on 2025-04-25 15:03:59+0000.","proposer":"0xDAa094A0Ed166FeDF8a0a4310f3F74a1e96F9195","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreidyg7mws4tn33ce7klgmge2gcqnvqitt2i5apaxaanu7ah4ucneae","votingEndTime":1744988663,"votingStartTime":1744383863,"id":"1026","cid":"bafkreidyg7mws4tn33ce7klgmge2gcqnvqitt2i5apaxaanu7ah4ucneae","summary":"## What is this about?\n\nThis proposal suggests updating the parameters for the StableswapNG pool identified by the address `0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F`. Specifically, it involves increasing the amplification factor from 500 to 1000. This change is planned to be gradually implemented over a one-week period, starting on April 18, 2025, and concluding on April 25, 2025.\n\n## What could be the impact of this?\n\nIncreasing the amplification factor in a stableswap pool can enhance the pool's efficiency in maintaining stable prices, especially during large trades. This adjustment could lead to improved liquidity and reduced slippage for users, potentially making the pool more attractive for trading stable assets.","globalTags":["Changes - Technical Change"],"searchKeywords":["Proposal","StableswapNG pool","0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F","Amplification factor","500 to 1000","April 18, 2025","April 25, 2025","Efficiency","Stable prices","Large trades","Liquidity","Reduced slippage","Stable assets"],"localTags":["StableswapNG","Amplification Factor"],"totalVotersFor":3,"totalWeightFor":1.460855014882518e+26,"totalVotersAgainst":4,"totalVoters":7,"totalWeight":5.3339050283731235e+26,"totalWeightAgainst":3.8730500134906046e+26,"score":3642.008010825275,"proposalResults":"## How is the community reacting?\n\n- The proposal has attracted a total of 7 voters, representing a combined voting weight of 533,390,502.84.\n- 3 voters (146,085,501.49 weight, or 27.40%) supported the proposal.\n- 4 voters (387,305,001.35 weight, or 72.60%) opposed the proposal.\n- The majority of voting weight is against the proposal, indicating that the community sentiment is predominantly negative.","tldr":"A proposal to increase the amplification factor of the StableswapNG pool at address 0xD65ed4BcE447195187f37cE7D82f56AdF1826F8F from 500 to 1000 between April 18, 2025 and April 25, 2025 aims to improve price stability and reduce slippage. However, the majority of the community voting weight (72.60%) is against the proposal.","headline":"Proposal to double Curve StableswapNG pool amplification factor from 500 to 1000 over one week","updated":1744769777,"timestamp":{"_seconds":1744769780,"_nanoseconds":515000000},"decayedScore":3523.3613349049956,"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"accessLevel":"1","creationTime":1744293179,"ipfsData":"$dc","proposer":"0xf71fc92e2949ccF6A5Fd369a0b402ba80Bc61E02","coolDownBeforeVotingStart":86400,"yesThreshold":3.2e+23,"description":"$dd","minPropositionPower":80000,"yesNoDifferential":8e+22,"title":"Caps Risk Oracle Activation on Base, Avalanche","votingPortal":"0xFe4683C18aaad791B6AFDF0a8e1Ed5C6e2c9ecD6","votingDuration":259200,"ipfsHash":"0xc4e57d0da88a6f7eb1a42d455d65adb6785158fd3152466c9e65203c5ce9c30d","queuingTime":0,"id":"292","cid":"QmbbFaYHd3KSS9K65TN96xCRMJXKyCAajcqxPgMkT7EdaU","searchKeywords":["Aave","AGRS","Base network","Avalanche network","Aave v3 Arbitrum","Dynamic management","Supply caps","Borrow caps","RiskOracle","AaveStewardCapsInjector","Whitelisted assets","RISK_ADMIN role","Cap adjustment","Market conditions","Stability","Performance"],"globalTags":["Changes - Technical Change","Proposal - Seeking feedback"],"localTags":["Aave Generalised Risk Stewards (AGRS)","RiskOracle","AaveStewardCapsInjector","RISK_ADMIN"],"votingStartBlock":22246124,"votingEndTime":1744638803,"votingStartTime":1744379603,"totalWeightAgainst":0,"currentStatus":"executed","currentStatusSinceTx":"0xd8cbcbc471a79cd2126a7efd49c61714c5d247e0bc309c301766dcfb866e14b4","summary":"$de","totalVotersFor":50,"totalVoters":50,"totalWeightFor":1.0837253330135782e+24,"totalWeight":1.0837253330135782e+24,"score":0,"decayedScore":0,"proposalResults":"## How is the community reacting?\n\n- The proposal received unanimous support, with all 50 voters voting \"For\" and none voting \"Against.\"\n- The total voting weight in favor is 1,083,725.33, while the weight against is 0.00.\n- Both the vote differential (1,083,725.33) and the \"Yes\" weighted threshold (1,083,725.33) far exceed the required minimums of 80,000 and 320,000, respectively.\n- The community is overwhelmingly supportive of this proposal, with no opposition recorded.","tldr":"This proposal seeks to deploy the automated AGRS system for managing supply and borrow caps on Aave v3 Base and Avalanche, aiming to improve efficiency and risk management through automation and integration with Chainlink Automation. The community is unanimously supportive, with no recorded opposition and all votes in favor.","headline":"Proposal to Extend Aave Generalised Risk Stewards Automation to Base and Avalanche Networks","updated":1744861479,"timestamp":{"_seconds":1744861481,"_nanoseconds":589000000},"type":"onchain","governor":"v3","protocol":"aave"},{"id":"0xfbaf8a48bc110a815e6b8cfaaf6c73451cb0c6e5e3d48e10e72893bf95911740","title":"[TEMP CHECK] Establish Uniswap v4 Licensing Process","summary":"$df","tldr":"This is about formalizing the process for managing Uniswap v4’s BSL exemptions and deployments, including creating tracking subdomains, granting the Uniswap Foundation a blanket exemption, and authorizing the UAC to manage the deployment registry. The proposal, which aims to accelerate v4 adoption and maintain a competitive edge until the license transitions to MIT in 2027, received overwhelming community support with over 41 million votes in favor.","protocol":"uniswap","slug":"temp-check-establish-uniswap-v4-licensing-process","snapshotUrl":"https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0xfbaf8a48bc110a815e6b8cfaaf6c73451cb0c6e5e3d48e10e72893bf95911740","startDate":1744362081,"endDate":1744794081,"updated":1744794101,"relatedLinks":["https://gov.uniswap.org/t/establish-uniswap-v4-licensing-process/25443","https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0xfbaf8a48bc110a815e6b8cfaaf6c73451cb0c6e5e3d48e10e72893bf95911740"],"state":"closed","results":{"quorum":10000000,"totalScores":"41288860.36","totalVotes":257,"choices":[{"id":0,"name":"For","scores":"41288828.60"},{"id":1,"name":"Against","scores":"31.38"},{"id":2,"name":"Abstain","scores":"0.38"}]},"decayedScore":0,"score":0.04559068438639131,"isFlagged":false,"globalTags":["Proposal - Result: Passed","Changes - Legal","Changes - New deployment","Newsworthy - Significant adoption"],"localTags":["Uniswap v4","BSL exemptions","Deployment registry","Uniswap Foundation","UAC","MIT license transition"],"headline":"Uniswap Proposes Formal Process for v4 BSL Exemptions and Deployment Management","type":"snapshot"},{"accessLevel":"1","creationTime":1744263611,"ipfsData":"$e0","proposer":"0xf71fc92e2949ccF6A5Fd369a0b402ba80Bc61E02","coolDownBeforeVotingStart":86400,"yesThreshold":3.2e+23,"description":"$e1","minPropositionPower":80000,"yesNoDifferential":8e+22,"title":"Removal of legacy VotingPortals from Governance v3","votingPortal":"0xFe4683C18aaad791B6AFDF0a8e1Ed5C6e2c9ecD6","votingDuration":259200,"ipfsHash":"0x2976c79737ef0a16930cab6eea90bf53c157fe01d9a3a904f435f266a4dddcf5","queuingTime":0,"id":"291","cid":"QmR8WUUNmDtZ6syGyYwXwyyEWLpzjzGwnpCogACsw4giKN","searchKeywords":["Proposal","Removal","Outdated VotingPortals","Aave Governance v3","Implementation","Proposal 273","Subsequent proposals","279 - 282","Eliminate","Confusion","Updated portals","Governance activities","Streamline","Efficiency","Reliability","Governance framework"],"globalTags":["Proposal - Currently voting"],"localTags":["Aave Governance v3","VotingPortals","Proposal 273","Governance framework"],"votingStartBlock":22243666,"votingEndTime":1744609235,"votingStartTime":1744350035,"totalWeightAgainst":0,"currentStatus":"executed","currentStatusSinceTx":"0x9ca3d9e47d8d68144316d96ec9086a52f8ba7e3e3bd24bff361de2e0a0c0bea2","summary":"## What is this about?\n\nThis proposal suggests the removal of outdated `VotingPortals` from Aave Governance v3. The new `VotingPortals` have been successfully tested and used in recent proposals, ensuring their reliability. The removal aims to eliminate any confusion or risk of using the deprecated portals for future proposals.\n\n## What could be the impact of this?\n\nRemoving the legacy `VotingPortals` will streamline the governance process by ensuring that only the updated, tested portals are used. This change reduces the potential for errors or misuse of outdated systems, enhancing the overall efficiency and security of the Aave governance framework.","totalVotersFor":50,"totalVoters":50,"totalWeightFor":1.0226233036599285e+24,"totalWeight":1.0226233036599285e+24,"score":0,"decayedScore":0,"proposalResults":"## How is the community reacting?\n\n- The proposal received unanimous support, with all 50 voters voting \"For\" and none voting \"Against.\"\n- Total voting weight was 1,022,623.30, all in favor, with 0.00 weight against.\n- Both the vote differential (1,022,623.30, exceeding the required 80,000) and the \"Yes\" weighted threshold (1,022,623.30, exceeding the required 320,000) were met by a wide margin.\n- The community is strongly supportive of this proposal, with no opposition recorded.","tldr":"This proposal is about removing outdated `VotingPortals` from Aave Governance v3 to ensure only the updated, reliable portals are used, which will improve efficiency and security. The community unanimously supports the change, with no recorded opposition and all voting thresholds exceeded.","headline":"Aave Proposal Seeks to Remove Outdated VotingPortals to Streamline Governance","updated":1744861481,"timestamp":{"_seconds":1744861482,"_nanoseconds":932000000},"type":"onchain","governor":"v3","protocol":"aave"},{"id":"0xaed836747d669ec0a9459e1c15a2a40621e066a9230e32ce830b6047dd8c70b0","title":"Upgrade Proposal #15: Isthmus Hard Fork","summary":"$e2","tldr":"The Citizens’ House unanimously decided not to veto Upgrade Proposal #15: Isthmus Hard Fork, allowing the upgrade to proceed as planned without delays or disruptions. This outcome reflects strong community consensus and confidence in both the proposal and the governance process.","protocol":"optimism","slug":"upgrade-proposal-15-isthmus-hard-fork","snapshotUrl":"https://snapshot.box/#/s:citizenshouse.eth/proposal/0xaed836747d669ec0a9459e1c15a2a40621e066a9230e32ce830b6047dd8c70b0","startDate":1744309261,"endDate":1744827661,"updated":1744827683,"relatedLinks":["https://snapshot.box/#/s:citizenshouse.eth/proposal/0xaed836747d669ec0a9459e1c15a2a40621e066a9230e32ce830b6047dd8c70b0","https://gov.optimism.io/t/upgrade-proposal-15-isthmus-hard-fork/9804"],"state":"closed","results":{"quorum":30,"totalScores":"32.00","totalVotes":32,"choices":[{"id":0,"name":"No Veto","scores":"32.00"},{"id":1,"name":"Veto","scores":0},{"id":2,"name":"I do not feel comfortable enough","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed","Newsworthy - Affecting Governance","Changes - Technical Change"],"localTags":["Citizens’ House","Upgrade Proposal #15","Isthmus Hard Fork","Community consensus"],"headline":"Citizens’ House Approves Isthmus Hard Fork, Signaling Community Optimism and Consensus","type":"snapshot"},{"id":"0xcadd1fcfd66913a953a12a9d07d052d0ff97ec16932c407a5582c66f279d5808","title":"Upgrade Proposal #14: Isthmus L1 Contracts + MT-Cannon","summary":"## What is this about?\n\nThis proposal concerns the Citizens’ House’s right to veto Protocol Upgrade Proposal #14: Isthmus L1 Contracts + MT-Cannon, which was previously approved by the Token House in Special Voting Cycle #35. The Citizens’ House could veto the upgrade if at least 30 members voted “Veto.” The proposal also introduced a third voting option to measure voter confidence.\n\n## What could be the impact of this?\n\nIf vetoed, the upgrade would not be enacted, potentially disrupting engineering timelines and milestones. However, since no veto was cast, the upgrade will proceed as planned, maintaining the current development trajectory.\n\n## How is the community reacting?\n\nThe community unanimously chose “No Veto” (31 out of 31 votes), indicating strong support or at least no significant opposition to the upgrade. No one expressed uncertainty or lack of confidence in voting, suggesting a clear understanding and consensus among voters.","tldr":"The Citizens’ House unanimously decided not to veto Protocol Upgrade Proposal #14, allowing the Isthmus L1 Contracts + MT-Cannon upgrade to proceed as planned without disruption. This outcome reflects strong community support and consensus, with no costs incurred from a veto.","protocol":"optimism","slug":"upgrade-proposal-14-isthmus-l1-contracts-mtcannon","snapshotUrl":"https://snapshot.box/#/s:citizenshouse.eth/proposal/0xcadd1fcfd66913a953a12a9d07d052d0ff97ec16932c407a5582c66f279d5808","startDate":1744308240,"endDate":1744826640,"updated":1744826654,"relatedLinks":["https://snapshot.box/#/s:citizenshouse.eth/proposal/0xcadd1fcfd66913a953a12a9d07d052d0ff97ec16932c407a5582c66f279d5808","https://gov.optimism.io/t/upgrade-proposal-14-isthmus-l1-contracts-mt-cannon/9796"],"state":"closed","results":{"quorum":30,"totalScores":"31.00","totalVotes":31,"choices":[{"id":0,"name":"No Veto","scores":"31.00"},{"id":1,"name":"Veto","scores":0},{"id":2,"name":"I do not feel comfortable enough","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed","Changes - Technical Change"],"localTags":["Citizens’ House","Protocol Upgrade Proposal #14","Isthmus L1 Contracts","MT-Cannon upgrade","Veto decision","Community consensus"],"headline":"Citizens’ House Approves Protocol Upgrade #14 for Isthmus L1 Contracts and MT-Cannon with Unanimous Support","type":"snapshot"},{"id":"0xe8105f767f9c5ec24bbc3f32b200ad204db6102649868cf2f4c5bc5d2f5f6011","title":"[BIP-812] Establishing the Balancer Alliance Program","summary":"$e3","tldr":"The proposal \"[BIP-812] Establishing the Balancer Alliance Program\" aims to align partners with the veBAL tokenomic model by incentivizing liquidity providers through revenue sharing, potentially enhancing liquidity and long-term participation in Balancer pools. The community has shown strong support, with unanimous voting in favor, and the next steps include implementing fee processing modifications and inviting protocols to join as Alliance members.","protocol":"balancer","slug":"bip812-establishing-the-balancer-alliance-program","snapshotUrl":"https://snapshot.box/#/s:balancer.eth/proposal/0xe8105f767f9c5ec24bbc3f32b200ad204db6102649868cf2f4c5bc5d2f5f6011","startDate":1744308000,"endDate":1744653600,"updated":1744653616,"relatedLinks":["https://forum.balancer.fi/t/bip-734-balancer-v3-launch-and-protocol-enhancements/6168","https://dune.com/queries/4746663","https://balancer.fi/pools/ethereum/v2/0x93d199263632a4ef4bb438f1feb99e57b4b5f0bd0000000000000000000005c2","https://dune.com/queries/4746791/7888262","https://docs.google.com/spreadsheets/d/1m7Npwr0eEJcao5G1-JbALIJYZ7fMtSFTOYOGnOXJtpE/edit?usp=sharing","https://discord.com/channels/@me/1300649462343139338/1349909682294358106","https://snapshot.box/#/s:balancer.eth/proposal/0xe8105f767f9c5ec24bbc3f32b200ad204db6102649868cf2f4c5bc5d2f5f6011","https://forum.balancer.fi/t/bip-812-establishing-the-balancer-alliance-program/6438"],"state":"closed","results":{"quorum":2000000,"totalScores":"3012334.30","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"3012334.30"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["BIP-812","Balancer Alliance Program","veBAL tokenomic model","Liquidity providers","Revenue sharing","Fee processing modifications","Alliance members"],"headline":"Balancer Alliance Program Proposal Gains Unanimous Support for veBAL Incentives","type":"snapshot"},{"id":"0xde4aded414e36534f2e97569115ff72d80bdfa179966cb4b6042f3770718c628","title":"[BIP-814] Grant Permissions for Latest V3 Chain Deployment: Optimism","summary":"$e4","tldr":"BIP-814 proposes extending Balancer V3 permissions to the Optimism chain, granting operational and emergency permissions to specific multisigs, which could enhance management efficiency and platform flexibility. The community unanimously supports the proposal, with all votes in favor, and the next step is to implement these permissions on Optimism.","protocol":"balancer","slug":"bip814-grant-permissions-for-latest-v3-chain-deployment-optimism","snapshotUrl":"https://snapshot.box/#/s:balancer.eth/proposal/0xde4aded414e36534f2e97569115ff72d80bdfa179966cb4b6042f3770718c628","startDate":1744308000,"endDate":1744653600,"updated":1744653615,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1908","https://forum.balancer.fi/t/bip-741-grant-v3-permissions-to-maxis-and-emergency-dao-multisigs/6220","https://forum.balancer.fi/t/bip-778-grant-maxis-stablesurge-parameter-change-permissions/6346","https://forum.balancer.fi/t/bip-787-grant-maxis-amplification-parameter-change-permissions-for-stablesurge-pools/6361","https://forum.balancer.fi/t/bip-790-grant-maxis-role-for-balancer-contract-registry/6370","https://forum.balancer.fi/t/bip-803-grant-v3-eclp-disable-permissions-to-the-emergency-dao-multisigs/6427","https://forum.balancer.fi/t/bip-789-grant-maxis-parameter-control-on-the-mev-tax-hook/6367","https://forum.balancer.fi/t/bip-670-update-the-optimism-fees-lm-multisig-to-include-beethoven-x-signers/5910","https://snapshot.box/#/s:balancer.eth/proposal/0xde4aded414e36534f2e97569115ff72d80bdfa179966cb4b6042f3770718c628","https://forum.balancer.fi/t/bip-814-grant-permissions-for-latest-v3-chain-deployment-optimism/6470"],"state":"closed","results":{"quorum":2000000,"totalScores":"3011676.06","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"3011676.06"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["BIP-814","Balancer V3","Optimism chain","Multisigs","Operational permissions","Emergency permissions"],"headline":"BIP-814 Approved: Balancer V3 to Extend Permissions to Optimism Chain","type":"snapshot"},{"id":"0x85f87aa704c0007019f7126a0e9ec70e3fb29eb92513fc5ee2a5d5a7ed244402","title":"[BIP-813] Grant Permissions for Latest V3 Chain Deployment: Avalanche","summary":"$e5","tldr":"BIP-813 proposes extending Balancer V3 permissions to the Avalanche chain, allowing entities like the Emergency DAO and Protocol Fee Sweeper to manage fees and emergencies, ensuring consistent governance and security. The community unanimously supports the proposal, with implementation as the next step.","protocol":"balancer","slug":"bip813-grant-permissions-for-latest-v3-chain-deployment-avalanche","snapshotUrl":"https://snapshot.box/#/s:balancer.eth/proposal/0x85f87aa704c0007019f7126a0e9ec70e3fb29eb92513fc5ee2a5d5a7ed244402","startDate":1744308000,"endDate":1744653600,"updated":1744653615,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1913","https://forum.balancer.fi/t/bip-741-grant-v3-permissions-to-maxis-and-emergency-dao-multisigs/6220","https://forum.balancer.fi/t/bip-778-grant-maxis-stablesurge-parameter-change-permissions/6346","https://forum.balancer.fi/t/bip-787-grant-maxis-amplification-parameter-change-permissions-for-stablesurge-pools/6361","https://forum.balancer.fi/t/bip-790-grant-maxis-role-for-balancer-contract-registry/6370","https://forum.balancer.fi/t/bip-797-wire-up-v3-protocol-fee-processing-permissions/6411","https://forum.balancer.fi/t/bip-803-grant-v3-eclp-disable-permissions-to-the-emergency-dao-multisigs/6427","https://snapshot.box/#/s:balancer.eth/proposal/0x85f87aa704c0007019f7126a0e9ec70e3fb29eb92513fc5ee2a5d5a7ed244402","https://forum.balancer.fi/t/bip-813-grant-permissions-for-latest-v3-chain-deployment-avalanche/6465"],"state":"closed","results":{"quorum":2000000,"totalScores":"3011680.55","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"3011680.55"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed","Changes - New deployment","Security"],"localTags":["BIP-813","Avalanche chain","Emergency DAO","Protocol Fee Sweeper"],"headline":"BIP-813 Gains Unanimous Support to Extend Balancer V3 Permissions to Avalanche Chain","type":"snapshot"},{"id":"0x83dd3ce2b1d8e945c82aeaefb3710a2862d73dc97956906733eec87ae038737a","title":"[BIP-811] Enable eBTC/wBTC eBTC/weETH eBTC/USDC Gauges [Arbitrum]","summary":"$e6","tldr":"The proposal \"[BIP-811] Enable eBTC/wBTC eBTC/weETH eBTC/USDC Gauges [Arbitrum]\" aims to enhance eBTC liquidity and yield optimization on the Arbitrum network by establishing liquidity pools on Balancer, which could increase eBTC's utility and adoption in DeFi. The community has shown strong support, with the proposal passing unanimously and exceeding the quorum requirement.","protocol":"balancer","slug":"bip811-enable-ebtcwbtc-ebtcweeth-ebtcusdc-gauges-arbitrum","snapshotUrl":"https://snapshot.box/#/s:balancer.eth/proposal/0x83dd3ce2b1d8e945c82aeaefb3710a2862d73dc97956906733eec87ae038737a","startDate":1744308000,"endDate":1744653600,"updated":1744653614,"relatedLinks":["http://ether.fi/","https://docs.lombard.finance/","https://dune.com/ether_fi/etherfi","https://etherfi.gitbook.io/etherfi/security/audits","https://balancer.fi/pools/arbitrum/v3/0x10f9e54aeea2fefa124238087dcfd919ba32f14d","https://balancer.fi/pools/arbitrum/v3/0x2d39c2ddf0ae652071d0550718cc7aacaf647d39","https://balancer.fi/pools/arbitrum/v3/0xa0e5e7728e026bde02810d255a6b94a9aa47b5f9","https://snapshot.box/#/s:balancer.eth/proposal/0x83dd3ce2b1d8e945c82aeaefb3710a2862d73dc97956906733eec87ae038737a","https://forum.balancer.fi/t/bip-811-enable-ebtc-wbtc-ebtc-weeth-ebtc-usdc-gauges-arbitrum/6458"],"state":"closed","results":{"quorum":2000000,"totalScores":"3012339.33","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"3012339.33"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["BIP-811","eBTC","wBTC","weETH","USDC","Gauges","Arbitrum","Liquidity pools","Balancer","DeFi"],"headline":"Balancer Proposal BIP-811 Approved to Boost eBTC Liquidity on Arbitrum","type":"snapshot"},{"id":"0x23943580643d6704c970d2dd7ac406ce2141a8951ce6a2859256e48643bff2d9","title":"[BIP-809] Enable YieldFi yUSD/USDC gauges on Balancer v3 Base deployment","summary":"$e7","tldr":"The proposal \"[BIP-809] Enable YieldFi yUSD/USDC gauges on Balancer v3 Base deployment\" aims to enhance liquidity and yield opportunities by redirecting rewards to a specific liquidity pool, potentially increasing Total Value Locked (TVL) and benefiting YieldFi, Balancer, and Aave. The community has shown unanimous support, and the next steps involve implementing the technical specifications to activate the gauge.","protocol":"balancer","slug":"bip809-enable-yieldfi-yusdusdc-gauges-on-balancer-v3-base-deployment","snapshotUrl":"https://snapshot.box/#/s:balancer.eth/proposal/0x23943580643d6704c970d2dd7ac406ce2141a8951ce6a2859256e48643bff2d9","startDate":1744308000,"endDate":1744653600,"updated":1744653613,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1901","https://etherscan.io/address/0x0D3F5D4022279c536a53aaa6bb8c225A0226d168","https://basescan.org/address/0x7Ac2f85069470959f5960B6054479aD46dB4d818","https://basescan.org/address/0x424d19d482a891b2c5cb881d651fbc32b349cb3c","https://yield.fi/","https://docs.yield.fi/","https://github.com/YieldFiLabs","https://x.com/getyieldfi","https://dune.com/queries/4756760/7896201","https://docs.yield.fi/resources/oracles","https://docs.yield.fi/resources/audits","https://dune.com/queries/4785783/7937254","https://snapshot.box/#/s:balancer.eth/proposal/0x23943580643d6704c970d2dd7ac406ce2141a8951ce6a2859256e48643bff2d9","https://forum.balancer.fi/t/bip-809-enable-yieldfi-yusd-usdc-gauges-on-balancer-v3-base-deployment/6457"],"state":"closed","results":{"quorum":2000000,"totalScores":"2890994.33","totalVotes":4,"choices":[{"id":0,"name":"Yes, let's do it","scores":"2890994.33"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed","Newsworthy - Technical"],"localTags":["BIP-809","YieldFi","yUSD/USDC gauges","Balancer v3 Base deployment","Total Value Locked (TVL)"],"headline":"BIP-809 Proposal to Boost Liquidity and TVL on Balancer v3 with YieldFi yUSD/USDC Gauges","type":"snapshot"},{"id":"0x0c47b5f5bbfdba42baf90b8418c9ecdd9c6e20a1c6b3deb7e3ee403be85ffce8","title":"[BIP-810] Enable slpUSD/waEthUSDC Gauge","summary":"$e8","tldr":"The proposal to enable a Balancer gauge for the slpUSD-waEthUSDC Stableswap pool on the Ethereum Mainnet aims to enhance liquidity, stability, and growth for slpUSD and Loop Finance, with unanimous community support evidenced by the voting results. The next step involves the Balancer Maxi LM Multisig adding the gauge to the Ethereum Mainnet.","protocol":"balancer","slug":"bip810-enable-slpusdwaethusdc-gauge","snapshotUrl":"https://snapshot.box/#/s:balancer.eth/proposal/0x0c47b5f5bbfdba42baf90b8418c9ecdd9c6e20a1c6b3deb7e3ee403be85ffce8","startDate":1744308000,"endDate":1744653600,"updated":1744653613,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1902","https://loopfi.xyz","https://docs.loopfi.xyz","https://github.com/orgs/LoopFi","https://discord.gg/mVqf2Q5Whg","https://docs.loopfi.xyz/extras/security","https://code4rena.com/bounties/loopfi#top","https://dune.com/rangonomics/loopfi","https://snapshot.box/#/s:balancer.eth/proposal/0x0c47b5f5bbfdba42baf90b8418c9ecdd9c6e20a1c6b3deb7e3ee403be85ffce8","https://forum.balancer.fi/t/bip-810-enable-slpusd-waethusdc-gauge/6462"],"state":"closed","results":{"quorum":2000000,"totalScores":"3012345.16","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"3012345.16"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["Balancer gauge","slpUSD-waEthUSDC Stableswap pool","Ethereum Mainnet","Loop Finance","Balancer Maxi LM Multisig"],"headline":"Balancer Gauge Proposal for slpUSD-waEthUSDC Pool Gains Unanimous Support","type":"snapshot"},{"id":"0xfc8692421985c2ad9caa2010711cb786a684ed4019251a8c8d8e06fe74347446","title":"[BIP-814] Grant Permissions for Latest V3 Chain Deployment: Optimism","summary":"$e9","tldr":"BIP-814 proposes extending V3 permissions to the Optimism chain, granting operational and emergency permissions to specific multisigs for efficient management of the Balancer protocol, which has been positively received by the community with unanimous support. The next step is to implement these permissions on Optimism following the proposal's approval.","protocol":"aura","slug":"bip814-grant-permissions-for-latest-v3-chain-deployment-optimism","snapshotUrl":"https://snapshot.box/#/s:aurafinance.eth/proposal/0xfc8692421985c2ad9caa2010711cb786a684ed4019251a8c8d8e06fe74347446","startDate":1744308000,"endDate":1744596000,"updated":1744596019,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1908","https://forum.balancer.fi/t/bip-741-grant-v3-permissions-to-maxis-and-emergency-dao-multisigs/6220","https://forum.balancer.fi/t/bip-778-grant-maxis-stablesurge-parameter-change-permissions/6346","https://forum.balancer.fi/t/bip-787-grant-maxis-amplification-parameter-change-permissions-for-stablesurge-pools/6361","https://forum.balancer.fi/t/bip-790-grant-maxis-role-for-balancer-contract-registry/6370","https://forum.balancer.fi/t/bip-803-grant-v3-eclp-disable-permissions-to-the-emergency-dao-multisigs/6427","https://forum.balancer.fi/t/bip-789-grant-maxis-parameter-control-on-the-mev-tax-hook/6367","https://forum.balancer.fi/t/bip-670-update-the-optimism-fees-lm-multisig-to-include-beethoven-x-signers/5910","https://snapshot.box/#/s:aurafinance.eth/proposal/0xfc8692421985c2ad9caa2010711cb786a684ed4019251a8c8d8e06fe74347446","https://forum.balancer.fi/t/bip-814-grant-permissions-for-latest-v3-chain-deployment-optimism/6470"],"state":"closed","results":{"quorum":0,"totalScores":"17555786.38","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"17555786.38"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["BIP-814","Optimism","Multisigs","Balancer protocol"],"headline":"BIP-814 to Extend V3 Permissions to Optimism Chain for Balancer Protocol Management","type":"snapshot"},{"id":"0xba191d572774b80fc35b63d0474702a464daea94d9e992ae13c22f139d35ce94","title":"[BIP-809] Enable YieldFi yUSD/USDC gauges on Balancer v3 Base deployment","summary":"$ea","tldr":"The proposal aims to enhance liquidity and Total Value Locked (TVL) on Base by enabling a root gauge on Ethereum to redirect rewards to a child gauge for the yUSD/waBasUSDC pool on Balancer v3, creating a high-yield stablecoin opportunity and strengthening synergies between YieldFi, Balancer, and Aave. The community has unanimously supported the proposal, and the next step involves implementing the technical specifications to add the gauge addresses.","protocol":"aura","slug":"bip809-enable-yieldfi-yusdusdc-gauges-on-balancer-v3-base-deployment","snapshotUrl":"https://snapshot.box/#/s:aurafinance.eth/proposal/0xba191d572774b80fc35b63d0474702a464daea94d9e992ae13c22f139d35ce94","startDate":1744308000,"endDate":1744596000,"updated":1744596019,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1901","https://etherscan.io/address/0x0D3F5D4022279c536a53aaa6bb8c225A0226d168","https://basescan.org/address/0x7Ac2f85069470959f5960B6054479aD46dB4d818","https://basescan.org/address/0x424d19d482a891b2c5cb881d651fbc32b349cb3c","https://yield.fi/","https://docs.yield.fi/","https://github.com/YieldFiLabs","https://x.com/getyieldfi","https://dune.com/queries/4756760/7896201","https://docs.yield.fi/resources/oracles","https://docs.yield.fi/resources/audits","https://dune.com/queries/4785783/7937254","https://snapshot.box/#/s:aurafinance.eth/proposal/0xba191d572774b80fc35b63d0474702a464daea94d9e992ae13c22f139d35ce94","https://forum.balancer.fi/t/bip-809-enable-yieldfi-yusd-usdc-gauges-on-balancer-v3-base-deployment/6457"],"state":"closed","results":{"quorum":0,"totalScores":"17555786.38","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"17555786.38"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["Liquidity Enhancement","Total Value Locked","Root Gauge","Child Gauge","yUSD/waBasUSDC Pool","Balancer v3","High-yield Stablecoin","YieldFi","Aave"],"headline":"Enhancing Base Liquidity: Community Supports New Gauge for yUSD/waBasUSDC Pool on Balancer v3","type":"snapshot"},{"id":"0x909463ea31b3a76d48f63014958bf081bd7b39b6b81b9e497d312cb4df11712e","title":"[BIP-812] Establishing the Balancer Alliance Program","summary":"$eb","tldr":"The proposal \"[BIP-812] Establishing the Balancer Alliance Program\" aims to align partners with the veBAL tokenomic model by sharing revenue in USDC converted to veBAL, incentivizing long-term engagement and liquidity provision. The community unanimously supports the initiative, and the next steps involve updating fee processing logic to implement the new fee-sharing model.","protocol":"aura","slug":"bip812-establishing-the-balancer-alliance-program","snapshotUrl":"https://snapshot.box/#/s:aurafinance.eth/proposal/0x909463ea31b3a76d48f63014958bf081bd7b39b6b81b9e497d312cb4df11712e","startDate":1744308000,"endDate":1744596000,"updated":1744596017,"relatedLinks":["https://snapshot.box/#/s:balancer.eth/proposal/0xe8105f767f9c5ec24bbc3f32b200ad204db6102649868cf2f4c5bc5d2f5f6011","https://forum.balancer.fi/t/bip-734-balancer-v3-launch-and-protocol-enhancements/6168","https://dune.com/queries/4746663","https://balancer.fi/pools/ethereum/v2/0x93d199263632a4ef4bb438f1feb99e57b4b5f0bd0000000000000000000005c2","https://snapshot.box/#/s:aurafinance.eth/proposal/0x909463ea31b3a76d48f63014958bf081bd7b39b6b81b9e497d312cb4df11712e","https://forum.balancer.fi/t/bip-812-establishing-the-balancer-alliance-program/6438"],"state":"closed","results":{"quorum":0,"totalScores":"17555786.38","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"17555786.38"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["BIP-812","Balancer Alliance Program","veBAL tokenomic model","USDC revenue sharing"],"headline":"[BIP-812] Proposal to Align Partners with veBAL Model Gains Community Support","type":"snapshot"},{"id":"0x764b37c520914020b91656b5d0ebc728d27e6dcdc0e0fa1818c1555116de6e89","title":"[BIP-810] Enable slpUSD/waEthUSDC Gauge","summary":"$ec","tldr":"The proposal to enable a Balancer gauge for the slpUSD-waEthUSDC Stableswap pool on Ethereum Mainnet aims to enhance liquidity, price stability, and yield opportunities for slpUSD, benefiting both Loop Finance and the Balancer ecosystem through revenue sharing and veBAL accumulation. The community has unanimously supported the proposal, and the next step involves adding the gauge via the Balancer Maxi LM Multisig.","protocol":"aura","slug":"bip810-enable-slpusdwaethusdc-gauge","snapshotUrl":"https://snapshot.box/#/s:aurafinance.eth/proposal/0x764b37c520914020b91656b5d0ebc728d27e6dcdc0e0fa1818c1555116de6e89","startDate":1744308000,"endDate":1744596000,"updated":1744596016,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1902","https://loopfi.xyz","https://docs.loopfi.xyz","https://github.com/orgs/LoopFi","https://discord.gg/mVqf2Q5Whg","https://docs.loopfi.xyz/extras/security","https://code4rena.com/bounties/loopfi#top","https://dune.com/rangonomics/loopfi","https://snapshot.box/#/s:aurafinance.eth/proposal/0x764b37c520914020b91656b5d0ebc728d27e6dcdc0e0fa1818c1555116de6e89","https://forum.balancer.fi/t/bip-810-enable-slpusd-waethusdc-gauge/6462"],"state":"closed","results":{"quorum":0,"totalScores":"17555786.38","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"17555786.38"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["Balancer gauge","slpUSD-waEthUSDC Stableswap pool","Ethereum Mainnet","Loop Finance","Revenue sharing","veBAL accumulation","Balancer Maxi LM Multisig"],"headline":"Balancer Gauge Proposal for slpUSD Stableswap Pool Gains Unanimous Support","type":"snapshot"},{"id":"0x44b702b259aa74004d3d768c0bb2f8197c3bc3ab3f4fcfd2dfc917e351df86c2","title":"[BIP-811] Enable eBTC/wBTC eBTC/weETH eBTC/USDC Gauges [Arbitrum]","summary":"$ed","tldr":"The proposal \"[BIP-811] Enable eBTC/wBTC eBTC/weETH eBTC/USDC Gauges [Arbitrum]\" aims to enhance eBTC liquidity and utility on the Arbitrum network by establishing pools with wBTC, weETH, and USDC on Balancer, which could increase trading efficiency and staking rewards. The community has shown unanimous support for the proposal, and the next steps involve executing transactions to implement the liquidity gauges.","protocol":"aura","slug":"bip811-enable-ebtcwbtc-ebtcweeth-ebtcusdc-gauges-arbitrum","snapshotUrl":"https://snapshot.box/#/s:aurafinance.eth/proposal/0x44b702b259aa74004d3d768c0bb2f8197c3bc3ab3f4fcfd2dfc917e351df86c2","startDate":1744308000,"endDate":1744596000,"updated":1744623215,"relatedLinks":["http://ether.fi/","https://docs.lombard.finance/","https://dune.com/ether_fi/etherfi","https://etherfi.gitbook.io/etherfi/security/audits","https://balancer.fi/pools/arbitrum/v3/0x10f9e54aeea2fefa124238087dcfd919ba32f14d","https://balancer.fi/pools/arbitrum/v3/0x2d39c2ddf0ae652071d0550718cc7aacaf647d39","https://balancer.fi/pools/arbitrum/v3/0xa0e5e7728e026bde02810d255a6b94a9aa47b5f9","https://snapshot.box/#/s:aurafinance.eth/proposal/0x44b702b259aa74004d3d768c0bb2f8197c3bc3ab3f4fcfd2dfc917e351df86c2","https://forum.balancer.fi/t/bip-811-enable-ebtc-wbtc-ebtc-weeth-ebtc-usdc-gauges-arbitrum/6458"],"state":"closed","results":{"quorum":0,"totalScores":"17555786.38","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"17555786.38"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["BIP-811","eBTC","wBTC","weETH","USDC","Arbitrum","Balancer","Liquidity Gauges"],"headline":"[BIP-811] Proposal to Boost eBTC Liquidity on Arbitrum with Balancer Pools","type":"snapshot"},{"id":"0x3b2dcf8e2a25bdd6119129c796d068f114fc777029a1d941fff355dffa6feed6","title":"[BIP-813] Grant Permissions for Latest V3 Chain Deployment: Avalanche","summary":"$ee","tldr":"BIP-813 proposes extending Balancer V3 permissions to the Avalanche chain, enhancing protocol functionality and governance, with unanimous community support from 5 voters totaling 13,539,736.54 votes in favor. The proposal is likely to pass, enabling improved management of fees, pool operations, and contract updates on the Avalanche chain.","protocol":"aura","slug":"bip813-grant-permissions-for-latest-v3-chain-deployment-avalanche","snapshotUrl":"https://snapshot.box/#/s:aurafinance.eth/proposal/0x3b2dcf8e2a25bdd6119129c796d068f114fc777029a1d941fff355dffa6feed6","startDate":1744308000,"endDate":1744596000,"updated":1744528165,"relatedLinks":["https://github.com/BalancerMaxis/multisig-ops/pull/1913","https://forum.balancer.fi/t/bip-741-grant-v3-permissions-to-maxis-and-emergency-dao-multisigs/6220","https://forum.balancer.fi/t/bip-778-grant-maxis-stablesurge-parameter-change-permissions/6346","https://forum.balancer.fi/t/bip-787-grant-maxis-amplification-parameter-change-permissions-for-stablesurge-pools/6361","https://forum.balancer.fi/t/bip-790-grant-maxis-role-for-balancer-contract-registry/6370","https://forum.balancer.fi/t/bip-797-wire-up-v3-protocol-fee-processing-permissions/6411","https://forum.balancer.fi/t/bip-803-grant-v3-eclp-disable-permissions-to-the-emergency-dao-multisigs/6427","https://snapshot.box/#/s:aurafinance.eth/proposal/0x3b2dcf8e2a25bdd6119129c796d068f114fc777029a1d941fff355dffa6feed6","https://forum.balancer.fi/t/bip-813-grant-permissions-for-latest-v3-chain-deployment-avalanche/6465"],"state":"active","results":{"quorum":0,"totalScores":"13539736.54","totalVotes":5,"choices":[{"id":0,"name":"Yes, let's do it","scores":"13539736.54"},{"id":1,"name":"No, this is not the way","scores":0},{"id":2,"name":"Abstain","scores":0}]},"decayedScore":0,"score":0,"isFlagged":false,"globalTags":["Proposal - Result: Passed"],"localTags":["BIP-813","Balancer V3","Avalanche chain"],"headline":"BIP-813 Gains Unanimous Support to Extend Balancer V3 Permissions to Avalanche Chain","type":"snapshot"},{"id":"0xad0e29aa7bc8e783c15b959b92b02b871af879b8f36372e80fc5ff5fc189ed8f","title":"[TEMP CHECK] BoB Uniswap v3 Incentives Package","summary":"$ef","tldr":"The Uniswap Growth Program and BOB proposed and passed a $375,000 UNI incentives package to boost Uniswap v3 liquidity and adoption on the BOB Hybrid Layer 2 network, with BOB matching $500,000 in incentives. The initiative aims to strengthen Uniswap’s presence in Bitcoin DeFi, deepen liquidity, and was met with strong community support, with no significant opposition or noted costs beyond the incentives.","protocol":"uniswap","slug":"temp-check-bob-uniswap-v3-incentives-package","snapshotUrl":"https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0xad0e29aa7bc8e783c15b959b92b02b871af879b8f36372e80fc5ff5fc189ed8f","startDate":1744300800,"endDate":1744732800,"updated":1744732807,"relatedLinks":["https://gov.uniswap.org/t/application-for-canonical-uniswap-v3-deployment-on-bob/24693","https://defillama.com/chain/BOB","https://defillama.com/protocol/uniswap-v3","https://defillama.com/chains/Superchain","https://blog.gobob.xyz/posts/bob-integrates-with-babylon-to-become-a-bitcoin-secured-network-bringing-bitcoin-finality-to-the-hybrid-l2","https://docs.gobob.xyz/whitepaper.pdf","https://blog.gobob.xyz/posts/bob-hybrid-l2-technical-blueprint","https://bitvm.org/bitvm_bridge.pdf","https://oku.trade/info/bob/overview","https://blog.gobob.xyz/posts/announcing-bob-rise-a-new-defi-campaign-in-collaboration-with-optimism","http://bobrise.xyz","https://app.charmverse.io/op-grants/build-the-future-of-bitcoin-defi-on-the-superchain-with-bob-01674730223691645","https://blog.gobob.xyz/posts/bob-fusion-the-final-season","https://app.gobob.xyz/fusion","https://gov.uniswap.org/t/uniswap-revitalization-and-growth/22616?u=getty","https://snapshot.box/#/s:uniswapgovernance.eth/proposal/0xad0e29aa7bc8e783c15b959b92b02b871af879b8f36372e80fc5ff5fc189ed8f","https://gov.uniswap.org/t/rfc-uniswap-onboarding-package-for-bob/25436"],"state":"closed","results":{"quorum":10000000,"totalScores":"37834497.80","totalVotes":219,"choices":[{"id":0,"name":"For $375k","scores":"32829328.81"},{"id":1,"name":"Against","scores":"4.95"},{"id":2,"name":"Abstain","scores":"5005164.04"}]},"decayedScore":0,"score":1529.2929014937865,"isFlagged":false,"globalTags":["Grants - Grant Funding","Proposal - Result: Passed","Newsworthy - Significant adoption"],"localTags":["Uniswap Growth Program","BOB Hybrid Layer 2","Bitcoin DeFi","Uniswap v3 liquidity","UNI incentives package"],"headline":"Uniswap Approves $375K Incentives Package for v3 Liquidity on BOB Hybrid Layer 2, Matched by BOB","type":"snapshot"},{"votingStartBlock":1744297021,"countingMode":"support=bravo&quorum=for¶ms=fractional","proposer":"0xc11846203b0121C28285FA89EAd2249AafffaD2C","quorum":6.3e+26,"description":"$f0","votingStartTime":1744297021,"id":"112142012854508751423955156601121618924383324119199970784935099214632480260394","title":"# [ZIP-9] V27 EVM Emulation Upgrade","searchKeywords":["ZIP-9","ZKsync","Version 27","EVM emulation","Fflonk verifier","Ethereum Virtual Machine","EVM contracts","Compatibility","Ethereum tools","Frameworks","Proof verification","Security","Transaction costs","Developer experience","Integration","Solidity","Vyper","Foundry","Hardhat","Adoption","Interoperability","Ethereum Layer 1","Execution costs","EraVM contracts","EVM equivalence"],"globalTags":["Changes - Technical Change"],"localTags":["ZIP-9","ZKsync V27","EVM emulation","Fflonk verifier"],"votingEndTime":1745005019,"votingEndBlock":1745005019,"totalVotersAbstain":70,"totalWeightAbstain":1.0694857393199044e+24,"totalVotersAgainst":60,"totalWeightAgainst":1.530453442357252e+23,"totalVotersFor":2681,"totalVoters":2811,"totalWeightFor":8.138736930468708e+26,"totalWeight":8.150962241304261e+26,"score":46.252294687977006,"decayedScore":46.09554851898731,"proposalResults":"## How is the community reacting?\n\n- The proposal attracted participation from 2,811 voters, with a total voting weight of 815,096,224.13.\n- The vast majority of votes were in favor: 2,681 voters (95.38%) representing 813,873,693.05 in weight (99.85% of total weight).\n- Only 60 voters (2.13%) were against, with a weight of 153,045.34 (0.02%).\n- 70 voters (2.49%) abstained, with a weight of 1,069,485.74 (0.13%).\n- The quorum was set at 630,000,000.00 (for votes only), and the proposal easily surpassed this with 813,873,693.05 \"for\" weight.\n- The community overwhelmingly supports the proposal, with minimal opposition or abstention.","proposalVoteReasons":"$f1","currentStatus":"executed","currentStatusSinceTx":"0xef8d3d6c0afde1cd9f867a82e32dad5a4fab54c7dc7f81f920fc611b0224540e","summary":"$f2","tldr":"This proposal introduces ZIP-9 (V27 upgrade) for ZKsync, adding optional EVM emulation for seamless Ethereum contract deployment and a Fflonk verifier to reduce on-chain proof costs by about 30%, with minor overhead for EVM contracts but significant improvements in compatibility and cost efficiency. The community overwhelmingly supports the upgrade, citing enhanced developer experience, scalability, and backward compatibility, with minimal opposition or abstention.","headline":"ZKsync Proposes V27 Upgrade (ZIP-9) with Optional EVM Emulation and Fflonk Verifier for Lower Costs and Greater Compatibility","updated":1745029350,"timestamp":{"_seconds":1745029354,"_nanoseconds":728000000},"type":"onchain","governor":"ZkProtocolGovernor","protocol":"zksync"},{"currentStatus":"created","currentStatusSinceTx":"0xaec1a75ad275294a8157711f1f6638975d8cf72efbc80e285dfcd75d41ca2d7c","votingStartBlock":22239098,"proposer":"0x393BC37ea5493233D2bDC68FD59Dd97Ee01B18Cf","quorum":2.5e+24,"description":"\"This proposal will execute the revoke function on Wonderland's vesting contract, following the successful completion of their work with Grants Lab as outlined in the original July 2023 proposal.\\n\\nAs agreed with Wonderland, this action will:\\n\\n* Stop the remaining vesting schedule\\n* Transfer already vested tokens to Wonderland\\n* Return any unvested tokens to the Gitcoin treasury\\n\\n\\n\\nWonderland has successfully delivered their technical and product management support for Grants Lab over the contracted period. This cancellation represents the planned conclusion of our engagement.\\n\\nIt's been a valuable partnership with the Wonderland team, and we look forward to potential future collaborations.\\n\\n\\n\\nOriginal proposals below. \"","votingEndTime":1744778279,"votingStartTime":1744294439,"id":"108988307804034315231415885432719400721031490539119630109782735447784485014013","title":"# Revoke Wonderland Vesting Contract - Contract Termination ","votingEndBlock":22279418,"summary":"## What is this about?\n\nThis proposal seeks to execute the revoke function on Wonderland's vesting contract with Gitcoin, marking the end of their collaboration. Wonderland has completed its commitments in providing technical and product management support for Grants Lab as per the agreement in the July 2023 proposal. The proposal outlines the cessation of the vesting schedule, the transfer of vested tokens to Wonderland, and the return of unvested tokens to the Gitcoin treasury.\n\n## What could be the impact of this?\n\nThe termination of the vesting contract will finalize the financial and contractual obligations between Gitcoin and Wonderland. This action will ensure that Wonderland receives the tokens they have earned, while unvested tokens will be returned to Gitcoin's treasury, potentially freeing up resources for future initiatives. The successful completion of this partnership may also pave the way for future collaborations between Gitcoin and Wonderland.","searchKeywords":["Proposal","Revoke function","Wonderland","Vesting contract","Gitcoin","Collaboration","Technical support","Product management","Grants Lab","July 2023 proposal","Cessation","Vested tokens","Unvested tokens","Gitcoin treasury","Financial obligations","Contractual obligations","Partnership","Future collaborations"],"globalTags":["Proposal - Result: Passed"],"localTags":["Wonderland","Gitcoin","Vesting Contract","Grants Lab","Token Transfer"],"totalVotersAbstain":8,"totalWeightAbstain":16582139490200345000,"totalVotersAgainst":17,"totalWeightAgainst":31239427034689560000,"totalVotersFor":175,"totalVoters":200,"totalWeightFor":1.2749165608152812e+24,"totalWeight":1.274964382381806e+24,"score":1.7376150287144527,"decayedScore":1.733205933532374,"proposalResults":"## How is the community reacting?\n\n- The proposal received participation from 200 voters, with a total voting weight of 1,274,964.38.\n- 175 voters (weight: 1,274,916.56) supported the proposal, representing 99.99% of the total voting weight.\n- 17 voters (weight: 31.24) voted against, and 8 voters (weight: 16.58) abstained.\n- The quorum requirement was 2,500,000.00, but only 1,274,964.38 voting weight was reached—approximately 50.99% of the required quorum.\n- Despite overwhelming support, the proposal did not meet quorum and therefore does not pass. Community sentiment is strongly in favor, but turnout was insufficient.","proposalVoteReasons":"- The main reason for voting FOR was satisfaction with the team's performance; they delivered as promised and met the community's requirements.\n- The resulting stable data layer was specifically highlighted as a positive outcome.\n- The sentiment expressed was positive and appreciative, indicating trust and willingness to collaborate again in the future.","tldr":"This proposal aimed to end Wonderland's vesting contract with Gitcoin, transferring vested tokens to Wonderland and returning unvested tokens to Gitcoin, with strong community support (99.99% by voting weight) but insufficient turnout to meet quorum, so the proposal did not pass. The community expressed satisfaction with Wonderland's performance and a positive outlook for future collaboration, with no costs or negative impacts identified.","headline":"Gitcoin Proposal to End Wonderland Vesting Contract Fails Due to Low Quorum Despite Strong Support","updated":1744785055,"timestamp":{"_seconds":1744785058,"_nanoseconds":440000000},"type":"onchain","governor":"v2","protocol":"gitcoin"},{"votingStartBlock":10384417,"proposer":"0x10b83c88e88910Cd5293324800d1a6e751004bE5","quorum":1e+26,"description":"$f3","votingEndTime":1744479252,"votingStartTime":1744220052,"id":"92","title":"# MIP-X19 Automated Liquidity Incentive Proposal","searchKeywords":["MIP-X19","Automated Liquidity Incentive Proposal","Moonwell protocol","Liquidity incentives","Base","Optimism","Moonbeam","ETH","USDC","AERO","Supply APY","Borrow APY","WELL Supply APR","OP Supply APR","April 18, 2025","May 16, 2025","Market conditions","Liquidity","User engagement","Borrowing behaviors","Lending behaviors","Liquidity stability"],"globalTags":["Proposal - Seeking feedback"],"localTags":["MIP-X19","Automated Liquidity Incentive","Moonwell Protocol","Base","Optimism","Moonbeam"],"totalWeightAbstain":1.0962072824369902e+24,"totalWeight":1.9679747258976672e+26,"totalWeightFor":1.9447450007340774e+26,"totalWeightAgainst":1.226765233921997e+24,"score":282.97786460322493,"proposalResults":"## How is the community reacting?\n\nThe proposal has received significant community engagement, with a total voting weight of 196,797,472.59. The quorum requirement of 100,000,000.00 has been surpassed, indicating strong participation.\n\n- **Weight For:** The majority of the community supports the proposal, with a voting weight of 194,474,500.07.\n- **Weight Against:** A smaller portion of the community opposes the proposal, with a voting weight of 1,226,765.23.\n- **Weight Abstain:** A voting weight of 1,096,207.28 represents those who chose to abstain from voting.\n\nOverall, the proposal has received overwhelming support from the community, with the \"For\" votes vastly outnumbering the \"Against\" votes.","decayedScore":274.7531007744401,"currentStatus":"executed","currentStatusSinceTx":"0xd362b3932999b6b40549c111d95eefbc5719c3837dee539ca46b121e6bf1fe5d","summary":"## What is this about?\n\nThis proposal, titled \"MIP-X19 Automated Liquidity Incentive Proposal,\" aims to automate the distribution and adjustment of liquidity incentives for the Moonwell protocol across the Base, Optimism, and Moonbeam networks. The proposal outlines specific metrics and changes for various assets, including adjustments to the WELL and OP token distributions, supply and borrow APYs, and daily incentives in USD. The proposal is set to take effect from April 18, 2025, to May 16, 2025.\n\n## What could be the impact of this?\n\nIf successful, the proposal would lead to a more dynamic and responsive allocation of liquidity incentives, potentially enhancing market efficiency and participation. Adjustments in WELL and OP distributions could affect the attractiveness of certain assets, influencing user behavior in terms of supply and borrowing. The proposal's automation aspect could streamline governance processes, reducing manual intervention and allowing for quicker adaptations to market conditions.","tldr":"The \"MIP-X19 Automated Liquidity Incentive Proposal\" seeks to automate liquidity incentives for the Moonwell protocol on Base, Optimism, and Moonbeam networks, aiming to enhance market efficiency and streamline governance by reducing manual intervention. The proposal, set to be implemented from April 18, 2025, to May 16, 2025, has received overwhelming community support, with the majority voting in favor.","headline":"Moonwell's MIP-X19 Proposal for Automated Liquidity Incentives Gains Strong Community Support","updated":1744571555,"timestamp":{"_seconds":1744571557,"_nanoseconds":917000000},"type":"onchain","governor":"govMultichain","protocol":"moonwell"},{"metadata":"ipfs:QmS81QBkRpwaicXFLJFeQG95RLWaSuEeR8wxk5kfisF8HL","votingStartBlock":22232820,"ipfsData":"Transfer 60k OP grant to distributor contract on Optimism to bootstrap LlamaLend. https://gov.curve.fi/t/bootstrap-optimism-llamalend-markets-with-60k-op-from-dao-vault/10569","proposer":"0x34d6Dbd097f6b739C59D7467779549Aea60e1F84","quorum":0,"yesThreshold":0,"ipfsHash":"QmS81QBkRpwaicXFLJFeQG95RLWaSuEeR8wxk5kfisF8HL","votingEndTime":1744824239,"votingStartTime":1744219439,"id":"1025","cid":"QmS81QBkRpwaicXFLJFeQG95RLWaSuEeR8wxk5kfisF8HL","searchKeywords":["60,000 OP grant","Distributor contract","Optimism network","Bootstrap","LlamaLend","Curve DAO","Voting","DAO vault","Development","Growth","Market establishment","Capabilities","Adoption","Utility","Presence","Influence","Decentralization","Innovation"],"globalTags":["Grants - Grant Proposal / Application","Proposal - Currently voting"],"localTags":["LlamaLend","Optimism network","Curve DAO"],"score":0,"decayedScore":0,"totalVotersFor":9,"totalVoters":9,"totalWeightFor":4.937223500600034e+26,"totalWeight":4.937223500600034e+26,"proposalResults":"## How is the community reacting?\n\n- All 9 voters participated in favor of the proposal, resulting in 100% support.\n- The total voting weight was 493,722,350.06, with the entire weight cast in support.\n- There were no votes against or abstentions, indicating unanimous community approval among participants.","currentStatus":"executed","currentStatusSinceTx":"0x1a5ba394d319d6151caa5138f9ea513bcb7a616cd1dc1d55085e9f6ec1eceba4","summary":"## What is this about?\n\nThis proposal seeks approval to transfer a 60,000 OP grant from the DAO vault to a distributor contract on Optimism. The purpose is to bootstrap LlamaLend markets on the Optimism network. More details are available in the linked governance forum post.\n\n## What could be the impact of this?\n\nIf approved, the grant will provide initial liquidity and incentives for LlamaLend on Optimism, potentially accelerating its adoption and growth. This could strengthen Curve’s presence on Optimism and support broader ecosystem development by encouraging lending activity and user participation.","tldr":"A proposal to transfer a 60,000 OP grant from the DAO vault to bootstrap LlamaLend markets on Optimism received unanimous community approval, with all voting weight in favor. The grant aims to provide initial liquidity and incentives, potentially accelerating LlamaLend adoption and strengthening Curve’s presence on Optimism, with no mentioned costs.","headline":"Curve Proposal Seeks Approval to Transfer 60,000 OP Grant for LlamaLend Markets on Optimism","updated":1744876711,"timestamp":{"_seconds":1744876713,"_nanoseconds":133000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"votingStartBlock":1744126091,"countingMode":"support=bravo&quorum=for,abstain","proposer":"0xc164411CCb8468E0c9F6a0Fc0B06E69f5845AC30","description":"$f4","votingEndTime":1744385291,"votingStartTime":1744126091,"id":"50762737827158927507207383385085921787966548787879753729017259789692735156595","title":"# [IP] eUSD Revenue Share Update 2025-04-1 ","votingEndBlock":1744385291,"searchKeywords":["Proposal","Revenue-sharing model","eUSD","Fintech companies","Ugly Cash","Sentz","stRSR","RToken Champion","Bi-weekly adjustment","Incentivize","Engagement","Promotion","Dynamic model","Responsive model","Adoption","Stability"],"globalTags":["Proposal - Seeking feedback"],"localTags":["eUSD","Revenue-sharing model","Ugly Cash","Sentz","stRSR","RToken Champion"],"score":0,"decayedScore":0,"quorum":-1890518040176527000,"totalVotersFor":4,"totalVoters":4,"totalWeightFor":5.658270654068476e+26,"totalWeight":5.658270654068476e+26,"proposalResults":"## How is the community reacting?\n\nThe community has shown unanimous support for the proposal, with all 4 voters casting their votes in favor. The total voting weight for the proposal is 565,827,065.41. The quorum is set at -1.89, and it considers only the votes of type \"for\" and \"abstain.\"","currentStatus":"executed","currentStatusSinceTx":"0xfd0a12986fb461d0cdb3e52a265d85e58a14cc56b239cb20185bb99efbacaa01","summary":"$f5","tldr":"The proposal suggests updating the revenue-sharing model for eUSD to better reflect the holdings of partners like Ugly Cash and Sentz, increasing their shares while slightly reducing stRSR's share, aiming for a fairer distribution that incentivizes partner engagement. The community has unanimously supported the proposal, indicating strong approval for the changes.","headline":"Proposal to Adjust eUSD Revenue-Sharing Model Gains Unanimous Support","updated":1744682054,"timestamp":{"_seconds":1744682058,"_nanoseconds":504000000},"type":"onchain","governor":"v2","protocol":"reserve"},{"motionData":[{"recipients":"0x87D93d9B2C672bf9c9642d853a8682546a5012B5","amounts":"100000000000000000000"}],"votingStartBlock":22224708,"proposer":"0x87D93d9B2C672bf9c9642d853a8682546a5012B5","description":"Top up stETH reward program","votingEndTime":1744380803,"motionTargets":["0x48c4929630099b217136b64089e8543db0e5163a","0xb9e5cbb9ca5b0d659238807e84d0176930753d86"],"votingStartTime":1744121603,"id":"818","objectionsThreshold":5e+24,"searchKeywords":["Proposal","stETH reward program","Voting","April 8, 2025","April 11, 2025","5,000,000 weighted 'no' votes","Incentives","Participants","Engagement","Participation","Lido protocol","Liquidity","Stability","Ecosystem"],"globalTags":["Proposal - Currently voting"],"localTags":["stETH reward program","Lido protocol"],"currentStatus":"executed","currentStatusSinceTx":"0xa720815e4e45036a48ae51151ac925a1b7e64e96e5f1e4a0bec59671b5c80549","summary":"## What is this about?\n\nThis proposal concerns the continuation of the stETH reward program by topping up its funds. The proposal is subject to a voting process, where it will pass if there are fewer than 5,000,000 weighted 'no' votes. The voting period started on April 8, 2025, and ended on April 11, 2025.\n\n## What could be the impact of this?\n\nIf passed, the proposal would ensure the continuation of the stETH reward program, potentially increasing incentives for participants and maintaining or enhancing engagement within the Lido ecosystem. This could lead to sustained or increased staking activity, benefiting the overall network.","tldr":"The proposal aims to continue the stETH reward program by replenishing its funds, with the decision based on a voting process that concluded on April 11, 2025. If approved, it could enhance participant incentives and engagement in the Lido ecosystem, potentially boosting staking activity and benefiting the network.","headline":"Lido Proposal for stETH Reward Program Continuation Under Voting Process","updated":1744404326,"timestamp":{"_seconds":1744404327,"_nanoseconds":787000000},"type":"onchain","governor":"easyTrack","protocol":"lido"},{"motionData":[{"recipients":"0x87D93d9B2C672bf9c9642d853a8682546a5012B5","amounts":"1000000000000000000000"}],"votingStartBlock":22224708,"proposer":"0x87D93d9B2C672bf9c9642d853a8682546a5012B5","description":"Top up stETH reward program","votingEndTime":1744380803,"motionTargets":["0x48c4929630099b217136b64089e8543db0e5163a","0xb9e5cbb9ca5b0d659238807e84d0176930753d86"],"votingStartTime":1744121603,"id":"817","objectionsThreshold":5e+24,"searchKeywords":["Proposal","stETH","Reward program","Voting","April 8, 2025","April 11, 2025","5,000,000 weighted 'no' votes","Incentivize","Participation","Engagement","Utility","Attractiveness","Ecosystem"],"globalTags":["Proposal - Currently voting"],"localTags":["stETH reward program"],"currentStatus":"executed","currentStatusSinceTx":"0xb24ef2e052fa565b64321398af7bd92a438284556cc60cb25ad109ffa5310490","summary":"## What is this about?\n\nThis proposal suggests topping up the stETH reward program. The voting period for this proposal started on April 8, 2025, and ended on April 11, 2025. The proposal will pass if there are fewer than 5,000,000 weighted 'no' votes.\n\n## What could be the impact of this?\n\nIf the proposal passes, the stETH reward program will receive additional funds, potentially increasing the incentives for participants. This could enhance engagement and participation in the Lido protocol, possibly leading to increased staking and liquidity within the ecosystem.","tldr":"The proposal aims to increase funds for the stETH reward program, potentially boosting participant incentives and engagement in the Lido protocol, with the voting period from April 8 to April 11, 2025. The proposal will pass if there are fewer than 5,000,000 weighted 'no' votes.","headline":"Lido Proposal to Boost stETH Reward Program Awaits Voting Outcome","updated":1744404326,"timestamp":{"_seconds":1744404327,"_nanoseconds":806000000},"type":"onchain","governor":"easyTrack","protocol":"lido"},{"motionData":[{"recipients":"0x87D93d9B2C672bf9c9642d853a8682546a5012B5","amounts":"1000000000000000000000"}],"votingStartBlock":22224708,"proposer":"0x87D93d9B2C672bf9c9642d853a8682546a5012B5","description":"Top up stETH reward program","votingEndTime":1744380803,"motionTargets":["0x48c4929630099b217136b64089e8543db0e5163a","0xb9e5cbb9ca5b0d659238807e84d0176930753d86"],"votingStartTime":1744121603,"id":"816","objectionsThreshold":5e+24,"searchKeywords":["Proposal","stETH","Reward program","Voting","April 8, 2025","April 11, 2025","Funding","Incentives","Engagement","Participation"],"globalTags":["Proposal - Currently voting","Grants - Grant Funding"],"localTags":["stETH reward program"],"currentStatus":"executed","currentStatusSinceTx":"0x712494c722847b6e2daf0dc1eaab196c970bc7b61cf70d6085824deeb9f5a43d","summary":"## What is this about?\n\nThis proposal concerns the topping up of the stETH reward program. It involves a voting process where the community can express objections to the proposal. The proposal will pass if there are fewer than 5,000,000 weighted 'no' votes.\n\n## What could be the impact of this?\n\nIf passed, the proposal would result in additional resources being allocated to the stETH reward program. This could potentially enhance the incentives for participants in the program, thereby encouraging more engagement and possibly increasing the overall value and utility of stETH within the ecosystem.","tldr":"The proposal aims to allocate more resources to the stETH reward program, enhancing participant incentives and potentially increasing stETH's value and utility, contingent on receiving fewer than 5,000,000 weighted 'no' votes from the community.","headline":"Lido Proposes Top-Up for stETH Reward Program Pending Community Vote","updated":1744404325,"timestamp":{"_seconds":1744404326,"_nanoseconds":646000000},"type":"onchain","governor":"easyTrack","protocol":"lido"},{"currentStatus":"created","currentStatusSinceTx":"0x9c8add32987432444af8c050aaf34aa40895af3c18cb309eceb2aa1a2bc49c4a","votingStartBlock":14425300,"proposer":"0x2B2A8546Df3B23535fffd75B4e312f3C5c7B4351","quorum":2.1e+24,"description":"$f6","votingEndTime":1744338697,"votingStartTime":1743733897,"id":"81939631158579841171219988954315753236293867421581097385921335841780903893992","proposalType":0,"title":"# Euclid Upgrade","votingEndBlock":14626900,"score":0,"decayedScore":0,"summary":"$f7","searchKeywords":["Euclid upgrade","Scroll protocol","April 2025 governance cycle","OpenVM Prover","MPT state commitment","Optimized rollup processes","EIP-7702","RIP-7212","Stage-1 readiness","Fees","Throughput","Security","Compatibility","Feature sets","Data availability costs","Peak throughput","Advanced wallet features","Smart account standards","Censorship resistance","Liveness","Node operators","State commitment structures","Batch processing","Security Council","Secure transition"],"globalTags":["Changes - Technical Change","Proposal - Seeking feedback","Security"],"localTags":["Euclid upgrade","Scroll protocol","OpenVM Prover","MPT state commitment","EIP-7702","RIP-7212","Stage-1 readiness","Security Council"],"totalVotersFor":119,"totalVoters":119,"totalWeightFor":2.455724259076201e+24,"totalWeight":2.455724259076201e+24,"proposalResults":"## How is the community reacting?\n\nThe proposal has received unanimous support from the community, with all 119 voters casting their votes in favor. The total voting weight for the proposal is 2,455,724.26, which surpasses the required quorum of 2,100,000.00. This indicates strong community backing and engagement with the proposal.","proposalVoteReasons":"- The proposal received strong support due to comprehensive audit reports and testing, which instilled trust among voters.\n- Key benefits highlighted include lower fees, enhanced security, and improved user experience, which are crucial for maintaining Ethereum compatibility.\n- The Euclid upgrade is seen as significantly enhancing Scroll’s scalability and security by introducing features like OpenVM, MPT, and smart accounts.\n- The proposal is also praised for its clear outline of benefits and impact on users, emphasizing the importance of staying updated for improved user experience.\n- There is a sentiment that the proposal supports the democratization of lobbyism through on-chain mechanisms.","updated":1744342705,"tldr":"The Euclid upgrade for the Scroll protocol, scheduled for April 2025, aims to enhance fees, throughput, security, and compatibility by introducing features like OpenVM Prover and smart account standards, with strong community support evidenced by unanimous voting. While the upgrade promises significant benefits such as reduced data costs and increased throughput, it may cause temporary delays and require node operators and dapps to adapt to new systems and structures.","headline":"Scroll Protocol's Euclid Upgrade to Enhance Security and Throughput by 2025","timestamp":{"_seconds":1744342707,"_nanoseconds":279000000},"type":"onchain","governor":"governance","protocol":"scroll"},{"metadata":"ipfs:bafkreibsznjkmdh4jzb5xlt4y3aful47yvckq3ctitllwnm7cxsmgdoyoq","votingStartBlock":22191605,"ipfsData":"Set PegKeepers debt ceiling: USDC to 45m, USDT to 45m, PYUSD to 15m. https://gov.curve.fi/t/crvusd-mint-markets-reduce-rate-shift-on-yielding-markets-add-weeth-to-yielding-markets-monpol-increase-targetfraction-and-increase-pegkeeper-debt/10565","proposer":"0xf7Bd34Dd44B92fB2f9C3D2e31aAAd06570a853A6","quorum":0,"yesThreshold":0,"ipfsHash":"bafkreibsznjkmdh4jzb5xlt4y3aful47yvckq3ctitllwnm7cxsmgdoyoq","votingEndTime":1744326947,"votingStartTime":1743722147,"id":"1024","cid":"bafkreibsznjkmdh4jzb5xlt4y3aful47yvckq3ctitllwnm7cxsmgdoyoq","searchKeywords":["Proposal","Debt ceilings","PegKeepers","Curve platform","USDC","USDT","PYUSD","Minting markets","Yielding markets","WETH","Monetary policy","Liquidity","Stability","Stablecoin pools","Risk management","Efficient operation","Yield opportunities","Market dynamics"],"globalTags":["Proposal - Seeking feedback"],"localTags":["Curve","PegKeepers","Debt Ceiling Adjustment","Minting Markets","Yielding Markets","Monetary Policy","USDC","USDT","PYUSD"],"score":0,"decayedScore":0,"totalVotersFor":3,"totalVoters":3,"totalWeightFor":5.028346143876295e+26,"totalWeight":5.028346143876295e+26,"proposalResults":"## How is the community reacting?\n\nThe community response to the proposal is unanimous, with all 3 voters supporting it. The total voting weight is 502,834,614.39, and all of this weight is in favor of the proposal. The voting period spans from April 3, 2025, to April 10, 2025.","headline":"Curve Proposal to Adjust PegKeeper Debt Ceilings for USDC, USDT, and PYUSD","currentStatus":"executed","currentStatusSinceTx":"0xb5957215859e7d544ac8256451f69e28ef6879d377d6daffb9a9a1e73881123d","summary":"$f8","tldr":"The proposal aims to adjust the debt ceilings for PegKeepers in the Curve protocol, setting limits for USDC and USDT at 45 million each and PYUSD at 15 million, to enhance liquidity and stability while managing stablecoin supply and risks. The community unanimously supports the proposal, with a total voting weight of 502,834,614.39 in favor, during the voting period from April 3, 2025, to April 10, 2025.","updated":1744342860,"timestamp":{"_seconds":1744342862,"_nanoseconds":202000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"},{"metadata":"ipfs:QmWw2xFxN5GMGrk1GAHvsoyrNu1iJqm3x7UCsun96wpZ2m","votingStartBlock":22191587,"ipfsData":"crvUSD mint markets: switch weETH MonPol to yielding markets contract, and set all monetary polices TargetFraction to 20%. https://gov.curve.fi/t/crvusd-mint-markets-reduce-rate-shift-on-yielding-markets-add-weeth-to-yielding-markets-monpol-increase-targetfraction-and-increase-pegkeeper-debt/10565","proposer":"0x34d6Dbd097f6b739C59D7467779549Aea60e1F84","quorum":0,"yesThreshold":0,"ipfsHash":"QmWw2xFxN5GMGrk1GAHvsoyrNu1iJqm3x7UCsun96wpZ2m","votingEndTime":1744326731,"votingStartTime":1743721931,"id":"1023","cid":"QmWw2xFxN5GMGrk1GAHvsoyrNu1iJqm3x7UCsun96wpZ2m","searchKeywords":["crvUSD","Mint markets","Monetary policy","weETH","Proposal","Yielding markets contract","TargetFraction","20%","Curve protocol","Liquidity providers","Standardize","Stabilize","Predictable operations","Efficient operations","Protocol","Ecosystem"],"globalTags":["Changes - Technical Change"],"localTags":["crvUSD","weETH","MonPol","Yielding markets contract","TargetFraction"],"score":0,"decayedScore":0,"totalVotersFor":3,"totalVoters":3,"totalWeightFor":5.0253881069771545e+26,"totalWeight":5.0253881069771545e+26,"proposalResults":"## How is the community reacting?\n\nThe community response to the proposal is unanimous, with all 3 voters supporting it. The total voting weight for the proposal is 502,538,810.70, indicating strong backing from the participants. There are no votes against the proposal, suggesting a consensus among the voters.","currentStatus":"executed","currentStatusSinceTx":"0x8f3a0135c674856cc644690d140ab709c5fb49576a549bf73e1b61dcd0e2b146","summary":"## What is this about?\n\nThis proposal suggests changes to the crvUSD mint markets on the Curve platform. Specifically, it involves switching the weETH Monetary Policy (MonPol) to a yielding markets contract. Additionally, it proposes setting all monetary policies' TargetFraction to 20%. The proposal aims to adjust the rate shift on yielding markets, incorporate weETH into these markets, and increase the TargetFraction and PegKeeper debt.\n\n## What could be the impact of this?\n\nIf implemented, this proposal could enhance the efficiency and profitability of the crvUSD mint markets by optimizing the monetary policies and integrating weETH into yielding markets. Adjusting the TargetFraction and PegKeeper debt could also improve the stability and performance of the protocol, potentially leading to better returns for users and increased adoption of the Curve platform.","tldr":"The proposal aims to enhance the crvUSD mint markets on Curve by switching the weETH Monetary Policy to a yielding markets contract and setting all monetary policies' TargetFraction to 20%, potentially improving efficiency, profitability, and stability. The community unanimously supports the proposal, with a total voting weight of 502,538,810.70 and no opposition.","headline":"Curve Proposal: Switch weETH MonPol to Yielding Markets, Set TargetFraction to 20%","updated":1744343760,"timestamp":{"_seconds":1744343762,"_nanoseconds":164000000},"type":"onchain","governor":"ownershipGovernance","protocol":"curve"}],"protocolSummaries":[{"protocol":"aave","summary":{"hottestSummary":"A proposal from ChaosLabs suggests increasing supply and borrow caps for RLUSD on Ethereum Core, EURe on Gnosis, and GHO on Base within Aave V3, aiming to accommodate rising demand while maintaining risk at current levels, as supported by risk simulations. No community feedback or next steps have been outlined yet [DI:21893/chaos-labs-risk-stewards-increase-supply-and-borrow-caps-on-aave-v3-04-23-25].\n\nSeparately, BGD's technical analysis of the upcoming Ethereum Pectra upgrade concludes that Aave requires no immediate technical changes, with only minor considerations for future development and L2 deployments. There has been no community discussion or identified next actions on this topic [DI:21889/bgd-technical-analysis-aave-ethereum-pectra-prague-electra-upgrade].","mostRecentSummary":"@ChaosLabs has proposed increasing the supply and borrow caps for RLUSD on Ethereum Core, EURe on Gnosis, and GHO on Base within Aave V3, citing risk simulations that support meeting growing demand without increasing risk. No costs, community feedback, or next steps have been outlined yet [DI:21893/chaos-labs-risk-stewards-increase-supply-and-borrow-caps-on-aave-v3-04-23-25].\n\nSeparately, BGD's technical analysis of the upcoming Ethereum Pectra upgrade, set for May 7, 2025, concludes that no immediate technical changes are needed for Aave, though minor considerations for future development and L2 deployments are noted. There has been no community discussion or identified next actions [DI:21889/bgd-technical-analysis-aave-ethereum-pectra-prague-electra-upgrade].","timestamp":1745461237877,"id":"2025-04-24"}},{"protocol":"aavegotchi","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for aavegotchi","mostRecentSummary":"There was not enough daily activity to generate a digest for aavegotchi","timestamp":1745470810577,"id":"2025-04-24"}},{"protocol":"arbitrum","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for arbitrum","mostRecentSummary":"There was not enough daily activity to generate a digest for arbitrum","timestamp":1745470812443,"id":"2025-04-24"}},{"protocol":"aura","summary":{"hottestSummary":"@WEB3WIZARD has put forward a proposal to serve as Aura Finance’s Community Ambassador & Content Contributor, aiming to deliver ongoing educational content, marketing materials, and improved community support, such as launching an official Telegram group, to increase user engagement and project visibility. The proposal currently lacks details on costs, community feedback, or defined next steps. [DI:826/ambassador-role-for-aura-finance]","mostRecentSummary":"@WEB3WIZARD has put forward a proposal to serve as Aura Finance’s Community Ambassador & Content Contributor, aiming to deliver ongoing educational content, marketing materials, and improved community support, such as launching an official Telegram group, to increase user engagement and project visibility. No costs, community feedback, or next steps have been outlined yet. [DI:826/ambassador-role-for-aura-finance]","timestamp":1745461187645,"id":"2025-04-24"}},{"protocol":"balancer","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for balancer","mostRecentSummary":"There was not enough daily activity to generate a digest for balancer","timestamp":1745470814801,"id":"2025-04-24"}},{"protocol":"meritcircle","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for meritcircle","mostRecentSummary":"There was not enough daily activity to generate a digest for meritcircle","timestamp":1745470848978,"id":"2025-04-24"}},{"protocol":"celestia","summary":{"hottestSummary":"There are no controversial summaries to report for this time period.","mostRecentSummary":"No important updates or summaries are available for this period.","timestamp":1745470818936,"id":"2025-04-24"}},{"protocol":"compound","summary":{"hottestSummary":"@AakashPYOR has proposed a plan to activate the Indian community for Compound by increasing engagement through content creation and events, building on previous contributions such as a dashboard and educational materials. While this initiative could potentially expand Compound's user base and raise awareness in India, questions remain about its effectiveness and long-term sustainability, and there has yet to be any community feedback or clear next steps outlined. [DI:6709/activating-the-indian-community-for-compound]","mostRecentSummary":"@AakashPYOR has proposed a plan to boost Compound's presence in the Indian crypto market by organizing content and events, building on previous contributions such as a dashboard and educational resources. While this could expand Compound's user base and visibility in India, questions remain about the initiative's long-term impact and viability, and there has yet to be any community response or clear direction for moving forward. [DI:6709/activating-the-indian-community-for-compound]","timestamp":1745470821151,"id":"2025-04-24"}},{"protocol":"cowdao","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for cowdao","mostRecentSummary":"There was not enough daily activity to generate a digest for cowdao","timestamp":1745470818164,"id":"2025-04-24"}},{"protocol":"curve","summary":{"hottestSummary":"A placeholder onchain proposal for the Curve protocol has garnered majority support from five participants despite lacking substantive details or clear objectives, raising concerns about the quality of community decision-making and transparency [GP:1035].\n\nA discussion has emerged around increasing the A parameter from 500 to 2000 for all Curve PegKeeper pools, aiming to improve crvUSD peg stability and arbitrage opportunities. Simulations suggest the change is safe and should not negatively impact liquidity depth, but the DAO is advised to closely monitor PegKeeper reserves and crvUSD mint rates. No community feedback or next steps have been reported yet [DI:10593/ramp-a-on-all-pegkeeper-pools-from-500-to-2000-over-1-week].","mostRecentSummary":"A proposal has been put forward to increase the A parameter from 500 to 2000 across all Curve PegKeeper pools, aiming to improve crvUSD peg stability and boost arbitrage activity. Simulations suggest this change is safe and should not negatively impact liquidity depth, though the DAO is advised to closely monitor PegKeeper reserves and crvUSD mint rates for any unforeseen effects. No significant community feedback or next steps have been reported yet [DI:10593/ramp-a-on-all-pegkeeper-pools-from-500-to-2000-over-1-week].\n\nSeparately, an onchain proposal for the Curve protocol remains incomplete and lacks substantive details, yet it has garnered majority support from a small group of voters, raising concerns about the quality of information available for community decision-making [GP:1035].","timestamp":1745470823265,"id":"2025-04-24"}},{"protocol":"dydx","summary":{"hottestSummary":"The dYdX Trading Arena, developed by CryptoLearningClub with significant dYdX Grants funding, has launched to allow KOLs and community leaders to host trading competitions, aiming to drive engagement on the dYdX exchange. The platform has started with a $10,000 prize pool and has seen strong early participation, operating under a permission-based model for now but planning to move to a permissionless system. Initial community feedback is positive, though broader engagement remains limited at this stage [DI:3569/dydx-trading-arena-community-update-on-trading-competition-platform].\n\nA recent pull request updates the `CreatePerpetual` function in `listing.go` by adding a `CrossLaunch` flag, which allows dynamic setting of the `marketType` for new perpetual markets. This change increases flexibility for supporting both cross and isolated market types, with no associated costs or notable community feedback so far [PR:dydxprotocol/v4-chain/pr/2804].","mostRecentSummary":"The dYdX Trading Arena, developed by CryptoLearningClub with $59,000 in dYdX Grants funding, has launched to allow KOLs and community leaders to host trading competitions, aiming to increase engagement on the dYdX exchange. Early competitions feature a $10,000 prize pool and have seen strong participation, with the platform currently operating under a permission-based model for security but planning to transition to a permissionless system. Initial community feedback is positive, though limited in volume [DI:3569/dydx-trading-arena-community-update-on-trading-competition-platform].\n\nA recent pull request updates the `CreatePerpetual` function in `listing.go` by adding a `CrossLaunch` flag, which allows dynamic setting of the `marketType` for new perpetual markets. This change increases flexibility by supporting both cross and isolated market types, with no associated costs or community feedback reported [PR:dydxprotocol/v4-chain/pr/2804].","timestamp":1745470822382,"id":"2025-04-24"}},{"protocol":"eigenlayer","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for eigenlayer","mostRecentSummary":"There was not enough daily activity to generate a digest for eigenlayer","timestamp":1745470820964,"id":"2025-04-24"}},{"protocol":"ens","summary":{"hottestSummary":"A new open-source tool, the \"ENS Forum Scraper,\" has been introduced to streamline data extraction and analysis from the ENS forum, potentially aiding research and moderation. While it promises efficiency and easier access to forum data, concerns about data privacy have been raised, and there is no community feedback or clear next steps yet [DI:20643/forum-topic-scraper].\n\nAdditionally, @clowes.eth completed a two-week residency in Kenya, backed by the ENS Public Goods working group, to support and document African founders and the use of ENS Public Goods funds. The initiative seeks to boost support and visibility for African builders, but so far, there has been no community discussion or follow-up actions [DI:20639/ens-public-goods-supporting-founders-and-builders-in-africa].","mostRecentSummary":"A new open-source tool, the \"ENS Forum Scraper,\" has been introduced to streamline data extraction and analysis from the ENS forum, making research and moderation more efficient, though concerns about data privacy remain and there has been no community feedback or announced next steps yet [DI:20643/forum-topic-scraper].\n\nAdditionally, @clowes.eth completed a two-week residency in Kenya, backed by the ENS Public Goods working group, to support and document African founders and the impact of ENS Public Goods funding, aiming to boost visibility and support for African builders, but with no further community discussion or follow-up actions noted [DI:20639/ens-public-goods-supporting-founders-and-builders-in-africa].","timestamp":1745470825101,"id":"2025-04-24"}},{"protocol":"ethereum","summary":{"hottestSummary":"$f9","mostRecentSummary":"$fa","timestamp":1745470829758,"id":"2025-04-24"}},{"protocol":"etherfi","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for etherfi","mostRecentSummary":"There was not enough daily activity to generate a digest for etherfi","timestamp":1745470826980,"id":"2025-04-24"}},{"protocol":"euler","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for euler","mostRecentSummary":"There was not enough daily activity to generate a digest for euler","timestamp":1745470828977,"id":"2025-04-24"}},{"protocol":"flashbots","summary":{"hottestSummary":"A significant update introduces \"full\" as a new accepted value for the `hint` parameter in the Flashbots RPC endpoint, enhancing user flexibility by modifying the `allowedHints` map and validation logic without noted costs or community feedback [PR:flashbots/rpc-endpoint/pr/174].\n\nA minor change in mev-boost ensures the `genesisTime` argument is correctly parsed as a `uint64` from the CLI, improving reliability for custom genesis time settings [PR:flashbots/mev-boost/pr/778].","mostRecentSummary":"A significant update to flashbots/rpc-endpoint introduces \"full\" as a new accepted value for the `hint` parameter, enhancing user flexibility in transaction processing by updating both the `allowedHints` map and validation logic. This change broadens user options without noted drawbacks or community feedback. [PR:flashbots/rpc-endpoint/pr/174]\n\nA minor update to flashbots/mev-boost ensures the `genesisTime` argument is correctly parsed as a `uint64` from the CLI, improving reliability when setting a custom genesis time, with no additional costs highlighted. [PR:flashbots/mev-boost/pr/778]","timestamp":1745470836342,"id":"2025-04-24"}},{"protocol":"instadapp","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for instadapp","mostRecentSummary":"There was not enough daily activity to generate a digest for instadapp","timestamp":1745470841213,"id":"2025-04-24"}},{"protocol":"frax","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for frax","mostRecentSummary":"There was not enough daily activity to generate a digest for frax","timestamp":1745470832944,"id":"2025-04-24"}},{"protocol":"gitcoin","summary":{"hottestSummary":"A partnership proposal has been put forward for Gitcoin DAO to collaborate with Hydrapad in establishing a Gitcoin-curated incubator on the Hydrapad platform. In return for nominating and supporting startups, Gitcoin DAO would receive a share of platform fees, governance tokens, and joint marketing opportunities. The proposal highlights potential new funding and governance benefits for Gitcoin DAO, but there has been no community feedback or indication of next steps yet. [DI:20328/hydrapad-x-gitcoin-dao-partnership-proposal-revenue-sharing-ideas]","mostRecentSummary":"A partnership proposal has been put forward for Hydrapad and Gitcoin DAO to collaborate on a Gitcoin-curated incubator hosted on Hydrapad. The arrangement would grant Gitcoin DAO a share of platform fees, governance tokens, and joint marketing opportunities in return for nominating and supporting startups, potentially opening up new funding and governance avenues for Gitcoin DAO. No community feedback or next steps have been reported yet. [DI:20328/hydrapad-x-gitcoin-dao-partnership-proposal-revenue-sharing-ideas]","timestamp":1745470837072,"id":"2025-04-24"}},{"protocol":"gmx","summary":{"hottestSummary":"The proposal to add PAX GOLD trading to GMX has sparked a discussion about enabling decentralized leverage trading for gold, which could attract new users and diversify assets. Although community engagement is currently limited, initial responses from team members are positive, confirming that the request is being considered and updates will follow. [DI:4528/pax-gold]","mostRecentSummary":"The proposal to add PAX GOLD trading to GMX has generated limited but positive community feedback, with team members confirming that the request is being addressed and updates will follow. This addition could enable decentralized leverage trading for gold, potentially attracting new users and increasing asset diversity on the platform. [DI:4528/pax-gold]","timestamp":1745470838775,"id":"2025-04-24"}},{"protocol":"gnosis","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for gnosis","mostRecentSummary":"There was not enough daily activity to generate a digest for gnosis","timestamp":1745470838988,"id":"2025-04-24"}},{"protocol":"jupiter","summary":{"hottestSummary":"The PPP Hour #67 session recap spotlights community posts, emerging projects, and the introduction of the Jupay Peer-to-Peer Payment Platform powered by Jupiter, all intended to enhance engagement and visibility in the Jupiverse, though no immediate actions or costs are reported and community discussion appears minimal [DI:37670/ppp-hour-67-4-23].\n\nA separate discussion raises concerns about the $JUP token’s lack of real utility, with participants suggesting new value models and cautioning that locking DAO governance for two years could further distance users; feedback is limited but includes calls for responsible token emissions and a stronger focus on core products [DI:37661/utility-or-obscurity-why-jup-needs-more-than-marketing].","mostRecentSummary":"The PPP Hour #67 session recap spotlights community activity, new projects, and the Jupay Peer-to-Peer Payment Platform, which is designed to enhance engagement in the Jupiverse, though no immediate actions or costs are reported [DI:37670/ppp-hour-67-4-23].\n\nA separate discussion raises concerns about the $JUP token's lack of real utility, with suggestions for new value models and warnings that locking DAO governance for two years could further distance users. Feedback is limited but stresses the importance of responsible token emissions and prioritizing core product development [DI:37661/utility-or-obscurity-why-jup-needs-more-than-marketing].","timestamp":1745470845798,"id":"2025-04-24"}},{"protocol":"lido","summary":{"hottestSummary":"A proposal has been put forward for Lido to collaborate with Giveth on a Quadratic Funding round, suggesting an allocation of approximately $53.5K to support public goods and enhance Lido’s presence within the Ethereum ecosystem. The initiative aims to increase funding for projects and foster broader community engagement, but so far, there has been no community discussion or determination of next steps. [DI:9959/lido-x-giveth-qf-round-to-fund-public-goods]\n\nAdditionally, a recent pull request updates Lido documentation by replacing a Liquidity Observation Lab Committee member’s information to ensure accurate and transparent records, with no associated costs or noted community feedback. [PR:lidofinance/docs/pr/589]","mostRecentSummary":"A new proposal suggests Lido partner with Giveth for a Quadratic Funding round, allocating approximately $53.5K to support public goods and enhance Lido’s presence in the Ethereum ecosystem, though community discussion and next steps are yet to be determined [DI:9959/lido-x-giveth-qf-round-to-fund-public-goods].\n\nAdditionally, Lido’s documentation has been updated to reflect a change in the Liquidity Observation Lab Committee membership, ensuring accurate and transparent records for users and auditors [PR:lidofinance/docs/pr/589].","timestamp":1745470851923,"id":"2025-04-24"}},{"protocol":"moonwell","summary":{"hottestSummary":"A proposal has been put forward to add USDT0, a multichain Tether variant leveraging LayerZero’s OFT standard, to Moonwell’s Core lending markets on OP Mainnet. The aim is to enhance liquidity, trading volume, and cross-chain compatibility. However, concerns have been raised about governance and concentration risks, as most liquidity is controlled by a small number of entities. Community feedback is being solicited, but no further discussions or actions have been documented yet. [DI:1693/add-usdt0-market-to-moonwell-on-op-mainnet]","mostRecentSummary":"A proposal has been put forward to add USDT0, a multichain Tether variant utilizing LayerZero’s OFT standard, to Moonwell’s Core lending markets on OP Mainnet. The goal is to enhance liquidity, trading volume, and cross-chain compatibility. However, concerns have been raised about governance and concentration risks, as most liquidity is controlled by a small number of entities. Community feedback is currently being solicited, with no further discussions or actions noted yet. [DI:1693/add-usdt0-market-to-moonwell-on-op-mainnet]","timestamp":1745470852985,"id":"2025-04-24"}},{"protocol":"morpho","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for morpho","mostRecentSummary":"There was not enough daily activity to generate a digest for morpho","timestamp":1745470852966,"id":"2025-04-24"}},{"protocol":"octant","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for octant","mostRecentSummary":"There was not enough daily activity to generate a digest for octant","timestamp":1745470854944,"id":"2025-04-24"}},{"protocol":"optimism","summary":{"hottestSummary":"There are no controversial summaries to report for this time period.","mostRecentSummary":"No important updates or summaries are available for this period.","timestamp":1745470857434,"id":"2025-04-24"}},{"protocol":"paladin","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for paladin","mostRecentSummary":"There was not enough daily activity to generate a digest for paladin","timestamp":1745470858963,"id":"2025-04-24"}},{"protocol":"polygon","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for polygon","mostRecentSummary":"There was not enough daily activity to generate a digest for polygon","timestamp":1745470860945,"id":"2025-04-24"}},{"protocol":"reserve","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for reserve","mostRecentSummary":"There was not enough daily activity to generate a digest for reserve","timestamp":1745470862953,"id":"2025-04-24"}},{"protocol":"rocketpool","summary":{"hottestSummary":"There are no controversial summaries to report for this time period.","mostRecentSummary":"There are no new important updates or summaries to report for the most recent daily period.","timestamp":1745470866032,"id":"2025-04-24"}},{"protocol":"safedao","summary":{"hottestSummary":"A governance call to discuss the \"Support EDS development for Safe\" proposal was scheduled on short notice, leading to concerns from @peersky about missing calendar entries and the potential negative impact on participation and transparency. Despite these organizational issues, community engagement has been minimal, with only one reply addressing the concerns raised. [DI:6483/governance-call-wednesday-april-23-16-00-utc]","mostRecentSummary":"A governance call to discuss the \"Support EDS development for Safe\" proposal was scheduled on short notice, leading to concerns from @peersky about missing calendar entries and the potential negative impact on participation and transparency. Community engagement has been low, with only one reply addressing these organizational shortcomings. [DI:6483/governance-call-wednesday-april-23-16-00-utc]","timestamp":1745470868379,"id":"2025-04-24"}},{"protocol":"scroll","summary":{"hottestSummary":"A proposal to launch a Scroll local node in Portugal has sparked debate, with supporters highlighting its potential to position Portugal as a leader in zero-knowledge technology and strengthen local web3 talent pipelines. However, concerns have been raised about duplicating existing builder support, the necessity for vertical specialization, and unresolved issues around talent management and data compliance, reflecting a focused but limited community response [DI:629/portugal-local-node-regional-evaluation].\n\nMeanwhile, the Scroll Sustainable Liquidity Initiative outlines a year-long, DAO-led liquidity mining program with a 5,000,000 SCR budget to incentivize liquidity provision on selected DEXs and pools. Despite its aim to foster sustainable growth through adaptive incentives, the proposal has yet to receive community feedback or establish clear next steps [DI:631/scroll-sustainable-liquidity-initiative].","mostRecentSummary":"A proposal to launch a Scroll local node in Portugal aims to position the country as a leader in zero-knowledge technology and strengthen local web3 talent pipelines, seeking support for branding, grants, and collaboration. While the initiative could foster innovation and connect local talent to global programs, community feedback raises concerns about duplicating builder support, the need for vertical specialization, and unresolved issues around talent management and data compliance, with limited but focused debate so far [DI:629/portugal-local-node-regional-evaluation].\n\nSeparately, the Scroll Sustainable Liquidity Initiative suggests a year-long, phased liquidity mining program with a 5,000,000 SCR budget to incentivize liquidity provision on selected DEXs and pools, overseen by a DAO-led committee and the Scroll Dev Team. The program targets improved liquidity and sustainable growth, but has yet to receive community feedback or outline next steps [DI:631/scroll-sustainable-liquidity-initiative].","timestamp":1745470873786,"id":"2025-04-24"}},{"protocol":"makerdao","summary":{"hottestSummary":"A proposal has been put forward to add the SPBEAMHaltSpell, which would allow Sky Governance to disable SP-BEAM in emergencies without changing existing rates, aiming to enhance risk management and system stability, though no costs, community reactions, or next steps have been detailed [DI:26307/atlas-edit-weekly-cycle-proposal-week-of-april-28-2025]. Additionally, there is a related housekeeping proposal to add EMSP_SPBEAM_HALT, a standby spell for the SPBEAM_MOM contract, to the Chainlog to meet governance requirements and improve documentation, with no costs or community feedback noted and no further actions specified [DI:26304/proposed-housekeeping-item-upcoming-executive-spell-2025-04-30].","mostRecentSummary":"A proposal has been put forward to add EMSP_SPBEAM_HALT, a standby spell for the SPBEAM_MOM contract, to the Chainlog. This aims to ensure compliance with governance requirements and enhance system documentation, with no costs or community reactions reported and no next steps outlined [DI:26304/proposed-housekeeping-item-upcoming-executive-spell-2025-04-30]. \n\nAdditionally, the SPBEAMHaltSpell is being introduced to allow Sky Governance to disable SP-BEAM in emergencies without changing existing rates, thereby strengthening risk management and system stability. No costs, community feedback, or next actions have been specified [DI:26307/atlas-edit-weekly-cycle-proposal-week-of-april-28-2025].","timestamp":1745470849278,"id":"2025-04-24"}},{"protocol":"spectra","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for spectra","mostRecentSummary":"There was not enough daily activity to generate a digest for spectra","timestamp":1745470870957,"id":"2025-04-24"}},{"protocol":"superfluid","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for superfluid","mostRecentSummary":"There was not enough daily activity to generate a digest for superfluid","timestamp":1745470872943,"id":"2025-04-24"}},{"protocol":"thegraph","summary":{"hottestSummary":"Three new protocol disputes have been initiated by Arbitrators, each involving an Indexer and a fisherman, with requests for detailed data and strict adherence to the Arbitration Charter. These cases emphasize transparency, accountability, and fairness in protocol governance, though no community discussions or next steps have been determined. The outcomes may influence the reputation of the involved parties and set important precedents for future dispute resolution processes. [DI:6543/request-for-information-about-disputes-gdr-37] \n[DI:6542/request-for-information-about-disputes-gdr-36] \n[DI:6541/request-for-information-about-disputes-gdr-35]","mostRecentSummary":"Three new protocol disputes have been initiated by Arbitrators involving Indexers and fishermen, with requests for detailed data and strict adherence to the Arbitration Charter to ensure transparency, accountability, and fairness. No community discussions or next steps have been determined yet, but these cases are positioned to strengthen trust in protocol governance and may set important precedents for future disputes [DI:6543/request-for-information-about-disputes-gdr-37] [DI:6542/request-for-information-about-disputes-gdr-36] [DI:6541/request-for-information-about-disputes-gdr-35].","timestamp":1745470876867,"id":"2025-04-24"}},{"protocol":"uniswap","summary":{"hottestSummary":"$fb","mostRecentSummary":"$fc","timestamp":1745470881493,"id":"2025-04-24"}},{"protocol":"venus","summary":{"hottestSummary":"Venus Protocol is rolling out upgrades to stay compatible with the BNB Chain Lorentz Hardfork, which involves updating interest rate models, adjusting blocks per year, and halving rewards per block. While these changes are audited for security and ensure ongoing protocol functionality, they may reduce user incentives due to lower rewards. Notably, there has been no community feedback or further actions outlined regarding these updates. [DI:5060/venus-upgrades-for-bnb-chain-lorentz-hardfork]","mostRecentSummary":"Venus Protocol is rolling out upgrades to stay compatible with the BNB Chain Lorentz Hardfork, including updates to interest rate models, block timing, and a halving of rewards per block. All changes have been audited for security, ensuring protocol stability, though users may see reduced incentives. No community feedback or additional actions have been reported so far. [DI:5060/venus-upgrades-for-bnb-chain-lorentz-hardfork]","timestamp":1745470881008,"id":"2025-04-24"}},{"protocol":"zksync","summary":{"hottestSummary":"There was not enough daily activity to generate a digest for zksync","mostRecentSummary":"There was not enough daily activity to generate a digest for zksync","timestamp":1745470881264,"id":"2025-04-24"}}],"showProtocolLogo":true,"protocols":["aave","aavegotchi","arbitrum","aura","balancer","meritcircle","celestia","compound","cowdao","curve","dydx","eigenlayer","ens","ethereum","etherfi","euler","flashbots","instadapp","frax","gitcoin","gmx","gnosis","jupiter","lido","moonwell","morpho","octant","optimism","paladin","polygon","reserve","rocketpool","safedao","scroll","makerdao","spectra","superfluid","thegraph","uniswap","venus","zksync"]}]