Switch to standard BTC testnet ports.

More s/krypton/xenon/

src/pages/mining.md

@@ -43,9 +43,9 @@ maxorphantx=1
 banscore=1
 
 [test]
-bind=0.0.0.0:18443
-rpcbind=0.0.0.0:18444
-rpcport=18443
+bind=0.0.0.0:18333
+rpcbind=0.0.0.0:18332
+rpcport=18332
 ```
 
 Finally, start bitcoind as follows: `$ bitcoind -conf=path/to/bitcoin.conf`. It will take a few hours for the node to synchronize with the Bitcoin testnet -- be patient!
@@ -100,8 +100,8 @@ mode = "xenon" # if connecting to Krypton, set this to "krypton"
 peer_host = "127.0.0.1"
 username = "your-bitcoind-username"
 password = "your-bitcoind-password"
-rpc_port = 18443
-peer_port = 18444
+rpc_port = 18333
+peer_port = 18332
 
 [[mstx_balance]]
 address = "STB44HYPYAT2BB2QE513NSP81HTMYWBJP02HPGK6"
@@ -158,7 +158,7 @@ To read more about the technical details of mining on the Stacks 2.0 network, ha
 In case you are running into issues or would like to see verbose logging, you can run your node with debug logging enabled. In the command line, run:
 
 ```bash
-BLOCKSTACK_DEBUG=1 stacks-node krypton
+BLOCKSTACK_DEBUG=1 stacks-node xenon
 ```
 
 ## Running a miner in Windows
@@ -302,6 +302,7 @@ miner = true
 
 [burnchain]
 chain = "bitcoin"
+# For Xenon, set to "xenon" and set `peer_host` to a local bitcoind as covered earlier.
 mode = "krypton"
 peer_host = "bitcoind.krypton.blockstack.org"
 #process_exit_at_block_height = 5340

src/pages/smart-contracts/public-registry-tutorial.md

@@ -184,7 +184,7 @@ Then subscribe for updates of the transaction status by creating a web socket cl
 useEffect(() => {
   let sub;
   const subscribe = async txId => {
-    const client = await connectWebSocketClient('ws://stacks-node-api.krypton.blockstack.org/');
+    const client = await connectWebSocketClient('ws://stacks-node-api.blockstack.org/');
     sub = await client.subscribeTxUpdates(txId, update => {
       console.log(update);
     });

src/pages/stacks-blockchain/running-testnet-node.md

@@ -60,7 +60,7 @@ To install Stacks node with extra debugging symbols, run:
 
 ```bash
 cargo build --workspace --bin stacks-node
-# binary will be in target/debug/stacks-node krypton
+# binary will be in target/debug/stacks-node
 ```
 
 -> This process will take a few minutes to complete
@@ -72,13 +72,13 @@ You're all set to run a node that connects to the testnet network.
 If installed without debugging symbols, run:
 
 ```bash
-target/release/stacks-node krypton
+target/release/stacks-node xenon
 ```
 
 If installed with debugging symbols, run:
 
 ```bash
-target/debug/stacks-node krypton
+target/debug/stacks-node xenon
 ```
 
 The first time you run this, you'll see some logs indicating that the Rust code is being compiled. Once that's done, you should see some logs that look something like the this:
@@ -123,7 +123,7 @@ Next, click on save file and Press **Ok** in the popup window.
 Once saved, Extract the binary. Open the command prompt **from the folder where binary is extracted** and execute the below command:
 
 ```bash
-stacks-node krypton
+stacks-node xenon
 # This command will start the testnet follower node.
 ```
 
@@ -135,7 +135,7 @@ To execute Stacks node with extra debugging enabled, run:
 ```bash
 set RUST_BACKTRACE=full
 set BLOCKSTACK_DEBUG=1
-stacks-node krypton
+stacks-node xenon
 # This command will execute the binary and start the follower node with debug enabled.
 ```
 
@@ -164,7 +164,7 @@ docker run -d \
   -p 20443:20443 \
   -p 20444:20444 \
   blockstack/stacks-blockchain:latest \
-/bin/stacks-node krypton
+/bin/stacks-node xenon
 ```
 
 -> The ENV VARS `RUST_BACKTRACE` and `BLOCKSTACK_DEBUG` are optional. If removed, debug logs will be disabled