Aug 29

Status Update

• Mainnet Migration result – (state snapshot Aug 27th)
  • Report: https://github.com/onflow/cadence/blob/master/migrations_data/staged-contracts-report-2024-08-27T15-00-00Z-mainnet.md
    • 1310 contracts staged
    • 1271 successfully upgraded
    • 39 failed to upgrade
  • (latest: https://staging.dnz.dev/index.html)
• Last test migration before MN Crescendo upgrade: Monday Sep 2nd.
• Updated version of CLI
• 90% of on-chain data staged to be upgraded
  • 88% of capabilities staged to be upgraded
• Mainnet upgrade timeline
  • starting 5am PDT
  • ~5 hour downtime
  • ETA network up & running 10-11am PDT on Wed 4th

Q&A

Aug 22

Status Update

• Mainnet Migration result – Aug 21th

  • Report: https://github.com/onflow/cadence/blob/master/migrations_data/staged-contracts-report-2024-08-21T15-00-00Z-mainnet.md
    • 1067 contracts staged
    • 1012 successfully upgraded
    • 55 failed to upgrade
  • Changes since last week:
    • Enabled FLIP 282 (Import of pre-Cadence 1.0 Programs) implementation for Mainnet (https://github.com/onflow/flips/pull/283)
    • https://github.com/onflow/cadence/issues/3527
    • (https://github.com/onflow/cadence/issues/3534 (Discord thread).
    • Fixed a regression that made the Cadence state migration non-deterministic (https://github.com/onflow/cadence/issues/3536)

  Reminder

  • Crescendo is no longer in preview since launch on Testnet, https://flow.com/upgrade/crescendo/bounty-program is no longer reduced to 50% reward.

  Summary of Disaster Recovery Plan for Crescendo Mainnet launch

  • When an issue is discovered on production network (TN or MN), we always first evaluate fix by deploying a new software version (roll-forward approach to fixing an issue)
  • Situations we might need to use more disruptive methods to minimize the value at risk:
    • 🗝️ Exploit of a vulnerability leading to resource duplication or unauthorized account manipulation.
    1. 📀 Bug in a storage layer causing corruption of the on-chain data which is hard to revert. (hard to revert means that the effort to revert to uncorrupted state would take days, not hours).
    2. 📜 Security / usability issue that requires Cadence Language breaking change to be fixed.
    3. 💔  Broken dapp functionality as a result of a bug in the state migration.
  1. Methods we will consider to reduce impact, fix and recover the network:
     1. 🛑 Halting of transaction execution.
     2. ↩️ Roll-back of Flow software.
     3. 🗑️ Roll-back of Flow software and on-chain state.

Q&A

• Unmigrated placeholder capabilities (Discord thread: https://discord.com/channels/613813861610684416/1253820764193296555)
  • should not panic
• DUC, DapperBalance, Resolver

Aug 8

Status Update

• Testnet Migration result – Aug 5th

  • Updates
    • Mainnet launch Sep 4th
    • Announced Wrapped USDC to enable holders to swap pre-Crescendo or bridge to USDC on EVM after Crescendo launch.
      • ⚠️ USDC migration guide: https://github.com/onflow/cadence-lang.org/blob/461dd1e5298ca237f8d82126d9ca75e0319ebde2/versioned_docs/version-1.0/cadence-migration-guide/usdc-migration.mdx
  • report: https://github.com/onflow/cadence/blob/master/migrations_data/staged-contracts-report-2024-08-07T10-00-00Z-testnet.md
    • No change since last week
      • 797 contracts staged
      • 756 successfully upgraded
      • 41 failed to upgrade

  

Q&A

Jul 31