Uniswap-Arbitrum Delegate Program (UADP) Communication Thread
- Published
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.
Key claims & sources
What it means
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 i
We only have 0 data 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.
Coverage timeline
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.
Uniswap governance forum
scoop
our clock
Arbitrum DAO forum
adds
our clock