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
The cryptocontract offers crypto tools that are fully developed in the cadence language and don't have to be built-in in the language. It makes more sense to take the crypto contract outside of the Cadence repo and add it as an independent standard library core-contract.
This issue is a follow-up on the discussion in #1447 (comment)
Suggested Solution
Moving the Crypto contract out of Cadence will require:
Given the effort required to complete this (moving this as a separate contract, updating all contracts to import this) it is unlikely we can complete it in C1.0. It might need to stay where it is.
I feel like if something breaking will be done here, better to moving native types ( HashAlgorithm.etc ) inside crypto in a native way. Crypto being pure Cadence has no value for the future. If we later have add something that is not in pure Cadence ( which seems pretty likely in the crypto context ) at least we can prevent polluting global namespace.
Issue to be solved
The
crypto
contract offers crypto tools that are fully developed in the cadence language and don't have to be built-in in the language. It makes more sense to take thecrypto
contract outside of the Cadence repo and add it as an independent standard library core-contract.This issue is a follow-up on the discussion in #1447 (comment)
Suggested Solution
Moving the Crypto contract out of Cadence will require:
Move tests (small)
No additional work in the contract itself is required, we had already previously refactored it to be deployable like any other contract
The text was updated successfully, but these errors were encountered: