Need your help with something easy

[Get-Paid.com]

I tried to accelerate this transaction:

https://www.blockchain.com/btc/tx/632e1733fb51412b7ddd3685f5e545fb9d58d25aae5fcd7d647ff6cd83f35b42

But ViaBTC says "Transaction input unconfirmed".

Can you please help me understand which transaction is unconfirmed so perhaps I can pay for an accelerator for it?

Thanks.


PS It should be easy for you but difficult for me.

[LoyceV]

Click the addresses on the left, you'll get https://www.blockchain.com/btc/address/1Dyii5mcN84QytY6FtVeuguDHNZG5rm2mY and https://www.blockchain.com/btc/address/14qb9XtSjDeBnfQJUhwxBooLQQjJNQVwKn.
The last one has an unconfirmed input, and if you click on them again, you'll find a long chain of unconfirmed inputs.

It looks like you've been doing many small payments, like sending 721 Satoshi, while fees are rising. Basically, you're creating Bitcoin dust. Not only do you pay more fee than the dust is worth, the dust can't be used because it would require a higher fee than it's worth at the moment.

You may want to read Fees are low, use this opportunity to Consolidate your small inputs!

By clicking addresses on the right, you see the unconfirmed chain continues in that direction too. Can you explain how you make these transactions: is it a script or manual work?

There are several things you can (and probably should) do: use Bech32 addresses, bundle transactions, and set a minimum payment amount to prevent creating worthless Bitcoin dust.
If you really want to keep doing what you're doing, you can prevent a long chain of unconfirmed transactions by using different inputs. If you own more smaller inputs, you can spend coins from a new confirmed input instead of building a deeper chain of unconfirmed transactions. However, this is not the preferred solution.

[Get-Paid.com]

It looks like you've been doing many small payments, like sending 721 Satoshi, while fees are rising. Basically, you're creating Bitcoin dust. Not only do you pay more fee than the dust is worth, the dust can't be used because it would require a higher fee than it's worth at the moment.

It's payments to users, some asked for $0.50 so we didn't use high fee...

Why SENT funds cause problem to use RECEIVED funds if all of our RECEIVED funds were fully confirmed?

[poordeveloper]

Actually not. The 2nd link LoyceV posted was, as he said, unconfirmed by the time you sent it.



The fact that you could send it doesn't mean it was confirmed.

[john2231]

It looks like you  have a series of unconfirmed transaction look at this 14qb9XtSjDeBnfQJUhwxBooLQQjJNQVwKn and click the every output from the left side you can see all transaction is unconfirmed.

OMG I tried to click all outputs to find where the bitcoin comes from but almost the series of transaction are unconfirmed but some of the transaction put enough fee.

Add this from LoyceV suggestion.
Why not collect all unconfirmed transactions and follow my guide below.
https://bitcointalk.org/index.php?topic=5127118.msg50421878#msg50421878

Then rebroadcast them from this list https://en.bitcoin.it/wiki/Transaction_broadcasting

So that you can notify miner's to don't forget about all of your transactions and let's hope that sooner it may includes all of unconfirmed transaction to next block.

[LoyceV]

It's payments to users, some asked for $0.50 so we didn't use high fee...

Well, there's your problem You can't do that anymore with fees on the rise.

[HCP]

Why SENT funds cause problem to use RECEIVED funds if all of our RECEIVED funds were fully confirmed?

It isn't a problem IF your funds are confirmed... but the problem is that your RECEIVED funds are NOT fully confirmed...

One input from: 632e1733fb51412b7ddd3685f5e545fb9d58d25aae5fcd7d647ff6cd83f35b42
comes from unconfirmed transaction: f7ef220c1b4eb23de43f514f433fc3b00fb0feda074bf6da29a9c502f75e8fc0
which comes from unconfirmed transaction: ee234ddc9555bb252f30389f274d9072ff9d11ca6f0677b3b91bde6c4d66e199
which comes from unconfirmed transaction: 04af53ab298a2d50edb33b2aa1bdad4c6f48d08e3942c7c4bb3ad80a9d1b070c
which comes from unconfirmed transaction: e5fe84a0337d216d9cd114eb9c803dfb61fc74b2142e0b1d708ba78be58c3a64
which comes from unconfirmed transaction: 4e4cf509a3cad247a3a623cd9d24f29baa84f6ffb99081ede9abc0112505a21e
which comes from unconfirmed transaction: 7c124f3b964bccde81760504700a089ef57caa6f528d303e30e008d260328e20
which comes from unconfirmed transaction: 8c8ef940004d935227b894b1277730d1232a8740662f4db4b6badad502a7944f
which comes from unconfirmed transaction: 8072d4034ebe2193407fdaf997ddcc3d2e2503317b8b888f10b13ddbf2d9d29f
which comes from unconfirmed transaction: bea4d21c603268d0a468a5fe542571d8f28f3d038fa49cac120fe506e7aba1fb
which comes from unconfirmed transaction: d118302e0d6b133edd4c49af76b55acb724dcb582da6c61b6c0c54fc0d59864f

