BitShares Forum
Main => Technical Support => Topic started by: gn1 on October 23, 2015, 05:21:39 pm
-
Whenever I try to place an order to an exchange, or transfer my fund from one wallet to another, I get the error message, "Failed to broadcast transaction."
I tried from both Openledger and Light wallet, but same thing. It used to work a few days ago.
What is going on right now?
-
Whenever I try to place an order to an exchange, or transfer my fund from one wallet to another, I get the error message, "Failed to broadcast transaction."
I tried from both Openledger and Light wallet, but same thing. It used to work a few days ago.
What is going on right now?
There is usually more detailed information in red that could help.
It could be any number of things.
-
There's no error message in red.
-
I had this issue on one of my accounts as well. There was no further error information in red.
In my case my active key was greyed out (not clickable) on the permissions tab. I had to remove the active key and set the owner key as the active key. After that i was able to broadcast transactions again.
-
I have two wallets, one account in each wallet. (I did this because I could not create multiple accounts in one wallet)
I was able to place orders and transfer balance on one of the accounts, but not in the other.
I have checked and found out that the account that is not working shows an active key that was greyed out, as you mentioned.
So looks like I am getting the same symptom as jaran.
The active key and owner key is different though. Is it correct to place owner key as active key? And...why did this happen on one of my accounts?
-
Can you adjust your system clock?
-
What about the System clock? I am on a Mac, and it is configured to set date and time automatically.
-
>> I had to remove the active key and set the owner key as the active key.
I tried this, and it started to work again. Thank you, Jaran. Hmm... what was that all about??
-
Check your time at time.is If not (error is more than 3 sec) resync system clock
-
>> I had to remove the active key and set the owner key as the active key.
I tried this, and it started to work again. Thank you, Jaran. Hmm... what was that all about??
Ya i have no idea man. I asked on here and nobody knew. also my account with the problem has since obtained another active key which is not the same as the owner key. I have the exact same setup as you with multiple wallets per account and the problem first appeared on mac but i saw it on windows too.
-
>> I had to remove the active key and set the owner key as the active key.
I tried this, and it started to work again. Thank you, Jaran. Hmm... what was that all about??
Ya i have no idea man. I asked on here and nobody knew. also my account with the problem has since obtained another active key which is not the same as the owner key. I have the exact same setup as you with multiple wallets per account and the problem first appeared on mac but i saw it on windows too.
Very interesting. Can you tell me which account?
-
PMed you, bytemaster.
-
>> I had to remove the active key and set the owner key as the active key.
I tried this, and it started to work again. Thank you, Jaran. Hmm... what was that all about??
Ya i have no idea man. I asked on here and nobody knew. also my account with the problem has since obtained another active key which is not the same as the owner key. I have the exact same setup as you with multiple wallets per account and the problem first appeared on mac but i saw it on windows too.
Very interesting. Can you tell me which account?
Actually my bad bytemaster the active key did not revert to another one and is still the same as the owner key that i set it too to fix the orignal issue of a greyed out active key. I was looking at the wrong account. The account that had the original issue is jaran2
-
Hi,
I have the same problem
- whenever I try to place an order to transfer my fund from one wallet to another I get: Not your account
- whenever I try to place an order to an exchange I get the error message, "Failed to broadcast transaction."
in red: Transaction was not signed. Do you have a private key? [no_signers]
On Tuesday everything was perfect, I exchanged BTS for Obits with no problem at all.
I really need some help here!
Thanks in advance!
one more thing; the key is grey, not clickable
-
I could use some help on this same issue.
I need to transfer funds to another account to create a UIA and getting this error:
Failed to broadcast the transaction:
Transaction was not signed. Do you have a private key? [no_signers]
However, I played with the permissions and added a key to active and owner permissions and that update transaction went through fine.
I have logged out and logged back in / restored wallet - with no change.
-
I get the same problem.
I get the following message:
bitshares-crypto digest 3bc2af1c6a26b87f122878fbc37caf3bdb8e975954217bccd7502f8ece084a8b transaction 289c42a6e500ba9465590101bd0400000000000000f39c16bd963f0000000000c10bd4e1d6180000000000a4e7cc62000000 {"ref_block_num":39976,"ref_block_prefix":15050306,"expiration":"2017-07-12T03:17:14","operations":[[1,{"fee":{"amount":"1213","asset_id":"1.3.0"},"seller":"1.2.364147","amount_to_sell":{"amount":"4167357","asset_id":"1.3.1473"},"min_to_receive":{"amount":"416735700","asset_id":"1.3.0"},"expiration":"2022-07-12T03:16:52","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["2059acf486b4a94508246a39d3fb823d6bf87a04fbbcf5596ea293f34c2bff7ded3cc2227042aff1b208dd173a04cdae1eb8e568ea556f6ea34d61080586a71e80"]}
I'm in Japan. I'm not sure if that has to do with anything but clocks are different.
-
I have seen that message too .. once .. I made a regular transfer and then tried again .. worked
My guess is that the browser may have some issues with the crypto module but am not sure ..
I never saw that error when using the python library
-
I'm also received the following when I try to transfer BTS out of my account:
bitshares-crypto digest 49e5669733b95cead95af5e88f8931a8e6b703376435b0df9ab45d6af648247c transaction 11e5244fba3d3773665901005b5a0000000000000080d215b7b0017f3cfd0100000000000102e7ac623ca2ed564c97158af66fa782342bac8ccb2b5f2fc396d1cfcc334815fe023b5580d751ec4527b195afeda81db5c1d3bed90ed8acc724b90d177992c064f0537cca31385d0100208fdb8ad9e9d51bb7250e0e8001608075af5e24d733138cbc218cb46f7771288e0000 {"ref_block_num":58641,"ref_block_prefix":1035620132,"expiration":"2017-07-12T19:06:31","operations":[[0,{"fee":{"amount":"23131","asset_id":"1.3.0"},"from":"1.2.354560","to":"1.2.22583","amount":{"amount":"33373311","asset_id":"1.3.0"},"memo":{"from":"BTS6eX91yxiUWamctttQ9JTqYwCNT4M7k7R9u3BYkhHVJKohcjqjd","to":"BTS5LcxgwGzMbMey1hyn27kUnXWKNo2uSwu5NbM2u6RcCov2nqiLP","nonce":"383970911616083","message":"8fdb8ad9e9d51bb7250e0e8001608075af5e24d733138cbc218cb46f7771288e"},"extensions":[]}]],"extensions":[],"signatures":["1f6ffb49260c982fb84f4ac9ef850f61fbfb621395cbe33a77091c7942293da85673813e7996d46a2ffcfe33ceeeb48f2fab9dfdbef3cf62c0e8059f6cca97a096"]}
Looking at the Chrome browser console, I see error:
Error: Assert Exception: itr->get_balance() >= -delta: Insufficient Balance: saia-coin's balance of 0.21851 BTS is less than required 0.23131 BTS
But my balance is currently 334 BTS. so not sure what that's about ::)
-
[[0,{"fee":{"amount":"23131","asset_id":"1.3.0"},"from":"1.2.354560","to":"1.2.22583","amount":{"amount":"33373311","asset_id":"1.3.0"}
Looking at the Chrome browser console, I see error:
Error: Assert Exception: itr->get_balance() >= -delta: Insufficient Balance: saia-coin's balance of 0.21851 BTS is less than required 0.23131 BTS
But my balance is currently 334 BTS. so not sure what that's about ::)
Your balance is precisely 333.95162 BTS. You are trying to transfer 333.73311 BTS and you have to pay a fee of 0.23131 BTS.
333.73311 + 0.23131 = 333.96442 > 333.95162, so the error is correct.
-
ehhh....but the fee gets accounted for automatically.
My total balance = 333.95162
Amount to transfer = 333.73311
Fee = 0.21851
333.73311 + 0.21851 = 333.95162
-
(http://i68.tinypic.com/245y5vl.png)
Something must be wrong with the transaction confirmation. See how the fee on my original request window is different than the one on the confirmation window?
.21851 vs .23131
The fee on the confirmation window is greater than what was is auto-calculated on the request window.
-
Something must be wrong with the transaction confirmation. See how the fee on my original request window is different than the one on the confirmation window?
.21851 vs .23131
The fee on the confirmation window is greater than what was is auto-calculated on the request window.
Interesting. I'd guess that the fee in the request window does not take the per-kb fee into account. @svk?
-
Something must be wrong with the transaction confirmation. See how the fee on my original request window is different than the one on the confirmation window?
.21851 vs .23131
The fee on the confirmation window is greater than what was is auto-calculated on the request window.
Interesting. I'd guess that the fee in the request window does not take the per-kb fee into account. @svk?
Correct, only the confirmation window has the full fee including per-kb fee for the memo.
-
I get the same problem.
I get the following message:
bitshares-crypto digest 3bc2af1c6a26b87f122878fbc37caf3bdb8e975954217bccd7502f8ece084a8b transaction 289c42a6e500ba9465590101bd0400000000000000f39c16bd963f0000000000c10bd4e1d6180000000000a4e7cc62000000 {"ref_block_num":39976,"ref_block_prefix":15050306,"expiration":"2017-07-12T03:17:14","operations":[[1,{"fee":{"amount":"1213","asset_id":"1.3.0"},"seller":"1.2.364147","amount_to_sell":{"amount":"4167357","asset_id":"1.3.1473"},"min_to_receive":{"amount":"416735700","asset_id":"1.3.0"},"expiration":"2022-07-12T03:16:52","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["2059acf486b4a94508246a39d3fb823d6bf87a04fbbcf5596ea293f34c2bff7ded3cc2227042aff1b208dd173a04cdae1eb8e568ea556f6ea34d61080586a71e80"]}
I'm in Japan. I'm not sure if that has to do with anything but clocks are different.
It's a transaction expiration problem, not fee related. I fixed it yesterday in the code and pushed a new version to bitshares.org/wallet