š
Original date posted:2013-07-23
š Original message:On Monday 22 July 2013 20:42:45 Jeff Garzik wrote:
> URL: https://github.com/bitcoin/bitcoin/pull/2844
>
> Adding an HTTP REST API for bitcoind has been occasionally tossed
> about as a useful thing. Such an API would essentially provide a
> decentralized block explorer capability, enabling easy external access
> to transaction/address/block indices that we maintain.
This is excellent.
> The first two implemented API calls are simple, returning a block or
> TX given a simple query string based on block hash, e.g.
>
> GET /rest/tx/TX-HASH
> or
> GET /rest/block/BLOCK-HASH
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.
Andy
--
Dr Andy Parkins
andyparkins at gmail.com
Andy Parkins [ARCHIVE] /
npub1nxā¦7wjrv
2023-06-07 15:04:57
in reply to nevent1qā¦8xzz
Author Public Key
npub1nxlvf9mj3jzgue25n5d9y47s3h5hvg0ded9hwpejdxj9mtrs34vs97wjrvPublished at
2023-06-07 15:04:57Event JSON
{
"id": "8333398a2f609eed8a87bce3e30d9d1b3a20da90a3d0ad3bd694f3c268ef4b73",
"pubkey": "99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59",
"created_at": 1686150297,
"kind": 1,
"tags": [
[
"e",
"2548e3bbd5806f0a91f1440e5be19b1893f723d052860cba20b98f557d042316",
"",
"root"
],
[
"e",
"cdb1406a2e3a44f561d43a6cf5e0f193c0787c2b083d880eb8b2069429939731",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "š
Original date posted:2013-07-23\nš Original message:On Monday 22 July 2013 20:42:45 Jeff Garzik wrote:\n\u003e URL: https://github.com/bitcoin/bitcoin/pull/2844\n\u003e \n\u003e Adding an HTTP REST API for bitcoind has been occasionally tossed\n\u003e about as a useful thing. Such an API would essentially provide a\n\u003e decentralized block explorer capability, enabling easy external access\n\u003e to transaction/address/block indices that we maintain.\n\nThis is excellent.\n\n\u003e The first two implemented API calls are simple, returning a block or\n\u003e TX given a simple query string based on block hash, e.g.\n\u003e \n\u003e GET /rest/tx/TX-HASH\n\u003e or\n\u003e GET /rest/block/BLOCK-HASH\n\nOne additional URL makes this pretty much perfect:\n\n GET /rest/block-with-tx/TX-HASH\n\nConstruction of the transaction-hash-to-block database is something the full \nclient's have to do anyway, so this query is no harder than the others for \nthem to supply; but suddenly makes it possible for an SPV client to trace the \nprovidence of any transaction without needing to maintain the entire chain.\n\n\nAndy\n\n-- \nDr Andy Parkins\nandyparkins at gmail.com",
"sig": "e0fb7e65d6b7b43a505b087fc051a6807f564b24d9a37afb791733e02cd152d25b1d8631698d1f4759e4d33f5299e62ce21c4a76723f94674daeff6091661464"
}