Create combined flow-evm article #1430
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| @@ -93,7 +93,7 @@ Learn how to leverage Flow's native VRF capabilities in both Cadence and Solidit | |||
|
|
|||
| - [Secure Randomness with Commit-Reveal in Cadence] - Learn how to implement secure randomness in Cadence using Flow's commit-reveal scheme | |||
| - [VRF (Randomness) in Solidity] - Learn how to use Flow's native VRF capabilities in Solidity. | |||
| - [Deploy a Solidity Contract Using Cadence] - Discover how to deploy and interact with Solidity contracts on Flow EVM using Cadence | |||
| - Deploy a Solidity Contract Using Cadence - Discover how to deploy and interact with Solidity contracts on Flow EVM using Cadence | |||
There was a problem hiding this comment.
This formatting looks off in the rich diff.
Is something missing here?
There was a problem hiding this comment.
Good catch, we eliminated that one.
|
|
||
| ### Cadence development on Flow | ||
|
|
||
| Cadence is Flow's native smart contract language, offering unique advantages for developers: |
There was a problem hiding this comment.
I am not a fan of calling Cadence Flow's native smart contract language.
It makes it seem like just a simple technical choice vs a super power for devs.
I would just remove this "native" part and simply say.
Cadence is developed by top smart contract developers for crypto app builders, offering unique advantages for developers.
^ that can be word smithed some but the intention is Cadence is on Flow because it is a better tool. Not just because "its native". Developers should pick it because it is a better tool.
|
Replaced with #1447 to avoid an ocean of merge conflicts |
This PR creates a new/combined article from the following: