You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: condor/migration-guide.md
+3-8
Original file line number
Diff line number
Diff line change
@@ -60,9 +60,9 @@ Please see instructions below for your specific SDK language:
60
60
- If you are using an SDK not listed in this chapter, please contact the Casper Exchange Support Team.
61
61
62
62
63
-
## Important changes/updates in Casper 2.0(Placeholder - Core Team input required)
63
+
## Important changes/updates in Casper 2.0
64
64
65
-
Casper 2.0 introduces new block structures, transaction formats and retrograde support. More details can be found below/here (LINK or content below).
65
+
Casper 2.0 introduces new block structures, transaction formats and retrograde support. More details can be found below.
66
66
67
67
### 1. New Block Structure
68
68
@@ -108,7 +108,7 @@ At the same time, Casper 1.x deploys will continue to be accepted by Casper 2.0,
108
108
109
109
- Common scenarios where the sidecar may disconnect and how to mitigate them.
110
110
111
-
## Minimal vs. Full Migration (Placeholder - Core Team input required)
111
+
## Minimal vs. Full Migration
112
112
113
113
It is highly recommended to switch entirely to new API endpoints and adopt new transaction formats.
114
114
@@ -117,11 +117,6 @@ However, where full migration is not feasible in the short term, exchanges may c
117
117
Minimal migration will be adapting new block and transaction structures.
118
118
119
119
120
-
## Common Integration Issues (Placeholder - Core Team input required)
121
-
122
-
Placeholder: Cover anticipated issues, including transaction failures and undelegation nuances.
123
-
124
-
125
120
## Casper Exchange Support Team
126
121
As an exchange, you likely already have a shared Telegram or Slack channel with the Casper Exchange Support Team. Please keep the Casper team apprised of your progress on migration, as we want to ensure that on the one hand you receive all the possible support from us, and on the other we track ecosystem readiness for Casper 2.0, of which you are an essential component.
0 commit comments