AIP-17A: Election of the First New Multisig Signer for AssangeDAO

General
1

AIP-17A: Election of the First New Multisig Signer for AssangeDAO

Summary

Following AIP-15, which established the process for adding two new Multisig Signers to AssangeDAO, this proposal (AIP-17A) initiates the first Snapshot vote to elect one Multisig Signer from five shortlisted finalists. A second vote (AIP-17B) will elect the second signer. This aims to restore efficient governance, transparency, and alignment with AssangeDAO’s mission.

Background

AIP-15 addressed governance gaps due to the departure of original Multisig Signers. After a three-week nomination period and two-week community discussion, the Governance Transition Unit (GTU) shortlisted five finalists based on governance activity, community trust, and role fit. This proposal submits them for a Snapshot vote to select the first Multisig Signer.

Roles & Responsibilities

Execution: Execute approved Snapshot proposals on Gnosis Safe within 72 hours.
Accountability: Justify any delays (e.g., legal/security concerns) publicly.
Transparency: Ensure responsiveness and transparent fund flows.

Finalists
The GTU shortlisted these candidates based on AIP-15 criteria. Review their nomination posts for details:

Loganweng: Nomination Post
sudongpo: Nomination Post
qingfeng.eth: Nomination Post
Versky (@michael_web3): Nomination Post
Gabriel Shipton: Nomination Post

Voting Process

Selection: Vote for one candidate. The highest vote-getter becomes the first Multisig Signer. AIP-17B will elect the second signer from remaining candidates.
Term Length: 2 years, eligible for re-election per AIP-15.
Voting Duration: 2 days.
Platform: Snapshot

Removal Mechanisms
Per AIP-15:

Voluntary Resignation: Allowed with notice and transition support.

Automatic Removal:
Formal resignation.
Proven fund misuse.
Collusion with anti-DAO actors.

Community-Triggered Removal (via Snapshot):
Documented misconduct.
Repeated failure to perform duties.
Security/governance risks.
Violation of AssangeDAO’s values.

Governance Design

Execution: On-chain via Gnosis Safe.
Transparency: Transactions are publicly verifiable.
Treasury: Funds in Gnosis Safe, spent only after Snapshot approval.

Mission Alignment
This proposal restores governance, encourages participation, and ensures transparent execution, aligning with AssangeDAO’s mission.

GTU Dissolution
The GTU will dissolve after electing and onboarding both Multisig Signers (post AIP-17B), per AIP-15.

Voting Options

Loganweng
sudongpo
qingfeng.eth
Versky (@michael_web3)
Gabriel Shipton
Abstain

Note: You may select only one candidate. The highest vote-getter is elected as the first Multisig Signer. AIP-17B will allow you to vote for the second Multisig Signer

3 Likes
2

https://snapshot.box/#/s:assangedao.eth/proposal/0xf53a612c6caa80e91b8cb082d0083d65d8dc29b13d372fb3401bd63288cde709

Timeline

Created

Sep 27, 2025 · 3:23 PM

Start

Sep 28, 2025 · 3:23 PM

End

Sep 30, 2025 · 3:23 PM

Directly after this one ends, AIP-17B will be posted in the same format, with the remaining 4 Multsigs nominees as options, in order to elect the 2nd Multisig signer.

2 Likes
3

My only comment is that nobody in leadership seem to be boosting this on social media.

1 Like
4

I have suggested we nominate DAO members for further positions,- I think we need social media managers/outreach, discord mods, forum mods, project leaders, etc. I have DM’d the twitter asking them to share it.

2 Likes
5

Great to see further progress! Hopefully, this time we can actually save the situation. Thank you all for your efforts.

6

Thanks a lot for time & efforts of all GTU members

7

Congrats! Gabriel has received the highest amounts of votes and will be added to the Safe Multisig.

1 Like
8

My ETH address: 0x2B794208FbB6ed6017e8FE129611dC0e2F68edBa

1 Like
9

Thank you

I need 2 Multisigners to confirm the on chain rejection of transaction 44 and then confirm transaction 45 which adds both multisigs

44 was to add Mike only but nobody else signed it in time so I just did another to add both Gabriel and Mike.

Please confirm on-chain rejection:

Please confirm transaction:

2 Likes
10

It’s been almost a month since the multisig was voted in, and yet the task hasn’t been completed. Is someone deliberately causing trouble? Why hasn’t multisig been added to the system yet? The entire community is waiting. Who is delaying this for their own selfish reasons?

11

Why hasn’t the multi-sig implemented this proposal? Delaying implementation of something decided by a community vote is a serious dereliction of duty and has severely hindered community development. If the current multi-sig no longer wishes to serve, please resign and allow the community to re-select a multi-sig that serves the community’s interests.