I think I found an unexpected problem with the most liquid B...

npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399s
hex
fe55adb01d0b12554fbe9681c5ceda18411490e70775723f4d131b0b7314528cnevent
nevent1qqs0u4ddkqwskyj4f7lfdqw9emdpssg5jrnswatj8ax3xxctwv299rqprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgszrqlfgavys8g0zf8mmy79dn92ghn723wwawx49py0nqjn7jtmjaggv3jsfKind-1 (TextNote)
I think I found an unexpected problem with the most liquid BIP110 prediction market.

It defines the "Yes" condition based on a mix of timestamp ("11:59:59 PM") and blockheight ("the BIP-110 activation point"). But since those are not always in sync on bitcoin, there's a chance that we simply haven't reached that blockheight yet when we reach the timestamp when the measurement is supposed to happen.
In that case, the Yes condition would obtain unexpectedly: if we are only at block 965660 at the timestamp, instead of 965664, then -- at the time of measurement -- there won't be any "blocks that violate BIP-110 constraints" from BIP-110's activation height forward...but only because we haven't reached that blockheight yet.
So a person who thinks BIP110 won't activate might find it reasonable to bet Yes anyway, because even if BIP110 never gets enforced, you can still win if blocks just get slower than we currently expect them to.
Link to the market: https://beta.predyx.com/market/will-bip-110-activate-and-be-enforced-on-bitcoin-by-sept-1-2026-1770282509
Click "Show More" under "Description" to see what I mean.
原始 JSON
{
"kind": 1,
"id": "fe55adb01d0b12554fbe9681c5ceda18411490e70775723f4d131b0b7314528c",
"pubkey": "2183e94758481d0f124fbd93c56ccaa45e7e545ceeb8d52848f98253f497b975",
"created_at": 1772132966,
"tags": [
[
"imeta",
"url https://image.nostr.build/2025d3ab7d0976ce8ec496f467342dd4fb729fa72e0edfdbaffbd125e6005c0c.jpg",
"ox 2025d3ab7d0976ce8ec496f467342dd4fb729fa72e0edfdbaffbd125e6005c0c",
"x f1612f4036c364c8270568102ae799d7a3059b00d99bb42244db6157bfb5a4c3",
"m image/jpeg",
"dim 675x237",
"bh L38||AtStQ~j07IaIcN2D+-+%IIa",
"blurhash L38||AtStQ~j07IaIcN2D+-+%IIa",
"thumb https://image.nostr.build/thumb/2025d3ab7d0976ce8ec496f467342dd4fb729fa72e0edfdbaffbd125e6005c0c.jpg"
]
],
"content": "I think I found an unexpected problem with the most liquid BIP110 prediction market.\n\nhttps://image.nostr.build/2025d3ab7d0976ce8ec496f467342dd4fb729fa72e0edfdbaffbd125e6005c0c.jpg\n\nIt defines the \"Yes\" condition based on a mix of timestamp (\"11:59:59 PM\") and blockheight (\"the BIP-110 activation point\"). But since those are not always in sync on bitcoin, there's a chance that we simply haven't reached that blockheight yet when we reach the timestamp when the measurement is supposed to happen.\n\nIn that case, the Yes condition would obtain unexpectedly: if we are only at block 965660 at the timestamp, instead of 965664, then -- at the time of measurement -- there won't be any \"blocks that violate BIP-110 constraints\" from BIP-110's activation height forward...but only because we haven't reached that blockheight yet.\n\nSo a person who thinks BIP110 won't activate might find it reasonable to bet Yes anyway, because even if BIP110 never gets enforced, you can still win if blocks just get slower than we currently expect them to.\n\nLink to the market: https://beta.predyx.com/market/will-bip-110-activate-and-be-enforced-on-bitcoin-by-sept-1-2026-1770282509\n\nClick \"Show More\" under \"Description\" to see what I mean.",
"sig": "2ab4d7908e2e265d1cbb73de73734099f438930f51c7ae3dbdda5cef44ec59b867231a2092a4ac2b51c348d2839a9972a27aa78e9e162350888ab9182ee0558e"
}