Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.neuro-tech.io/llms.txt

Use this file to discover all available pages before exploring further.

The Neuro security model is built around identity, trust, signatures, federation, and controlled access. Instead of relying on anonymous participation and proof-of-work, the platform uses strongly identified actors, Trust Providers, authenticated communication, signed objects, and auditable operations. This is a core difference between Neuro and more traditional distrust-based distributed systems.

​
Security starts with identity

In Neuro, security is not only about encrypting traffic — it starts with knowing who is participating. Participants have network identities and, where relevant, cryptographically secured legal identities. Those identities are part of how access, signatures, contracts, and traceability work across the platform.

​
Security principles in the platform

The model is built on:
  • Identified participants — actors are known, not anonymous
  • Federated domains — each domain governs its own environment
  • Trust relationships — cooperation is based on established trust, not open access
  • Consent-based access — access is not assumed by default
  • Cryptographic signatures — used to protect identities, contracts, records, and actions
  • Auditable actions — important operations are traceable over time
  • Algorithm agility — cryptographic methods can evolve over time, avoiding long-term lock-in to fixed algorithms
That last point is important: cryptographic methods should be able to evolve over time, instead of being permanently fixed into the infrastructure in a way that creates long-term risk.

​
Why federation matters for security

The platform is designed for cross-domain systems. That means security cannot depend only on one application boundary or one central operator. Federation allows different domains to manage their own environments while still interoperating in a controlled and standardized way. That gives the platform a model better suited for real collaboration across organizations and systems.

​
The role of signatures

Signatures are central to the security model. They are used to protect:
  • Identities
  • Contracts
  • Ledger-backed records
  • Token-related actions
  • Important platform objects
This helps provide integrity, traceability, and non-repudiation across the platform. Access is not assumed by default. The platform is built around controlled interaction based on trust, consent, and authorization — important for systems where participants need to exchange information or act on shared resources without exposing everything to everyone.

​
Why algorithm agility matters for long-lived systems

The platform’s emphasis on algorithm agility is not theoretical. Systems built on Neuro are intended to last for years or decades — medical records, land registries, sustainability ledgers, and infrastructure IoT systems all operate on long timescales. A security model that locks in one cryptographic algorithm permanently creates technical debt that becomes a liability as algorithms age. Neuro’s design allows algorithms to be renegotiated and replaced without breaking the trust model or invalidating historical records.

​
Key takeaways

When designing with the platform, think about:
  • Who the actor is
  • What identity level is required
  • What must be signed
  • What should be recorded
  • What must be restricted
  • How actions will be validated later
Security in Neuro is identity-first, signature-based, and built for interoperable systems.

​
Further reading

Neuro-Foundation

Platform specification and standards

TAG Documentation

Neuron and associated technologies

TAG Community

Tutorials and implementation guides