You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Go to Tokens > BGST, click on the token badge and copy the token address
Go to Finance and click new transfer
Under token select "Other..."
Copy the address from step one into the token address field.
See available balance, and specify an amount less than current balance.
Add reference and click submit deposit, sign transaction and wait for transaction to fail.
Expected behavior
Should be able to deposit the token into finance.
Screenshots
Desktop (please complete the following information):
Chrome + Metamask
Additional context
I've used this workflow in the past without issue, but have repeated this failure on multiple new rinkeby orgs since experiencing this issue.
The text was updated successfully, but these errors were encountered:
I was able to get this to work by manually increasing the Gas Limit in metamask. Will leave this issue open as there seems to be an issue with the gas estimation that would need to still be addressed.
Describe the bug
Previously I have been able to deposit an organization token (created via the onboarding or via the CLI) into the finance app.
Attempting to do so results in a failed transaction like the following: https://rinkeby.etherscan.io/tx/0xb0f79a2aad63c2d5621f7dea2e6796ecef77572ae1d8c481040148002fb186b4
Mainnet or testnet?
Rinkeby
Organization
https://rinkeby.aragon.org/#/bg
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should be able to deposit the token into finance.
Screenshots
![image](https://user-images.githubusercontent.com/4986634/59362817-1e574e80-8d02-11e9-80b1-615021b33fa4.png)
Desktop (please complete the following information):
Chrome + Metamask
Additional context
I've used this workflow in the past without issue, but have repeated this failure on multiple new rinkeby orgs since experiencing this issue.
The text was updated successfully, but these errors were encountered: