Design: Difference between revisions
Jarrad Hope (talk | contribs) mNo edit summary |
Jarrad Hope (talk | contribs) |
||
| Line 26: | Line 26: | ||
== Core Microkernel == | == Core Microkernel == | ||
P2P systems constantly evolve and have different deployment configurations depending on system resources, as such the core of the system should be minimal, using a microkernel architecture that runs microservices | |||
* [[Design/Requirements|Requirements]] | * [[Design/Requirements|Requirements]] | ||
* [[Design/Architecture|Architecture]] | * [[Design/Architecture|Architecture]] | ||
Revision as of 07:18, 28 December 2024
The Logos Design
Concepts & Issues
- Cyberspace as Reality
- Territorialization of Cyberspace
- Surveillance
- Virtual States & Supra-jurisdictions
- Neomedievalism
- Voice of Civil Society
- Legitimacy & Competitive Governance
- Polycentric & Autocentric Law
- Sound Money
Personas
Organisational
Open Source & Chapters
Core Microkernel
P2P systems constantly evolve and have different deployment configurations depending on system resources, as such the core of the system should be minimal, using a microkernel architecture that runs microservices
Core Modules
Transport Modules
MPTCP, MPQUIC, MPUDP
Networking Modules
Anon DHT, Mixnet, Isontonic Routing, Smallworlds
Application Modules
Name Registry
Module Manager
Handles updating of modules and depdencies, queries the Peer Data Management System and Name Registry, and resolves module data using Decentralised File Storage.
Peer Data Management System
Effectively functions as a search engine