autonity · cmjc · Sep 26, 2025 · Sep 25, 2025 · Sep 25, 2025 · Sep 26, 2025
@@ -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"

@@ -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

@@ -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)
@@ -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.
 

@@ -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.
@@ -11,16 +11,3 @@ listing:
 ---
 
 
-In the run-up to mainnet launch Autonity provides Piccadilly Testnet as an open testnet for node operators, validators and developers.
-
-## Get Auton test funds
-
-Take part in the [Piccadilly Tiber Challenge](https://autonity.org/tiber) to get free [auton](/concepts/protocol-assets/auton) to fund your account for testing.
-
-An alternative way to get auton is by requesting some from the Autonity [Discord Server](https://discord.gg/autonity). Please note this will take much longer.
-
-<!--
-To get started on either the Bakerloo or Piccadilly testnet, you can use the [Faucet](https://faucet.autonity.org/) to get free auton to fund your account for testing.
-
-If the Faucet is down for maintenance, an alternative way to get auton is by requesting some from the Autonity [Discord Server](https://discord.gg/autonity). Please note this will take much longer.
--->
@@ -9,7 +9,7 @@ Autonity Mainnet is the live Autonity blockchain network for transactions and de
 
 Mainnet is for participants interested in:
 
-- The Autonity Futures Protocol
+- The [Autonity Futures Protocol](https://afp.autonity.org/)
 - Decentralized application (dApp) use cases
 - Providing live validator and public RPC endpoint node infrastructure
 - The Autonity community!
@@ -27,7 +27,7 @@ Mainnet is for participants interested in:
 
 ::: {.callout-tip title="Adding Autonity as a custom network to your wallet" collapse="false"}
 
-The above information can be used to add Autonity as a custom network to to an existing client such as [MetaMask](https://support.metamask.io/configure/networks/how-to-add-a-custom-network-rpc/)).
+The above information can be used to add Autonity as a custom network to to an existing client such as [MetaMask](https://support.metamask.io/configure/networks/how-to-add-a-custom-network-rpc/).
 
 :::
 

@@ -1,17 +1,18 @@
 ---
 title: "Bakerloo Testnet"
 description: >
- Public Autonity Testnet running the stable version of the Autonity protocol
+ Public Autonity Testnet for test and development
 draft: false
 ---
 
-Bakerloo is a general purpose public Testnet providing a stable testing environment for those developing a project on top of Autonity.
+Bakerloo is a general purpose public testnet that simulates the mainnet protocol configuration.
 
-Bakerloo provides a reliable test network for community developers, node operators, and infrastructure providers to:
+Testnet provides a stable environment for community developers, node operators, and infrastructure providers to:
 
-- test their tooling, software and operational practices
+- test protocol upgrades before rollout to Mainnet
+- test tooling, software and operational practices
 - work in a safe sandbox environment to build, test, and debug before deployment to mainnet without transaction cost
-- innovate new protocols, ideas, and projects.
+- innovate and develop new protocols, ideas, and projects for Autonity.
 
 ## Bakerloo Testnet details
 
@@ -25,7 +26,7 @@ Bakerloo provides a reliable test network for community developers, node operato
 
 ::: {.callout-tip title="Adding Autonity as a custom network to your wallet" collapse="false"}
 
-The above information can be used to add Autonity as a custom network to to an existing client such as [MetaMask](https://support.metamask.io/configure/networks/how-to-add-a-custom-network-rpc/)).
+The above information can be used to add Autonity as a custom network to to an existing client such as [MetaMask](https://support.metamask.io/configure/networks/how-to-add-a-custom-network-rpc/).
 
 :::
 

@@ -8,6 +8,17 @@ description: >
 - Ensure that the host machine meets the [minimum requirements](/node-operators/install-aut/#requirements)
 :::
 
+
+## Running the Autonity Go Client
+
+When initialised Autonity Go Client will connect to the specified Autonity network, find peer nodes, and begin to sync. AGC's default setting is to connect to Mainnet.
+
+If connecting to the [Bakerloo Testnet](/networks/testnet-bakerloo/), then the `--bakerloo` command-line option is specified when running the node. The Mainnet and Bakerloo genesis configuration are specified along with bootnodes in the AGC configuration and do not need to be specified.
+
+If connecting to a custom network genesis configuration and bootnode addresses will need to be specified. For how to do this see the Development guide page [Setting up custom networks](https://docs.autonity.org/developer/custom-networks/).
+
+This guide exemplifies connecting to Bakerloo. If connecting to Mainnet simply remove the `--bakerloo` flag.
+
 ## Run Autonity (binary or source code install) {#run-binary}
 
 - Ensure that the Autonity Go Client has been installed from a [pre-compiled binary](/node-operators/install-aut#install-binary) or from [source code](/node-operators/install-aut#install-source)

@@ -131,11 +131,11 @@ You are now ready to run telegraf in your working directory.
 
 To configure Autonity for exporting metrics set [command line options](/reference/cli/#command-line-options) when starting the node for:
 
-- the Autonity testnet being connected to: `--piccadilly` or `--bakerloo`.
+- the Autonity Bakerloo Testnet if connecting to Testnet not Mainnet: `--bakerloo`.
 - enabling metrics collection and reporting: `--metrics`.
 - enabling the pprof HTTP server: `--pprof`.
 
-The [Piccadilly Testnet](https://docs.autonity.org/networks/testnet-piccadilly/) is connected to in the example configuration here. For a minimal command line start configuration see the how to [Run Autonity](/node-operators/run-aut/).
+The [Bakerloo Testnet](https://docs.autonity.org/networks/testnet-bakerloo/) is connected to in the example configuration here. Omit the `--bakerloo` option when connecting to Mainnet. For a minimal command line start configuration see the how to [Run Autonity](/node-operators/run-aut/).
 
 Autonity will serve an http feed that provides metrics at `http://localhost:6060/debug/metrics/prometheus`, which you can view in a browser. Notice this is the input specified in `telegraf.conf` above. If you are using Docker, make sure you run the container as host, as shown below:
 
@@ -148,7 +148,7 @@ docker run \
 --rm \
 ghcr.io/autonity/autonity/autonity:latest \
     --datadir ./autonity-chaindata  \
-    --piccadilly \
+    --bakerloo \
     --http  \
     --http.api aut,eth,net,txpool,web3,admin  \
     --ws  \

@@ -249,9 +249,9 @@ A basic set of data adaptor plugins for sourcing this data is provided out the b
 
 - Built by the `make` process when building from source. Run the make command appropriate for the Testnet you are connecting to as described in [Build from source code](/oracle/install-oracle/#install-source). You can view the built plugins in the directory `./build/bin/plugins`.
 
-- Included pre-built as part of the pre-built executable.  You can view the built plugins in the directory `/plugins`. The executable is built for Piccadilly Testnet only.
+- Included pre-built as part of the pre-built executable.  You can view the built plugins in the directory `/plugins`. The executable is built for Mainnet only.
 
-- Included pre-built as part of oracle server Docker image and the pre-built executable. Install the Docker image for the Testnet you are connecting to as described in [Installing the Docker image](/oracle/install-oracle/#install-docker). The built plugins are included in the Docker container at the path `/usr/local/bin/plugins`.
+- Included pre-built as part of oracle server Docker image and the pre-built executable. Install the Docker image for the network you are connecting to as described in [Installing the Docker image](/oracle/install-oracle/#install-docker). The built plugins are included in the Docker container at the path `/usr/local/bin/plugins`.
 
 ::: {.callout-note title="Note" collapse="false"}
 <!--The Simulator plugin for simulated ATN and NTN price data is built when building from source for Bakerloo Testnet. -->You can build the Simulator plugin independently by running the command `make simulator`. This will build the `simulator_plugin` in the `/plugins` directory. A local testnet could be a scenario for setting up and using a simulator.