Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEATURE: Cadence 1.0 Core Contracts Changes #319

Open
wants to merge 130 commits into
base: master
Choose a base branch
from

Conversation

joshuahannan
Copy link
Member

@joshuahannan joshuahannan commented Nov 2, 2022

Includes changes related to Cadence 1.0

Many functions have been changed to view for new view function requirements
Updates casting to use correct as syntax
changes pub to access(all)
Adds entitlements
Uses the new fungible token standard and Burner contract
Removes custom destructors

joshuahannan and others added 4 commits July 13, 2023 11:36
* update to view functions for stable cadence

* remove unreachable code

* update templates to Stable Cadence

* update to Stable Cadence preview 4

* update for stable cadence

* fix parse error

---------

Co-authored-by: Josh Hannan <hannanjoshua19@gmail.com>
Co-authored-by: Bastian Müller <bastian@axiomzen.co>
* Don't copy dictionary in getEpochMetadata
@joshuahannan joshuahannan requested review from jordanschalm, janezpodhostnik and sisyphusSmiling and removed request for bluesign May 7, 2024 16:42
@joshuahannan
Copy link
Member Author

I think we're basically ready to merge this to master, so I added a few people who might be able to give it a review! The changes are fairly straightforward, just lots of boilerplate updates to be compatible with the new token standards and Cadence 1.0. Let me know if you'd like to chat with me first about the changes before you review.

Copy link
Collaborator

@janezpodhostnik janezpodhostnik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mostly checked the changes to the contracts

Copy link
Contributor

@sisyphusSmiling sisyphusSmiling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leaving a few follow up questions about entitlements. They're probably alright, I just lack the context to understand if there's any risk of down casting from public capabilities.

contracts/FlowContractAudits.cdc Show resolved Hide resolved
contracts/FlowServiceAccount.cdc Show resolved Hide resolved
contracts/FlowServiceAccount.cdc Show resolved Hide resolved
contracts/FlowStakingCollection.cdc Show resolved Hide resolved
contracts/FlowStakingCollection.cdc Show resolved Hide resolved
contracts/LockedTokens.cdc Show resolved Hide resolved
contracts/LockedTokens.cdc Show resolved Hide resolved
contracts/LockedTokens.cdc Show resolved Hide resolved
contracts/StakingProxy.cdc Show resolved Hide resolved
contracts/epochs/FlowClusterQC.cdc Show resolved Hide resolved
@joshuahannan
Copy link
Member Author

@sisyphusSmiling The changes were big enough that I just created a PR with them for you to review. Can you take a look?
#429

* better use of  revertible random with correct types

* improve random distribution
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants