From 97c40b76f087dec21c1421e361c516bcb544538e Mon Sep 17 00:00:00 2001
From: Frames Jenco <97039210+framesjenco@users.noreply.github.com>
Date: Thu, 14 Apr 2022 08:24:31 -0400
Subject: [PATCH] accurately describe the POST endpoint to /tx/:txid

As currently implemented the raw tx hex must be supplied in the body or the endpoint exits early without creating an entry in the db.
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 7bada4e..17ebe17 100644
--- a/README.md
+++ b/README.md
@@ -106,7 +106,7 @@ it's not recommeded for production environments in mainnet at the moment.
 
 * `POST /trust/:txid?` - Trusts a transaction to execute its code, as well as any untrusted ancestors. To trust multiple transactions at once, you may add an array of txids in the body as application/json.
 * `POST /ban/:txid` - Bans a transaction from being executed, and unindexes it and its descendents
-* `POST /tx/:txid?` - Indexes a transaction and any ancestors. You may optionally add the raw hex data for the transaction in the body as text/plain.
+* `POST /tx/:txid?` - Indexes a transaction and any ancestors. Takes the raw hex data for the transaction in the body as text/plain.
 
 * `DELETE /trust/:txid` - Removes trust for a transaction, and unindexes it and its descendents
 * `DELETE /ban/:txid` - Removes a transaction ban, and reindexes it and its descendents