Uniswap-Arbitrum Delegate Program (UADP) Communication Thread

GOVERNANCEUniswap-Arbitrum DelegateProgram (UADP)Communication Thread46IMPORTANCECLOSED2NEWS MEDIA2PIECESSep 22, 2026 21:37blockboard.net

The Uniswap-Arbitrum Delegate Program recorded abstentions on automatic Snapshot challenges tied to the LTIPP bridge challenge addendum proposals, including MUX and Stargate, and said the late application meant the abstain was a procedural default. In a separate communication thread, the UADP said Uniswap received a little over 4 million ARB in Arbitrum’s ecosystem token airdrop a few months earlier.

What this rests on

Claim by claim, with its source
✓
A separate UADP communication said Uniswap received a little over 4 million ARB when Arbitrum airdropped tokens to ecosystem projects a few months earlier.
✓
The same communication identified the UADP delegate address as 0x8326D18edfC50B4335113C33b25116ec268FF3fE and listed the thread as a UADP delegate update.
✓
The UADP defaulted to Abstain on the June 2024 LTIPP Bridge Challenge and Addendum proposals in the automatic Snapshot process.
✓
The abstain on the STIP Bridge Challenge was described as a procedural default tied to the protocol’s late application, and the statement said the challenge itself was not being assessed there.

What it means

Who it affects, what changes and what is still unconfirmed

Each sentence links inside to the piece that supports it.

For Arbitrum governance participants watching the June votes, the immediate effect is that the UADP is recorded as abstaining on the automatic Snapshot challenges around the LTIPP bridge items, including the MUX and Stargate proposals. That changes the visible delegate stance in the vote tracker, while leaving the challenge process itself in place.

In practice, the later communication shows the UADP presenting itself as an identified delegate group tied to a specific address and forum handle. The earlier vote update shows that the abstain status can apply automatically when an application arrives late, so the procedural step remains separate from any proposal-specific judgment.

Market reaction

We track UNI, but we only have 0 price points in that window. The series is stored every half hour, so newer events will have it. Computing it from two points would not be a reaction, it would be a coincidence.

How the story was built

Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.

first
Sep 22 21:37
Uniswap governance forum scoop our clock
Breaks the event
+0 min
Sep 22 21:37
Arbitrum DAO forum adds our clock
Adds the identifier 0x8326d18edfc50b4335113c33b25116ec268ff3

Has this happened before?

Nothing comparable yet.