adding sprint kick off doc for 12/13/2024

agendas/2024/sprint-kickoff/2024-12-13-Flow-Sprint-Kickoff.md

@@ -0,0 +1,220 @@
+# Overview
+
+ ### Team Wins 🎉
+
+ * 
+
+--- 
+
+### Mainnet Uptime - Last 14 days (11/30/24 to 12/13/24) \[JP]
+
+|                         | Target | Current Score | Error budget used |
+|:------------------------|:------:|:-------------:|:-----------------:|
+| Collection Finalization | 99.9%   |    100%       |       0%         |
+| Block Finalization      | 99.9%   |    100%       |       0%         |
+| Transaction Execution   | 99.9%   |    100%       |       0%         |
+| Block Sealing           | 99.9%   |    100%       |       0%         |
+| Access API Liveness     | 99.9%   |    99.97%     |       32.2%      |
+
+#### Incidents
+* 
+
+
+---
+
+
+# Working Group Updates
+
+### **Cadence and Virtual Machine** \[Jan]
+Cycle Objective(s):
+
+1) Upgrade Mainnet to Crescendo Release with minimal impact on developers, to lower the barrier for cross chain liquidity on Flow
+2) Calibrate Transaction fees so that they accurately reflect resource usage during execution and deploy as part of Crescendo to avoid future disruption.
+3) Analyze execution runtime trends and risks to plan next set of scalability OKRs.
+
+* Stretch-goals:
+4) Expand testing capability of storehouse so that we can validate execution correctness and benchmark performance on Mainnet data
+5) Design a new Trie to improve performance of update operation, reduce memory usage and size of proofs and to support more flexible proof queries.
+6) Enable Concurrent Execution on one EN on Mainnet to validate correctness of the implementation (Detect execution forks)
+7) Improve execution performance to mitigate the impact of adding metadata to token standards
+
+**Done last sprint**
+
+* 
+
+**This sprint**
+
+* 
+
+**On Hold**
+
+Objective 2: Calibrate Transaction fees so that they accurately reflect resource usage during execution and deploy as part of Crescendo to avoid future disruption
+- KR1: Update weights for the execution operations on TN and MN
+  - [Execution effort recalibration - data collection](https://github.com/onflow/flow-go/issues/5026)
+
+
+**Active Epics**
+
+Objective 1: Upgrade Mainnet to Crescendo Release with minimal impact on developers, to lower the barrier for cross chain liquidity on Flow
+- KR1: Enable Developers and the Flow Foundation to simulate Cadence 1.0 Contract upgrades
+- KR2: Launch Cadence 1.0 on Crescendo Testnet
+- KR3: Launch EVM on Crescendo Testnet
+Objective 3: Analyze execution runtime trends and risks to plan next set of scalability OKRs
+- KR1: Measure execution state growth trends, identify future bottlenecks and prioritize by urgency
+
+---
+
+### **Core Protocol** \[Jerome]
+Cycle Objective(s): 
+
+* Translate crypto performance improvements to consensus block rate increase
+* Provide developers secure and non-rate limited way to access all of chain data (transactions, blocks, account balance, events, account balance etc) by locally running an access or an observer node
+* Reduce CPU usage on Execution node by 30%
+* Continue BFT mitigations to enable 10 permissionless ANs
+* Continue design of Dynamic Protocol 
+
+**Done last sprint**
+
+* 
+
+**This sprint**
+
+* 
+
+**On Hold**
+* Deliver public roadmap & vision for technical protocol decentralization focusing on current challenges and upcoming updates for permissionless consensus on Flow.
+
+**Active Epics**
+
+- Reinforcing Flow’s commitment to full protocol autonomy and scalability
+- Improve network performance
+- Improve network availability 
+- Simplify community contributions to core protocol and maintainability
+- Improve network reliability and data availability for dApp developers
+- Data-driven Prioritization and Scaling Engineering
+
+---
+
+### **DeFi** \[Jerome]
+
+Cycle Objective(s): 
+- Resolving Circle's existing engineering improvements for USDC on Flow
+- DEX Prep - IncrementFi
+- Bridge Prep - Axelar
+
+**Done last sprint**
+
+* 
+
+**This sprint**
+
+*
+
+**On Hold**
+- N/A
+
+**Active Epics**
+
+- Establish Defi/Liquidity infrastructure for Cadence 1.0 update
+- Ensure Flow has best-in-class on- and off-ramps for USDC liquidity across DeFi ecosystem
+- Expand Flow DeFi ecosystem primitives and protocols
+
+---
+
+### **User Experience** \[Greg]
+
+Cycle Objective(s): 
+- Bring Cadence 1.0 to market as part of the Crescendo release to minimize customer impact and developer effort
+- Bring EVM on Flow to Market as part of the Crescendo release to increase liquidity and bring top-tier developer platforms to our network
+- Use the Crescendo Release grow Flow's developer base and network activity
+
+**Done last sprint**
+
+*
+
+**This sprint**
+
+**Sprint goal focusing on adding docs and tool support for Crescendo network and Cadence 1.0**
+
+- [Add Crescendo network support to FCL Discovery](https://github.com/orgs/onflow/projects/13/views/85?pane=issue&itemId=50332654)
+- [Add Crescendo Network to CLI (config, cmds, docs, etc)](https://github.com/orgs/onflow/projects/13/views/85?pane=issue&itemId=50297186)
+- [Add/Publish Initial EVM Docs](https://github.com/orgs/onflow/projects/13/views/85?pane=issue&itemId=51952883)
+- [Docs Revamp v3](https://github.com/orgs/onflow/projects/13/views/85?pane=issue&itemId=49327073)
+- [Add C1.0 Rules to Cadence Linter](https://github.com/orgs/onflow/projects/13/views/85?pane=issue&itemId=51952640)
+- [Update Playground to support Cadence 1.0](https://github.com/orgs/onflow/projects/13/views/85?pane=issue&itemId=49844013)
+- [Stable Cadence Installation Workflow](https://github.com/orgs/onflow/projects/13/views/85?pane=issue&itemId=51951905)
+
+
+**On Hold**
+
+- [Update Flowport for Cadence Crescendo instance](https://github.com/orgs/onflow/projects/13/views/85?pane=issue&itemId=51960824)
+
+---
+
+### **Wallet** \[Jeff]
+
+Cycle Objective(s): 
+
+- Ensure there exists a wallet ecosystem supports FlowEVM
+  - Release version 2.2 of Flow Wallet which supports FlowEVM
+    - Support Authn / Authz / User Sign with Web3.js and WalletConnect
+    - Support FT and NFT management cross VMs
+    - FlowEVM onboarding and COA creation
+  - Ensure commitments from key EVM wallet providers to support FlowEVM
+    - Secure FlowEVM as an option in the network selector list for MetaMask.
+    - Reach out to Coinbase wallet for a commitment to support FlowEVM
+  - Ensure commitments from key EVM wallet providers to support FlowEVM
+    - Reach out to Privy for a commitment to support FlowEVM
+    - Reach out to Bastion for a commitment to support FlowEVM
+    - Ensure awareness for existing Cadence aware wallet (aside from Flow Wallet) to support FlowEVM
+  - Provide a design document outlining the steps existing Cadence aware wallets can take to support FlowEVM.
+    - Reach out to Blocto for a commitment to support FlowEVM
+    - Reach out to Shadow wallet for a commitment to support FlowEVM
+    - Reach out to Magic for a commitment to support FlowEVM
+
+- Promote safe, human readable transaction authorization on Flow
+  - Secure a partnership with Blockaid to integrate their transaction simulation and security platform with FlowEVM.
+  - Ensure the existing MetaMask Blockaid integration is compatible with FlowEVM.
+
+- Modernize and improve FCL Discovery
+  - Create a PRD and associated community bounty/grant for UI/UX improvements and analytics additions to FCL Discovery.
+
+**Done last sprint**
+
+- N/A
+
+**This sprint**
+
+- Begin creating developer documentation highlighting FlowEVM
+- Updating cadence transactions / scripts for Cadence 1.0
+- Begin executing on FlowEVM updates to Flow Wallet
+- Scheduled calls with MetaMask and Coinbase Wallet teams to intro FlowEVM and gather their requirements.
+
+**On Hold**
+
+- N/A
+
+**Active Epics**
+
+- TBD
+
+---
+
+### **Infra - JP**
+Cycle Objective(s): 
+- Migrate Flow metrics & logs to Flow Foundation grafana account to reduce cost on DapperLabs
+
+**Done last sprint**
+
+* 
+
+**This sprint**
+
+**Goal of Sprint is to migrate from DapperLabs account to FlowFoundation account** 
+
+* 
+
+**On Hold**
+**Active Epics**
+
+---