Author

Topic: Coinb.in - You have a confirmed balance of 0 BTC unable to send (Read 235 times)

hero member
Activity: 2044
Merit: 784
Leading Crypto Sports Betting & Casino Platform
Was that after changing the broadcast and mempool settings? (the error you got from wallet tab).
Their wallet is more broken that I thought.
Yes, even though I changed mempool settings the error persisted on that tab.
And there are some other bugs too.

For transactions generated using the other tabs, just broadcast the "Signed RAW Transaction", the long HEX string result from sign tab.
Ok, did like you said and now the transaction is going normally. I'm just waiting for confirmation that must happen soon.

Thanks for your kind support and sorry for my lack of knowledge!

I would like to send you merit points, but I have none disponible here. Sad

Got 1 merit and sent you, thanks! Wink
legendary
Activity: 2618
Merit: 6452
Self-proclaimed Genius
But wait, I thought you're using their wallet feature/tab?
If it is, you only have to use the "spend" button under your address.
Through the wallet feature I couldn't send the transaction (same *You have a confirmed balance of 0 BTC unable to send...* message appearing).
So I did it through +New > transaction tab and signed it in *Sign tab* later, and ended verifying it in *Verify tab*.

Maybe I should have done something else?
Was that after changing the broadcast and mempool settings? (the error you got from wallet tab).
Their wallet is more broken that I thought.

For transactions generated using the other tabs, just broadcast the "Signed RAW Transaction", the long HEX string result from sign tab.

hero member
Activity: 2044
Merit: 784
Leading Crypto Sports Betting & Casino Platform
Sounds like you used a fee that was too low and the transaction was not confirmed... it was then dropped by the network (likely purged because of a low fee) and you were able to see the BTC in your wallet again.
I put 20,000 satoshis fee.

After signing and verifying... did you actually "Broadcast" the transaction? Huh If it has not been broadcast, then the network has no knowledge of this transaction Wink
This? If so, what would be the hex encoded bitcoin transaction? Is it the same code I used to verify the transaction before?
HCP
legendary
Activity: 2086
Merit: 4361
Ok, I did like this, the transaction was launched (generated a txid) and the btcs disappeared from the wallet for a while.

But it didn't concretize and the btcs returned to my wallet.
Sounds like you used a fee that was too low and the transaction was not confirmed... it was then dropped by the network (likely purged because of a low fee) and you were able to see the BTC in your wallet again.



Through the wallet feature I couldn't send the transaction (same *You have a confirmed balance of 0 BTC unable to send...* message appearing).
So I did it through +New > transaction tab and signed it in *Sign tab* later, and ended verifying it in *Verify tab*.

Maybe I should have done something else?
After signing and verifying... did you actually "Broadcast" the transaction? Huh If it has not been broadcast, then the network has no knowledge of this transaction Wink
hero member
Activity: 2044
Merit: 784
Leading Crypto Sports Betting & Casino Platform
How do I sign it now?
There's a "sign" tab but you have to paste your private key to use it.
The private key of the input should be pasted on the text box above and the "raw transaction" from the transaction tab below it.

Importantly, you must double-check the transaction before broadcasting it using the "verify" tab, because the new transaction window doesn't automatically generate change for you.
Any excess amount will be used as fee.
Ok, I did like this, the transaction was launched (generated a txid) and the btcs disappeared from the wallet for a while.
https://www.blockchain.com/en/btc/tx/63bc2133d50369fdf5922f54a055505c8e7d48d0b5be01cf7d9a5d32bd20a732

But it didn't concretize and the btcs returned to my wallet.

But wait, I thought you're using their wallet feature/tab?
If it is, you only have to use the "spend" button under your address.
Through the wallet feature I couldn't send the transaction (same *You have a confirmed balance of 0 BTC unable to send...* message appearing).
So I did it through +New > transaction tab and signed it in *Sign tab* later, and ended verifying it in *Verify tab*.

Maybe I should have done something else?
legendary
Activity: 2618
Merit: 6452
Self-proclaimed Genius
How do I sign it now?
There's a "sign" tab but you have to paste your private key to use it.
The private key of the input should be pasted on the text box above and the "raw transaction" from the transaction tab below it.

Importantly, you must double-check the transaction before broadcasting it using the "verify" tab, because the new transaction window doesn't automatically generate change for you.
Any excess amount will be used as fee.

But wait, I thought you're using their wallet feature/tab?
If it is, you only have to use the "spend" button under your address.
hero member
Activity: 2044
Merit: 784
Leading Crypto Sports Betting & Casino Platform
Ok, changed unspent outputs and broadcast to Blockcypher and created a new transaction. I've already clicked submit button.

Now this message appears with a code below:
Quote
Transaction
The transaction below has been generated and encoded. It can be broadcasted once it has been signed.

How do I sign it now?
legendary
Activity: 2618
Merit: 6452
Self-proclaimed Genius
I forgot: In addition to my post (#5), you might need to set "Broadcast" to blockcypher as well because the input may be missing from coinb.in's mempool that could cause "inputs missing or spent" error when sending the transaction.
legendary
Activity: 3038
Merit: 4418
Crypto Swap Exchange
Try changing your settings: https://coinb.in/#settings/.

Change the unspent output from coinb.in to another source. Coinb.in's own server seems to be down when retrieving unspent outputs.


legendary
Activity: 2618
Merit: 6452
Self-proclaimed Genius
Already tried to decrease the amount of BTCs on the transaction, but it doesn't work.
Looks like their mempool is having problems with native SegWit UTXO.
You can temporarily fix it by using blockcypher as the mempool backend instead of coinb.in, that option is in the "settings".

In "New->Transaction", expand "Advanced Options" and click "setting" under network.
From there, expand "unspent outputs", select "Blockcypher (Bitcoin Mainnet)" and then "Submit", it should return with "Settings updates successfully".
Now try to send a new transaction.
legendary
Activity: 2758
Merit: 6830
6 confirmations and completed about a month ago. And I can see the balance of 0.00124 btc at my Coinb.in wallet.
I even tried to transact 0.00123 btc total (a little less of the total amount), but still doesn't work.
You can always go to Keys, copy your private key and import it on Electrum. See if your balance shows up there.
hero member
Activity: 2044
Merit: 784
Leading Crypto Sports Betting & Casino Platform
That message would tend to indicate that you're trying to spend coins you don't actually have... Are the coins from an "unconfirmed" transaction? Huh
No, it's already confirmed. You can check it on the link below:
https://live.blockcypher.com/btc/address/bc1qdz3f44h5p2jvlhas550ud95fjf88dy5f7yke6c/

6 confirmations and completed about a month ago. And I can see the balance of 0.00124 btc at my Coinb.in wallet.
I even tried to transact 0.00123 btc total (a little less of the total amount), but still doesn't work.
HCP
legendary
Activity: 2086
Merit: 4361
That message would tend to indicate that you're trying to spend coins you don't actually have... Are the coins from an "unconfirmed" transaction? Huh
hero member
Activity: 2044
Merit: 784
Leading Crypto Sports Betting & Casino Platform
I have some satoshis in Coinb.in virtual wallet, but it doesn't let me withdraw my funds. I'm trying to pay a 4000 satoshis fee, but when I click *send* button the message always repeat:
Quote
You have a confirmed balance of 0 BTC unable to send...
Already tried to decrease the amount of BTCs on the transaction, but it doesn't work.
Jump to: