Skip to content

Commit

Permalink
Merge branch 'master' into Poloidal-launch-date-update
Browse files Browse the repository at this point in the history
  • Loading branch information
@MarcoT0S
MarcoT0S authored Dec 5, 2024
2 parents cbe1a14 + 0111764 commit 98d845a
Show file tree
Hide file tree
Showing 3 changed files with 57 additions and 56 deletions.
73 changes: 20 additions & 53 deletions roadmap/entries/data-decentralization.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -14,21 +14,23 @@
"in_beta": false
},
{
"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",
"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",
"is_community": false,
"in_beta": false,
"milestone_id": "Solenoid"
"milestone_id": "Solenoid",
"imported": true
},
{
"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",
"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",
"docs": "",
"eta": "",
"status": "in_progress",
Expand All @@ -42,9 +44,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": "",
"docs": "https://github.com/dfinity/ic-gateway",
"eta": "",
"status": "upcoming",
"status": "in_progress",
"is_community": false,
"in_beta": false,
"milestone_id": "Solenoid"
Expand All @@ -55,8 +57,8 @@
"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.",
"milestone_id": "Solenoid",
"status": "in_progress",
"eta": "Q2 2024",
"eta_to_render": "December 2024"
"eta": "Q1 2025",
"eta_to_render": "January 2025"
},
{
"title": "SEV-SNP-protected API Boundary Nodes",
Expand Down Expand Up @@ -113,17 +115,6 @@
"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 @@ -137,16 +128,15 @@
"imported": true
},
{
"title": "Alerting of NP in case of Node Failure",
"overview": "Alert Node Providers if one of their nodes starts misbehaving or underperforming.",
"forum": "",
"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",
"proposal": "",
"docs": "",
"eta": "",
"status": "in_progress",
"is_community": true,
"in_beta": false,
"imported": true
"is_community": false,
"in_beta": false
},
{
"title": "HTTP Asset Caching",
Expand Down Expand Up @@ -218,18 +208,7 @@
{
"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": "",
"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": "",
"forum": "https://forum.dfinity.org/t/technical-working-group-node-providers/30255",
"proposal": "",
"docs": "",
"eta": "",
Expand Down Expand Up @@ -270,18 +249,6 @@
"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
4 changes: 2 additions & 2 deletions roadmap/entries/data-governance.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
"milestone_id": "Plasma",
"status": "in_progress",
"eta": "",
"eta_to_render": "November 2024"
"eta_to_render": "January 2025"
},

{
Expand Down Expand Up @@ -132,7 +132,7 @@
"proposal": "",
"docs": "",
"eta": "",
"status": "in_progress",
"status": "deployed",
"is_community": true,
"in_beta": false,
"milestone_id": "Plasma"
Expand Down
36 changes: 35 additions & 1 deletion roadmap/entries/deployed-decentralization.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,40 @@
"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
},
{
"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",
"is_community": false,
"in_beta": false,
"milestone_id": "Solenoid"
}
]
}
}

0 comments on commit 98d845a

Please sign in to comment.