Devnet Information
What is Devnet?
The Casper 2.0 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: Casper 2.0 - RC10
- Commit Hash:
a7e4ff100549d6b34aa6b800812f29313378663b
- Latest Devnet Release Date: 04-Apr-2025
What are the Casper 2.0 Compatible branches/commits of downstream components?
casper-sidecar:
- Release Candidate :
v1.0.4
- Branch/Repo : casper-sidecar-v1.0.4
casper-client-rs:
- Release Candidate :
v3.0.1
- Branch/Repo : casper-client-v3.0.1
NCTL:
- New NCTL image with
v200-rc10
available on Docker Hub:makesoftware/casper-nctl:v200-rc10
CEP-18:
- A version of CEP-18 compatible with Casper 2.0 is available in the forked repository here
CEP-78:
- A version of CEP-78 compatible with Casper 2.0 is available in the forked repository here
SDKs:
-
JavaScript/TypeScript
- Github release : casper-js-sdk-5.0.6
- npm : casper-js-sdk
-
.NET
- Github release : casper-net-sdk-v3.0.0
- Nuget package : Casper.Network.SDK 3.0.0
-
Go
- Github release : casper-go-sdk-2.0.3-beta1
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 https://devnet.cspr.live/
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.
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.