You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Control Plane Configuration & Segmentation Demo
A live demonstration showcased the new control plane features for managing multi-deployment topologies.
Configuration Modes: The control plane can now be configured via a static configuration file (where the topology acts as the single source of truth) or dynamically via APIs (allowing links and segments to be added/removed on the fly).
Network Segmentation: A new segmentation feature was demonstrated, allowing strict isolation between groups (e.g., for multi-tenant environments). Groups in different segments cannot see or route to each other's applications, even if connected to the same central hub.
Failover: The demo successfully showed that if a gateway node is killed, the control plane automatically detects the failure, selects a new gateway node, and updates the routing tables seamlessly.
2. Security Fix: Node Spoofing Prevention
Identity Verification: A critical security feature has been merged to prevent nodes from spoofing their group membership. When a node connects to the control plane, it must now provide a cryptographic identity (via Spire or SharedSecret). The control plane verifies this identity against the requested group before allowing the connection.
Status: The core logic is already merged and available in the latest Alpha release. The corresponding SlimCTL API commands to configure this feature are currently in a PR and expected to merge shortly.
3. WebAssembly (Wasm) & Browser WebSockets
The PR implementing browser-native WebSockets is undergoing final review.
Code Organization: Review feedback focused on cleanly separating the compilation flows for Wasm32 versus Native targets to maintain codebase readability and avoid excessive compilation switches.
Release Strategy: Once this PR is merged, a new core Alpha release will be cut. The language bindings will then be rebased onto this release to fully enable and test in-browser Wasm support for the upcoming V2.0 launch.
4. SLIM v2.0 Documentation & Migration Guide
A massive PR is currently under review. It overhauls the technical content to reflect the new V2.0 architecture, adds comprehensive tutorials, and includes the critical V1 to V2 migration guide. This will be published to the new landing page (slim.agntcy.org) alongside the V2.0 release.
5 Decentralized Discovery & libp2p Integration
Contributors from the libp2p project shared results from testing AGNTCY on a hyperscaler with 2,000 live connections.
Peer Discovery: While SLIM's current bootstrap method works well for global environments, recommendations were made to introduce alternative discovery methods (e.g., mDNS, random walk, rendezvous) for local or hybrid environments.
NAT Traversal: To support SLIM nodes operating behind strict enterprise firewalls or VPNs, the integration of NAT traversal modules (AutoNAT, hole punching, circuit relays) was strongly recommended. The teams will collaborate on these networking enhancements via Discord.
Next Steps & Action Items
Spoofing Prevention: Merge the pending SlimCTL API commands PR to finalize the group identity verification feature.
Wasm WebSockets: Address code organization feedback on the Wasm WebSocket PR and merge it into the main branch.
Bindings & Alpha Release: Cut a new SLIM Alpha release post-Wasm merge, and rebase the language bindings to test full browser support.
V2.0 Documentation: Complete the review and merge the comprehensive V2.0 documentation and migration guide PR.
Decentralized Networking: Continue architectural discussions on Discord regarding peer discovery methods, NAT traversal, and custom libp2p specifications for the AGNTCY ecosystem.
Blog Troubleshooting: Investigate and resolve the authentication permissions error preventing previews on community blog PRs.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Key Topics & Outcomes
1. Control Plane Configuration & Segmentation Demo
A live demonstration showcased the new control plane features for managing multi-deployment topologies.
Configuration Modes: The control plane can now be configured via a static configuration file (where the topology acts as the single source of truth) or dynamically via APIs (allowing links and segments to be added/removed on the fly).
Network Segmentation: A new segmentation feature was demonstrated, allowing strict isolation between groups (e.g., for multi-tenant environments). Groups in different segments cannot see or route to each other's applications, even if connected to the same central hub.
Failover: The demo successfully showed that if a gateway node is killed, the control plane automatically detects the failure, selects a new gateway node, and updates the routing tables seamlessly.
2. Security Fix: Node Spoofing Prevention
Identity Verification: A critical security feature has been merged to prevent nodes from spoofing their group membership. When a node connects to the control plane, it must now provide a cryptographic identity (via Spire or SharedSecret). The control plane verifies this identity against the requested group before allowing the connection.
Status: The core logic is already merged and available in the latest Alpha release. The corresponding SlimCTL API commands to configure this feature are currently in a PR and expected to merge shortly.
3. WebAssembly (Wasm) & Browser WebSockets
The PR implementing browser-native WebSockets is undergoing final review.
Code Organization: Review feedback focused on cleanly separating the compilation flows for Wasm32 versus Native targets to maintain codebase readability and avoid excessive compilation switches.
Release Strategy: Once this PR is merged, a new core Alpha release will be cut. The language bindings will then be rebased onto this release to fully enable and test in-browser Wasm support for the upcoming V2.0 launch.
4. SLIM v2.0 Documentation & Migration Guide
A massive PR is currently under review. It overhauls the technical content to reflect the new V2.0 architecture, adds comprehensive tutorials, and includes the critical V1 to V2 migration guide. This will be published to the new landing page (slim.agntcy.org) alongside the V2.0 release.
5 Decentralized Discovery & libp2p Integration
Contributors from the libp2p project shared results from testing AGNTCY on a hyperscaler with 2,000 live connections.
Peer Discovery: While SLIM's current bootstrap method works well for global environments, recommendations were made to introduce alternative discovery methods (e.g., mDNS, random walk, rendezvous) for local or hybrid environments.
NAT Traversal: To support SLIM nodes operating behind strict enterprise firewalls or VPNs, the integration of NAT traversal modules (AutoNAT, hole punching, circuit relays) was strongly recommended. The teams will collaborate on these networking enhancements via Discord.
Next Steps & Action Items
Spoofing Prevention: Merge the pending SlimCTL API commands PR to finalize the group identity verification feature.
Wasm WebSockets: Address code organization feedback on the Wasm WebSocket PR and merge it into the main branch.
Bindings & Alpha Release: Cut a new SLIM Alpha release post-Wasm merge, and rebase the language bindings to test full browser support.
V2.0 Documentation: Complete the review and merge the comprehensive V2.0 documentation and migration guide PR.
Decentralized Networking: Continue architectural discussions on Discord regarding peer discovery methods, NAT traversal, and custom libp2p specifications for the AGNTCY ecosystem.
Blog Troubleshooting: Investigate and resolve the authentication permissions error preventing previews on community blog PRs.
All reactions