Design: Difference between revisions
Jarrad Hope (talk | contribs) |
Jarrad Hope (talk | contribs) |
||
| Line 40: | Line 40: | ||
=== Networking Modules === | === Networking Modules === | ||
Anon DHT, Mixnet, Isotonic Routing, Smallworlds | NAT Traversal, Anon DHT, Mixnet, Isotonic Routing, Smallworlds | ||
== Core Application Modules == | == Core Application Modules == | ||
Revision as of 07:30, 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
- World Reserve Currency & Agreements between (Non-)State Actors
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 hybrid microkernel architecture that runs microservices - the microkernel should not be a bottle neck for communication.
Core Modules
Transport Modules
MPTCP, MPQUIC, MPUDP
Networking Modules
NAT Traversal, Anon DHT, Mixnet, Isotonic Routing, Smallworlds
Core 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
A general purpose query engine using RDF-Star & SPARQL-star.
It should act as an alternative to a trusted JSON-RPC interface found in Blockchains, with RML adapters to other systems, such as Blockchains.
It should also function as a search engine for content discovery.