some nodes are more relax on rules and recommendations than others.
one hurdle passed.
just because blockcypher accepts, doesn't mean others will.
here's another set to try with.
https://testnet.blockchain.info/pushtx
https://testnet.blockchain.info/decode-tx
Topic: Failing to send a testnet transaction manually (Read 157 times)
Thank you! That's a great tool.
It turned out that my transaction was dropped with "alert: fee too high" (which is quite strange).
I changed the transaction and broadcasted it via blockcypher, however it wasn't processed for a long time and I can't find it in other testnet explorers.
What could be the reason for that?
The transaction is https://live.blockcypher.com/btc-testnet/tx/77e0516a009a7f4a0a53846e287e06303f111c5d488d24b472430330b4a15921/
Thank you.
It turned out that my transaction was dropped with "alert: fee too high" (which is quite strange).
I changed the transaction and broadcasted it via blockcypher, however it wasn't processed for a long time and I can't find it in other testnet explorers.
What could be the reason for that?
The transaction is https://live.blockcypher.com/btc-testnet/tx/77e0516a009a7f4a0a53846e287e06303f111c5d488d24b472430330b4a15921/
Thank you.
send your transaction through here to make sure it's sane:
https://live.blockcypher.com/btc-testnet/pushtx/
https://live.blockcypher.com/btc-testnet/decodetx/
sometimes it will give you the clues you need.
https://live.blockcypher.com/btc-testnet/pushtx/
https://live.blockcypher.com/btc-testnet/decodetx/
sometimes it will give you the clues you need.
I use Ken Shirriff's great post on how to manually create and send a transaction: http://www.righto.com/2014/02/bitcoins-hard-way-using-raw-bitcoin.html
As in the blog post, I use version 60002 of the protocol. I adjusted it to work with testnet. AFAIK after adjusting to the testnet addresses, no further adjustments should be made in the tx creation and signature process.
However, my transaction is not processed...
I successfully connect to peer 185.28.76.179:18333, send version and receive verack, send the transaction but... nothing happens. What should I do to figure this out? My code verifies the signatures and everything seems fine. How can I figure out where I'm wrong?
Here is the raw tx:
010000000142ad1ac9d0214d326a9f5f4e0051bb6f0e197bb7bf0661266623f865a1a38d1000000 0008b4830450221008e434d7e6e0dc3741d99142b1fdb3a6eeba7a6d1d1e95e1aa90dcb638fc17c 7b0220179a9004bac06ac64914af1e9f29db3a7cb50942bf3e865a23727151f3bbd6330141047bc 52c13eacc1adcb1eea06317760537947d67a9208351e4c213bed82f0ce843249c9675e5f28ca4b0 848036118a43defa8b6c5d5d77250ac8709eca8f88e30bffffffff017b000000000000001976a91 49437a39c0ddd64205002c3f9adda6bb77df1be8288ac00000000
Thanks!
As in the blog post, I use version 60002 of the protocol. I adjusted it to work with testnet. AFAIK after adjusting to the testnet addresses, no further adjustments should be made in the tx creation and signature process.
However, my transaction is not processed...
I successfully connect to peer 185.28.76.179:18333, send version and receive verack, send the transaction but... nothing happens. What should I do to figure this out? My code verifies the signatures and everything seems fine. How can I figure out where I'm wrong?
Here is the raw tx:
010000000142ad1ac9d0214d326a9f5f4e0051bb6f0e197bb7bf0661266623f865a1a38d1000000 0008b4830450221008e434d7e6e0dc3741d99142b1fdb3a6eeba7a6d1d1e95e1aa90dcb638fc17c 7b0220179a9004bac06ac64914af1e9f29db3a7cb50942bf3e865a23727151f3bbd6330141047bc 52c13eacc1adcb1eea06317760537947d67a9208351e4c213bed82f0ce843249c9675e5f28ca4b0 848036118a43defa8b6c5d5d77250ac8709eca8f88e30bffffffff017b000000000000001976a91 49437a39c0ddd64205002c3f9adda6bb77df1be8288ac00000000
Thanks!
Jump to: