Client: Trouble confirming Aragon vote with nano ledger

Created on 4 May 2019  路  4Comments  路  Source: aragon/client

Describe the bug
Hey Aragon team!

I am testing out bounties with @nebali for the Aragon org. listed below, where @nebali is logged into aragon mainnet via metamask at the following address: 0xcE1d57A86628fb54a0692715f1CB6ba61973C888

@nebali has clicked to vote to confirm a member mint and it opens the transaction, which then can be confirmed, but when accessed on ledger nano, they get a spinning wheel for a while
then the error message in the screenshot below . . .

Mainnet or testnet?
Mainnet.

Organization
https://mainnet.aragon.org/#/oncommunity.aragonid.eth

Screenshots
40d611380af1150cd746252ee2ee142afcf93356_2_690x371

I believe this issue may lie with ledger confirmation - please let us know if there are quick next steps to help resolve!

bug

Most helpful comment

@Ro5s It looks like vote # 10 was asked as a "question" in the voting app, rather than an action initiated from the Finance app. Unfortunately the Voting app is not smart enough to know what you mean from the "New Question" text field 馃槃.

It is a bit of a spoofing vector, but we're working on a redesign of Voting to make it more clear when a vote actually has an action embedded inside if it vs. just a harmless question (outside of the new "Question" and "Action" labels on the card).

All 4 comments

@Ro5s I have seen this error a couple times with ledgers being connected through Metamask. I'm not particularly sure if there's a fix, outside of restarting the ledger and/or retrying multiple times (I personally do this multiple times when trying to interact through Metamask through my ledger). You may also want to double check that you're on the latest firmware for your ledger.

Another option, perhaps more reliable, is to use frame instead. The Aragon client will connect automatically to a running frame instance without the extension (although it will prefer metamask if that's available).

Thanks for this feedback @sohkai !

So, we will try and brute force with the ledger (firmware is up-to-date), as you suggested.

Otherwise, we were able to create a vote using frame // however, oddly enough, the vote didn't seem to actually execute after our approval: https://mainnet.aragon.org/#/oncommunity.aragonid.eth/0xae974ac35f728a51a8b685dda53c675116b2a76b

(Compare result of Vote # 10 with Finance app).

@Ro5s It looks like vote # 10 was asked as a "question" in the voting app, rather than an action initiated from the Finance app. Unfortunately the Voting app is not smart enough to know what you mean from the "New Question" text field 馃槃.

It is a bit of a spoofing vector, but we're working on a redesign of Voting to make it more clear when a vote actually has an action embedded inside if it vs. just a harmless question (outside of the new "Question" and "Action" labels on the card).

Coming back here - thanks for all your notes!

We have resolved our issue through burning nonfunctioning (ledger) address.

Was this page helpful?
0 / 5 - 0 ratings