It then branches at this point... as all 4 inputs there come from unconfirmed transactions...

Branch 1:
c42ec709069cf22dbd0ff22514194d2487c8aba47722b6e6ab0dca1d4ba37b1f

Branch 2:
c336d40b375d64f262fd78377dbcdec5b57112934219951441018b7d7b1e33c8
7548505d013fa630d38f887ae8b433731b48591812e7554abac65c2d9c1c2f4d
131035a0be8415cbffc63289872cb62f11772a4703ab40d28fd08018df9a5fe9

Branch 3:
7d510cd0d0dd58b1b6f58cef7f4612dbca084738418946b39ff4a97277659227
ea0671e7b05eabe9a727ae71ed6f75cc9c84cfdeb1451d65b991255f0ec21335

Branch 3 also splits here:
Branch 3a:
cac7eb21c30f8ee8be79957809d0d257c59ef862166c45b725c0a7e6bb7d2456
f3d739861ebec71c9cc35a63997e5a62992b663e6892dfc327ef3c484f9f7f45

Branch 3b:
fb55444011306f8c3eadf2d9b765423c4cb7052c22b4a01ead8bc68643e63d76


Branch 4:
5886236164c7c9dba08ce890dae5a55a06ea3147ba1e606726d5ac9fc6c6bfe6
61c6924395091ccd968c3c6a43ee4cede5d3ea813cc4c56ee7f55d666db03adc

it is going to take a while for all of this to confirm... especially with the pump in BTC value, the network is going nuts, blocks are full and fees have shot up.


I suggest you either learn how to batch up transactions, so you can send multiple amounts in ONE single transaction... implement a "minimum payout"... (possibly even switch to a different coin like Bitcoin Cash where block space is plentiful and fees are practically zero )


EDIT: and wouldn't you know it... just as I finish typing all this, the transactions confirm! #youGotLucky

[Get-Paid.com]

EDIT: and wouldn't you know it... just as I finish typing all this, the transactions confirm! #youGotLucky

No, it's not about being lucky.
The transaction was urgent for us, so we paid ViaBTC to accelerate many of the unconfirmed transactions until it hits this one.

The costs? 0.3 BCH approx. (around $56) but we probably spent so much less than that, we bought BCH when it was $180, now it's $260, we have 1 BCH extra we saved aside, so we will just convert it to BTC and it would compensate for what we spent.

Is it worth it? At these circumstances yes. ViaBTC is 100% genuine and it works.

[Get-Paid.com]

Well, there's your problem You can't do that anymore with fees on the rise.

We sent a message to all users in our site we won't process any Bitcoin withdrawals until further notice, so they must choose an alternative or wait for the network to get stabilized.

This was time consuming and we cannot allow ourselves to deal with similar incidents in the near future.

[HCP]

If you can't afford another similar incident... then I'd seriously reconsider your entire methodology regarding withdrawals for customers...

I realise you like the idea of offering "instant" withdrawals... but creating a long string of small fee transactions obviously comes with some downsides if the network conditions are not favourable. Given how many transactions your system created in such a short time (approx 10-15 in about a 5 minute window), you might be better off implementing a "batching" system to collate withdrawal requests in a given 5-15 minute window and creating one single transaction.

Your overall fee costs will decrease and you're less likely to create such long unconfirmed transaction chains. There is a reason why most of the "big" sites do exactly this

Also, as the block time is typically averaged to 10 minutes, collating transactions means users are generally going to have to wait for that sort of timeframe to get a confirmation when the mempool is empty and fees are 1 sat/vbyte etc... so, they're not really likely to be disadvantaged too much by such a batching system.

The really tricky part will be making sure you communicate any change with your user base so they understand why you're doing what you're doing... and the benefits for all involved.

[Get-Paid.com]

I realise you like the idea of offering "instant" withdrawals... but creating a long string of small fee transactions obviously comes with some downsides if the network conditions are not favourable. Given how many transactions your system created in such a short time (approx 10-15 in about a 5 minute window), you might be better off implementing a "batching" system to collate withdrawal requests in a given 5-15 minute window and creating one single transaction.

Thanks for the advice.
How do you send 1 single transaction with multiple payments to users?

[Pmalek]

How do you send 1 single transaction with multiple payments to users?

It depends on the wallet you use.
If you use Electrum there is an option called Pay to many Click on Send > Pay to many.

[LoyceV]

How do you send 1 single transaction with multiple payments to users?

See your own topic: Bitcoin Mass Payment 

[Get-Paid.com]

How do you send 1 single transaction with multiple payments to users?

It depends on the wallet you use.
If you use Electrum there is an option called Pay to many Click on Send > Pay to many.

How do you send 1 single transaction with multiple payments to users?

See your own topic: Bitcoin Mass Payment 

I've used your advice and sent 9 small payments like this:

https://www.blockchain.com/btc/tx/1ab7e16441c6d7dc9e9cb3d0648c42ec2053dc2dd8fece8dfbfa2bacdf61b89b

Is this better?

[LoyceV]

Is this better?

Much better