bad-txns-vin-empty on segwit tx

[ghost]

I can take an encoding like below and have it decoded and transmitted on other sites such as https://testnet.blockchain.info/pushtx

But on blockexplorer.com (which uses insight) and https://test-insight.bitpay.com/tx/send, I get this error:

An error occured:
16: bad-txns-vin-empty. Code:-26

Encoded TX Hex:

010000000001015893c7eed9c723ba4bc50c1726c3e0b5aef3a6cd787a247916138347fe82344900000000171600149eaf55b34115e90bf4f9c4da69ab89e288dfea6effffffff02e0e7de030000000017a914ddad7d22cf51d12476cb4887d966d112377e57ba870000000000000000226a20c65c6184e3d5a945ddb5437e93ea312411fd33aa1def22b0746d6ecd4aa30f200247304402202f245b4b429920456864becbc6ce7786ac51cf38b455840219c0c80aba91296d02201bdc3996a2720a0122089ceb3d23cf90b78b5a44fd3080f6f0818f585368756c01210266bb8bbbfca4b02eb66577d4033e8af11f287b8d33c3de9b24bc8faabd37b20d00000000

Note that I've already transmitted this transaction, after it wouldn't work on insight, with blockchain.info

[bendelo]

I have the same issue trying to broadcast SegWit

[rmn-boiko]

Any luck? Have the same issue? Will it be improve to support segwit inputs?

[lacksfish]

I am also currently facing this issue when trying to publishing a transaction with a segwit input (and a normal p2sh input).

[afk11]

The bitcore node seems to only support v0.12, which is why it doesn't recognize the segwit version bits being locked in.

@Soyoudie Trezor dropped insight as it's API recently.. No point relying on bitpay any more. Their OSS software has been struggling since 2016.

[festus1973]

@afk11 Hey there, I'm basically abandoning Insight due to lack of SegWit support but before recoding for another API, just wanted to check in with you and make there wasn't come SegWit/Bech32 capability right around the corner (e.g. within next couple weeks or so).

Kind of a shame. It was a nice API but they just sort of let it drift into obsolescence for some reason. Similar downward path for BlockCypher. BlockChair seems solid, also looking at chain.so and btc.com. Any others you'd recommend ?

[lacksfish]

Depending on which type of data you need, you might find what you are looking for in electrum nodes?

https://electrumx.readthedocs.io/en/latest/protocol-methods.html

You could do something like this project to interface with the electrum nodes via TLS sockets to get data from them. There are very little alternatives for some of the functionality provided by electrum.

[matiu]

The current Bitcore runs on top of the latest bitcoin core.

…

On Mon, Jan 14, 2019, 8:00 PM lacksfish ***@***.*** wrote: Depending on which type of data you need, you might find what you are looking for in electrum nodes? https://electrumx.readthedocs.io/en/latest/protocol-methods.html You could do something [ https://github.com/btccom/wallet-recovery-data-bridge](like this project) to interface with the electrum nodes via TLS sockets to get data from them. There are very little alternatives for some of the functionality provided by electrum. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#924 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGCHP4ocTzfMMPRzlvNc0D_kd_tOSg2ks5vDQwggaJpZM4TmK3w> .