Skip to main content

Devnet Information

What is Devnet?​

The Casper Condor release is being rolled out in a phased fashion, allowing people to test their code, SDKs and smart contracts, before migrating to Mainnet. The first phase of this is rolling out to Devnet.

This article/FAQ is a guide to the process for gaining access to Devnet, what to expect when you do access Devnet, and any other concerns.

How can I access Devnet?​

You can request access to Devnet using the provided form here:

Be sure to include a valid Casper public key in this form, which we will fund with CSPR tokens to allow you to test.

Once your request has been processed, you will be notified and provided with a list of IP addresses to which you can connect to DevNet.

What is the latest commit/release candidate deployed on to the Devnet?​

  • Release Candidate: Condor/2.0.0 - RC6
  • Commit Hash: 2178ad3aad9488076b38d8de467e6d1123f4b66b
  • Latest Devnet Release Date: 08-Jan-2025

What are the Condor/2.0.0 Compatible branches/commits of downstream components?​

casper-sidecar:

casper-client-rs:

NCTL:

  • New NCTL image with v200-rc6 available on Docker Hub:
    • makesoftware/casper-nctl:v200-rc6

CEP-18:

  • A version of CEP-18 compatible with Condor RC5/6 is available in the forked repository here

  • Please note that this is meant for testing SDKs and scripts

CEP-78:

  • Work in progress

SDKs:

NOTE: The SDKs have a couple of known serialisation issues. We're working on patch updates to address these issues.

How can I explore the transactions in Devnet?​

You can explore using the DevNet mini-explorer that points to the Devnet (RC6) at https://devnet.make.services/

Please note that SSE is listening at 52.90.123.125.

How can I report a bug/issue when testing in Devnet?​

Should you have any feedback, feature requests or face any issues or bugs, please file it using the GitHub Form here.

issue form

We appreciate you taking the time to file your feedback and/or issues/bugs. Please provide as much information as possible, especially in case of an issue or a bug. It would be advantageous for the team to conduct a comprehensive analysis and respond promptly.

Please refer to this reference ticket for information on providing all the required supporting information for a seamless analysis.