From 59600300c2f87e5245d87c4025cfcc95b99b156b Mon Sep 17 00:00:00 2001 From: Devendran Date: Wed, 19 Mar 2025 17:00:48 +0530 Subject: [PATCH 1/3] Fix errors in migration guide --- condor/migration-guide.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/condor/migration-guide.md b/condor/migration-guide.md index 2be7a4b9..ad5c46ec 100644 --- a/condor/migration-guide.md +++ b/condor/migration-guide.md @@ -14,9 +14,9 @@ Whether you need to migrate before Casper 2.0’s Mainnet launch depends on your | Integration Type | Required actions | |---------------------|-------------| -| **Indirect integration via 3rd party Partner [ⓘ](a "Exchanges that don’t directly integrate with Casper Network but use liquidity from other exchanges via APIs.")** | No migration required, assuming the partner updates their integration.| -| **[Running your own node](#) [ⓘ](a "Exchanges that run their own node and interface with its RPC methods")** | Node software upgrade is required | -| **[SDK Integration](#) [ⓘ](a "Exchanges that use the publicly available Casper SDKs(e.g. JavaScript SDK, C#.NET SDK, Go SDK, etc.)")** | Depending on the SDK language (e.g. JS, Go) and the methods you use, upgrade to a Casper 2.0 compatible version is required| +| **Indirect integration via 3rd party Partner ⓘ** | No migration required, assuming the partner updates their integration.| +| **[Running your own node](#) ⓘ** | Node software upgrade is required | +| **[SDK Integration](#) ⓘ** | Depending on the SDK language (e.g. JS, Go) and the methods you use, upgrade to a Casper 2.0 compatible version is required| More information about the specific changes in, and features introduced by Casper 2.0 can be found [here](https://docs.casper.network/condor/index). @@ -93,7 +93,8 @@ At the same time, Casper 1.x deploys will continue to be accepted by Casper 2.0, - New API endpoints and modifications to existing ones - Expected changes in response formats ->[!IMPORTANT] +> **IMPORTANT** +> > **Deprecation of 1.x Structures (e.g. Deploys)** > > **1.x structures, such as Deploys, are being deprecated.** While they will continue to function in **Casper 2.0**, they are scheduled to be phased out. @@ -130,9 +131,9 @@ Email: Casper Exchange Support: exchange-support@casper.network ## Summary Casper 2.0 is coming to Mainnet in the very foreseeable future, and we're honored and excited that you and your user community are part of this massively consequential event in the history of the Casper blockchain. In order to make sure you and your users are prepared for the Mainnet activation of Casper 2.0, please follow these steps: -Determine your [current type of integration](https://docs.make.software/exchange-migration-draft#should-i-migrate-my-integration) with Casper Network +Determine your current type of integration with the Casper Network. Refer to the "Should I update my integration?" section to identify your integration type. -If your integration type requires a migration, follow the [Migration Documentation](https://docs.make.software/exchange-migration-draft#integration-specific-migration-documentation) for your integration +If your integration type requires a migration, follow the respective migration process for your integration as outlined in the sections above. Actively communicate with the [Casper Exchange Support Team](https://docs.make.software/exchange-migration-draft#casper-exchange-support-team), to receive support for a successful migration, and to allow Casper to track ecosystem readiness. From 9f361a377c3668c33b82afc8728f78c0652d0815 Mon Sep 17 00:00:00 2001 From: Devendran Date: Thu, 20 Mar 2025 15:51:04 +0530 Subject: [PATCH 2/3] Fix support team link --- condor/migration-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/condor/migration-guide.md b/condor/migration-guide.md index ad5c46ec..cba684a1 100644 --- a/condor/migration-guide.md +++ b/condor/migration-guide.md @@ -135,7 +135,7 @@ Determine your current type of integration with the Casper Network. Refer to the If your integration type requires a migration, follow the respective migration process for your integration as outlined in the sections above. -Actively communicate with the [Casper Exchange Support Team](https://docs.make.software/exchange-migration-draft#casper-exchange-support-team), to receive support for a successful migration, and to allow Casper to track ecosystem readiness. +Actively communicate with the [Casper Exchange Support Team](https://docs.casper.network/condor/migration-guide#casper-exchange-support-team), to receive support for a successful migration, and to allow Casper to track ecosystem readiness. From e7f5ab6c27a7805d2908c9bc781eb714c8f50f2d Mon Sep 17 00:00:00 2001 From: Muhammet Kara Date: Thu, 20 Mar 2025 14:40:05 +0300 Subject: [PATCH 3/3] Update migration-guide.md to use relative links within the page --- condor/migration-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/condor/migration-guide.md b/condor/migration-guide.md index cba684a1..186a69c7 100644 --- a/condor/migration-guide.md +++ b/condor/migration-guide.md @@ -131,11 +131,11 @@ Email: Casper Exchange Support: exchange-support@casper.network ## Summary Casper 2.0 is coming to Mainnet in the very foreseeable future, and we're honored and excited that you and your user community are part of this massively consequential event in the history of the Casper blockchain. In order to make sure you and your users are prepared for the Mainnet activation of Casper 2.0, please follow these steps: -Determine your current type of integration with the Casper Network. Refer to the "Should I update my integration?" section to identify your integration type. +Determine your current type of integration with the Casper Network. Refer to the "[Should I update my integration?](#should-i-update-my-integration)" section to identify your integration type. If your integration type requires a migration, follow the respective migration process for your integration as outlined in the sections above. -Actively communicate with the [Casper Exchange Support Team](https://docs.casper.network/condor/migration-guide#casper-exchange-support-team), to receive support for a successful migration, and to allow Casper to track ecosystem readiness. +Actively communicate with the [Casper Exchange Support Team](#casper-exchange-support-team), to receive support for a successful migration, and to allow Casper to track ecosystem readiness.