Remove Piccadilly Testnet - Piccadilly decommissioning scheduled for 2025-09-26

_quarto.yml

@@ -38,7 +38,6 @@ website:
       contents:
       - "networks/mainnet/index.md"
       - "networks/testnet-bakerloo/index.md"
-      - "networks/testnet-piccadilly/index.md"
     - section: "Accounts"
       contents:
       - "account-holders/setup-aut/index.md"

concepts/oracle-server/index.md

@@ -53,10 +53,6 @@ ATN and NTN symbols are preview listed but untraded:
 - https://www.coingecko.com/en/coins/auton
 - https://www.coingecko.com/en/coins/newton
 
-Plugins for retrieving ATN-NTN price data are to be developed for Mainnet launch.
-
-ATN-NTN price data for [Piccadilly Testnet](/networks/testnet-piccadilly/) is computed using mock 'USDCx'. Piccadilly Testnet validators can retrieve ATN-USDCx and NTN-USDCx price data from a Uniswap V2 AMM clone deployed on the testnet using the `crypto_uniswap` plugin. For how to configure this see the Guide _Running an Oracle Server_ and [Setup crypto plugin config](/oracle/run-oracle/#setup-crypto-plugin-config).
-
 :::
 
 #### Developing data plugins

concepts/protocol-assets/newton/index.md

@@ -43,7 +43,3 @@ The exact parameters of the Mainnet inflation mechanism will be determined throu
 ![Figure 1, example inflation curve. Note that parameters are purely illustrative and the Mainnet curve will likely change.](./images/example-inflation-curve.png)
 
 Please note that in the graph above, the y-axis percentage returns assume a 100% [participation rate](/glossary/#participation-rate) (i.e. all tokens are staked). To model for yourself the expected inflation yield, divide the value on the y-axis by an estimated participation rate (e.g. 0.7 for an expected participation rate of 70%, resulting in an inflation yield of 14.3% at genesis for an inflation rate of 10%).
-
-For the [Piccadilly Circus Games Competition ](https://game.autonity.org/) and the [Autonity Piccadilly Tiber Challenge](https://github.com/autonity/tiber-challenge) on the [Piccadilly Testnet](/networks/testnet-piccadilly/), a slightly different inflation schedule has been used to aid in testing. The PCGC Round 6 emission schedule can be seen below:
-
-![Figure 2, inflation curve for Round 6 of the Piccadilly Circus Games Competition.](./images/r6-inflation.png)

developer/custom-networks/index.md

@@ -12,7 +12,7 @@ To connect your node to a custom Autonity network, you will need the network's:
   See [Local Autonity Network configuration](/reference/genesis/#local-autonity-network-configuration) in the [Genesis](/reference/genesis/) reference for how to create these files.
 
 ::: {.callout-note title="Note" collapse="false"}
-Note that the client provides command-line flag options for connecting to public Autonity testnets: `--bakerloo` and `--piccadilly`. The node will not run if you specify both genesis and bootnodes for a custom network **and** a testnet flag. The client will create a genesis block for the custom network's genesis configuration and the node's local store will then have an incompatible genesis with the testnet.
+Note that the client provides a [command-line option](/reference/cli/agc/#command-line-options) for connecting to the Autonity Bakerloo Testnet `--bakerloo`. The node will not run if you specify both genesis and bootnodes for a custom network **and** a testnet flag. The client will create a genesis block for the custom network's genesis configuration and the node's local store will then have an incompatible genesis with the testnet.
 :::
 
 1. Install Autonity in a working directory and create an `autonity-chaindata` sub-directory as described in [Running a node, Install Autonity](/node-operators/install-aut/).
@@ -29,7 +29,7 @@ cp ./<PATH>/static-nodes.json ./autonity-chaindata/
 cp ./<PATH>/genesis.json ./
 ```
 
-4. Run the node as described in [Running a node, Run Autonity](/node-operators/run-aut/), replacing the network specifier flag (e.g. `--piccadilly`) with the options:
+4. Run the node as described in [Running a node, Run Autonity](/node-operators/run-aut/), specifying your custom network by the options:
 	- `--genesis`: to provide the genesis file.
 	- `--networkid`: to provide the network identifier. This is typically the same value as the `chainId` file in the genesis configuration file, but may be different.
 

developer/deploy-brownie/index.md

@@ -16,9 +16,9 @@ pipx install eth-brownie
 
 Add the testnet you would like to deploy the contract to, given an `RPC_URL` from <https://chainlist.org/?testnets=true&search=autonity>:
 ```bash
-brownie networks add Ethereum piccadilly host=$RPC_URL chainid=65100003
+brownie networks add Ethereum bakerloo host=$RPC_URL chainid=65100003
 ```
-Here we have used the [Piccadilly testnet](/networks/testnet-piccadilly/) as an example.  See [here](/networks/) for other possible networks.
+Here we have used the [Bakerloo Testnet](/networks/testnet-bakerloo/) as an example.
 
 Install the OpenZeppelin package, which contains a base ERC20 token implementation:
 ```bash
@@ -99,7 +99,7 @@ brownie accounts generate deployer
 
 Run the deploy script on the testnet:
 ```bash
-brownie run --network piccadilly deploy main <OWNER>
+brownie run --network bakerloo deploy main <OWNER>
 ```
 
 Take note of the address of the deployed contract.  This can be used with the `--token` option of the `aut token` commands in order to interact with the deployed token.