I’m genuinely curious about the issue with dice rolls. Are you saying it’s an opsec issue or an entropy issue? Assuming the goal is to generate a minimum of 128 bits worth of entropy.

I think you’re missing my point. I’m saying, regardless of what the hashers of foundry do or don’t vote for, foundry have made it clear that they are willing to run bip110 (with the caveat that this info is true)
Ultimately if the hashes decide against bip110 the decision still rests with foundry, who to reiterate are obviously neutral on bip110 for them to be giving the courtesy to their hashes.

If foundry were against it, wouldn’t it make sense for them to not offer the option at all? Foundry ultimately gets to choose.
Assuming this is real, the fact that they have offered the choice to its hashers means they are willing to run bip110. This means they must have tested a node implementation that enforces bip110. To me this doesn’t sound like opposition, it sounds like neutrality. A neutral party to bip110 will always run bip110 if it becomes clear that opposing it is becoming increasingly riskier.

This is a ~100kb image, give or take the extra metadata added by iPhotos. 100kb seems sufficient to get a high enough level of detail.

Has core lost your support as well?

Yeah so he was right about the sync time using assumevalid as 0.
However most users probably won’t go to the terminal and manually set this to 0. Conversely, by skipping validation of some scripts I guess there is very small but nonetheless present risk your node accepts a script relating to a historically invalid transaction. I can’t testify as to how much of an issue this is, but is probably one of those things where if you set assumeValid to 0 you can never be 100% sure the synced chain is completely accurate.
Either way I’d still say he’s missing the bigger picture.

I’m going to assume he’s being honest, but he’s missing the bigger picture, which is, clearly people are pointing out that IBD greatly slows when it gets to about 2023. His argument seems to be it “it was fine for me so it’s not a problem”.
From my point of view I know that the 2 times I attempted to IBD on my older laptop, the first took about a month and the second time I had to give up on, because it completely stalled, (had to resync cause I accidentally corrupted the data).
It’s pretty clear to me that from my experience and from hearing other people’s experiences that IBD on older or less powerful machines is an issue especially for node adoption.
Maybe other factors such as internet bandwidth and proximity to the nodes bootstrapping yours has a great effect on IBD. However on the more powerful machine I bought, with the same internet bandwidth and proximity other nodes it took just over 2 days. This is obviously greatly reduced from 1 month, suggesting in my case at least, hardware was the greater bottle neck.

Your response tacitly acknowledges that you think there should be no more forks / updates / fixes, and that bitcoin should ossify.

Arbitrary data has definitely disrupted the usage of bitcoin as money over the last 3 years. Have you tried syncing a node recently on an older but still fairly capable laptop. Syncs very fast until about 70%, then completely hits a wall, with an estimated time to finish of over a year. This forced me to spend $800 on a more powerful machine.

I suspect that most people will turn away from that and therefore a lesser ratio of people using bitcoin will run nodes. This does not just disrupt bitcoin as money, but also disrupts bitcoin as a decentralised network.

Maybe the state does have jurisdiction of the child’s rights and property? Maybe upon mother and father signing the birth certificate, this transfers the child’s rights and property into estate administered by the state, where the state acts as the lawfully appointed trustee who acts to “benefit” the beneficiary (child).
We assume the birth certificate is the record of the birth of a new born, but maybe it’s recording the birth of an estate under name of the surname.
In this case the parents do have a limited authority over the child only because the state grants it. The state as the lawful administer / trustee appoints mother and father to look after the new born under the name “parents”, but parents must follow the rules the state sets.
I would argue parents are different and distinct from mother and father.
Just a thought experiment.

Yeah fair enough. I guess whether it depends on Luke isn’t as relevant anymore as bip 110 is out there now and can be ran and audited.
To the point of it being temporary, I can see that if it worked flawlessly then yes it doesn’t make sense for it to be temporary, but because of the unseen issues in past soft forks I do see the value in it being temporary. Only time will tell if there are any unseen issues with it.
From my point of view I accept that maybe bip 110 isn’t perfect in its design or release schedule, but I agree with the direction it takes bitcoin if it succeeds, and since currently I can see no better alternative I give it my support.

I guess my question to you is, do you not support bip 110 because you oppose what it proposes, or do you not support it because you don’t think it will succeed? I believe there is an important difference.