Electrum: What does bad-txns-vin-empty mean?

[rpstatic]

Code:

I wanted to test out a segwit wallet on electrum, but when I broadcast a new transaction I get the this error.
[code]
error: {'code': 1, 'message': 'the transaction was rejected by network rules.\n\n16: bad-txns-vin-empty

Steps to reproduce
1. Create new segwit wallet with electrum
2. Send funds to an andress from this wallet
3. Send funds from this address

What does this error mean and how can I fix it?[/code]

[AdolfinWolf]

Code:

I wanted to test out a segwit wallet on electrum, but when I broadcast a new transaction I get the this error.
[code]
error: {'code': 1, 'message': 'the transaction was rejected by network rules.\n\n16: bad-txns-vin-empty

Steps to reproduce
1. Create new segwit wallet with electrum
2. Send funds to an andress from this wallet
3. Send funds from this address

What does this error mean and how can I fix it?[/code]

I think the error here in this case is related to you trying to spend coins with a segwit scrip/adress, while the wallet/server you are using doesn't recognize the script, and is thus unable to broadcast it.

Which is pretty weird, considering i also use Electrum segwit and never had any issues.

Try switching electrum servers, see if that does anything?

See https://bitcoin.stackexchange.com/questions/75942/16-bad-txns-vin-empty-code-26/75944

[rpstatic]

I think the error is related to you trying to spend coins with a segwit scrip/adress, while the wallet/server you are using doesn't recognize the script, and is thus unable to broadcast it.

Which is pretty weird, considering i also use Electrum segwit and never had any issues.

Try switching electrum servers, see if that does anything?

https://bitcoin.stackexchange.com/questions/75942/16-bad-txns-vin-empty-code-26/75944

Thank you! Switching the server worked and I was able to broadcast the transaction.

[HCP]

Seems like either the server you were connected to was non-SegWit compatible (possibly an old version of Bitcoin Core or ElectrumX etc)... or it was out of sync.

Either way, good to see you managed to get it working.