BIP 110 signaling is way too vague, who's actually checking the nodes?

[arjen]

Honestly, the signaling for BIP 110 is all over the place and super vague. I’ve looked everywhere, but who’s actually verifying that these nodes are legit? Feels like we’re just guessing support levels without a real audit.

 

[nikolAsss]

I'm not sure what the exact requirements are for BIP 110 signaling but according to the bitcoin wiki, BIP 91 had a minimum block threshold of 75% which I think gave a good indication of network consensus. If it's too vague then maybe they should set a definitive threshold for the number of blocks required before they consider the signaling successful.

 

[Falkona]

I get what you're saying, I was thinking the same thing when I read it. It seems like the BIP 110 signaling process relies on the honor system, hoping that nodes will actually be checking, but what if someone intentionally tries to game the system?

 

[zedavid]

I'm not sure what the solution is, but I think requiring a certain percentage of the network to signal support could make it more meaningful. Right now it's more of an opt-in, which doesn't really give anyone confidence that the change is gonna stick. Maybe it's time to revisit the signaling process and make it more robust.

 

[Пипец]

I gotta agree, BIP 110 is super vague and leaves a lot of room for interpretation. Unless someone's actively monitoring multiple nodes and checking for correct signaling, how can we trust that the right chain is being chosen? I think we need more concrete criteria laid out for this to work effectively.

 

[sasha592142]

I think we're putting the cart before the horse here, BIP 110 was initially created as an optional signalling mechanism, not a strict requirement, so it's not like nodes are really expected to enforce it, they just need to signal that they support it. The real issue is likely just a matter of educating users and node operators on what the signalling means and how to use it effectively. Does anyone know if there are any concrete plans to revisit and refine this BIP in the future?

 

[MMX]

i think this is a pretty valid concern, the lack of clear guidelines on how to implement it is gonna lead to a lot of confusion down the line, maybe we need a separate spec or something.

 

[slavik-killer]

I agree with the OP, BIP 110 does have some ambiguity, but I think the real issue is how many nodes even bother to implement these soft forks in the first place. We all know Bitcoin is heavily reliant on a small pool of high-volume nodes, so even if they're not actively checking, their behavior still affects the network significantly.

 

[volga_34]

BIP 110 is indeed pretty vague and I think that's exactly why some nodes might not be signaling even if the underlying software supports it. I've seen some nodes not catching onto the signaling due to misconfigured or outdated software, which in turn might affect the overall adoption and effectiveness of the signal.

 

[kamm]

I've been thinking the same thing, the current spec is pretty open to interpretation and I'm not sure many nodes are actually checking for the required 900 of 1000 blocks. Has anyone tried reaching out to the devs for clarification or is this something we can test ourselves? Maybe we can get some devs to chime in on this thread and give us a better idea of what's going on.

 

[Ramzi abdi]

I've been digging into this and it seems like only a handful of nodes are actually checking the BIP 110 headers. Most are just blindly relaying the updates without any real verification, which kinda defeats the purpose. Anyone know if there's been any discussion on tightening up the spec to require more stringent node checks?