diff --git a/roadmap/entries/data-chain_fusion.json b/roadmap/entries/data-chain_fusion.json index a9eb708026..bc15dfe8b1 100644 --- a/roadmap/entries/data-chain_fusion.json +++ b/roadmap/entries/data-chain_fusion.json @@ -35,26 +35,6 @@ "eta": "Q4 2024", "eta_to_render": "" }, - { - "title": "Dogecoin Integration", - "is_milestone": true, - "description": "With this milestone, chain fusion is extended to offer support for Dogecoin, allowing canister smart contracts to hold and transfer Dogecoin in a decentralized way.", - "milestone_id": "Meridian", - "status": "future", - "eta_to_render": "" - }, - { - "title": "Native Dogecoin integration", - "overview": "Native Dogecoin integration will extend ICP replicas to also follow the Dogecoin network and collect its UTXO set in a special Dogecoin canister. This allows canisters on ICP to securely read the Dogecoin state. Combined with the existing threshold ECDSA signing functionality, this allows canisters to securely hold and transfer native dogecoin.", - "status": "future", - "milestone_id": "Meridian" - }, - { - "title": "ckDOGE", - "overview": "Building on the native Dogecoin integration, ckDOGE is a twin token to native Doge, offering fast transaction speeds and low fees. Furthermore, ckDOGE makes it easy to use the Dogecoin integration for canister smart contracts, as it follows the existing ICRC token standards.", - "status": "future", - "milestone_id": "Meridian" - }, { "title": "EVM in a canister", "overview": "An low-fee, high-performance EVM implemented as set of canisters on ICP with trustless integration with the Bitcoin network.", diff --git a/roadmap/entries/data-decentralization.json b/roadmap/entries/data-decentralization.json index c45014f66d..fb544b70a2 100644 --- a/roadmap/entries/data-decentralization.json +++ b/roadmap/entries/data-decentralization.json @@ -13,9 +13,22 @@ "is_community": false, "in_beta": false }, + { + "title": "SEV-SNP-protected API Boundary Nodes", + "overview": "Security for API boundary nodes is improved using trusted execution (AMD SEV-SNP), enabling anyone to attest that the correct software is running.", + "forum": "https://forum.dfinity.org/t/long-term-r-d-boundary-nodes-proposal/9401", + "proposal": "https://dashboard.internetcomputer.org/proposal/35671", + "docs": "", + "eta": "", + "milestone_id": "Levitron", + "status": "upcoming", + "is_community": true, + "in_beta": false, + "imported": true + }, { "title": "Public API Boundary Node logs and metrics", - "overview": "Ensuring logs are verifiable and trustworthy (e.g., signed by API BNs) and publishing them in a publicly accessible repository.", + "overview": "Anyone can analyze the API boundary node access logs to gain insights into app usage patterns etc.", "forum": "", "proposal": "", "milestone_id": "Levitron", @@ -29,16 +42,11 @@ "title": "Decentralized access logs and metrics", "is_milestone": true, "milestone_id": "Levitron", - "description": "This milestone enhances visibility into the Internet Computer's edge infrastructure by making aggregated API boundary node access logs publicly accessible. Developers gain valuable insights into their dapps' usage patterns, enabling traffic analysis and user statistics. To ensure log integrity and verifiability, this milestone builds on the trusted execution environments introduced in Magnetosphere.", + "description": "This milestone establishes visibility into the Internet Computer's edge infrastructure by making aggregated API boundary node access logs publicly accessible. This provides developers with valuable insights into their dapps' usage patterns and facilitates the generation of user statistics, offering key information on traffic sources. To guarantee the integrity of these logs, the milestone focuses on leveraging trusted execution environments, specifically AMD SEV-SNP.", "status": "in_progress", + "eta": "", "eta_to_render": "" }, - { - "title": "Privacy-Preserving Logs", - "overview": "Anonymizing identifying data while enabling global analysis across all API BNs (e.g., counting unique IPs), achieved through a secret salt managed by an NNS-controlled canister and shared among all API BNs.", - "status": "in_progress", - "milestone_id": "Levitron" - }, { "title": "Subnet rental", "overview": "Anyone can rent subnets created with possibly different decentralization properties than mainnet, and have full control over the subnet's resources.", @@ -72,17 +80,6 @@ "in_beta": false, "imported": true }, - { - "title": "Support public contributions to the dfinity/ic GitHub repository", - "overview": "The dfinity/ic GitHub repository, which provides an implementation for the Internet Computer Protocol, was made public in July 2024. This allowed the community to see all branches and Pull Requests that were created by the DFINITY Foundation and thus increased transparency. There’s more and more demand from the community to be able to make contributions to this repository. Currently this process is cumbersome and this feature is about streamlining the process and making it more user friendly. This milestone aims to create a process and technical means to support public contributions to the ic repository. It includes ensuring that no secrets can be leaked via DFINITY’s CI processes, no unauthorised access can be gained to DFINITY’s internal infrastructure and that no bad or malicious code can be merged", - "forum": "", - "proposal": "", - "docs": "", - "eta": "", - "status": "in_progress", - "is_community": false, - "in_beta": false - }, { "title": "Performance-based node provider rewards", "overview": "Node rewards are awarded according to the node's contributions to the protocol, based on trustworthy node metrics, which are provided and signed by the IC network itself. This creates a cryptoeconomic incentive to encourage honest node provider behaviour.", @@ -113,7 +110,7 @@ "proposal": "", "docs": "", "eta": "", - "status": "future", + "status": "upcoming", "is_community": false, "in_beta": false, "imported": true @@ -126,7 +123,7 @@ "docs": "", "is_community": false, "in_beta": false, - "status": "future" + "status": "upcoming" }, { "title": "CDN canisters on edge infrastructure", diff --git a/roadmap/entries/data-digital_assets.json b/roadmap/entries/data-digital_assets.json index 2d63ebcea4..4febddec6f 100644 --- a/roadmap/entries/data-digital_assets.json +++ b/roadmap/entries/data-digital_assets.json @@ -1,10 +1,10 @@ { "categoryName": "Digital Assets", - "categoryDescription": "DeFi protocols, real-word asset tokenization, and other digital asset solutions are strong drivers of Web3 adoption. ICP’s Chain Fusion capabilities, unparalleled scalability, and the ability to serve web assets from chain opens up novel digital asset classes. Moreover, it makes ICP an attractive platform to build multi chain custody solutions and wallets.", + "categoryDescription": "DeFi protocols, real-word asset tokenization, and other digital asset solutions are strong drivers of web3 adoption. ICP’s Chain Fusion capabilities, unparalleled scalability, and the ability to serve web assets from chain opens up novel digital asset classes. Moreover, it makes ICP an attractive platform to build multi chain custody solutions and wallets.", "elements": [ { "title": "Solana Integration", - "overview": "OISY widens its multichain reach beyond Bitcoin and Ethereum, and will integrate with the most important networks. Solana is the first one to be implemented, a crucial step forward in our mission to deliver a true multichain wallet for decentralized finance (DeFi) users.", + "overview": "OISY widens its multi-chain reach beyond Bitcoin and Ethereum, and will integrate with the most important networks. Solana is the first one to be implemented, a crucial step forward in our mission to deliver a true multi-chain wallet for decentralized finance (DeFi) users.", "status": "in_progress", "forum": "", "proposal": "", @@ -37,12 +37,12 @@ }, { "title": "OISY Wallet v1.0 - The official Launch", - "description": "With the Helios release, officially named v1.0, OISY will step out of the beta status into its first production version. This includes functional coverage of all key features like buy, receive, send, swap, and convert from and to chain-key tokens, and with several major blockchains integrated, also a true multichain nature. Behind the scenes, it also includes setting up proper processes for product improvement, marketing, automated testing, and setting up a user friendly support process.", + "description": "With the Helios release, officially named v1.0, OISY will step out of the beta status into its first production version. This includes functional coverage of all key features like buy, receive, send, swap, and convert from and to chain-key tokens, and with several major blockchains integrated, also a true multi-chain nature. Behind the scenes, it also includes setting up proper processes for product improvement, marketing, automated testing, and setting up a user friendly support process.", "is_milestone": true, "milestone_id": "Helios", "status": "in_progress", "eta": "", - "eta_to_render": "February 2025" + "eta_to_render": "January 2025" }, { "title": "Orbit Multi custody wallet for ICP", @@ -86,131 +86,6 @@ "eta": "", "eta_to_render": "February 2025" }, - { - "title": "Enterprise-grade Ledgers", - "description": "This milestone extends the ICRC suite of ledger standards to meet enterprise requirements, unlocking key use cases such as stablecoins, Utopia, and the tokenization of real-world assets, driving the future of trustless digital asset management on the Internet Computer.", - "status": "in_progress", - "is_milestone": true, - "milestone_id": "Nexus", - "eta_to_render": "" - }, - { - "title": "CMTAT Ledger", - "overview": "Building a secure and scalable ledger on the Internet Computer with transparent access control management. By adhering to the CMTAT standard, management access remains verifiable and auditable, ensuring regulatory compliance.", - "status": "in_progress", - "milestone_id": "Nexus" - }, - { - "title": "Expanded Orbit Framework", - "description": "Orbit is a secure solution for digital assets and smart contract management, and this milestone will broaden its asset management capabilities by enabling seamless integration of native tokens from other blockchains, starting with ETH and ERC-20. This will create a unified platform for treasury management, allowing users to securely sign and send transactions across multiple chains. Additionally, we will introduce automatic smart contract upgrades, ensuring that users always have access to the latest security updates and features with minimal manual intervention.", - "status": "future", - "is_milestone": true, - "milestone_id": "Echelon", - "eta_to_render": "" - }, - { - "title": "ETH and ERC-20 Integration", - "overview": "Users will be able to sign and send ETH transactions through their Orbit Station, leveraging the Internet Computer EVM RPC canister.", - "status": "future", - "milestone_id": "Echelon" - }, - { - "title": "Automatic upgrades", - "overview": "A streamlined update system will allow users to subscribe for automatic contract updates, ensuring they stay on the latest secure version without manual intervention.", - "status": "future", - "milestone_id": "Echelon" - }, - { - "title": "Off app notifications", - "overview": "Orbit’s core approval policies operate asynchronously, facilitating collaboration across multiple users. To enhance this experience, we will introduce more notification options, ensuring users stay informed and engaged with pending approvals or updates.", - "status": "future", - "milestone_id": "Echelon" - }, - { - "title": "Orbit Wallet v1", - "description": "To further improve Orbit’s usability and accessibility, we will enhance the user experience through intuitive approval flows, a revamped onboarding, and a comprehensive documentation hub. These improvements will ensure the Orbit App is efficient for both individual users and teams managing their digital assets management needs.", - "status": "future", - "is_milestone": true, - "milestone_id": "Neutron", - "eta_to_render": "" - }, - { - "title": "Documentation Hub", - "overview": "A knowledge base providing in-depth guidance on Orbit’s core concepts, approval policies, and example configurations, structured under the Orbit System Configuration & Approval Policy (OSCAP) framework.", - "status": "future", - "milestone_id": "Neutron" - }, - { - "title": "Onboarding", - "overview": "A more guided, interactive onboarding flow will help new users quickly configure their Orbit Station, set up approval policies, and integrate assets with minimal friction.", - "status": "future", - "milestone_id": "Neutron" - }, - { - "title": "UX Improvements", - "overview": "A revamped configuration flow will simplify the setup of Orbit Station, making it easier for users of all technical levels to integrate smart contracts and manage assets.", - "status": "future", - "milestone_id": "Neutron" - }, - { - "title": "Decentralized Marketplace for Sovereign Apps", - "description": "A new foundation for a decentralized software marketplace is built, providing developers with a clear path to adoption for their applications without reliance on centralized platforms. By integrating transparent deployment flows and seamless discovery tools, this initiative lays the groundwork for a sovereign software ecosystem where developers can easily package and distribute their applications, and users retain full control over their installed apps.", - "status": "future", - "is_milestone": true, - "milestone_id": "Dynamo", - "eta_to_render": "" - }, - { - "title": "Developer Packaging & Submission Tools", - "overview": "Tools to streamline app packaging, validation, and deployment, ensuring a smooth onboarding experience for developers.", - "status": "future", - "milestone_id": "Dynamo" - }, - { - "title": "App Manager", - "overview": "A dashboard where users can manage installed applications, providing an intuitive way to access and control their apps.", - "status": "future", - "milestone_id": "Dynamo" - }, - { - "title": "Core Marketplace Framework", - "overview": "A decentralized app catalog where developers can publish applications with metadata (version, description, screenshots). Users can search, filter, and explore categorized apps effortlessly.", - "status": "future", - "milestone_id": "Dynamo" - }, - { - "title": "First Sovereign Productivity Apps", - "overview": "A set of initial applications designed to showcase the power of sovereign software, serving as reference for future developers.", - "status": "future", - "milestone_id": "Dynamo" - }, - { - "title": "Zero to Degen-Hero", - "description": "Low-friction onboarding and streamlined user experience", - "status": "future", - "is_milestone": true, - "milestone_id": "Apex", - "eta_to_render": "" - }, - { - "title": "Ledgers as a first class citizen on ICP", - "overview": "Ledgers are an important part of the blockchain ecosystem. Making it easy to create, discover, and use is fundamental to greater adoption.", - "status": "future", - "milestone_id": "Apex" - }, - { - "title": "Faster institutional integrations of new tokens", - "overview": "Support multi-token Resetta", - "status": "future", - "milestone_id": "Apex" - }, - { - "title": "Fiat on-ramp", - "overview": "Facilitate the exchange of fiat currencies for ICP native tokens.", - "status": "future", - "milestone_id": "Apex" - }, - { "title": "Rosetta for ICRC ledgers", "overview": "Implement the Rosetta standard for ICRC-based ledgers. Enables ICRC tokens to be handled by centralized exchanges.", diff --git a/roadmap/entries/data-dx.json b/roadmap/entries/data-dx.json index 1c59ad6686..b79bc7a600 100644 --- a/roadmap/entries/data-dx.json +++ b/roadmap/entries/data-dx.json @@ -14,6 +14,31 @@ "in_beta": false, "imported": true }, + { + "title": "Canister snapshots", + "overview": "Allow for canister snapshots to be created on chain. Snapshots can be exported to and imported from off-chain storage.", + "status": "deployed", + "forum": "https://forum.dfinity.org/t/canister-backup-and-restore-community-consideration/22597", + "proposal": "", + "docs": "", + "eta": "Q2 2024", + "is_community": true, + "in_beta": false, + "milestone_id": "Beryllium" + }, + { + "title": "Canister logging", + "overview": "New APIs for writing and reading canister runtime logs. The logs survive upgrades and traps and ensure developers are able to record key error data.", + "forum": "https://forum.dfinity.org/t/canister-logging/21300", + "proposal": "", + "docs": "", + "eta": "2024-08-28", + "status": "deployed", + "is_community": true, + "in_beta": false, + "milestone_id": "Beryllium", + "imported": true + }, { "title": "Canister lifecycle hooks", "overview": "Push model for canisters receiving notifications from the ICP, e.g., when they are low on cycles. More resource efficient than periodic pulling.", @@ -27,6 +52,38 @@ "milestone_id": "Thorium", "imported": true }, + { + "title": "Standardized canister response codes", + "overview": "Standardize canister response codes, particularly error codes, to enable better composability of services from canister smart contracts.", + "status": "deployed", + "forum": "", + "proposal": "", + "docs": "", + "is_community": true, + "in_beta": false, + "milestone_id": "Beryllium" + }, + { + "title": "Actionable error messages and backtraces", + "overview": "Improve error messages by providing more actionable information to developers such as backtraces, error codes, and links to the documentation explaining how to fix the error.", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", + "status": "deployed", + "is_community": true, + "in_beta": false, + "milestone_id": "Beryllium" + }, + { + "title": "Canister DevOps", + "is_milestone": true, + "description": "This milestone provides substantial simplifications and improvements for the developer lifecycle of canisters, particularly regarding their development and operations. Snapshotting capabilities, a powerful logging infrastructure and improved error handling as well as push of relevant events brings canisters closer to Web2 services in terms of DevOps.", + "milestone_id": "Beryllium", + "eta": "", + "status": "deployed", + "eta_to_render": "November 2024" + }, { "title": "Coding and Development in ICP Ninja", "is_milestone": true, @@ -171,51 +228,6 @@ "status": "in_progress", "eta_to_render": "" }, - - { - "title": "Amazing first time developer experience with ICP Ninja", - "description": "ICP Ninja as the go to tool for ICP developers, experienced or not.", - "status": "future", - "is_milestone": true, - "milestone_id": "Atlas", - "eta_to_render": "" - }, - { - "title": "Open Caffeine projects", - "overview": "Users can open their Caffeine generated applications in ICP Ninja and continue manually refining them. Once satisfied with the result, one can return to Caffeine and iterate with prompts.", - "status": "future", - "milestone_id": "Atlas" - }, - { - "title": "Generate a project with AI", - "overview": "Get a head start in developing your next project with ICP Ninja by using the integrated AI project generator. Simply describe what you want to build and it’ll do it for you.", - "status": "future", - "milestone_id": "Atlas" - }, - { - "title": "More sample projects to get you started", - "overview": "Users can browse, open, and run the official ICP examples from ICP Ninja.", - "status": "future", - "milestone_id": "Atlas" - }, - { - "title": "Community published projects", - "overview": "Show your coding skills to the community by publishing your project to the gallery.", - "status": "future", - "milestone_id": "Atlas" - }, - { - "title": "Structured learning through mini tutorials", - "overview": "Add tutorials that teach ICP programming concepts and design patterns.", - "status": "future", - "milestone_id": "Atlas" - }, - { - "title": "Dark mode", - "overview": "Introduce dark mode for the app", - "status": "future", - "milestone_id": "Atlas" - }, { "title": "dfx ergonomics", "overview": "Better developer experience when using the ICP SDK.", diff --git a/roadmap/entries/data-governance.json b/roadmap/entries/data-governance.json index 224e02a9c9..e12a93ac34 100644 --- a/roadmap/entries/data-governance.json +++ b/roadmap/entries/data-governance.json @@ -1,25 +1,21 @@ { "categoryName": "Governance & Tokenomics", - "categoryDescription": "ICP has two kinds of built-in governance systems. The NNS is the DAO governing the ICP protocol. The SNS framework is a toolbox for creating DAOs that govern individual dapps. Both are open for everyone to participate and facilitate decentralized decision making. Tokenomics incentivise voting participation and ensure that DAO decisions are aligned with the long-term interests of the ICP and the governed dapps.", + "categoryDescription": "The ICP has two kinds of built-in governance systems. The NNS is the DAO governing the ICP protocol. The SNS framework is a toolbox for creating DAOs that govern individual dapps. Both are open for everyone to participate and facilitate decentralized decision making. Tokenomics incentivise voting participation and ensure that DAO decisions are aligned with the long-term interests of the ICP and the governed dapps.", "elements": [ { - "title": "Enabling governance token holdings and broader participation", + "title": "Prepare for Scaling", "is_milestone": true, - "description": "The main focus of the Neon milestone is on expanding the user base and improving the user experience. Holding governance tokens is intuitive and seamless, ensuring that new users can quickly understand their holdings and easily explore and engage with new opportunities, such as SNS launches. Additional features aim to make the governance process more intuitive and simplify SNS DAO operations, laying the basis for the next milestone.", + "description": "As both the number of SNS DAOs and the number of DAO participants grow within them, it is crucial to have a robust system that can handle the ever-growing communities. Preparing for growth means not only improving the underlying infrustucture to handle increased load, but also enhancing the user experience at all levels (from developers to end users), so when new people come to the ICP ecosystem, they will have a frictionless onboarding.", "milestone_id": "Neon", "status": "in_progress", + "eta": "", "eta_to_render": "" }, + { - "title": "Portfolio page", - "overview": "Introduce a new portfolio page for NNS dapp users where they can find an overview of their holdings and the possible actions that they can take.", - "status": "in_progress", - "milestone_id": "Neon" - }, - { - "title": "Engaged and active DAO communities", + "title": "Focus on User Experience", "is_milestone": true, - "description": "This milestone focuses on boosting user involvement in governance. It aims to create a sense of belonging to DAO communities and encourage users to contribute to the liquid democracy processes. SNS communities can apply their decisions easily by proposals.", + "description": "All ICP governance milestones have aspects that focus on the end user, as all of ICP's technological innvations must in the end support the user. Nucleon doubles down on the user experience and aims to present ICP's governance systems in ways that are easier to understand and interact with regardless of one's technical skills.", "milestone_id": "Nucleon", "status": "future", "eta": "", @@ -33,7 +29,7 @@ "proposal": "https://dashboard.internetcomputer.org/proposal/55651", "docs": "", "eta": "", - "status": "deployed", + "status": "in_progress", "is_community": true, "in_beta": false, "imported": true, @@ -53,45 +49,62 @@ "milestone_id": "Neon" }, { - "title": "Large Wasm support for SNS controlled dapp canisters", - "overview": "This simplifies owning large dapp canisters for SNS DAO communities by a built-in process to do so in the SNS framework.", - "status": "in_progress", + "title": "Improved neuron following experience", + "overview": "Neuron following is a key component of ICP's liquid democracy. Improvements to following include grouped SNS proposal topics, simplified staking user flow, and more.", + "description": "Today, it is quite cumbersome to set up several neurons at the same time, especially in cases where a user intends to follow a more diverse set of neurons based on the proposal topic. This is because neuron followees are saved each time they are set for a topic. A potential solution would be to allow the user to create a followee setup, and save it once they are happy with it, or even do batch neuron actions. Another goal is to improve the NNS dapp so that special cases for proposal following become intuitively visible, for example if some proposals are not covered by the “catch-all” following or are categorized as critical.", + "forum": "", + "proposal": "", + "wiki": "", + "docs": "", + "eta": "", + "status": "future", "is_community": false, "in_beta": false, "milestone_id": "Neon" }, { - "title": "Automatic SNS framework canister upgrades", - "overview": "For easier management of the SNS framework canisters, allow SNS DAOs to opt-in to receive automatic upgrades to canisters as soon as they are approved and released by the NNS.", - "status": "deployed", + "title": "Notifications in the NNS dapp", + "overview": "The NNS is constantly evolving. This feature will let users know of new features, if they are required to take actionm or alert them if they are missing voting rewards.", + "description": "The NNS is constantly evolving. This feature will let users know of new features, if they are required to take actionm or alert them if they are missing voting rewards.", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", + "status": "future", "is_community": false, "in_beta": false, "milestone_id": "Neon" }, { - "title": "Leverage liquid democracy in SNS DAOs", - "overview": "Liquid democracy is a key component of ICP's governance systems. Further leverage the potential of this mechanism in the SNS DAOs, including by introducing SNS topics and a notion of named or known neurons.", - "status": "in_progress", + "title": "Disburse maturity for NNS neurons", + "overview": "Unlike SNS neurons, NNS neurons spawn maturity into a newly created neurons. This feature will move to a flow where NNS neurons would also disburse maturity.", + "description": "In its current implementation, NNS neurons spawn maturity into a new neuron, whereas SNS DAOs disburse maturity directly into the user's account, which greatly simplifies the flow and reduces the new neurons created.", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", + "status": "future", "is_community": false, "in_beta": false, "milestone_id": "Neon" }, { - "title": "Disburse maturity for NNS neurons", - "overview": "Unlike SNS neurons, NNS neurons spawn maturity into a newly created neuron. This feature will move to a flow where NNS neurons would also disburse maturity.", - "description": "In its current implementation, NNS neurons spawn maturity into a new neuron, whereas SNS DAOs disburse maturity directly into the user's account, which greatly simplifies the flow and reduces the new neurons created.", + "title": "SNS communities portal", + "overview": "Introduce a landing page for each SNS DAO to the NNS dapp to foster the DAO communities.", + "description": "This feature has the goal of improving the experience on the NNS dapp to create a sense of community for the individual SNS DAOs and make all information concerning one DAO more readily accessible. To achieve this, one could introduce a new landing page for each SNS DAO which includes a summary of the DAO, for example the name and a description, but also summarizes the actionable proposals where a logged-in user can still vote on and links to the user’s neurons in that SNS.", "forum": "", "proposal": "", "docs": "", "eta": "", - "status": "in_progress", + "status": "future", "is_community": false, "in_beta": false, "milestone_id": "Neon" }, { - "title": "SNS communities portal", - "overview": "A redesign of the voting interface that encourages community involvement and a sense of belonging, for example by allowing for announcement and updates.", + "title": "Named SNS neurons", + "overview": "Increase and facilitate active participation in SNS DAOs by introducing an easy way to find experts and follow them.", + "description": "Unlike the NNS, there is currently no notion of named neurons in the SNSs. Therefore it is harder for users to find actively voting neurons that they can follow. The goal of this feature is to change this and make it easier for actively voting neurons to identify themselves and for other users to find and follow them.", "forum": "", "proposal": "", "docs": "", @@ -99,7 +112,7 @@ "status": "future", "is_community": false, "in_beta": false, - "milestone_id": "Nucleon" + "milestone_id": "Neon" }, { "title": "SNS treasury management", @@ -112,32 +125,20 @@ "status": "future", "is_community": false, "in_beta": false, - "milestone_id": "Nucleon" - }, - { - "title": "Council-based digital assets management", - "is_milestone": true, - "description": "This milestone integrates Orbit’s multi-approval framework with the Network Nervous System (NNS), designating the NNS as the root of trust. By having the NNS “bless” new versions, Orbit gains a robust, decentralized governance layer without requiring each council to implement its own governance from scratch.", - "milestone_id": "Nucleus", - "status": "future", - "eta_to_render": "" - }, - { - "title": "Root of Trust Integration", - "overview": "The Orbit control panel and core user interface are placed under NNS control. New versions of Orbit must be “blessed” by the NNS, ensuring a community-vetted approach to upgrades and governance.", - "status": "future", - "milestone_id": "Nucleus" + "milestone_id": "Neon" }, { - "title": "Public councils", - "overview": "Projects can create open, trackable councils using Orbit’s multi approval tools. All key actions—like canister upgrades—are fully transparent, enabling end users to monitor and verify changes in real time.", + "title": "ICRC-2 support", + "overview": "Certain parts of the NNS require complex logic to function properly as they were designed before ICRC-2. This roadmap item aims to reduce this complexity, and potential problems by implementing ICRC-2", + "description": "Certain parts of the NNS require complex logic to function properly as they were designed before ICRC-2. This roadmap item aims to reduce this complexity, and potential problems by implementing ICRC-2", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", "status": "future", - "milestone_id": "Nucleus" - }, - { - "title": "NNS Neuron index", - "overview": "Introduce a governance endpoint that allows to index all NNS neurons.", - "status": "future" + "is_community": false, + "in_beta": false, + "milestone_id": "Neon" }, { @@ -157,7 +158,8 @@ }, { "title": "Launchpad redesign", - "overview": "Launchpad is one of the central places where newcomers may find SNS DAOs. This roadmap item aims to show more interesting and dynamic information about DAOs on ICP, allowing users to find opportunities and engage with new SNS launches.", + "overview": "Launchpad is one of the central places where newcomers may find SNS DAOs. This roadmap item aims to show more interesting statistics about DAOs on ICP, and allow SNS DAOs to show more information about themselves, and send users to relevant places.", + "description": "Launchpad is one of the central places where newcomers may find SNS DAOs. This roadmap item aims to show more interesting statistics about DAOs on ICP, and allow SNS DAOs to show more information about themselves, and send users to relevant places.", "forum": "", "proposal": "", "docs": "", @@ -165,11 +167,16 @@ "status": "future", "is_community": false, "in_beta": false, - "milestone_id": "Neon" + "milestone_id": "Nucleon" }, { - "title": "Guide users from swap participating to governance", - "overview": "After successful participation in an SNS launch, guide users to the next steps they can take. This can include using their tokens or setting up the neurons that they received. This encourages users to remain active after the SNS launch and become governance participants.", + "title": "User participation in SNS DAOs", + "overview": "Writing code, creating proposals and voting on proposals from others are just a few ways of participating in SNS DAOs. This roadmap item aims to extend how users can participate, including no-code options like topping up SNS canisters, creating upgrade proposals, and more.", + "description": "Writing code, creating proposals and voting on proposals from others are just a few ways of participating in SNS DAOs. This roadmap item aims to extend how users can participate, including no-code options like topping up SNS canisters, creating upgrade proposals, and more.", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", "status": "future", "is_community": false, "in_beta": false, @@ -179,25 +186,42 @@ "title": "Fiat values in the NNS dapp", "overview": "It's hard to get a glance on one's SNS/ICP portfolio by only seeing the number of tokens held. This feature aims to show USD values of tokens, which also makes ordering more meaningful.", "description": "It's hard to get a glance on one's SNS/ICP portfolio by only seeing the number of tokens held. This feature aims to show USD values of tokens, which also makes ordering more meaningful.", - "status": "deployed", - "milestone_id": "Neon" + "forum": "", + "proposal": "", + "docs": "", + "eta": "", + "status": "future", + "is_community": false, + "in_beta": false, + "milestone_id": "Nucleon" }, { - "title": "Incentivise exceptional voting", - "overview": "All ICP governance participants are rewarded equally whether they vote manually or follow other neurons, even if the former takes significantly more effort. This roadmap item aims to explore ways to find a better balance.", + "title": "NNS overview page", + "overview": "A homepage for everything NNS. Once the user signs in, they are presented with an NNS homepage that shows their neurons, tokens, actionable proposals all in one page.", + "description": "A homepage for everything NNS. Once the user signs in, they are presented with an NNS homepage that shows their neurons, tokens, actionable proposals all in one page.", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", "status": "future", "is_community": false, "in_beta": false, "milestone_id": "Nucleon" }, { - "title": "NNS known and named neurons", - "overview": "Currently there are a lot of known neurons and some that only focus on a few topics. It is hard for users to find good candidates to follow / delegate their vote to for different topics. This feature aims to improve this and to consider introducing names also for other public neurons.", + "title": "Incentivise active participation", + "overview": "All ICP governance participants are rewarded equally whether they vote manually or follow other neurons, even if the former takes significantly more effort. This roadmap item aims to expore ways to find a better balance.", + "description": "All ICP governance participants are rewarded equally whether they vote manually or follow other neurons, even if the former takes significantly more effort. This roadmap item aims to expore ways to find a better balance.", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", "status": "future", "is_community": false, "in_beta": false, "milestone_id": "Nucleon" }, + { "title": "NNS FE Dapp Re-write", "overview": "Replacing Flutter with Svelte for the NNS Frontend dapp. Significant speed and UX improvements expected.", @@ -428,28 +452,41 @@ "in_beta": false }, { - "title": "Proposal error visibility", - "overview": "Make it easier for SNS communities to execute decisions via proposals by making potential errors visible. For example, if an SNS proposal fails to execute, users of the NNS dapp do not see the reason for why this happened. This feature introduces user-readable error messages.", + "title": "NNS landing page", + "overview": "The NNS dapp provides a simple user interface to interact with ICP's different governance systems. The NNS landing page would give newcomers an introduction of what the NNS is, host documentation, and a release log. Everything that is outside of the NNS dapp itself.", + "description": "The NNS dapp provides a simple user interface to interact with ICP's different governance systems. The NNS landing page would give newcomers an introduction of what the NNS is, host documentation, and a release log. Everything that is outside of the NNS dapp itself.", "forum": "", "proposal": "", "docs": "", "eta": "", "status": "future", "is_community": false, - "in_beta": false, - "milestone_id": "Nucleon" + "in_beta": false }, { - "title": "Expand reporting functionality", - "overview": "Extending the reporting functionality, for example with SNS neurons or fiat values.", + "title": "Error messages for failed proposals", + "overview": "If an SNS proposal fails to execute, users of the NNS dapp do not see the reason for why this happened. This feature introduces user-readable error messages across the NNS dapp.", + "description": "If an SNS proposal fails to execute, users of the NNS dapp do not see the reason for why this happened. This feature introduces user-readable error messages across the NNS dapp.", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", "status": "future", + "is_community": false, + "in_beta": false, "milestone_id": "Nucleon" }, { - "title": "Governance basic portfolio reporting capabilities", - "overview": "Reporting functionality that allows users to obtain summary information about their NNS neurons.", - "status": "deployed", - "milestone_id": "Neon" + "title": "Governance portfolio reporting capabilities", + "overview": "Reporting functionality that allows users to obtain summary information about their neurons.", + "description": "Currently, it is difficult for users to obtain detailed historic information on received voting rewards and the neuron spawning history. In practice, users need to manually track their actions periodically or use third-party canisters to obtain this information. This feature enables ICP to provide reports to users regarding voting rewards and neurons", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", + "status": "future", + "is_community": false, + "in_beta": false }, { @@ -464,6 +501,18 @@ "is_community": false, "in_beta": false }, + { + "title": "Simplification of NNS neurons", + "overview": "NNS neurons have different properties, such as dissolve delay and age. Some of these properties must be in a certain relation at all times. This feature is to abstract away more of these details from the users so that neurons are easier to understand.", + "description": "NNS neurons have different properties, such as dissolve delay and age. Some of these properties must be in a certain relation at all times. This feature is to abstract away more of these details from the users so that neurons are easier to understand.", + "status": "future", + "forum": "", + "proposal": "", + "wiki": "", + "docs": "", + "is_community": false, + "in_beta": false + }, { "title": "Manual overwriting of following-triggered votes", "overview": "This feature enables manual (overwrite) voting throughout the entire voting period of governance proposals even when a neuron is following another neuron.", diff --git a/roadmap/entries/data-icp_as_compute_platform.json b/roadmap/entries/data-icp_as_compute_platform.json index 102851864e..f191ab123c 100644 --- a/roadmap/entries/data-icp_as_compute_platform.json +++ b/roadmap/entries/data-icp_as_compute_platform.json @@ -1,11 +1,11 @@ { "categoryName": "Compute Platform", - "categoryDescription": "All computations of the world can run on ICP. ICP is a decentralized compute platform operating as an extension of the Internet, offering cost effective compute and storage services, with infrastructure provided by independent entities around the globe. The platform allows anyone to deploy canister smart contracts on the Internet and run them in a decentralized manner.", + "categoryDescription": "Blockchain Singularity — all computations of the world can run on ICP. ICP is a decentralized compute platform operating as an extension of the Internet, offering cost effective compute and storage services, with infrastructure provided by independent entities around the globe. The platform allows anyone to deploy canister smart contracts on the Internet and run them in a decentralized manner.", "elements": [ { - "title": "Load Balancing & increased compute capacity", + "title": "Increase scalability and compute capacity", "is_milestone": true, - "description": "ICP subnets can handle even more compute load, by better handling many distinct canisters and taking checkpoints asynchronously. When a subnet's load grows even beyond that, this milestone introduces canister migration, which enables better load balancing between subnets, ensuring all ICP subnets are well utilized.", + "description": "ICP subnets can handle even more compute load, by better handling many distinct canisters and by using more CPU threads. When a subnet's load grows even beyond that, this milestone introduces canister migration, which enables better load balancing between subnets, ensuring all ICP subnets are well utilized.", "milestone_id": "Flux", "status": "in_progress", "eta": "", @@ -25,8 +25,8 @@ }, { "title": "Canister migration", - "overview": "Allows controllers to migrate a canister to another subnet, without changing its canister id. This is crucial to balance load across subnets and fully benefit from ICP’s scaling via subnets. It also allows canisters to move to another subnet which may differ in features or replication factor.", - "status": "in_progress", + "overview": "Migrating canisters between subnets. Important for balancing subnet utilization and scaling the IC.", + "status": "future", "forum": "", "proposal": "", "docs": "", @@ -36,50 +36,16 @@ "milestone_id": "Flux" }, { - "title": "Canister Snapshots can be imported and exported", - "overview": "With canister snapshots, it became possible for controllers to take a full snapshot of their canister, allowing it to revert back to this state at a later point in time. This feature is an extension to the canister snapshot functionality, allowing controllers to retrieve snapshots and upload snapshots. This would enable storing canister snapshots in a canister or off-chain, using snapshots for testing purposes in a local environment, or loading a state snapshot of canister A into another canister B. The latter can be useful for testing purposes and is also a building block towards canister migration.", - "status": "in_progress", - "milestone_id": "Flux" - }, - { - "title": "Enhance Subnet Capacity for Active Canisters", - "overview": "Increase the maximum number of concurrently active canisters supported by a subnet. This will be achieved through optimizations to the canister scheduling algorithm, improvements to canister sandbox management, and increased memory efficiency within canister sandboxes. This enhancement is crucial for ICP scaling and more predictable handling of peak loads.", + "title": "Configurable Wasm memory limit", + "overview": "Introduce an explicitly configurable Wasm heap limit. Exceeding the limit alerts the developer instead of bricking the canister when hitting the 4GiB limit.", + "forum": "https://forum.dfinity.org/t/proposal-configurable-wasm-heap-limit/17794", + "proposal": "https://dashboard.internetcomputer.org/proposal/105322", + "docs": "", + "eta": "2024", "status": "deployed", - "milestone_id": "Flux" - }, - { - "title": "Load Balancing via subnet splitting", - "is_milestone": true, - "description": "This milestone introduces subnet splitting, which allows one subnet to split into two, each subnet hosting half of the workload of the original subnet. Whenever a subnet is overloaded, the NNS can decide to split the subnet, which helps balance load across multiple subnets and avoids overloaded subnets. The first subnet split on ICP mainnet will mark the completion of this milestone.", - "milestone_id": "Fission", - "status": "in_progress", - "eta_to_render": "" - }, - { - "title": "Subnet splitting with minimal downtime", - "overview": "In a previous feature, subnet splitting became possible via a sequence of NNS proposals, which would incur significant downtime. In this feature, the goal is to make subnet splitting practically possible with minimal downtime for the subnet.", - "status": "in_progress", - "milestone_id": "Fission" - }, - { - "title": "Integrity of Node State", - "is_milestone": true, - "description": "This milestone brings trusted execution environments (TEE) to the nodes in the Internet Computer to enforce node integrity. It ensures that the node state remains protected, preventing tampering while also keeping sensitive key shares confidential. By guaranteeing the trustworthiness of the nodes, verifiable API BN access logs and secure queries are unlocked.", - "milestone_id": "Magnetosphere", - "status": "in_progress", - "eta_to_render": "" - }, - { - "title": "TEE-capable IC-OS", - "overview": "Adapt IC-OS to run inside SEV-SNP, ensuring it boots securely and allows for mutual remote attestation among all nodes.", - "status": "in_progress", - "milestone_id": "Magnetosphere" - }, - { - "title": "Remote Attestation for Users", - "overview": "Allowing users to verify that an API boundary node is running trusted software inside a genuine trusted execution environment.", - "status": "in_progress", - "milestone_id": "Magnetosphere" + "is_community": true, + "in_beta": false, + "imported": true }, { "title": "Best-effort messaging", @@ -177,6 +143,17 @@ "milestone_id": "", "imported": true }, + { + "title": "Canister control audit trail", + "overview": "Seamless audit trail of management actions on canisters (creation, update, deletion). Allows to trace the sequence of installed canister versions to source code through a Wasm hash.", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", + "status": "deployed", + "is_community": false, + "in_beta": false + }, { "title": "Improved state certification", "overview": "The protocol requires certifying parts of the replicated state every round, which includes hashing the respective parts of the state. The faster this is, the more time can be spent on other things during the round. This feature is about optimizing certification times.", @@ -387,6 +364,17 @@ "is_community": false, "in_beta": false }, + { + "title": "Subnet splitting V2", + "overview": "An enhanced version of subnet splitting where all the heavy lifting is done by the protocol.", + "forum": "", + "proposal": "", + "docs": "", + "eta": "", + "status": "", + "is_community": false, + "in_beta": false + }, { "title": "Blob storage", "overview": "Storage of large amounts of data in a subnet using a new blob storage architecture with the cost of around 2x the SSD cost. More efficient and cheaper compared to regular storage on ICP.", diff --git a/roadmap/entries/data-identity.json b/roadmap/entries/data-identity.json index 89e725bc83..91e3f7ede8 100644 --- a/roadmap/entries/data-identity.json +++ b/roadmap/entries/data-identity.json @@ -1,6 +1,6 @@ { "categoryName": "Identity", - "categoryDescription": "An identity solution that is privacy-preserving, self-sovereign, and user-friendly is a fundamental building block for Web3 adoption. Internet Identity provides a robust authentication solution based on passkeys, with easy onboarding and support for identity attributes while protecting the users’ privacy.", + "categoryDescription": "An identity solution that is privacy-preserving, self-sovereign, and user-friendly is a fundamental building block for web3 adoption. Internet Identity provides a robust authentication solution based on passkeys, with easy onboarding and support for identity attributes while protecting the users’ privacy.", "elements": [ { "title": "Identity signer standards", @@ -50,84 +50,6 @@ "status": "in_progress", "eta_to_render": "" }, - { - "title": "Rethinking the Internet Identity user experience", - "description": "Focus on improving the user experience for Internet Identity", - "status": "in_progress", - "is_milestone": true, - "milestone_id": "Pulse", - "eta_to_render": "" - }, - { - "title": "Sing in with OpenID", - "overview": "Implement the OpenID standard and let users sign in with their existing email accounts.", - "status": "in_progress", - "milestone_id": "Pulse" - }, - { - "title": "Make account numbers obsolete", - "overview": "Account numbers are confusing and hard to remember. Explore ways to deprecate them through the use of the latest WebAuthn features.", - "status": "future", - "milestone_id": "Pulse" - }, - { - "title": "Streamline the authentication flow", - "overview": "Make the authentication flow clear to the user. Avoid pitfalls and frustrations.", - "status": "future", - "milestone_id": "Pulse" - }, - { - "title": "One account, multiple identities", - "overview": "Internet Identity provides users with the tools to manage multiple identities.", - "status": "future", - "milestone_id": "Pulse" - }, - { - "title": "Disentangle identity / wallet / app", - "overview": "Resolve the confusion that exists between Internet Identity and wallets. Clearly define the role that Internet Identity plays for applications.", - "status": "future", - "milestone_id": "Pulse" - }, - { - "title": "Additional measures for securing accounts", - "overview": "Implement additional security measures for protecting accounts when a device is compromised or stolen.", - "status": "future", - "milestone_id": "Pulse" - }, - - - { - "title": "Credentials solution for everyone", - "description": "Make the credential solution that Internet Identity offers a preferred option for a diverse range of issuers.", - "status": "future", - "is_milestone": true, - "milestone_id": "Plexus", - "eta_to_render": "" - }, - { - "title": "Bring the verifiable credentials protocol closer to the industry standard", - "overview": "Evolve the verifiable credentials protocol by bringing it closer to the industry standards.", - "status": "future", - "milestone_id": "Plexus" - }, - { - "title": "Credential issuers discoverability", - "overview": "Facilitate the discovery of credentials issuers through aggregation APIs.", - "status": "future", - "milestone_id": "Plexus" - }, - { - "title": "Increase adoption of the credentials solution", - "overview": "Lower the time to onboard new issuers and verifiers. Explore partnerships with key players in the industry.", - "status": "future", - "milestone_id": "Plexus" - }, - { - "title": "Sustainable business model for issuers and verifiers", - "overview": "Define and implement a sustainable business model for all: issuers, verifiers, users.", - "status": "future", - "milestone_id": "Plexus" - }, { "title": "Resident passkeys", "overview": "Explore the potential of resident passkeys to remove the requirement for users to remember their identity numbers.", diff --git a/roadmap/entries/data-privacy.json b/roadmap/entries/data-privacy.json index 8ce77e18a9..800fb8fc89 100644 --- a/roadmap/entries/data-privacy.json +++ b/roadmap/entries/data-privacy.json @@ -37,14 +37,6 @@ "eta": "Q2 2025", "eta_to_render": "" }, - { - "title": "Confidentiality of Canister States", - "description": "This milestone takes Trusted Execution Environments (TEE) to its final form, ensuring complete confidentiality of canister state. All canister state remains shielded from unauthorized access while maintaining its integrity. This further strengthens the confidentiality guarantees for dapp developers and users alike.", - "status": "future", - "is_milestone": true, - "milestone_id": "Containment", - "eta_to_render": "" - }, { "title": "Disaster recovery for SEV-SNP-enabled subnets", "overview": "SEV-SNP raises the level of security, but also makes disaster recovery harder. SEV-SNP-enabled subnets need to be made recoverable, e.g., by securely escrowing its secure enclave key material on the NNS.", diff --git a/roadmap/entries/data-trusted_ai.json b/roadmap/entries/data-trusted_ai.json index fe6db92330..a0100bf47c 100644 --- a/roadmap/entries/data-trusted_ai.json +++ b/roadmap/entries/data-trusted_ai.json @@ -3,65 +3,79 @@ "categoryDescription": "Today, users have to blindly trust AI models running on centralized servers with no visibility into how data is used and how AI models produce responses. Decentralized AI solves this problem by bringing the trustworthiness, security, verifiability, and resilience of smart contracts to AI applications.", "elements": [ { - "title": "Foundational LLMs", - "description": "AI agents are a growing paradigm in software, and the Internet Computer is uniquely positioned to be the home of AI agents. Compared to the traditional IT stack, AI agents on the Internet Computer can securely and easily manage digital assets, transact amongst each other, be fully sovereign, and be tokenized and managed by DAOs. This milestone focuses on providing access to foundational LLMs, along with basic tools to make it as simple as possible to deploy agents on the Internet Computer.", + "title": "API for AI computations", + "overview": "API for smart contracts that allows them to run hardware-accelerated AI computations. Initially, hardware acceleration will rely on the CPU, paving the way for GPU hardware acceleration in the future.", + "description": "AI computations are typically a graph of a large number of floating-point operations. Abstracting those operations into an API streamlines the development of AI applications, and paves the way to introduce optiizations to these specialized workload.", "status": "in_progress", - "is_milestone": true, "milestone_id": "Ignition", - "eta": "", - "eta_to_render": "" + "forum": "", + "proposal": "", + "docs": "", + "is_community": false, + "in_beta": false }, { - "title": "LLM Canister MVP", - "overview": "A canister will be made available that provides an API for processing LLM prompts. This canister is an MVP and will initially rely on a centrally-managed service by DFINITY for processing the prompts. A small set of foundational models will be supported.", + "title": "Wasm64 execution environment", + "overview": "The execution environment is lifted to Wasm64 with the benefit of a 64-bit address space and its much larger addressable memory, allowing developers to load larger models in main memory.", + "description": "The execution environment is lifted to Wasm64 with the benefit of a 64-bit address space and its much larger addressable memory.", "status": "in_progress", + "forum": "", + "proposal": "", + "docs": "", + "is_community": false, + "in_beta": false, "milestone_id": "Ignition" }, { - "title": "LLM Developer Experience", - "overview": "Tools and libraries to simplify the local development and the interaction with the LLM canister.", - "status": "in_progress", - "milestone_id": "Ignition" - }, - { - "title": "Motoko coding fine-tuned model", - "overview": "Fine-tune multiple Large Language Models (LLMs) using high-quality Motoko code samples to develop the most efficient and high-performing model for Motoko programming.", - "status": "in_progress", - "milestone_id": "Beacon" - }, - { - "title": "Model benchmarks for Motoko coding", - "overview": "Develop a comprehensive set of benchmarks to evaluate model performance for Motoko programming. This includes assessing both existing base LLMs and fine-tuned models to ensure accurate measurement of the effectiveness of fine-tuning efforts.", - "status": "in_progress", - "milestone_id": "Beacon" + "title": "Tooling and libraries for developing AI smart contracts", + "overview": "Providing developer tooling and libraries for building AI smart contracts on ICP, reusing existing AI ecosystem tools wherever possible.", + "description": "Developers need tooling and libraries to implement AI smart contracts. Ideally, the existing AI ecosystem is reused as much as possible, but specialized tools and libraries might be needed for developing onchain AI applications.", + "status": "", + "milestone_id": "Ignition", + "forum": "", + "proposal": "", + "docs": "", + "is_community": false, + "in_beta": false }, { - "title": "Caffeine integration", - "overview": "Integrate the results of the fine-tuning work into Caffeine to improve the quality of generated Motoko code. This will involve leveraging the highest-performing fine-tuned model, implementing a Retrieval-Augmented Generation (RAG) solution, and optimizing prompt engineering.", + "name": "Onchain AI Inference of Larger Models", + "description": "In order to perform AI inference and training of larger models on chain, canister smart contracts need to run more compute- and memory-intensive workloads. This milestone expands the compute and memory capabilities of canisters and paves the way for future GPU hardware acceleration. A special focus is being placed on the developer experience by building tools to simplify writing AI applications.", "status": "in_progress", - "milestone_id": "Beacon" + "is_milestone": true, + "milestone_id": "Ignition", + "eta": "", + "eta_to_render": "" }, { - "title": "AI Model for Motoko code generation", - "description": "This milestone is the first step towards improving the capability of Large Language Models to effectively generate code in the Motoko programming language.", - "status": "in_progress", - "is_milestone": true, - "milestone_id": "Beacon", - "eta_to_render": "April 2025" + "title": "Public specification for GPU-enabled nodes", + "overview": "The ICP community needs to agree and adopt the hardware specification for replica nodes with GPUs.", + "status": "future", + "forum": "", + "proposal": "", + "docs": "", + "is_community": false, + "in_beta": false }, { - "title": "Sovereign AI Agents", - "description": "This milestone builds on previous milestones by focusing on the security and the decentralization of the LLM services available on the Internet Computer.", + "title": "AI-specialized subnets with GPU-enabled nodes", + "overview": "AI-specialized subnets are created from nodes with GPUs and host AI smart contracts for training and inference of large models.", "status": "future", - "is_milestone": true, - "milestone_id": "Vortex", - "eta_to_render": "" + "forum": "", + "proposal": "", + "docs": "", + "is_community": false, + "in_beta": false }, { - "title": "LLM Workers", - "overview": "Introduce worker nodes that specialize in processing LLM prompts. Workers will have security guarantees similar to canister smart contracts on the Internet Computer", + "title": "Increase the instruction limit in queries from 5 billion instructions to 40 billion instructions.", + "overview": "The goal of this feature is to bring the instruction limit of queries on par with that of update calls by introducing a way for canisters to opt in into query charging.", "status": "future", - "milestone_id": "Vortex" + "forum": "", + "proposal": "", + "docs": "", + "is_community": false, + "in_beta": false } ] } diff --git a/roadmap/entries/deployed-dx.json b/roadmap/entries/deployed-dx.json index 7a5d912975..0f35093a55 100644 --- a/roadmap/entries/deployed-dx.json +++ b/roadmap/entries/deployed-dx.json @@ -2,63 +2,6 @@ "categoryName": "", "categoryDescription": "", "elements": [ - { - "title": "Canister snapshots", - "overview": "Allow for canister snapshots to be created on chain. Snapshots can be exported to and imported from off-chain storage.", - "status": "deployed", - "forum": "https://forum.dfinity.org/t/canister-backup-and-restore-community-consideration/22597", - "proposal": "", - "docs": "", - "eta": "Q2 2024", - "is_community": true, - "in_beta": false, - "milestone_id": "Beryllium" - }, - { - "title": "Canister logging", - "overview": "New APIs for writing and reading canister runtime logs. The logs survive upgrades and traps and ensure developers are able to record key error data.", - "forum": "https://forum.dfinity.org/t/canister-logging/21300", - "proposal": "", - "docs": "", - "eta": "2024-08-28", - "status": "deployed", - "is_community": true, - "in_beta": false, - "milestone_id": "Beryllium", - "imported": true - }, - { - "title": "Standardized canister response codes", - "overview": "Standardize canister response codes, particularly error codes, to enable better composability of services from canister smart contracts.", - "status": "deployed", - "forum": "", - "proposal": "", - "docs": "", - "is_community": true, - "in_beta": false, - "milestone_id": "Beryllium" - }, - { - "title": "Actionable error messages and backtraces", - "overview": "Improve error messages by providing more actionable information to developers such as backtraces, error codes, and links to the documentation explaining how to fix the error.", - "forum": "", - "proposal": "", - "docs": "", - "eta": "", - "status": "deployed", - "is_community": true, - "in_beta": false, - "milestone_id": "Beryllium" - }, - { - "title": "Canister DevOps", - "is_milestone": true, - "description": "This milestone provides substantial simplifications and improvements for the developer lifecycle of canisters, particularly regarding their development and operations. Snapshotting capabilities, a powerful logging infrastructure and improved error handling as well as push of relevant events brings canisters closer to Web2 services in terms of DevOps.", - "milestone_id": "Beryllium", - "eta": "", - "status": "deployed", - "eta_to_render": "November 2024" - }, { "title": "Bitcoin Integration with DFX", "overview": "Configure and run a Bitcoin adapter on the dev machine supporting the development with the native Bitcoin integration.", diff --git a/roadmap/entries/deployed-icp_as_compute_platform.json b/roadmap/entries/deployed-icp_as_compute_platform.json index 1278ece561..832da5d6d5 100644 --- a/roadmap/entries/deployed-icp_as_compute_platform.json +++ b/roadmap/entries/deployed-icp_as_compute_platform.json @@ -386,29 +386,6 @@ "status": "deployed", "is_community": false, "in_beta": false - }, - { - "title": "Configurable Wasm memory limit", - "overview": "Introduce an explicitly configurable Wasm heap limit. Exceeding the limit alerts the developer instead of bricking the canister when hitting the 4GiB limit.", - "forum": "https://forum.dfinity.org/t/proposal-configurable-wasm-heap-limit/17794", - "proposal": "https://dashboard.internetcomputer.org/proposal/105322", - "docs": "", - "eta": "2024", - "status": "deployed", - "is_community": true, - "in_beta": false, - "imported": true - }, - { - "title": "Canister control audit trail", - "overview": "Seamless audit trail of management actions on canisters (creation, update, deletion). Allows to trace the sequence of installed canister versions to source code through a Wasm hash.", - "forum": "", - "proposal": "", - "docs": "", - "eta": "", - "status": "deployed", - "is_community": false, - "in_beta": false } ] } \ No newline at end of file