I usually connect to a recognisable server. It's easier to spot as when I start with electrum there were probably about 8 servers.
I have noticed the servers going slower I got bored waiting and just started importing transaction hashes from. File.
I have a bech32 address that I use to send to my bech32 multisig cold storage and that works fine. If bech32 to bech32 didn't work then we wouldn't be using it as electrum. Then can't handle change.
Topic: Strange error when broadcasting:bad-txns-vin-empty 3.3.4 (Read 173 times)
Ah, so it is some kind of server issue perhaps, wasn't aware of DDOS going on. I did realise syncing was taking longer than usual the past few days but I usually assume it's just my internet. I have it on to auto but after my issue I manually selected a joechen hoenicke server (which broadcast my tx fine).
that linked thread is quite old and SegWit has been around for over a year now and every server has to have upgraded already. but i am very curious to know what you mean by a "rare tx" though. do you mean rare just because it was using bech32 addresses or did it include some special OP codes that are not regularly used (non-standard maybe)?
That's what I thought, a year ago, but that's why I thought maybe it was native SW. What I meant by rare is for myself, native-to-native.
I still generally am spending to non-bech32 addresses, though mostly Segwit. I'd say over 95% are non-bech32, maybe even less if I don't count my own consolidations of own wallets. Receiving-wise, even worse, I only have the 1 sender who's on it.
~ It WAS a rare bech32 to bech32 tx though, maybe that's it?
that linked thread is quite old and SegWit has been around for over a year now and every server has to have upgraded already. but i am very curious to know what you mean by a "rare tx" though. do you mean rare just because it was using bech32 addresses or did it include some special OP codes that are not regularly used (non-standard maybe)?
That's what I thought, a year ago, but that's why I thought maybe it was native SW. What I meant by rare is for myself, native-to-native.
I still generally am spending to non-bech32 addresses, though mostly Segwit. I'd say over 95% are non-bech32, maybe even less if I don't count my own consolidations of own wallets. Receiving-wise, even worse, I only have the 1 sender who's on it.
~ It WAS a rare bech32 to bech32 tx though, maybe that's it?
that linked thread is quite old and SegWit has been around for over a year now and every server has to have upgraded already. but i am very curious to know what you mean by a "rare tx" though. do you mean rare just because it was using bech32 addresses or did it include some special OP codes that are not regularly used (non-standard maybe)?
I wouldn't mind being able to get that far, heh. I've not had much luck even connecting to servers in the new 3.3.4 release. I tried at least 10 different ones. The circle in the corner stays red. How long should it take before it starts synchronising?
Straight away. If it doesn't do that keep switching. Servers are being heavily ddosed because the phishing vulnerability has created an incentive for scammers to control which server you connect to. It's turned into a war!
I've not had much luck even connecting to servers in the new 3.3.4 release. I tried at least 10 different ones. The circle in the corner stays red. How long should it take before it starts synchronising?
I just try open my Electrum (3.3.4) to see if there is some problem with sync, and it take less then 5 seconds for full sync which is in my case almost common thing. I have set server to automatic, did you try to do that or you check them manually? Maybe you just have bad luck, but if 10 servers is not working for you, maybe you should check your antivirus / firewall settings.
In case you for some reason delete Electrum data folder, sync time can be a bit longer than usual because it is necessary to download blockchain_headers file (size 40+MB).
I wouldn't mind being able to get that far, heh. I've not had much luck even connecting to servers in the new 3.3.4 release. I tried at least 10 different ones. The circle in the corner stays red. How long should it take before it starts synchronising?
If I get that bit sorted, then I can try a bech32-to-bech32 transaction to see if I can reproduce the issue.
If I get that bit sorted, then I can try a bech32-to-bech32 transaction to see if I can reproduce the issue.
Referencing this thread,I've resolved this, by changing servers, but I had to change a second time to a third server, because even the 2nd server was displaying the same error when I tried to broadcast.
In my transaction list I also saw a tag marked Local which I guess meant it hadn't been broadcasted. Linked thread above suggests it's to-do with non SW compatible servers.
I should have taken down the names of the 2 servers to see if anyone could confirm but I can't recall of course. Just curious why I'd get this error now for the first time. It WAS a rare bech32 to bech32 tx though, maybe that's it?
In my transaction list I also saw a tag marked Local which I guess meant it hadn't been broadcasted. Linked thread above suggests it's to-do with non SW compatible servers.
I should have taken down the names of the 2 servers to see if anyone could confirm but I can't recall of course. Just curious why I'd get this error now for the first time. It WAS a rare bech32 to bech32 tx though, maybe that's it?
Jump to: