1176 - Migrate from other chains

[KMCreatesWorlds]

What does this PR fix/introduce?

This PR introduces the overview of how the move from some blockchains can be made to Casper.

Additional context

The PR gives insight into Ethereum, Near, Solana, and Aptos and how they compare to Casper regarding aspects such as Contract Lifecycle, State Management, or how to interact with the Contract.

This is not a comprehensive explanation of how the migration of a Contract for example on Ethereum can be made on Casper, but instead gives high-level hints on how to approach the individual aspects to make the move to Casper easier.

Checklist

• Docs are successfully building - yarn install && yarn run build.
• For new internal links I used relative file paths (with .md extension) - e.g. ../../faq/faq-general.md - instead of introducing absolute file path, or relative/absolute URL.
• All external links have been verified with yarn run check:externals.

Reviewers

@caspermel

[ipopescu]

Thanks for putting this together! Not an easy document to write, so it needs a bit more polishing.

I have submitted a thorough editing pass with PR #1183. Please take a look at this first. After reviewing my updates, please rename the file to moving-to-casper.md to remove any ambiguity with the word “migrate”.

In addition, I have a few more requests.

Please try to remove repeated explanations in the five categories you defined (lifecycle, storage, methods etc.). For example, we are referencing Named Keys and Dictionaries three times. Resources are defined twice.

State management can be combined with storage, actually. If you want to keep them separate, try to find another way to organize the content so there is less duplication.

I would like to see more links to coding examples. There are some, but many sections seem theoretical. You could link to any relevant topics (either in the Casper docs or externally).
For example, when explaining get_key, at a minimum, link to docs.rs. Also, point to the reading-and-writing-to-the-blockchain.md file.
This request applies to all concepts and explanations introduced.

Finally, a little more structure would be needed. For example, what are the comparison points in each tab? Are they covered for each blockchain?

Please also check the Casper docs style guidelines before submitting a PR. It's not in this PR's checklist, but it's not optional.

[ipopescu]

@KMCreatesWorlds @andrzej-casper Acknowledging the review request.

[ipopescu]

@KMCreatesWorlds, please address or respond to my requests from the previous review feedback. The document still needs some polishing. Summarizing my previous feedback here:

• rename the file to moving-to-casper.md to remove ambiguity with the word “migrate”
• try to remove repeated explanations in the five categories you defined (lifecycle, storage, methods, etc.). For example, we are referencing Named Keys and Dictionaries three times. Resources are defined twice.
• combine state management with storage; or try to find another way to remove duplication
• add cross-links to each topic in the Casper docs or link out to coding examples when introducing a concept/feature
• try to add the same structure in each tab. What are the comparison points in each tab? Are they covered for each blockchain?

cc @andrzej-casper @melpadden

[Adrian-Wrona]

@KMCreatesWorlds could you take a look at @ipopescu review feedback?

[github-actions]

🚀 Deployed on https://650432ee7d7cc5063a2a1e96--sensational-creponne-f0e56d.netlify.app

[ipopescu]

Thanks for the updates, @KMCreatesWorlds.
Here are a few minor edit requests. From the previous feedback, I see the following have been addressed - thanks!

• Renamed file to moving-to-casper.md
• Combined state management with storage
• Removed repeated definitions (Resouces, Named Keys, Dictionaries)

Let's discuss the following on the live call:

• Cross-links to each topic in the Casper docs or link out to coding examples
• Tab structure. What are the comparison points in each tab? Are they covered for each blockchain?

cc @ACStoneCL

[ipopescu]

I would move this higher, perhaps after build-on-casper.
Also, the table on the resouces/index.md page needs to be updated with this topic (the table matches the left nav order).

[ipopescu]

Let's discuss the following on the live call:

• Cross-links to each topic in the Casper docs or link out to coding examples
• Tab structure. What are the comparison points in each tab? Are they covered for each blockchain?

cc @ACStoneCL

Karol and I spoke and we are on the same page. We have cross-links for Casper, but we won't add links on the other tabs. Developers coming from other protocols should already be familiar with them.
Finally, the tabs have structure, but not every topic is a 1-to-1 mapping. This is ok.

[ipopescu]

I ran this locally and it looks great. Thank you, @KMCreatesWorlds!