After upgrading to 2.0, I decided to test the variable collateral. So I opened one of my usd-collateral-holder accounts and reduced my leverage on one to free up some collateral. Then I attempted to transfer the freed up collateral to another account, but when I click on transfer and type in that account to the FROM field, it says Not your account. Is there any way to claim it?
Quote from: wmbutler on October 13, 2015, 08:48:19 PM
After upgrading to 2.0, I decided to test the variable collateral. So I opened one of my usd-collateral-holder accounts and reduced my leverage on one to free up some collateral. Then I attempted to transfer the freed up collateral to another account, but when I click on transfer and type in that account to the FROM field, it says Not your account. Is there any way to claim it?
I have the same issue. I've been asking about this since the test net. I still have received no response.
Quote from: clout on October 13, 2015, 10:06:07 PM
Quote from: wmbutler on October 13, 2015, 08:48:19 PM
After upgrading to 2.0, I decided to test the variable collateral. So I opened one of my usd-collateral-holder accounts and reduced my leverage on one to free up some collateral. Then I attempted to transfer the freed up collateral to another account, but when I click on transfer and type in that account to the FROM field, it says Not your account. Is there any way to claim it?
I have the same issue. I've been asking about this since the test net. I still have received no response.
We're working on this now. Has to do with legacy addresses. There is temporary fix checked in but I don't think it is deployed. I should have the permanent fix tomorrow.
Awesome!
Any updates on the release? I also have a much larger issue regarding my OS X full wallet no longer working.
This should fix the issue in the repo as of Oct 14th...
https://github.com/cryptonomex/graphene-ui/issues/330
It is running at openledger. However, the last release v2.15.286 happened on Oct 13th.
Can anyone confirm the fix at open ledger?
Quote from: jcalfee1 on October 20, 2015, 08:08:23 PM
This should fix the issue in the repo as of Oct 14th...
https://github.com/cryptonomex/graphene-ui/issues/330
It is running at openledger. However, the last release v2.15.286 happened on Oct 13th.
Can anyone confirm the fix at open ledger?
there are more recent releases (including 4 hours ago)
https://github.com/bitshares/bitshares-2-ui/releases
the ppa:showard314/bitshares on ubuntu has it and windows/mac binaries are available here:
https://github.com/bitshares/bitshares-2/releases