Author

Topic: Why this is taking so long to find a block ? (Read 1194 times)

legendary
Activity: 2226
Merit: 1052
No... I'm not using shared send function. I am using https://blockchain.info/api/api_receive for an application I'm developing on. A is the user address and C is the admin address. B is the intermediary provided by blockchain.info where my fund is now sitting.

Looks like blockchain.info is now unable to show any fund at all !!!

Got temporary error 1218 'Send Buffers overloaded in NDB kernel' from NDBCLUSTER

Has the problem been solved now? If not, trying sending a support ticket, or send a PM to piuk.

This is disgusting !!! We seriously need an alternative good API provider for send/receive functionality !!!

What about running a local bitcoind?  Huh

After 5 hour the fund was forwarded properly and reached C, but an associated callback never took place. So the associated activity in my application for the successful receival of user fund has been halted.

Previously I tried to reach PIUK but he does not reply for months. Not even the concerns raised in blockchain.info thread is addressed.

Running only a local bitcoind wont solve my problem. I need send/receive API support.


hero member
Activity: 653
Merit: 500
No... I'm not using shared send function. I am using https://blockchain.info/api/api_receive for an application I'm developing on. A is the user address and C is the admin address. B is the intermediary provided by blockchain.info where my fund is now sitting.

Looks like blockchain.info is now unable to show any fund at all !!!

Got temporary error 1218 'Send Buffers overloaded in NDB kernel' from NDBCLUSTER

Has the problem been solved now? If not, trying sending a support ticket, or send a PM to piuk.

This is disgusting !!! We seriously need an alternative good API provider for send/receive functionality !!!

What about running a local bitcoind?  Huh
newbie
Activity: 3
Merit: 0
up on your luck Grin
Sorry it's can't help.
legendary
Activity: 2226
Merit: 1052
Reading between the lines of your question:  were you using the shared send function?

If so go back into your blockchain.info account and go back to the "Shared Coin" page.  At the bottom you will see the following:

Quote
Something went wrong?
When sending a shared coin transaction a number of intermediate addresses are used. If anything interupts the process or an error prevents the transaction from completing the coins may be left in an intermediate address. Click the button below to claim any coins left in intermediate addresses, this process can take several minutes to complete.

Recover Intermediate Addresses

Try pressing the "Recover Intermediate Addresses" button


No... I'm not using shared send function. I am using https://blockchain.info/api/api_receive for an application I'm developing on. A is the user address and C is the admin address. B is the intermediary provided by blockchain.info where my fund is now sitting.

Looks like blockchain.info is now unable to show any fund at all !!!

Got temporary error 1218 'Send Buffers overloaded in NDB kernel' from NDBCLUSTER


This is disgusting !!! We seriously need an alternative good API provider for send/receive functionality !!!
OK, understand, and agree we need a backup.  A large portion of the entire Bitcoin network relies on the blockchain.info services.

Just imagine if this happens when the application goes public. User will curse my app and call me a scammer because their coins are sitting in a no man's land !!!

Any idea, how is coinbase API ?
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
Reading between the lines of your question:  were you using the shared send function?

If so go back into your blockchain.info account and go back to the "Shared Coin" page.  At the bottom you will see the following:

Quote
Something went wrong?
When sending a shared coin transaction a number of intermediate addresses are used. If anything interupts the process or an error prevents the transaction from completing the coins may be left in an intermediate address. Click the button below to claim any coins left in intermediate addresses, this process can take several minutes to complete.

Recover Intermediate Addresses

Try pressing the "Recover Intermediate Addresses" button


No... I'm not using shared send function. I am using https://blockchain.info/api/api_receive for an application I'm developing on. A is the user address and C is the admin address. B is the intermediary provided by blockchain.info where my fund is now sitting.

Looks like blockchain.info is now unable to show any fund at all !!!

Got temporary error 1218 'Send Buffers overloaded in NDB kernel' from NDBCLUSTER


This is disgusting !!! We seriously need an alternative good API provider for send/receive functionality !!!
OK, understand, and agree we need a backup.  A large portion of the entire Bitcoin network relies on the blockchain.info services.
legendary
Activity: 2226
Merit: 1052
Reading between the lines of your question:  were you using the shared send function?

If so go back into your blockchain.info account and go back to the "Shared Coin" page.  At the bottom you will see the following:

Quote
Something went wrong?
When sending a shared coin transaction a number of intermediate addresses are used. If anything interupts the process or an error prevents the transaction from completing the coins may be left in an intermediate address. Click the button below to claim any coins left in intermediate addresses, this process can take several minutes to complete.

Recover Intermediate Addresses

Try pressing the "Recover Intermediate Addresses" button


No... I'm not using shared send function. I am using https://blockchain.info/api/api_receive for an application I'm developing on. A is the user address and C is the admin address. B is the intermediary provided by blockchain.info where my fund is now sitting.

Looks like blockchain.info is now unable to show any fund at all !!!

Got temporary error 1218 'Send Buffers overloaded in NDB kernel' from NDBCLUSTER


This is disgusting !!! We seriously need an alternative good API provider for send/receive functionality !!!
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
Reading between the lines of your question:  were you using the shared send function?

If so go back into your blockchain.info account and go back to the "Shared Coin" page.  At the bottom you will see the following:

Quote
Something went wrong?
When sending a shared coin transaction a number of intermediate addresses are used. If anything interupts the process or an error prevents the transaction from completing the coins may be left in an intermediate address. Click the button below to claim any coins left in intermediate addresses, this process can take several minutes to complete.

Recover Intermediate Addresses

Try pressing the "Recover Intermediate Addresses" button
newbie
Activity: 28
Merit: 0
Bitcoin is about beeing patient, so don't wory, it happens
legendary
Activity: 2226
Merit: 1052
Please read and join us in this thread:

https://bitcointalksearch.org/topic/40-minute-btc-block-time-no-big-deal-670431

and perhaps close this redundant thread.

Thanks for pointing out, but I'm having an associated problem here due to block delay. I paid from A to B, which was an autogenerated address by blockchain.info receive API, whereas B was supposed to forward the fund to C. So, naturally I dont have access to B.

A --> B -x-> C

Now, as the Tx from A to B has taken almost 1 and half hour to be included in the block, B is now sitting on my fund without forwarding it to C !!! How can I get my fund out of B now ?
legendary
Activity: 2646
Merit: 1137
All paid signature campaigns should be banned.
Please read and join us in this thread:

https://bitcointalksearch.org/topic/40-minute-btc-block-time-no-big-deal-670431

and perhaps close this redundant thread.
hero member
Activity: 896
Merit: 1000
Sometimes it take a bit longer but some times it only took less than a min  Wink

be patient !
legendary
Activity: 2226
Merit: 1052
Block #308922 => https://blockchain.info/block-index/447956/00000000000000000b1f71cc3f709b2a88fcc1e7482343bbb5291c866eed6c30



Block #308923 => https://blockchain.info/block-index/447957/00000000000000001b2a18b0219f071b49b3f6ff25c891f92b6a992245f40794

I made a Tx which was supposed to get redirected. It took so much time for the first Tx to be included in the block, the redirect wont probably take place  Undecided
Jump to: