Request: Provide a Way for CrabDAO and CKTON DAO to Propose and Vote on Sunsetting Summary

[sonoferin2000]

Summary
CrabDAO and CKTON DAO currently have no mechanism to create proposals or vote on decisions. Sunsetting the network requires legitimate approval from the stakeholders who actually hold CRAB and CKTON. A temporary, minimal-effort governance method must be provided so these DAOs can create proposals and vote before shutdown.

Request
Provide a simple, low-cost way for CrabDAO and CKTON DAO to:

Submit proposals related to the sunsetting process.

Vote on those proposals using their token balances.

Have the results executed exactly by RingDAO, since Crab has no on-chain governance module.

Reasoning (System Logic)
Inputs:
– CrabDAO and CKTON DAO lack any voting infrastructure.
– Major decisions cannot be taken without token-holder approval.
– Sunsetting requires consent from those holding economic exposure.

Levers:
– One-time snapshot of CRAB + CKTON + optional LP positions.
– Off-chain signature voting (Snapshot-style).
– RingDAO executes results exactly as decided.

Outputs:
– A legitimate way for Crab and CKTON holders to govern the sunsetting.
– No long-term infrastructure needed.
– Minimal workload for the team.

Proposal

Establish a temporary proposal system (GitHub issue template or simple form) where CrabDAO and CKTON DAO members can submit sunsetting-related proposals.

Enable a temporary off-chain weighted vote, where each wallet signs a message to vote.

Weight each vote by the snapshot of CRAB and CKTON balances.

Require RingDAO to execute the exact result without modification, except for documented, necessary security or technical constraints.

Ask
Approve a temporary, snapshot-weighted, signature-based governance method so CrabDAO and CKTON DAO can propose and vote on all sunsetting steps before execution.

[boundless-forest]

The simplest way from my understanding is to use Polkadot Apps to vote on referenda, the weight of your vote depends on the balance. See https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fcrab-rpc.darwinia.network%2F#/referenda.
Voters can connect their accounts with Talisman wallet and cast their votes there.

For the proposal discussion of Crab sunset, github discussion or forum channels in the discord are available.

[sonoferin2000]

thanks. not user friendly by any means, and you say that is the simpleist way? i barely figured out how to do the wallet setup. i hope i can get a little help submitting it, im not a computer engineer by any means. Thanks for shareing that link. was very helpful, just a lot overwhelming I must admit.

[2xJDubs]

@boundless-forest to use on-chain voting through polkadot.js/app we would need to shutdown all staking now and return all staked CRAB since polkadot.js/app does not see gCRAB as a token that can be used for governance.

[2xJDubs]

I like your idea of how to handle this voting as I agree that polkadot based governance is very hard for the average user to understand and use. I think your idea has merit but needs more work so it can not be gamed so I do think we need to work on a possibility.

cKTONDAO does have a tally page setup here: https://www.tally.xyz/gov/cktondao

But I could not find one for CrabDAO.

@boundless-forest how costly and difficult would it be to setup a degov for CrabDAO and possibly cKtonDAO?

[boundless-forest]

how costly and difficult would it be to setup a degov for CrabDAO and possibly cKtonDAO?

It's another option. I see no difficulty to do that. The chain indexer sync may take at most 3 days.

[sonoferin2000]

[sonoferin2000]

boundless-forest to the rescue. i was really struggling to think of novel workarounds.

[sonoferin2000]

i know tally is not reflecting the true token counts, unsure how often it looks at the contract to refresh.

[2xJDubs]

i know tally is not reflecting the true token counts, unsure how often it looks at the contract to refresh.

In talking with the team, the cKTON Tally is not active or connected anymore. It is not usable for this. We are discussing other options at the moment.

[sonoferin2000]

How about we simply take one snapshot of the gCKTON pool so everyone’s voting power is frozen in place. No one can add or remove weight after that.

Then we post the list of who can vote. It’s a tiny group anyway, around 50 wallets. Each wallet already has its own weight from the snapshot.

To vote, you don’t mess with Polkadot.js or anything technical. You just send 0.1 CRAB from your governance wallet to one of two addresses:

• One address means YES
• One address means NO

That’s it. Sending the 0.1 CRAB is basically your “vote marker.”

Then when the vote is done, you just look at the chain.
If an address sent 0.1 CRAB to YES, their snapshot weight goes into the YES total.
If they sent it to NO, their weight goes into NO.
Anyone not on the snapshot list doesn’t count.
If someone tries to vote twice, the first vote is the one that matters.

Add up the weights on each side → that’s the result.
Simple, cheap, verifiable, and impossible to cheat.

[hackfisher]

To vote, you don’t mess with Polkadot.js or anything technical. You just send 0.1 CRAB from your governance wallet to one of two addresses:

• One address means YES
• One address means NO

This is a good idea

[hackfisher]

Below are some resources and suggested actions that may be useful for the proposal initiator:

1. Select and finalize a specific block height.

2. At that block height, use the CrabScan API (This is one of the essential services provided by RingDAO, community can also run alternative instances by themselves)
   (https://crab-scan.darwinia.network/api-docs)
   to generate a full snapshot, download the data, and merge/process it as needed.
   (AI-assisted tools may help automate this step.)
   It is recommended that the proposal initiator handles the snapshot process independently if possible, in order to avoid introducing additional technical support costs.

3. Define unique YES / NO addresses for each proposal, ensuring they are distinct and not reused by others.

4. Set a fixed voting duration, such as 7 days or 14 days.

[hackfisher]

Sample:

response_1763865536653.json

[sonoferin2000]

Thanks for laying out the steps so clearly. This gives me a workable path forward.

I should mention I’m a mechanic with very limited computer skills, so while I can choose the snapshot block, post the YES/NO vote addresses, and set the voting window, I’m not able to run the CrabScan API tools or process the snapshot and tally by myself.

Since you already understand the mechanics and outlined the method, your guidance—or direct help with the snapshot and final tally—would ensure this process is done correctly and concluded cleanly. I’m ready to move as soon as the block height is set, and with your support we can bring this to a proper, verifiable finish.