github.com/gnolang/gno@v0.0.0-20240520182011-228e9d0192ce/docs/concepts/testnets.md (about)

     1  ---
     2  id: testnets
     3  ---
     4  
     5  # Gno Testnets
     6  
     7  This page documents all Gno.land testnets, what their properties are, and how
     8  they are meant to be used. For testnet configuration, visit the 
     9  [reference section](../reference/network-config).
    10  
    11  Gno.land testnets are categorized by 4 main points:
    12  - **Persistence of state**
    13    - Is the state and transaction history persisted?
    14  - **Timeliness of code**
    15    - How up-to-date are Gno language features and demo packages & realms?
    16  - **Intended purpose**
    17    - When should this testnet be used?
    18  - **Versioning strategy**
    19    - How is this testnet versioned?
    20  
    21  Below you can find a breakdown of each existing testnet by these categories.
    22  
    23  ## Portal Loop
    24  Portal Loop is an always up-to-date rolling testnet. It is meant to be used as 
    25  a nightly build of the Gno tech stack. The home page of [gno.land](https://gno.land)
    26  is the `gnoweb` render of the Portal Loop testnet. 
    27  
    28  - **Persistence of state:**
    29    - State is kept on a best-effort basis 
    30    - Transactions that are affected by breaking changes will be discarded
    31  - **Timeliness of code:**
    32    - Packages & realms which are available in the `examples/` folder on the [Gno
    33  monorepo](https://github.com/gnolang/gno) exist on the Portal Loop in matching 
    34  state - they are refreshed with every new commit to the `master` branch.
    35  - **Intended purpose**
    36    - Providing access the latest version of Gno for fast development & demoing
    37  - **Versioning strategy**:
    38    - Portal Loop infrastructure is managed within the
    39  [`misc/loop`](https://github.com/gnolang/gno/tree/master/misc/loop) folder in the 
    40  monorepo
    41  
    42  For more information on the Portal Loop, and how it can be best utilized, 
    43  check out the [Portal Loop concept page](./portal-loop.md).
    44  
    45  ## Staging
    46  Staging is a testnet that is reset once every 60 minutes.
    47  
    48  - **Persistence of state:**
    49    - State is fully discarded
    50  - **Timeliness of code:**
    51    - With every reset, the latest commit of the Gno tech stack is applied, including
    52    the demo packages and realms
    53  - **Intended purpose**
    54    - Demoing, single-use code in a staging environment, testing automation which
    55    uploads code to the chain, etc.
    56  - **Versioning strategy**:
    57    - Staging is reset every 60 minutes to match the latest monorepo commit
    58  
    59  ## Test4 (upcoming)
    60  Test4 (name subject to change) is an upcoming, permanent, multi-node testnet. 
    61  To follow test4 progress, view the test4 milestone
    62  [here](https://github.com/gnolang/gno/milestone/4).
    63  Once it is complete, it will have the following properties:
    64  
    65  - **Persistence of state:**
    66    - State is fully persisted unless there are breaking changes in a new release,
    67  where persistence partly depends on implementing a migration strategy
    68  - **Timeliness of code:**
    69    - Versioning mechanisms for packages & realms will be implemented for test4
    70  - **Intended purpose**
    71    - Running a full node, testing validator coordination, deploying stable Gno 
    72  dApps, creating tools that require persisted state & transaction history
    73  - **Versioning strategy**:
    74    - Test4 will be the first testnet to be release-based, following releases of
    75  the Gno tech stack.
    76  
    77  ## TestX
    78  These testnets are deprecated and currently serve as archives of previous progress.
    79  
    80  ### Test3
    81  Test3 is the most recent persistent Gno testnet. It is still being used, but 
    82  most packages, such as the AVL package, are outdated.
    83  
    84  - **Persistence of state:**
    85    - State is fully preserved
    86  - **Timeliness of code:**
    87    - Test3 is at commit [1ca2d97](https://github.com/gnolang/gno/commit/1ca2d973817b174b5b06eb9da011e1fcd2cca575)
    88  of Gno, and it can contain new on-chain code
    89  - **Intended purpose**
    90    - Running a full node, building an indexer, showing demos, persisting history  
    91  - **Versioning strategy**:
    92    - There is no versioning strategy for test3. It will stay the way it is, until
    93  the team chooses to shut it down.
    94  
    95  Since Gno.land is designed with open-source in mind, anyone can see currently 
    96  available code by browsing the [test3 homepage](https://test3.gno.land/). 
    97  
    98  Test3 is a single-node testnet, ran by the Gno core team. There is no plan to 
    99  upgrade test3 to a multi-node testnet. 
   100  
   101  Launch date: November 4th 2022  
   102  Release commit: [1ca2d97](https://github.com/gnolang/gno/commit/1ca2d973817b174b5b06eb9da011e1fcd2cca575)
   103  
   104  ### Test2 (archive)
   105  The second Gno testnet. Find archive data [here](https://github.com/gnolang/tx-exports/tree/main/test2.gno.land).
   106  
   107  Launch date: July 10th 2022  
   108  Release commit: [652dc7a](https://github.com/gnolang/gno/commit/652dc7a3a62ee0438093d598d123a8c357bf2499) 
   109  
   110  ### Test1 (archive)
   111  The first Gno testnet. Find archive data [here](https://github.com/gnolang/tx-exports/tree/main/test1.gno.land).
   112  
   113  Launch date: May 6th 2022  
   114  Release commit: [797c7a1](https://github.com/gnolang/gno/commit/797c7a132d65534df373c63b837cf94b7831ac6e)