waxwing on Nostr: Yes, I did see (at least what's publically written) about Binance. It's not really ...
Yes, I did see (at least what's publically written) about Binance. It's not really either clear what you are saying (it didn't make a difference to what, precisely?), nor what the right choice is for each situation. A ZkSNARK nor a bulletproofs or other similar ZKP system won't be needed for the *assets* side of a proof of reserves, *if* you don't care about onchain privacy - which Binance doesn't; they just publish all the onchain addresses. While those systems can help a lot with the trickier proof of liabilities. If you do care about onchain privacy, these systems have tradeoffs; to get a bigger anon set on bitcoin than taproot, you have to address the hashing problem. The original Provisions protocol of Bunz completely sidestepped this problem; with zksnarks you *can* address it but it is quite, quite tough because you have to build multiple non-algebraic hash function circuits. The result is that at the very least, pre-processing takes horrendous amounts of time.
Published at
2024-09-18 17:43:04Event JSON
{
"id": "b00039403f3354c42ec0968c8c16238efcd1d17c5c0796cabfc7a9c2428aa735",
"pubkey": "675b84fe75e216ab947c7438ee519ca7775376ddf05dadfba6278bd012e1d728",
"created_at": 1726681384,
"kind": 1,
"tags": [
[
"e",
"7e011cf7d21d3cd01a566a6fa6882e27003671a4a64039ea43e33e18aafb4c09",
"",
"root"
],
[
"e",
"a80256a22666c905efde2d211c4d049198a048d794921a4385e0bbeba3cab31c"
],
[
"e",
"ebeff488dbd230d88ae63099f57066daf3bea8f5a337032a7905519517b72db4",
"",
"reply"
],
[
"p",
"675b84fe75e216ab947c7438ee519ca7775376ddf05dadfba6278bd012e1d728"
],
[
"p",
"6681268ace4748d41a4cfcc1e64006fb935bbc359782b3d9611f64d51c6752d9"
]
],
"content": "Yes, I did see (at least what's publically written) about Binance. It's not really either clear what you are saying (it didn't make a difference to what, precisely?), nor what the right choice is for each situation. A ZkSNARK nor a bulletproofs or other similar ZKP system won't be needed for the *assets* side of a proof of reserves, *if* you don't care about onchain privacy - which Binance doesn't; they just publish all the onchain addresses. While those systems can help a lot with the trickier proof of liabilities. If you do care about onchain privacy, these systems have tradeoffs; to get a bigger anon set on bitcoin than taproot, you have to address the hashing problem. The original Provisions protocol of Bunz completely sidestepped this problem; with zksnarks you *can* address it but it is quite, quite tough because you have to build multiple non-algebraic hash function circuits. The result is that at the very least, pre-processing takes horrendous amounts of time.",
"sig": "711d1bb9b5c5135d42380d9b02d31dcc364efd07086027ab133d429243ed89e67b3d7248bcf38acf563352d9c682acc5b4e3f405e0ffaeb78e6f6e2aeae28be7"
}