Skip to content

Commit

Permalink
revert roadmap
Browse files Browse the repository at this point in the history
  • Loading branch information
@reigj1
reigj1 committed Dec 18, 2024
1 parent 3cf0beb commit 0e82523
Showing 1 changed file with 57 additions and 58 deletions.
115 changes: 57 additions & 58 deletions roadmap/roadmap.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@
"status": "in_progress",
"elements": [
{
"title": "Asynchroddnous Checkpointing",
"title": "Asynchronous Checkpointing",
"overview": "Replicas currently persist the replicated state to disk every couple hundreds of rounds in a process called checkpointing. Currently some parts of checkpointing are done synchronously, which leads to drops in the execution rate in the checkpointing rounds and users have to wait longer for their responses during these rounds. The goal of this feature is to make more checkpointing steps run asynchronously in the background to make the IC's performance more consistent and predictable.",
"forum": "",
"proposal": "",
Expand Down Expand Up @@ -1533,27 +1533,25 @@
"name": "Edge Infrastructure is Fully Decentralized",
"milestone_id": "Solenoid",
"description": "ICP is accessible through a decentralized edge infrastructure, which is split into NNS-controlled API Boundary Nodes and HTTP Gateways. The NNS will appoint node machines to run API Boundary Nodes and anyone will be able to run HTTP Gateways, enabling a much more decentralized ICP edge infrastructure with a diverse set of service providers.",
"eta": "January 2025",
"eta": "December 2024",
"status": "in_progress",
"elements": [
{
"title": "HTTP Gateways",
"overview": "The HTTP Gateway becomes a standalone component as part of the new Boundary Node architecture.",
"title": "API Boundary Nodes (NNS controlled)",
"overview": "In the new boundary-node architecture, API boundary nodes are placed under the full control of the NNS and function as the edge of the IC.",
"status": "in_progress",
"forum": "https://forum.dfinity.org/t/boundary-node-roadmap/15562",
"proposal": "https://dashboard.internetcomputer.org/proposal/35671",
"docs": "",
"eta": "",
"status": "in_progress",
"is_community": false,
"in_beta": false,
"milestone_id": "Solenoid",
"imported": true
"milestone_id": "Solenoid"
},
{
"title": "Incident Handling under the New Boundary Node Architecture",
"overview": "To protect the core of the Internet Computer, processes must be established to configure temporary rate limits at API boundary nodes during incidents.",
"forum": "https://forum.dfinity.org/t/incident-handling-with-the-new-boundary-node-architecture/36390",
"proposal": "https://dashboard.internetcomputer.org/proposal/134031",
"title": "HTTP Gateways",
"overview": "The HTTP Gateway becomes a standalone component as part of the new Boundary Node architecture.",
"forum": "https://forum.dfinity.org/t/boundary-node-roadmap/15562",
"proposal": "https://dashboard.internetcomputer.org/proposal/35671",
"docs": "",
"eta": "",
"status": "in_progress",
Expand All @@ -1567,20 +1565,9 @@
"overview": "As part of the new boundary-node architecture, the HTTP gateway is turned into a standalone service, which is easily deployable by anyone, including end users.",
"forum": "https://forum.dfinity.org/t/boundary-node-roadmap/15562",
"proposal": "https://dashboard.internetcomputer.org/proposal/35671",
"docs": "https://github.com/dfinity/ic-gateway",
"docs": "",
"eta": "",
"status": "in_progress",
"is_community": false,
"in_beta": false,
"milestone_id": "Solenoid"
},
{
"title": "API Boundary Nodes (NNS controlled)",
"overview": "In the new boundary-node architecture, API boundary nodes are placed under the full control of the NNS and function as the edge of the IC.",
"status": "deployed",
"forum": "https://forum.dfinity.org/t/boundary-node-roadmap/15562",
"proposal": "https://dashboard.internetcomputer.org/proposal/35671",
"docs": "https://github.com/dfinity/ic/tree/master/rs/boundary_node/ic_boundary",
"status": "upcoming",
"is_community": false,
"in_beta": false,
"milestone_id": "Solenoid"
Expand Down Expand Up @@ -1744,29 +1731,6 @@
"is_community": false,
"in_beta": false,
"imported": true
},
{
"title": "Alerting of Node Providers in case of Node Failure",
"overview": "Alert Node Providers if one of their nodes starts misbehaving or underperforming.",
"forum": "",
"proposal": "",
"docs": "https://wiki.internetcomputer.org/wiki/Node_Provider_Alerting_Options",
"eta": "",
"status": "deployed",
"is_community": true,
"in_beta": false,
"imported": true
},
{
"title": "Public access to a subset of node metrics",
"overview": "Giving node providers access to a subset of node metrics to help them find out in a fully decentralized manner whether nodes are behaving well, and to roughly compare node performance.",
"forum": "https://forum.dfinity.org/t/public-internet-computer-ic-node-metrics-available-now/32961",
"proposal": "",
"docs": "https://github.com/dfinity/ic-observability-stack",
"eta": "",
"status": "deployed",
"is_community": false,
"in_beta": false
}
]
},
Expand Down Expand Up @@ -1808,6 +1772,17 @@
"is_community": false,
"in_beta": false
},
{
"title": "Public access to a subset of node metrics",
"overview": "Giving node providers access to a subnet of node metrics to help them find out what is failing in case of node issues.",
"forum": "",
"proposal": "",
"docs": "",
"eta": "",
"status": "in_progress",
"is_community": false,
"in_beta": false
},
{
"title": "Off-chain observability stack for Node Providers",
"overview": "Observability solution for Node Providers to enable them to independently triage node health and take corrective action in case of problems.",
Expand All @@ -1821,15 +1796,16 @@
"imported": true
},
{
"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.",
"forum": "https://forum.dfinity.org/t/performance-based-node-rewards/35208",
"title": "Alerting of NP in case of Node Failure",
"overview": "Alert Node Providers if one of their nodes starts misbehaving or underperforming.",
"forum": "",
"proposal": "",
"docs": "",
"eta": "",
"status": "in_progress",
"is_community": false,
"in_beta": false
"is_community": true,
"in_beta": false,
"imported": true
},
{
"title": "HTTP Asset Caching",
Expand Down Expand Up @@ -1901,7 +1877,18 @@
{
"title": "Strengthened node provider checks and audits",
"overview": "Strengthening the checks of entities intending to join ICP as node providers. May also include node provider audits.",
"forum": "https://forum.dfinity.org/t/technical-working-group-node-providers/30255",
"forum": "",
"proposal": "",
"docs": "",
"eta": "",
"status": "",
"is_community": false,
"in_beta": false
},
{
"title": "Penalties for non-compliant node providers",
"overview": "Non-compliant node providers are penalized economically or excluded from future network participation. This creates a cryptoeconomic incentive to encourage honest node provider behaviour.",
"forum": "",
"proposal": "",
"docs": "",
"eta": "",
Expand Down Expand Up @@ -1942,6 +1929,18 @@
"is_community": false,
"in_beta": false
},
{
"title": "Decentralized virtual personhood validation",
"overview": "Scalable, decentralized, virtual proof of personhood to distinguish people from machines.",
"forum": "https://forum.dfinity.org/t/long-term-r-d-people-parties-proof-of-human-proposal/9636",
"proposal": "https://dashboard.internetcomputer.org/proposal/35668",
"docs": "",
"eta": "",
"status": "",
"is_community": false,
"in_beta": false,
"imported": true
},
{
"title": "Public contributions to IC repository",
"overview": "Allowing for contributions by the public to the IC source code repository.",
Expand Down Expand Up @@ -2420,7 +2419,7 @@
"name": "The Orbit Multi-Custody Asset Framework",
"milestone_id": "Poloidal",
"description": "Orbit is a comprehensive digital assets framework, enabling simple to advanced rules over user digital assets. Initially tailored for token management, it provides robust support for 1-out-of-M to complex approval policies for financial transactions. It also supports secure management of infrastructure like canister installations and upgrades. Teams and businesses can confidently handle ICP, ckETH, and compatible tokens using Orbit's advanced security features, vital for those seeking a stable and reliable management over their treasury.",
"eta": "February 2025",
"eta": "January 2025",
"status": "in_progress",
"elements": [
{
Expand Down Expand Up @@ -2729,7 +2728,7 @@
"name": "Active Liquid Democracy",
"milestone_id": "Plasma",
"description": "The NNS and SNS DAOs facilitate active liquid democracies by lowering the entry barrier for participation and providing better inputs for well-informed decisions. This includes direct voting as well as delegating some voting decisions to others. As a result, more users stake tokens and participate in DAOs to form lively communities. The resulting network effects foster additional adoption and growth.",
"eta": "January 2025",
"eta": "November 2024",
"status": "in_progress",
"elements": [
{
Expand Down Expand Up @@ -2831,7 +2830,7 @@
"proposal": "",
"docs": "",
"eta": "",
"status": "deployed",
"status": "in_progress",
"is_community": true,
"in_beta": false,
"milestone_id": "Plasma"
Expand Down Expand Up @@ -4327,4 +4326,4 @@
}
]
}
]
]

0 comments on commit 0e82523

Please sign in to comment.