NO it doesn't work
You need to elaborate
Topic: "node is offline, cannot broadcast" - paging goatpig (Read 560 times)
Did you warn people not to upgrade to 0.15.0.1?
0.96.4 has a fix for that.
Did you warn people not to upgrade to 0.15.0.1?
0.96.4 has a fix for that.
I use https://bitcoinfees.21.co and pick a fee in the green zone, to be safe. It this overkill?
I believe so. In my case, I ran Core 0.15.0.1 and was given a suggested fee/byte. I recalled hearing some people say that various factors were tilting the fees:
- The mempool is mostly clear these days. (Some people went elsewhere, some attackers gave up after they realized they were pissing away their money, etc.)
- Companies like Coinbase, who are behind a lot of the transactions, haven't upgraded to SegWit and haven't changed their fees. So, you see a lot of fees that are way too high.
- In recent days, I've heard that the mempool has gone back up somewhat. I believe there's a website somewhere with more recent info. I can't find it offhand, sadly.
If you don't mind playing with Armory a bit and aren't in a hurry, you can always use RBF and play with the fees a bit. I started at 10 sat/byte and would've bumped it up if, say, an hour had gone by without any confirmations. It cleared immediately. Maybe I got lucky. In any event, play with what Core recommends. I've only used it a couple of times but both times have seen the recommended fee still be too high. At least it was suggesting 20 and not 200.
If your node is offline, you want to look at that. 0.96.2 is compatible with 0.15, it's 0.15.1 that doesn't work with anything but 0.96.4.
At any rate, can't help you without log files.
At any rate, can't help you without log files.
Downgrading from 0.15.0.1 to 0.15 did the trick. (It also fixed the ArmoryDB-not-automatically-exiting problem.)
Did you warn people not to upgrade to 0.15.0.1?
If your node is offline, you want to look at that. 0.96.2 is compatible with 0.15, it's 0.15.1 that doesn't work with anything but 0.96.4.
At any rate, can't help you without log files.
At any rate, can't help you without log files.
I tried the 0.96 signer too. I also tried going back to standard mode.
Nothing works.
So now my BTCs are stuck...
Is there any reason to believe 0.96.4 RC1 would fix this problem? (I ask because I only run binaries I compile and it's a bit of hassle to compile.)
I'll think carefully before upgrading Bitcoin Core from now on! Especially if it's not backwards compatible like 0.14 -> 0.15 in terms of blockchain data. My bad...
Nothing works.
So now my BTCs are stuck...
Is there any reason to believe 0.96.4 RC1 would fix this problem? (I ask because I only run binaries I compile and it's a bit of hassle to compile.)
I'll think carefully before upgrading Bitcoin Core from now on! Especially if it's not backwards compatible like 0.14 -> 0.15 in terms of blockchain data. My bad...
It suggests I raise my fee, but my fees are already at 300 satoshi / byte - really high.
FYI, I sent a transaction a couple of days ago for 10 satoshis/byte. It was accepted almost immediately. I'm pretty sure you could bump it down to 5, especially on a weekend. Unless there was a crazy spike in the mempool, there's no reason whatsoever to do 100 satoshis/byte, much less 300.
As for the problem, I don't know if I can speak to it. Are you running 0.15 or 0.15.0.1?
I use https://bitcoinfees.21.co and pick a fee in the green zone, to be safe. It this overkill?
I'm running 0.15.0.1.
It suggests I raise my fee, but my fees are already at 300 satoshi / byte - really high.
FYI, I sent a transaction a couple of days ago for 10 satoshis/byte. It was accepted almost immediately. I'm pretty sure you could bump it down to 5, especially on a weekend. Unless there was a crazy spike in the mempool, there's no reason whatsoever to do 100 satoshis/byte, much less 300.
As for the problem, I don't know if I can speak to it. Are you running 0.15 or 0.15.0.1?
When I try to send BTC, I get an "node is offline, cannot broadcast".
It suggests I raise my fee, but my fees are already at 300 satoshi / byte - really high.
I keep getting this error and I tried multiple times.
I have Armory 0.96.2. I'm running Bitcoin Core 0.15 in the background and Armory Dashboard shows I'm online.
One idea:
I'm in Expert mode and I let Armory choose the signer for me. Could it be choosing the BCH signer by default? I wonder if it's doing that because the last signer I manually picked was BCH when I was dumping my Bcash. In this case, which signer should I manually pick instead?
It suggests I raise my fee, but my fees are already at 300 satoshi / byte - really high.
I keep getting this error and I tried multiple times.
I have Armory 0.96.2. I'm running Bitcoin Core 0.15 in the background and Armory Dashboard shows I'm online.
One idea:
I'm in Expert mode and I let Armory choose the signer for me. Could it be choosing the BCH signer by default? I wonder if it's doing that because the last signer I manually picked was BCH when I was dumping my Bcash. In this case, which signer should I manually pick instead?
Jump to: