📅 Original date posted:2017-10-06
📝 Original message:There have been some other proposals to deal with this such as
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2012-June/001506.html
that may be possible to implement in existing miners.
On Tue, Oct 3, 2017 at 9:52 AM, 潘志彪 via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> Here is a solution may solve Block Withholding Attack. The general idea is
> came from Aviv Zohar(avivz at cs.huji.ac.il), I made it work for Bitcoin.
> Anyway, thanks Aviv.
>
> =====================
>
> DIFF_1 = 0x00000000FFFF0000000000000000000000000000000000000000000000000000;
>
> Diff = DIFF_1 / target
>
> this is equal to
>
> Diff = DIFF_1 / (target - 0) or Diff = DIFF_1 / abs(target - 0)
>
> now, we change diff algo to below:
>
> New_Diff = DIFF_1 / abs(target - offset)
>
> Offset is 32 bytes, like uint256 in Bitcoin, range is [0, 2^256),
> define: offset_hash = DSHA256(offset).
>
> we need to do a little change to the merkle root hash algo, put the
> offset_hash as a tx hash in the front of tx hashes.
>
> [offset_hash, coinbase_tx_hash, tx01_hash, tx02_hash, … , tx_n_hash]
>
> Actually could put offset_hash in any place in the array of hashes.
>
> network_hash_range = network_hash_end - network_hash_begin
>
> miner_hash_range = miner_hash_end - miner_hash_begin
>
> The offset value MUST between network_hash_begin/end or
> miner_hash_begin/end.
>
> https://user-images.githubusercontent.com/514951/31133378-e00d9ca2-a891-11e7-8c61-73325f59f6ed.JPG
>
> When mining pool send a job to miners, put the PoW hash range
> (miner_hash_begin/end) in the job. So if the miners find a hash which value
> is between [miner_hash_begin, miner_hash_end], means it's SHOULD be a
> valid share, could submit the share to the pool. If the hash value is
> between [network_hash_begin, network_hash_end] means find a valid block.
>
> The network_diff is much much high than the miner's diff, means the
> network_hash_range is much much smaller than miner_hash_range. By now,
> a typical miner's pool diff is around 16K, network diff is 1123863285132,
> so miner_hash_range is at least million times bigger than
> network_hash_range.
> The miners only know miner_hash_range, it's impossible for cheat miners
> to find out which share could make a valid block or not.
>
> Problems:
> 1. it's a hard fork.
> 2. will make existed asic dsha256 chips useless, but I think it's only a
> small change to make new asic chips based on existed tech.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
James Hilliard [ARCHIVE] /
npub10r…kgk2d
2023-06-07 18:06:51
in reply to nevent1q…ct5g
Author Public Key
npub10r9d6edmnrljk59wsf06zqp494l3qtjpa3w245hy6t5euqxlzw2qdkgk2dPublished at
2023-06-07 18:06:51Event JSON
{
"id": "da903c4a0341fc5daba96c64e8cffd6ffaa31637305e163f7ebde00676f083c1",
"pubkey": "78cadd65bb98ff2b50ae825fa100352d7f102e41ec5caad2e4d2e99e00df1394",
"created_at": 1686161211,
"kind": 1,
"tags": [
[
"e",
"1e4bb11c725227f652f7dfa07483b3f6bfbc98db3c5ca258709868b4d39b3671",
"",
"root"
],
[
"e",
"0941798e962a2d6abc6e61ddeae9248e3a6d3126d6abce6b89d1751b661bef3e",
"",
"reply"
],
[
"p",
"026d573c7ef982eab8b0e6e9b2b5bb2bcd5ebf2fb320e1e3d27254dedb4fba81"
]
],
"content": "📅 Original date posted:2017-10-06\n📝 Original message:There have been some other proposals to deal with this such as\nhttps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2012-June/001506.html\nthat may be possible to implement in existing miners.\n\nOn Tue, Oct 3, 2017 at 9:52 AM, 潘志彪 via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e Here is a solution may solve Block Withholding Attack. The general idea is\n\u003e came from Aviv Zohar(avivz at cs.huji.ac.il), I made it work for Bitcoin.\n\u003e Anyway, thanks Aviv.\n\u003e\n\u003e =====================\n\u003e\n\u003e DIFF_1 = 0x00000000FFFF0000000000000000000000000000000000000000000000000000;\n\u003e\n\u003e Diff = DIFF_1 / target\n\u003e\n\u003e this is equal to\n\u003e\n\u003e Diff = DIFF_1 / (target - 0) or Diff = DIFF_1 / abs(target - 0)\n\u003e\n\u003e now, we change diff algo to below:\n\u003e\n\u003e New_Diff = DIFF_1 / abs(target - offset)\n\u003e\n\u003e Offset is 32 bytes, like uint256 in Bitcoin, range is [0, 2^256),\n\u003e define: offset_hash = DSHA256(offset).\n\u003e\n\u003e we need to do a little change to the merkle root hash algo, put the\n\u003e offset_hash as a tx hash in the front of tx hashes.\n\u003e\n\u003e [offset_hash, coinbase_tx_hash, tx01_hash, tx02_hash, … , tx_n_hash]\n\u003e\n\u003e Actually could put offset_hash in any place in the array of hashes.\n\u003e\n\u003e network_hash_range = network_hash_end - network_hash_begin\n\u003e\n\u003e miner_hash_range = miner_hash_end - miner_hash_begin\n\u003e\n\u003e The offset value MUST between network_hash_begin/end or\n\u003e miner_hash_begin/end.\n\u003e\n\u003e https://user-images.githubusercontent.com/514951/31133378-e00d9ca2-a891-11e7-8c61-73325f59f6ed.JPG\n\u003e\n\u003e When mining pool send a job to miners, put the PoW hash range\n\u003e (miner_hash_begin/end) in the job. So if the miners find a hash which value\n\u003e is between [miner_hash_begin, miner_hash_end], means it's SHOULD be a\n\u003e valid share, could submit the share to the pool. If the hash value is\n\u003e between [network_hash_begin, network_hash_end] means find a valid block.\n\u003e\n\u003e The network_diff is much much high than the miner's diff, means the\n\u003e network_hash_range is much much smaller than miner_hash_range. By now,\n\u003e a typical miner's pool diff is around 16K, network diff is 1123863285132,\n\u003e so miner_hash_range is at least million times bigger than\n\u003e network_hash_range.\n\u003e The miners only know miner_hash_range, it's impossible for cheat miners\n\u003e to find out which share could make a valid block or not.\n\u003e\n\u003e Problems:\n\u003e 1. it's a hard fork.\n\u003e 2. will make existed asic dsha256 chips useless, but I think it's only a\n\u003e small change to make new asic chips based on existed tech.\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e",
"sig": "b2d9a974a88f46c4f2e505e5d85bb17a481b918f33def0a175cef3224891d6a86392a79ddc4bc8c318929d3336166adc5a437f2ed9879c91699a6621e9ba5bd6"
}