replace signet with testnet4

citadel-tech · Jan 8, 2025 · 656873f · 656873f
1 parent b846f70
commit 656873f
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 13 deletions.
diff --git a/docs/app demos/bitcoind.md b/docs/app demos/bitcoind.md
@@ -61,7 +61,7 @@ After setting up the configuration file, our node will be ready to run in `regte
 
 
 > **NOTE**: `Regtest` is a toy network that allows for creating custom blocks and generating coins, making it ideal for easy integration testing of applications.  
-> For actual swap markets, use `Signet`. Switch to `Signet` by setting `signet=1` in the configuration.
+> For actual swap markets, use `testnet4`. Switch to `testnet4` by setting `testnet4=1` in the configuration.
 ---
 
 ### **3. Basic Operations**

diff --git a/docs/app demos/maker-cli.md b/docs/app demos/maker-cli.md
@@ -359,11 +359,7 @@ Next, let's send `10,000 sats` from the maker's wallet to an external address.
 #### **Step 1**: Derive an External Address Using `bitcoin-cli`'s `deriveaddresses` Command
 
 ```bash
-$ bitcoin-cli deriveaddresses <descriptor in signet> "[0,0]"
-
-[
-  <derived address>
-]
+$ bitcoin-cli getnewaddress
 ```
 
 #### **Step 2**: Use `maker-cli`'s `send-to-address` Command to Send the Amount to the Derived Address

diff --git a/docs/app demos/makerd.md b/docs/app demos/makerd.md
@@ -71,10 +71,10 @@ This section focuses on `Makerd`, walking you through the process of starting an
 
 ### 1. Start Bitcoin Core (Pre-requisite)
 
-`Makerd` requires a **Bitcoin Core** RPC connection running on **Signet** for its operation. To get started, you need to start `bitcoind`:
+`Makerd` requires a **Bitcoin Core** RPC connection running on **testnet4** for its operation. To get started, you need to start `bitcoind`:
 
 > **Important:**  
-> All apps are designed to run on **Signet** for testing purposes. The DNS server that Maker connects to will also be on Signet. While you can run these apps on other networks, there won't be any DNS available, so Maker won’t be able to connect to the DNS server or other Coinswap networks.
+> All apps are designed to run on **testnet4** for testing purposes. The DNS server that Maker connects to will also be on testnet4. While you can run these apps on other networks, there won't be any DNS available, so Maker won’t be able to connect to the DNS server or other Coinswap networks.
 
 To start `bitcoind`:
 
@@ -101,7 +101,7 @@ coinswap 0.1.0
 Developers at Citadel-Tech
 Coinswap Maker Server
 
-The server requires a Bitcoin Core RPC connection running in Signet. It requires some starting balance (0.05 BTC Fidelity + Swap Liquidity). After the successful creation of a Fidelity Bond, the server will start listening for incoming swap requests and earn swap fees.
+The server requires a Bitcoin Core RPC connection running in testnet4. It requires some starting balance (0.05 BTC Fidelity + Swap Liquidity). After the successful creation of a Fidelity Bond, the server will start listening for incoming swap requests and earn swap fees.
 
 The server is operated with the maker-cli app, for all basic wallet-related operations.
 
@@ -191,7 +191,7 @@ This will launch `makerd` and connect it to the Bitcoin RPC core running on it's
 
   > **Note**: Currently The transaction fee for the fidelity bond is hardcoded at `1000 sats`. This approach of directly considering `fee` not `fee rate` will be improved in v0.1.1 milestones.
 
-- Since the maker wallet is empty, we'll need to fund it with at least `0.00051000 BTC` to cover the fidelity amount and transaction fee. To fund the wallet, we can use a Signet faucet from [Signet Faucets](https://signetfaucet.com/).
+- Since the maker wallet is empty, we'll need to fund it with at least `0.00051000 BTC` to cover the fidelity amount and transaction fee. To fund the wallet, we can use a testnet4 faucet from [testnet4 Faucets](https://mempool.space/testnet4/faucet).
   Let's just take `0.01 BTC`testcoins as extra amount will be used in doing wallet related operations in [maker-cli demo](./maker-cli.md)
 
 - The server will regularly sync the wallet every 10 seconds, increasing the interval in the pattern 10,20,30,40..., to detect any incoming funds.

diff --git a/docs/app demos/taker.md b/docs/app demos/taker.md
@@ -13,10 +13,10 @@ The taker CLI is an application that allows you to perform coinswaps as a taker.
 
 ### Start Bitcoin Core (Pre-requisite)
 
-`Taker` requires a **Bitcoin Core** RPC connection running on **Signet** for its operation. To get started, you need to start `bitcoind`:
+`Taker` requires a **Bitcoin Core** RPC connection running on **testnet4** for its operation. To get started, you need to start `bitcoind`:
 
 > **Important:**  
-> All apps are designed to run on **Signet** for testing purposes. The DNS server that Taker connects to will also be on Signet. While you can run these apps on other networks, there won't be any DNS available, so Taker won’t be able to connect to the DNS server fir getting maker's offers and can't do coinswap with makers.
+> All apps are designed to run on **testnet4** for testing purposes. The DNS server that Taker connects to will also be on testnet4. While you can run these apps on other networks, there won't be any DNS available, so Taker won’t be able to connect to the DNS server fir getting maker's offers and can't do coinswap with makers.
 
 To start `bitcoind`:
 
@@ -87,7 +87,7 @@ $ taker -r 127.0.0.1:38332 -a user:pass get-new-address
 bcrt1qyywgd4we5y7u05lnrgs8runc3j7sspwqhekrdd
 ```
 
-Now we can use a Signet faucet to send some coins to this address. You can find a Signet faucet [here](https://signetfaucet.com/).
+Now we can use a testnet4 faucet to send some coins to this address. You can find a testnet4 faucet [here](https://mempool.space/testnet4/faucet).
 
 Once you have some coins in your wallet, you can check your balance by running the following command: