Skip to main content
These are the research documents that shaped NTL. They sit alongside the polished protocol docs and are intentionally rawer — they capture the why behind the architecture, not only the what. Read these when you want to understand why NTL is designed as an actual neural network rather than a messaging protocol, why the signal is a new concurrency primitive rather than a message type, and why IPv6 is a hard requirement rather than a preference.
NTL is a transport layer and specifies storage only as an interface. For complementary work on graph-native storage, see siafudb.org — one ecosystem backend among several, not a dependency.
Last modified on September 11, 2026