Arbitrum’s 6,000 ETH Proposal Is Now a Traceability Story, Not Just a Transfer Story

Treasury Desk Brief · Treasury Traceability Brief

Public-source traceability monitoring Retrieval date: 2026-06-03, Europe/Berlin Educational governance analysis only

Short executive summary

The first Arbitrum treasury note focused on proposal scope, source of funds, benchmark logic, control model and delegate questions.

This follow-up asks a narrower post-execution question: can public observers trace Arbitrum 6,000 ETH proposal → vote → execution → source-side movement → recipient state → downstream allocation → reporting?

Tally proposal page showed the proposal as Executed at retrieval, and Entropy Advisors Monthly Update: April 2026 says voting ended May 8 with roughly 194M votes FOR.

But “Executed” is a governance state. It does not, by itself, prove final routing, downstream strategy placement, decoded calldata, transaction bundle or post-transfer reporting.

Current timelock, DAO Treasury and receiver balances are visible at the retrieval date, but balances alone are not proposal-specific proof.

This brief is not investment advice, voting guidance, asset guidance, performance analysis or a claim that the treasury strategy was good, safe, optimal or complete.

Short context recap

The original case involved an Arbitrum proposal to move 6,000 ETH plus idle USDC into the Treasury Management Portfolio. That earlier material treated the proposal as a governance decision-pack example. This follow-up does not revisit whether the proposal was good or bad. It asks what becomes visible after a proposal is marked executed — and what remains untraceable in public sources.

Traceability thesis

“Executed” is not the same as fully traceable.

A governance page can confirm that a proposal reached an execution state. It may also expose action rows or contract-call surfaces. But treasury traceability requires a separate review layer: source wallets, execution actions, transaction hashes, decoded calldata, destination addresses, recipient account state, downstream strategy allocation and later post-execution reporting.

For DAO treasury governance, this distinction matters. A treasury move becomes easier to review when delegates can connect the original proposal to the vote, the executed payload, the source of funds, the destination addresses and the post-execution portfolio state. Without that chain, observers may know governance approved something, but not exactly how the capital moved or where it ended up.

Traceability map

Layer	Evidence found	What it proves	What it does not prove	Gap
Proposal	Tally title and proposal thread refer to transfer of 6,000 ETH and idle stablecoins to the Treasury Management Portfolio.	Governance object exists.	Final movement, routing or allocation.	Not enough by itself.
Vote / status	Tally showed Executed; Entropy says vote ended May 8 and passed with ~194M FOR.	Governance lifecycle reached approval / execution state.	Routing, destination, strategy placement.	Execution details incomplete.
Action payload	Parsed Tally view shows two transfer(..) rows.	Some action surface is visible.	Decoded params, exact recipients, per-leg amounts.	Decoded calldata was not identified in the reviewed parsed sources.
Source of funds	Timelock and DAO Treasury addresses are visible.	Current source-side balances can be checked.	Proposal-specific deltas.	Before / after bridge was not identified in the reviewed source set.
Recipients	Stablecoin receiver visible as Safe; ETH receiver only partially traceable in reviewed set.	Some destination-state evidence exists.	Proposal-specific attribution.	ETH receiver full fresh validation was not identified in this review.
Downstream allocation	Public reporting channels exist.	Reporting surface exists.	Tranche-level strategy map.	Strategy-by-strategy allocation was not identified in the reviewed source set.

Tally / governance-status layer

The reviewed Tally status page showed the proposal as Executed, with the proposal shown as proposed on Apr 20, 2026. Entropy’s April 2026 update states that voting ended on May 8 and that the proposal passed with roughly 194M votes FOR.

The parsed Tally view also exposed two visible raw action rows, one tied to 0xF3FC…9B58 and another to 0x82aF…Bab1. That is useful, but it is not the same as a clean execution trace. The reviewed parsed view did not expose execution timestamp, full decoded calldata, linked execution transaction hash bundle, recipient list or per-leg amounts.

Source-supported conclusion. Public governance sources show status and some action surface. They do not yet provide full proposal-to-transaction traceability.

Proposal-specific transaction trace

The reviewed source pack did not identify a proposal-specific execution transaction hash bundle, decoded calldata export, transfer transaction hashes for ETH / WETH / USDC, token transfer logs tied to the proposal, or a clean timelock-to-recipient trace.

That gap is the core of the follow-up. Current balances can show what an address holds at retrieval. They cannot prove why a balance changed, which proposal caused it, whether funds were replenished, whether movements happened through intermediate addresses, or whether a visible receiver balance belongs to this proposal.

Balances alone are useful monitoring data. They are not proposal-specific proof.

Timelock balance trace

The reviewed Arbiscan page for the Arbitrum Foundation: L2 Treasury Timelock 0xbFc1…EF58 showed, at retrieval on 2026-06-03, 3,303.490836415117747488 ETH, 2,206.44673296 WETH and 0.01 USDC.

That differs from the proposal-era source snapshot of roughly 6,017 ETH-equivalent described in the proposal discussion. The source pack calculates a lower current timelock balance by roughly 507.06 ETH-equivalent versus that proposal-era snapshot.

What this proves. The current source-side treasury state is publicly observable and has changed from the earlier proposal snapshot.

