Skip to content
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

Error when redeeming TORN token from tornado.cash #11742

Closed
Serhy opened this issue Feb 12, 2021 · 3 comments
Closed

Error when redeeming TORN token from tornado.cash #11742

Serhy opened this issue Feb 12, 2021 · 3 comments

Comments

@Serhy
Copy link
Contributor

Serhy commented Feb 12, 2021

Bug Report

Problem

Originally reported by user that he is not able to redeem TORN tokens using the status wallet. transaction failing with the following error:

cannot unmarshal non-string into Go struct field SendTxArgs.value of type *hexutil.Big

Can't reproduce because I don't have TORN tokens to redeem :(

Expected behavior

Can redeem vTORN tokens from https://app.tornado.cash/airdrop/

Actual behavior

cannot unmarshal non-string into Go struct field SendTxArgs.value of type *hexutil.Big error when redeem tokens from https://app.tornado.cash/airdrop/

Preconditions

Address with vTORN tokens available to redeem exists

Reproduction

  • Open Status and recover an account with vTORN tokens available to redeem
  • In Browser -> open https://app.tornado.cash/airdrop/ dapp
  • Click top-right ... -> 'Connect' -> Web3 wallet -> Allow
  • Click Redeem
  • Sign and send transaction

Additional Information

  • Status version: release 1.10
  • Operating System: Android and iOS
@Serhy Serhy added the bug label Feb 12, 2021
@flexsurfer flexsurfer self-assigned this Feb 12, 2021
@Serhy
Copy link
Contributor Author

Serhy commented Feb 15, 2021

Attached geth.log and Status.log from user report

@churik
Copy link
Member

churik commented May 11, 2021

linked here another issue with same dapp #11565

@churik
Copy link
Member

churik commented Jul 27, 2022

Closing, as page doesn't exist anymore

@churik churik closed this as completed Jul 27, 2022
@ilmotta ilmotta removed the bug label Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants