š
Original date posted:2013-07-23
š Original message:On Tuesday 23 July 2013 10:42:05 Pieter Wuille wrote:
> On Tue, Jul 23, 2013 at 10:30:13AM +0100, Andy Parkins wrote:
> > One additional URL makes this pretty much perfect:
> > GET /rest/block-with-tx/TX-HASH
> >
> > Construction of the transaction-hash-to-block database is something the
> > full client's have to do anyway, so this query is no harder than the
> > others for them to supply; but suddenly makes it possible for an SPV
> > client to trace the providence of any transaction without needing to
> > maintain the entire chain.
>
> There is actually no such index being maintained by default, and doing so
> is an unnecessary burden IMHO (you need to enable -txindex since 0.8 to
> get this). Of course, if enabled, it can be exposed.
Wow. I'm surprised at that. How does a newly received transaction have its
inputs verified then? Multiple linear brute force searches of the block chain
for every new transaction? Or is it that transactions are only recorded if
they were in a block, and just their presence indicates they're valid?
Andy
--
Dr Andy Parkins
andyparkins at gmail.com
Andy Parkins [ARCHIVE] /
npub1nxā¦7wjrv
2023-06-07 15:04:58
in reply to nevent1qā¦4gem
Author Public Key
npub1nxlvf9mj3jzgue25n5d9y47s3h5hvg0ded9hwpejdxj9mtrs34vs97wjrvSeen on
wss://relay.nostr.bandPublished at
2023-06-07 15:04:58Event JSON
{
"id": "890bf7ea3e79e6a22f62c3a0166893606e0a849fd3bc4e87537f48e535b0aa7e",
"pubkey": "99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59",
"created_at": 1686150298,
"kind": 1,
"tags": [
[
"e",
"2548e3bbd5806f0a91f1440e5be19b1893f723d052860cba20b98f557d042316",
"",
"root"
],
[
"e",
"6201a06a91e99a75fcce49974f225525d959b800972495939f851568c25e99a3",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "š
Original date posted:2013-07-23\nš Original message:On Tuesday 23 July 2013 10:42:05 Pieter Wuille wrote:\n\u003e On Tue, Jul 23, 2013 at 10:30:13AM +0100, Andy Parkins wrote:\n\u003e \u003e One additional URL makes this pretty much perfect:\n\u003e \u003e GET /rest/block-with-tx/TX-HASH\n\u003e \u003e \n\u003e \u003e Construction of the transaction-hash-to-block database is something the\n\u003e \u003e full client's have to do anyway, so this query is no harder than the\n\u003e \u003e others for them to supply; but suddenly makes it possible for an SPV\n\u003e \u003e client to trace the providence of any transaction without needing to\n\u003e \u003e maintain the entire chain.\n\u003e \n\u003e There is actually no such index being maintained by default, and doing so\n\u003e is an unnecessary burden IMHO (you need to enable -txindex since 0.8 to\n\u003e get this). Of course, if enabled, it can be exposed.\n\nWow. I'm surprised at that. How does a newly received transaction have its \ninputs verified then? Multiple linear brute force searches of the block chain \nfor every new transaction? Or is it that transactions are only recorded if \nthey were in a block, and just their presence indicates they're valid?\n\n\nAndy\n\n-- \nDr Andy Parkins\nandyparkins at gmail.com",
"sig": "a607931ab2cf2ab3e65a5b55455716f89708a1959e3da6a686fb4445c251058203e494e7166a52d2818c349d606c07c025df2e503f0938094eccf63fe268b284"
}