Could you please explain why this is correct?
From the way I’m reading BIP 301:
https://github.com/bitcoin/bips/blob/master/bip-0301.mediawiki#user-content-Specification
… it appears that only miners care about these messages being exchanged.
From the section “Backwards Compatibility”:
“As a soft fork, older software will continue to operate without modification. To enforce BMM trustlessly, nodes must watch "pairs" of transactions, and subject them to extra rules. Non-upgraded nodes will notice that this activity is present in the blockchain, but they will not understand any of it.”
So imagine that most miners upgrade but the rest of us run “older software”. We’re not miners so we don’t care about these messages (or even understand the message content).
So, how is it true that nodes running older software will enforce or prevent this soft fork? It seems to me that only miners need to upgrade to activate it because only they have a need to know what this data means.
Think of it another way. Since this is only messages being exchanged by miners, then they could use op_return to pass messages to each other. The data inserted n the blockchain would be unreadable to the rest of us. How could we prevent a private group from passing messages to each other using the base chain?
What am I missing? How is it impossible to covertly enable drivechains?
techfeudalist /
npub1nz…0yxqu
2023-08-17 03:30:48
in reply to nevent1q…xzu6
Author Public Key
npub1nz3cd3mx4jf9paxwrdgqvchaprjdge9pj9t58mkusw74q5saajkqu0yxquPublished at
2023-08-17 03:30:48Event JSON
{
"id": "a30d0e6211e650392dd04702edcf54b0591ee10af6f0ae00c2ee5a5f175c8d05",
"pubkey": "98a386c766ac9250f4ce1b500662fd08e4d464a1915743eedc83bd50521decac",
"created_at": 1692243048,
"kind": 1,
"tags": [
[
"e",
"bab97be31ae39cab24a2ad4da9ac6fa0ca75c976e6ad22e9354ee37d1c2aae59",
""
],
[
"e",
"f5d367982c00ee2635b1713132ddf9fef5bc83351b0b9b3e62b73060479879af"
],
[
"p",
"fdd5e8f6ae0db817be0b71da20498c1806968d8a6459559c249f322fa73464a7"
],
[
"p",
"21b419102da8fc0ba90484aec934bf55b7abcf75eedb39124e8d75e491f41a5e"
]
],
"content": "Could you please explain why this is correct?\n\nFrom the way I’m reading BIP 301:\n\nhttps://github.com/bitcoin/bips/blob/master/bip-0301.mediawiki#user-content-Specification\n\n… it appears that only miners care about these messages being exchanged. \n\nFrom the section “Backwards Compatibility”:\n\n“As a soft fork, older software will continue to operate without modification. To enforce BMM trustlessly, nodes must watch \"pairs\" of transactions, and subject them to extra rules. Non-upgraded nodes will notice that this activity is present in the blockchain, but they will not understand any of it.”\n\nSo imagine that most miners upgrade but the rest of us run “older software”. We’re not miners so we don’t care about these messages (or even understand the message content). \n\nSo, how is it true that nodes running older software will enforce or prevent this soft fork? It seems to me that only miners need to upgrade to activate it because only they have a need to know what this data means. \n\nThink of it another way. Since this is only messages being exchanged by miners, then they could use op_return to pass messages to each other. The data inserted n the blockchain would be unreadable to the rest of us. How could we prevent a private group from passing messages to each other using the base chain? \n\nWhat am I missing? How is it impossible to covertly enable drivechains?",
"sig": "1a5890ea35cb82aebd15600f8fde564a9a8fea1203807469ce81b8c78eec4398b568a67fa3ff9b9525f9090c285d3983fa4085530c775bbfb7204ea0e913007b"
}