-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WalletConnect] Snapshot votes don't get registered, and need at times several submissions before being picked up #3522
Comments
@francovenica , the card is converted to the issue, as you was able to reproduce in case of 30 mints delay |
Let's check if Snapshot votes have an intrinsic timeout. |
I created a space in https://testnet.snapshot.org/ to test this but trying to connect to my Sepolia safe via WC doesn't work as its not supported. Edit: There is a small bug in Snapshot that prevents this from working on Sepolia. I've opened a PR to address it in their codebase: snapshot-labs/snapshot-v1#4692 |
Update from Usame:
|
The fix was merged. I will test this again |
Ok, I was able to test this on a testnet space that I created: https://testnet.snapshot.org/#/asd.eth I checked both 1/1 and n/m safes with WC. Here are my results: 1/1
n/m
It might have to do with it being a testnet space but even their graphql endpoint doesn't return any votes. |
After digging into it a bit more I realized that I should be using Snapshot as a safe app. Unfortunately the testnets.snapshot.org doesn't seem to have a relayer that is necessary to support safe votes so I created an issue on their board: snapshot-labs/snapshot-v1#4793 Not necessarily a blocker but the only way to test is to have eligible tokens for an official space via snapshot.org and vote on a real proposal. |
existing 20.11.24 |
What was the fix? |
"We've been using safe successfully to manage our DAO's operations for a while.
However recently there's been issues when using Safe with Snapshot. Votes don't get registered, and need at times several submissions before being picked up.
This wasn't an issue in the past, but is now impacting the smooth running of our operations.
What can be done to make sure our votes and proposals pass?
Steps:
Current result : the message gets submitted on-chain/off-chain but doesn't get recognised by snapshot
What to test:
The text was updated successfully, but these errors were encountered: