From c06488d5f66eb10ab914047cdc4db7da29856727 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 00:29:32 +0000 Subject: [PATCH] Edited ch06_transactions.adoc with Atlas code editor --- ch06_transactions.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc index e08bd9db..0234bb14 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -107,7 +107,7 @@ transactions. .Protecting Presigned Transactions **** -The last step before broadcasting a transaction to the network for +The last step ((("transactions", "presigned", id="transaction-presign")))((("presigned transactions", id="presign-transaction")))before broadcasting a transaction to the network for inclusion in the blockchain is to sign it. However, it's possible to sign a transaction without broadcasting it immediately. You can save that presigned transaction for months or years in the belief that it @@ -135,7 +135,7 @@ If you implement a protocol that uses presigned transactions, ensure that it doesn't use any features that are reserved for future upgrades. Bitcoin Core's default transaction relay policy does not allow the use of reserved features. You can test whether a transaction complies with -that policy by using the Bitcoin Core RPC +testmempoolaccept+ on Bitcoin +that policy by using the Bitcoin Core RPC +testmempoolaccept+ on ((("transactions", "presigned", startref="transaction-presign")))((("presigned transactions", startref="presign-transaction")))Bitcoin mainnet. ****