You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The REST API can be enabled with the `-rest` option.
5
+
6
+
Supported API
7
+
-------------
8
+
`GET /rest/tx/TX-HASH.{bin|hex|json}`
9
+
10
+
Given a transaction hash,
11
+
Returns a transaction, in binary, hex-encoded binary or JSON formats.
12
+
13
+
`GET /rest/block/BLOCK-HASH.{bin|hex|json}`
14
+
15
+
Given a block hash,
16
+
Returns a block, in binary, hex-encoded binary or JSON formats.
17
+
18
+
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.
19
+
20
+
For full TX query capability, one must enable the transaction index via "txindex=1" command line / configuration option.
21
+
22
+
Risks
23
+
-------------
24
+
Running a webbrowser on the same node with a REST enabled bitcoind can be a risk. Accessing prepared XSS websites could read out tx/block data of your node by placing links like `<script src="http://127.0.0.1:1234/tx/json/1234567890">` which might break the nodes privacy.
0 commit comments