📅 Original date posted:2017-04-06
📝 Original message:On Fri, Apr 7, 2017 at 12:48 AM, Tomas <tomas at tomasvdw.nl> wrote:
> Bitcrust separates script validation (base load, when transaction come
> in) from order validation (peak load, when blocks come in).
How do you deal with validity rules changing based on block height?
> For script validation it would obviously need the ~2GB (or I think
> ~1.5GB) of outputs needed to validate these.
So it sounds like to work the software still needs an analog of a
(U)TXO database? I am confused by the earlier comments about thinking
the the resource consumption of the (U)TXO database is not a
consideration in your design.
> For order validation it
> needs ~200mb or the spent-index (for bit-lookups) and I would guess
> roughly ~500mb of the spent-tree (for scanning), though I don't think
> the 5.7GB full spend tree isn't worth pruning anytime soon.
If you get a transaction claiming to spend 0xDEADBEEFDEADBEEF, an
output that never existed how does your spent index reject this spend?
Gregory Maxwell [ARCHIVE] /
npub1f2…crwet
2023-06-07 17:59:43
in reply to nevent1q…q3rp
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwetPublished at
2023-06-07 17:59:43Event JSON
{
"id": "ee3ebb2f7f12052a1c44bc75e56a46c31b43ee2bed7b3af502ad6cdf1da8386b",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686160783,
"kind": 1,
"tags": [
[
"e",
"d4a682be1f6603f0ff8798c52b7225cac6554e21f3aedb0c80e7d41cf71983ad",
"",
"root"
],
[
"e",
"af4efc3a015fd7e187b5f4e56510c6220281b18ce66852efa56bfedf7e820c80",
"",
"reply"
],
[
"p",
"1c03575343555d1132a621c49466190d680da4a306ba8b992e8b87e267609cdd"
]
],
"content": "📅 Original date posted:2017-04-06\n📝 Original message:On Fri, Apr 7, 2017 at 12:48 AM, Tomas \u003ctomas at tomasvdw.nl\u003e wrote:\n\u003e Bitcrust separates script validation (base load, when transaction come\n\u003e in) from order validation (peak load, when blocks come in).\n\nHow do you deal with validity rules changing based on block height?\n\n\u003e For script validation it would obviously need the ~2GB (or I think\n\u003e ~1.5GB) of outputs needed to validate these.\n\nSo it sounds like to work the software still needs an analog of a\n(U)TXO database? I am confused by the earlier comments about thinking\nthe the resource consumption of the (U)TXO database is not a\nconsideration in your design.\n\n\u003e For order validation it\n\u003e needs ~200mb or the spent-index (for bit-lookups) and I would guess\n\u003e roughly ~500mb of the spent-tree (for scanning), though I don't think\n\u003e the 5.7GB full spend tree isn't worth pruning anytime soon.\n\nIf you get a transaction claiming to spend 0xDEADBEEFDEADBEEF, an\noutput that never existed how does your spent index reject this spend?",
"sig": "4c3b6716888f2cb3ceccbcccf37e5354de623286008c52431de40b7b0a58087c40d93c2ad58e426c0b32fd3aa60ffd36f212a4d0c769a115437a806e8b84c103"
}