... he said basically until there is an attack there is no attack ...
AnonyMint, this is, trivially, the case.and he is going to the beach.
...and kept thinking about the problem. Walks help the mind get unstuck. What does geographics have to do with it? Specifics please.
Since you ask about geographics specifics, the way nodes connect to each other cause orphans and "opportunity cost orphans" due to delay. The real world is far from uniform. This is informative for a modelWhat's interesting to me is that he said "roughly", he said "at present time" and said it three months ago. I hardly see how this could still be accurate.
You make sweeping ass-u-me-ptions. Do you actually have your mind deep in the Github commits?
Sorry buddy, seems you're the one making the assumption. I DON'T assume the time interval length is independent from hash rate, etc etc etc. you ASSUME it is independent. Afaics, you've likely got the wrong model, so you aren't seeing anything.
So you answer none of my questions and instead broadly say my model is wrong. Well, that is not an argument.
All models are wrong, but some are useful. If you don't understand this, go deeper into modelling. You assume your model is right. Mine allows for some uncertainty. Certainly black swans are black swans by definition.I didn't change the experiment. You framed the experiment wrong. There aren't 12 gaps, rather there were 4 time intervals of 1 minute. If you have the wrong model, you see noise.
I don't have to consider permutations because there are 2-4 orders-of-magnitude between the probabilities I showed. There is the stratification I am referring to. We could get more analytical, but really isn't necessary.
We will have to agree that this was my model from the beginning, and you have a different model, possibly from the beginning, and then the numbers are not directly comparable. I certainly fail to see why "blocks per minute" is more fundamental than "length of gap". They're certainly inversely proportional. You're just throwing away data.It is quite obvious that we saw a rare event. And no one has shown otherwise yet.
See above for correction. At least an even rarer than that was found with little manual inspection.Block lengths don't exist, there are only timestamps (or the differential, gaps). As smoothie argued, everyone can "manipulate" them because it is not enforced in any way. It is also not very useful to do so.
You ass-u-me that is not a vulnerability. Can you prove it is not?
Barring weird implementation artifacts, timestamps only influence difficulty, thus we're talking strictly about a time warp attack or another difficulty-adjustment-attack. This would be seen in the data. It is true that using the wrong model you might not see the pattern, but I said that the dataset is too small to support you noticing a change or that screenshot being relevant.