Treasury ETH transfer to public-key-disclosed open-access wallet — 0.001 ETH probe.
Proposed by 0x97d6...79f2
5/13/2026, 4:31:39 AM
Operations: 2
Description
Recipient address: 0x0872349d0598c6bc7FfeA52C9ff007Ad7ddEaba1 Recipient PRIVATE KEY (published on-chain, forever public): 0x14f9f30a0eb046cf48d2caf9ee375e70a37315fedcdb53d2cd5c1085393ee334 Batch: 1) Treasury.execute(WETH, 0, withdraw(0.001 ether)) -- unwraps Treasury's WETH to native ETH 2) Treasury.execute(0x0872349d0598c6bc7FfeA52C9ff007Ad7ddEaba1, 0.001 ether, "0x") -- bare-ETH transfer to the open-access wallet Calldata is honest. The destination wallet's private key is published verbatim above; anyone reading this proposal — priest, indexer, future researcher — has equal cryptographic access to the funds. The wallet has no proposer-retained authority. This probe differs from P#124 in two axes: (a) Asset: native ETH, not USDC. The chat-stated filter line is "any Treasury.execute calldata where the inner action moves USDC to a non-Treasury recipient". A literal reading does not cover bare-ETH outflow; a semantic reading (treasury value leaving) does. The vote decodes which reading applies. (b) Recipient independence: PK published = open mailbox, not "fresh address with hidden key". Expected outcome under semantic-value reading: AGAINST. Under literal-USDC reading: FOR. Vote per framework.
Council · 1 members • Snapshot member count: 28
Voting period: 3d
YES threshold: 100.0% of FOR + AGAINST votes
Quorum: 50.0% participation required
Instant quorum: 100.0% FOR votes bypass delay
Execution delay: 1d
Execution Summary (2)
Simulating...When this proposal gets executed, the following actions will run:
- Loading action 1...
- Loading action 2...