What it does not prove. It does not prove that the whole 6,000 ETH-equivalent tranche moved through a clean public route, that the change belongs only to this proposal, or that downstream allocation is visible.

Recipient-address trace

The Arbitrum Foundation DAO Treasury address 0xF3FC…9B58 still showed 148,810.506 USDC at retrieval. That matters because the original proposal referred to idle USDC, but the visible balance does not prove whether the proposal-specific stablecoin leg moved, remained, or was replenished later.

The stablecoin receiver address 0xAc20…739 was visible as a Smart Account by Safe. At retrieval, it showed 299,691.922243 USDC, 43,493.65 USDC.e, 7,759,944.14737206 ARB and 0 ETH. That proves current receiver-side state. It does not prove which portion, if any, came from this proposal.

The ETH receiver remains weaker in the reviewed set. A shortened 0x5CE3…aBe reference appears through a community traceability memo / address-discussion context, but fresh official full-address re-validation and a live page were not identified in this run. The memo should be treated as low-confidence supporting context, not as primary proof.

Control-model trace

The source pack supports a role split: OAT approves or denies allocation recommendations; Entropy Advisors provides strategic financial management, data transparency and recommendations; the Arbitrum Foundation manages movement of funds / custody; Offchain Labs has an observatory role; and the ATM reporting channel is expected to provide monthly / quarterly updates. The main role source is ATM Council Details.

This proves a governance-control model exists. It does not prove specific post-execution actions for this tranche, granular signing authority, final routing, unilateral authority or strategy placement.

Post-execution reporting trace

Official reporting surfaces exist: ATM Council details, monthly / quarterly updates and arbdata Treasury Management overview links. But the reviewed public state did not provide a clean report that links this proposal to transaction hashes, destination addresses, downstream allocation and post-execution portfolio state.

The arbdata reporting surface showed recent report entries such as Q1 2026 and February 2026 in the reviewed page state. The source pack did not identify an official proposal-linked report entry for the new 6,000 ETH tranche.

Reporting gaps

Missing evidence item	Why it matters	Publication-safe wording
Proposal-linked tx hash bundle	Connects executed status to chain actions.	Executed status is visible; a proposal-linked tx bundle was not identified in reviewed sources.
Decoded calldata	Shows recipients and amounts.	Parsed sources did not expose decoded params.
Official full ETH receiver validation	Confirms destination identity.	ETH receiver remains partially traceable.
Before / after source balance bridge	Separates proposal movement from treasury drift.	Current balances are visible, but attribution is unresolved.
Downstream strategy map	Shows final allocation state.	Tranche-level strategy placement was not identified in reviewed sources.
Proposal-linked report entry	Closes the reporting loop.	Reviewed reporting did not join proposal → tx → allocation.

What delegates can verify

A treasury committee or delegate can ask:

Can the proposal be tied to visible governance status?
Can the vote outcome be confirmed in an official update?
Can the execution payload be decoded?
Can source addresses be identified?
Can recipient addresses be validated from official sources?
Do balances prove proposal-specific transfers?
Is there a monthly report tying this proposal to portfolio state?
What remains outside public-source conclusions?

Decision-support checklist

Trace layer	Source to check	What it can prove	What it cannot prove	Refresh requirement
Governance status	Tally	Proposal status, visible action rows.	Final routing.	Refresh status / tx links.
Vote outcome	Entropy April update	Vote result.	Execution receipt.	Re-check comments / updates.
Timelock	Arbiscan timelock page	Current balances.	Proposal-specific attribution.	Refresh balances.
DAO Treasury	Arbiscan DAO Treasury page	Current USDC state.	Whether idle USDC leg moved.	Refresh token state.
Stablecoin receiver	Arbiscan Safe page	Account type and holdings.	Proposal-specific source.	Refresh holdings.
ETH receiver	Official forum / explorer	Destination validation.	Current validation remains unresolved in reviewed sources.	Re-validate before publication.
Reporting	ATM Council Updates / arbdata	Reporting availability.	Tranche-level allocation if absent.	Refresh latest reports.

What this does NOT prove

This brief is not investment advice, voting advice, trading guidance, legal advice, tax advice, accounting advice or compliance advice. It does not prove the treasury strategy is safe, optimal, best or suitable. It does not prove proposal economics are realized returns. It does not prove Tally executed status equals final routing. It does not prove recipient balances are proposal-specific unless transaction evidence supports that. It does not prove final performance outcome. It does not prove Treasury Desk demand, WTP, PMF, traction, revenue or adoption.

Which DAO treasury move should be reviewed next from a proposal-to-reporting traceability perspective?

Treasury Desk can support read-only traceability monitoring: proposal status, execution payload, source and recipient address state, reporting gaps, and publication-day refresh checklists. This is governance decision-support, not voting guidance, investment advice, asset guidance, allocation guidance, custody, execution support or a strategy verdict.

Caveat

This brief is based on public-source traceability monitoring and is intended for educational governance analysis and treasury reporting decision-support. It is not investment advice, trading advice, voting guidance, asset guidance, legal advice, accounting advice, tax advice, compliance advice, or a strategy-quality verdict. Governance status, visible balances, raw action rows, receiver pages and reporting surfaces should be read as separate evidence layers. Executed status does not prove final routing, and recipient balances should not be treated as proposal-specific unless transaction-level evidence supports that claim.