The Drayker network is built on two networks: a main network, and a test / interaction network with three layers. Other networks can take part in resolving it, as long as the requirements of the system architecture are preserved.
Why this exists
Drayker is a way of working where people keep creating, discovering and learning while intelligence carries the rest, and what results reaches the work that produced it. The network is what that distributed intelligence actually runs on, and who is allowed to hold a piece of it.
The argument in full is on the manifesto. The economy page states plainly what contributing here earns and what it does not.
The requirements
These are the published requirements of the network, and they come before any implementation:
- Protocol compatible with Living Cryptography
- Modular and evolutionary protocol
- Intelligent interconnection
- Separation of layers and subnetworks
- Distributed and fault-tolerant
- Offline adaptability
- DFM architecture
Further requirements are specified in the Initial Network Architecture.
How it fits the whole
The network is the ground everything else stands on — and the reason none of it needs a data centre. Drayker is a way of working where people keep creating, discovering and learning while intelligence carries the rest; the network is what that distributed intelligence actually runs on, and who is allowed to hold a piece of it.
Dk rides on it: the intelligence distributes work across the network, and uses its excess processing and storage as a second layer. The tunnels between the parts are Living Cryptography. Devices join through OSDK. Distributed support is the physical side of a network with no data centre — machines and people holding it up. And stations and embassies are where the same network touches the ground, places where volunteers meet, work and travel between.
Because the network is the floor of the ecosystem, its requirements come before any implementation: protocol compatible with Living Cryptography, modularity, intelligent interconnection, separation of layers, fault tolerance and offline adaptability. A network that only works while everything is reachable is not the network this ecosystem needs.
State of this documentation
The requirements are written down. The Initial Network Architecture referred to above is not published, which means the most consequential document of this layer is currently a reference to itself. Recovering or rewriting it is open work.
All proposed resolutions presented here are solutions to the requirements of Dk and the Drayker platform, and only those requirements are final. The definitive architecture is expected to come from optimal solutions developed through research organized via DFMP.
Contributing
Open an issue. Issues small enough for one person to finish carry the open-function label and appear on the board at drayker.org.
Related: bsdk · living-cryptography · dk
Other languages: Português · Español. Both currently behind this English version.
Content licensed CC BY 4.0.