📅 Original date posted:2017-02-02
📝 Original message:Currently in order to signal support for changes to Bitcoin, only miners are able to do so on the blockchain through BIP9.
One criticism is that the rest of the community is not able to participate in consensus, and other methods of assessing community support are fuzzy and easily manipulated through Sybil.
I was trying to think if there was a way community support could be signaled through transactions without requiring a hard fork, and without increasing the size of transactions at all.
My solution is basically inspired by hashcash and vanity addresses.
The output address of a transaction could basically have the last 4 characters used to signal support for a particular proposal.
To generate an address with 4 consecutive case-insensitive characters should be roughly 34^4 which is just over a million attempts. On typical hardware this should take less than a second.
An example bitcoin address that wanted to support the core roadmap might be:
1CLNgjuu8s51umTA76Zi8v6EdvDp8qCorE
or to signal support for a big block proposal might be:
1N62SRhBioRFrigS5eJ8kR1WYcfcYr16mB
Popularity could be measured weighted by fee paid per voting kb.
Issues are that this could lead to transactions been censored by particular miners for political reasons. Also miners might attempt to manipulate the results by stuffing their block with 'fake' transactions. Such attempts could be identified if a large number of voting transactions were not in the mempool.
Despite the limitations, I believe this offers a very accessible way to immediately allow the entire economic community to signal their support within transactions. The only cost is that of a tiny hashing PoW that should tie up a CPU for a barely noticeable amount of time, and could be implemented relatively easily into wallet software.
For its weaknesses, surely it is better than the existing methods we use to assess support from the wider economic community?
While it could just be used for signaling support and giving users a 'voice' on chain, if considered effective it could also be used to activate changes in the future.
Any thoughts welcome.
Thanks,
John Hardy
john at seebitcoin.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170203/1916d1f2/attachment-0001.html>;
John Hardy [ARCHIVE] /
npub15f…get3u
2023-06-07 17:55:59
in reply to nevent1q…nx4h
Author Public Key
npub15fe6jcj3a2vykwk9tshyjc47s4q0t7jza444dnffcympur2v7myq6get3uPublished at
2023-06-07 17:55:59Event JSON
{
"id": "04e1d0cf0c9d5850071ec17b327f5d016c55616ecb9886d25b4629a27eb2d809",
"pubkey": "a273a96251ea984b3ac55c2e4962be8540f5fa42ed6b56cd29c1361e0d4cf6c8",
"created_at": 1686160559,
"kind": 1,
"tags": [
[
"e",
"d64d4e4c8c69e37ecd4e578182cd4c185e4757a74a5764eac7b919a01860003f",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2017-02-02\n📝 Original message:Currently in order to signal support for changes to Bitcoin, only miners are able to do so on the blockchain through BIP9.\n\n\nOne criticism is that the rest of the community is not able to participate in consensus, and other methods of assessing community support are fuzzy and easily manipulated through Sybil.\n\n\nI was trying to think if there was a way community support could be signaled through transactions without requiring a hard fork, and without increasing the size of transactions at all.\n\n\nMy solution is basically inspired by hashcash and vanity addresses.\n\n\nThe output address of a transaction could basically have the last 4 characters used to signal support for a particular proposal.\n\nTo generate an address with 4 consecutive case-insensitive characters should be roughly 34^4 which is just over a million attempts. On typical hardware this should take less than a second.\n\nAn example bitcoin address that wanted to support the core roadmap might be:\n\n1CLNgjuu8s51umTA76Zi8v6EdvDp8qCorE\n\n\nor to signal support for a big block proposal might be:\n\n1N62SRhBioRFrigS5eJ8kR1WYcfcYr16mB\n\n\nPopularity could be measured weighted by fee paid per voting kb.\n\n\nIssues are that this could lead to transactions been censored by particular miners for political reasons. Also miners might attempt to manipulate the results by stuffing their block with 'fake' transactions. Such attempts could be identified if a large number of voting transactions were not in the mempool.\n\n\nDespite the limitations, I believe this offers a very accessible way to immediately allow the entire economic community to signal their support within transactions. The only cost is that of a tiny hashing PoW that should tie up a CPU for a barely noticeable amount of time, and could be implemented relatively easily into wallet software.\n\n\nFor its weaknesses, surely it is better than the existing methods we use to assess support from the wider economic community?\n\n\nWhile it could just be used for signaling support and giving users a 'voice' on chain, if considered effective it could also be used to activate changes in the future.\n\n\nAny thoughts welcome.\n\n\nThanks,\n\n\nJohn Hardy\n\njohn at seebitcoin.com\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170203/1916d1f2/attachment-0001.html\u003e",
"sig": "70bffd7a71d9f64ab8cd056cd8d0b371d22fe8fe730a52ce13c1c98621c8dc105189b8005d7e2507f55895f35fee5c67271b39c0b28fff35cab655fb402b77d0"
}