-
Notifications
You must be signed in to change notification settings - Fork 30
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
Transactions are ignored (Bug in aragonOS?!) #115
Comments
I will pay $10 in ETH to somebody fixing this bug. |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 0.026 ETH (9.99 USD @ $384.12/ETH) attached to it.
|
@vporton It's working for me just incremented the counter to 44. You might need to check your network in Metamask http://localhost:8545 and import an account in Metamask from the terminal. |
Does not work for me (even after |
Bug confirmed with both Buidler node and |
Did you use |
Simply cloned. |
Don't do that better stable approach will be :
Hope this solves your problem. 👍 |
Did that, it does not help. |
It got even weirder: I sent 10 test ETH to the proxy contract address I added
to the Then when I try to call Increment, the transaction fails. I know from Buidler logs that namely this contract is called. Why can't I send 1 ETH? |
So I run
What the hell? |
When I transfer to my other MetaMask account, the transfer is reflected in the MetaMask, but Looks like I run two different blockchains, one is used by MetaMask and for sending Increment transactions and another for reading the counter variable. I ran If I run just
and when I try to click Increment:
So what is the correct way to run this blockchain at localhost? |
So, the real question is how to configure |
The config is done with
How to change this constant?! |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of 0.026 ETH (11.4 USD @ $379.91/ETH) attached to this issue has been cancelled by the bounty submitter
|
After I increment the counter it remains 42, as if I did nothing.
Yes, I cleared the application cache.
I checked, that the value of the variable in contract remains the same (does not change).
Bug report for the commit
3cfd17acae7869addcbe35c5208baafc724d3a92
.The text was updated successfully, but these errors were encountered: