From 7027726f61764a68c0f12ddff3b522185a03575d Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 17:22:49 +0000 Subject: [PATCH] Edited ch11_blockchain.adoc with Atlas code editor --- ch11_blockchain.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch11_blockchain.adoc b/ch11_blockchain.adoc index 621e6e28..322493ed 100644 --- a/ch11_blockchain.adoc +++ b/ch11_blockchain.adoc @@ -665,7 +665,7 @@ happen, testnet becomes unusable for users and ((("blockchain", "test blockchain ==== Signet: The Proof of Authority Testnet -There's no known way for a system dependent on permissionless PoW to +There's no ((("blockchain", "test blockchains", "signet", id="blockchain-test-signet")))((("test blockchains", "signet", id="test-block-signet")))((("signet", id="signet")))known way for a system dependent on permissionless PoW to provide a highly usable blockchain without introducing economic incentives, so Bitcoin protocol developers began considering alternatives. The primary goal was to preserve as much of the structure of @@ -720,7 +720,7 @@ mining software occur on testnet3 and that all other public testing of Bitcoin software occur on the default signet. To interact with your chosen signet, you can use the +-signet+ parameter -with +bitcoin-cli+, similar to how you used testnet. For example: +with +bitcoin-cli+, similar to how you used testnet. For((("blockchain", "test blockchains", "signet", startref="blockchain-test-signet")))((("test blockchains", "signet", startref="test-block-signet")))((("signet", startref="signet"))) example: ---- $ bitcoin-cli -signet getblockchaininfo