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
With upcoming breaking changes to Cadence (Cadence 1.0) requiring all developers to upgrade their contracts, it is important that we utilize as many channels of communication to developers as possible. FCL-JS is one of the most widely used codebases by dApp developers and arguably one of Flow's most effective channels of developer messaging. Therefore, some form of Cadence 1.0 messaging should be added to FCL-JS in order to alert developers about these upcoming changes.
Potentially integrate into FCL discovery/wallets somehow, display to users that contract has not been updated when approaching Cadence 1.0 release date? (if tenable, would not require installation of new FCL version
Other?
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered:
Issue to be solved
With upcoming breaking changes to Cadence (Cadence 1.0) requiring all developers to upgrade their contracts, it is important that we utilize as many channels of communication to developers as possible. FCL-JS is one of the most widely used codebases by dApp developers and arguably one of Flow's most effective channels of developer messaging. Therefore, some form of Cadence 1.0 messaging should be added to FCL-JS in order to alert developers about these upcoming changes.
Suggest A Solution
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered: