From cae548685dc26c3be823f132ab88947175d19af6 Mon Sep 17 00:00:00 2001 From: Jonas Schnelli Date: Sat, 6 Dec 2014 10:54:09 +0100 Subject: [PATCH] [REST] added /rest/block/notxdetails/ into REST-interface.md documentation --- doc/REST-interface.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/REST-interface.md b/doc/REST-interface.md index 05c532be5..0af650b4e 100644 --- a/doc/REST-interface.md +++ b/doc/REST-interface.md @@ -11,12 +11,15 @@ Given a transaction hash, Returns a transaction, in binary, hex-encoded binary or JSON formats. `GET /rest/block/BLOCK-HASH.{bin|hex|json}` +`GET /rest/block/notxdetails/BLOCK-HASH.{bin|hex|json}` Given a block hash, Returns a block, in binary, hex-encoded binary or JSON formats. The HTTP request and response are both handled entirely in-memory, thus making maximum memory usage at least 2.66MB (1 MB max block, plus hex encoding) per request. +With the /notxdetails/ option JSON response will only contain the transaction hash instead of the complete transaction details. The option only affects the JSON response. + For full TX query capability, one must enable the transaction index via "txindex=1" command line / configuration option. Risks