nice animation by organofcorti, fee (btc/KB) against time
http://organofcorti.blogspot.it/2016/03/block-size-and-transaction-fee-animation.html?m=1
http://organofcorti.blogspot.it/2016/03/block-size-and-transaction-fee-animation.html?m=1
Could this be a "sucking down the blockchain from various nodes" attack, I wonder?
Trying to bust peoples' bandwidth limits?
I have 3 nodes. It only happened on one. Ramped to a 12 hour sustained ~130Mbs then dropped to normal again.was the bandwidth spike across many nodes, or just a few?
[doublepost=1457634917][/doublepost]can someone give a short summary on segwit, its expected timeframe and is it really what it looks like? Having some blackbox of bits external to the blockchain to make updating the blockchain state more difficult for all the independent core devs?
Expected. The bull bucks hardest for the bulls.Lots of despondency here.
If people want to sell, then do it, but keep watching, keep an open mind and some ready fiat to re-buy later. This is definitely not the time to throw in the towel and walk away.
No, just the Blockstream folk.Did people miss the fact that there are solutions to scale bitcoin onchain?
ok, it wasnt iguana then. I was inadvertently testing with just 2 peers for a while and it was only doing 30MB/sec.I have 3 nodes. It only happened on one. Ramped to a 12 hour sustained ~130Mbs then dropped to normal again.
Just eyeballing the percentage change it looks like Core 0.11.2 and 0.12.0 on Jan 28th have lost just 0.6% of market share between then and March 9th.Theres this idea that the classic node count is a cannibalisation of XT and not really indicative of people converting core nodes. This has been bugging me for a while. Tonight I though I'm just going to do a quick check on the figures.
This idea has been based on the node counts. I thought what would happen if you looked at the relative distribution?
It just so happens that 21.co already put things in percentages and strip out the trash!
What you are looking at here *is* cannibalisation of core.
Jan 28th: 64% Core / 36% other
Today: 54% Core / 25% Classic / 21% Other
"The wind of change blows straight into the face of time"
You know what would be a good business plan?"But Greg, what about that money? Hill and PWC will want a return. We have to do something. We have to keep going. Let's burn all the monies! At least we can say we tried."
Bitnodes keeps 90 days worth of data, including IPs. I ran an analysis a while back to see what was going on with conversions. I'll pull some fresh data and run it again.Theres this idea that the classic node count is a cannibalisation of XT and not really indicative of people converting core nodes. This has been bugging me for a while. Tonight I though I'm just going to do a quick check on the figures.
Surely a script which follows the log and does some iptables magic would be the thing to do?Standard debug.log for bitcoin not really giving anything away afaict some peer connections from "Why? Because FU thats why" but not massive amounts
I take the same view I do with cold callers. If I can keep them tied up wasting their time, it stops them moving on to the next target and hurts their "bottom line"Bitnodes keeps 90 days worth of data, including IPs. I ran an analysis a while back to see what was going on with conversions. I'll pull some fresh data and run it again.
[doublepost=1457648967][/doublepost]
Surely a script which follows the log and does some iptables magic would be the thing to do?