Incomplete contracts deployed printed at emulator startup
Opened this issue · 0 comments
bjartek commented
flow-c1 emulator -v
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
⚠ Upgrade to Cadence 1.0
The Crescendo network upgrade, including Cadence 1.0, is coming soon.
You may need to update your existing contracts to support this change.
Please visit our migration guide here:
https://cadence-lang.org/docs/cadence_migration_guide
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1:14PM INF ⚙️ Using service account 0xf8d6e0586b0a20c7 serviceAddress=f8d6e0586b0a20c7 serviceHashAlgo=SHA3_256 servicePrivKey=a23c739c95a4550e1cdadd475556b2ab0eea29ca3feae886137a70580a13c56b servicePubKey=ee3ad03d0e430e3d7f04ee9a6894c1a096a8606a204aeb9f4746557f0b270caf2518c5487f087c05fc4847651682d4533c4c81068868ebec5255aca09212eafc serviceSigAlgo=ECDSA_P256
1:14PM INF 📜 Flow contract EVM=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract FlowClusterQC=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract FlowDKG=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract FlowEpoch=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract FlowFees=0xe5a8b7f23e8b548f
1:14PM INF 📜 Flow contract FlowIDTableStaking=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract FlowServiceAccount=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract FlowStorageFees=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract FlowToken=0x0ae53cb6e3f42a79
1:14PM INF 📜 Flow contract FungibleToken=0xee82856bf20e2aa6
1:14PM INF 📜 Flow contract MetadataViews=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract NodeVersionBeacon=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract NonFungibleToken=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract RandomBeaconHistory=0xf8d6e0586b0a20c7
1:14PM INF 📜 Flow contract ViewResolver=0xf8d6e0586b0a20c7```
This list of deployed contracts is not complete. For instance 0xee82856bf20e2aa6 has more contracts. This is very confusing when configuring new projects and can lead to people deploying invalid versions of contracts.