Skip to content

Commit 57ca3af

Browse files
committed
Add Devnet info page
1 parent 3d696e7 commit 57ca3af

File tree

7 files changed

+20681
-2913
lines changed

7 files changed

+20681
-2913
lines changed

condor/condor.sidebar.js

+1
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ const sidebars = {
2525
'transactions',
2626
'validator-rewards',
2727
'zug',
28+
'devnet-info',
2829
],
2930
//
3031
// {

condor/devnet-info.md

+79
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
# Devnet Information
2+
3+
## What is Devnet?
4+
5+
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.
6+
7+
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.
8+
9+
## How can I access Devnet?
10+
11+
You can request access to Devnet using the provided form [here](https://forms.gle/NXYtoK7gPXB1iPP3A):
12+
13+
14+
Be sure to include a valid Casper public key in this form, which we will fund with CSPR tokens to allow you to test.
15+
16+
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.
17+
18+
## What is the latest commit/release candidate deployed on to the Devnet?
19+
20+
- Release Candidate: Condor/2.0.0 - RC6
21+
- Commit Hash: `2178ad3aad9488076b38d8de467e6d1123f4b66b`
22+
- Latest Devnet Release Date: 08-Jan-2025
23+
24+
## What are the Condor/2.0.0 Compatible branches/commits of downstream components?
25+
26+
**casper-sidecar:**
27+
- Release Candidate : `release-1.0.0-rc3_node-2.0.0-rc6`
28+
- Branch/Repo : [casper-sidecar-release-1.0.0-rc3_node-2.0.0-rc6](https://github.com/casper-network/casper-sidecar/tree/release-1.0.0-rc3_node-2.0.0-rc6)
29+
30+
**casper-client-rs:**
31+
- Release Candidate : WIP
32+
- Branch/Repo : WIP
33+
34+
**NCTL:**
35+
- New NCTL image with `v200-rc6` available on Docker Hub:
36+
- `makesoftware/casper-nctl:v200-rc6`
37+
38+
**CEP-18:**
39+
- A version of CEP-18 compatible with Condor RC5/6 is available in the forked repository [here](https://github.com/davidatwhiletrue/cep18-limited/tree/casper-2.0.0-rc5)
40+
41+
- Please note that this is meant for testing SDKs and scripts
42+
43+
**CEP-78:**
44+
- Work in progress
45+
46+
**SDKs:**
47+
- JavaScript/TypeScript
48+
- Github release : [casper-js-sdk-v5.0.3-beta2](https://github.com/casper-ecosystem/casper-js-sdk/releases/tag/5.0.3-beta2)
49+
- npm : [casper-js-sdk-v5.0.3-beta2](https://www.npmjs.com/package/casper-js-sdk/v/5.0.3-beta2)
50+
51+
- .NET
52+
- Github release : [casper-net-sdk-v3.0.0-beta2](https://github.com/make-software/casper-net-sdk/releases/tag/v3.0.0-beta2)
53+
- Nuget package : [Casper.Network.SDK 3.0.0-beta2](https://www.nuget.org/packages/Casper.Network.SDK/3.0.0-beta2)
54+
55+
- Go
56+
- Github release : [casper-go-sdk-v2.0.0-beta2](https://github.com/make-software/casper-go-sdk/releases/tag/v2.0.0-beta2)
57+
- Java (WIP)
58+
- Python (WIP)
59+
- Rust (WIP)
60+
- PHP (WIP)
61+
62+
NOTE:
63+
The SDKs have a couple of known serialisation issues. We're working on patch updates to address these issues.
64+
65+
## How can I explore the transactions in Devnet?
66+
67+
You can explore using the DevNet mini-explorer that points to the Devnet (RC6) at https://devnet.make.services/
68+
69+
Please note that SSE is listening at 52.90.123.125.
70+
71+
## How can I report a bug/issue when testing in Devnet?
72+
73+
Should you have any feedback, feature requests or face any issues or bugs, please file it using the GitHub Form [here](https://github.com/casper-network/casper-node/issues/new?assignees=devendran-m%2Cpiotr-dziubecki%2Csacherjj%2Ccspramit%2CSaiProServ&labels=condor-feedback&projects=&template=feedback.yml&title=%5BCondor-Release%5D%3A+Specify+your+feedback%2Fissue+briefly).
74+
75+
![issue form](../image_archive/condor/casper_condor_issue_form.png)
76+
77+
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.
78+
79+
Please refer to this [reference ticket](https://github.com/casper-network/casper-node/issues/4999) for information on providing all the required supporting information for a seamless analysis.
Loading

0 commit comments

Comments
 (0)