DePIN Assets and Messaging
POSITRONIC adds an asset class for identity and memberships, and a private messaging layer whose membership is decided by that asset class. The full developer documentation is in the DePIN section. This page summarizes what the upgrade brings.
DePIN assets and messaging are available on testnet and regtest. Messaging follows protocol 2.
DePIN assets
A DePIN asset is a Neurai asset whose name starts with &, such as &DEVICE. It is designed for device identity, memberships and credentials.
| Property | Detail |
|---|---|
| Naming | &NAME root, &NAME/SUB sections for fleets or channels, &NAME! owner token |
| Units | Whole units only, no fractional supply |
| Soulbound | Holders cannot transfer. Only the owner token moves the asset. A holder may burn its own holding with selfrevokedepin |
| Owner controls | freezedepin and unfreezedepin per address. Unfreeze also undoes a self-revocation |
| Transfer states | Closed (default, soulbound), Open (holders may transfer), Sealed (owner-only forever, irreversible). Set with opendepin, closedepin, sealdepin |
| Sections | Issuing &NAME/SUB requires &NAME! and hands &NAME/SUB! to the receiver |
Typical uses: one asset per device, revocable access passes, per-cohort encrypted channels, gating an AI responder, soulbound badges and certifications.
Details and RPCs: Tokens and access.
DePIN messaging
An off-chain, encrypted, ephemeral message pool whose membership is defined by on-chain holdings of a DePIN asset. Nothing is written to the chain.
| Property | Detail |
|---|---|
| Access | Active holders of the token or any ancestor. Frozen and self-revoked holdings do not count |
| Confidentiality | ECIES with secp256k1 ECDH and AES-256-GCM. One ciphertext per message, one wrapped key per recipient |
| Integrity | DER ECDSA signature from the sender on every message. Every node reply signed with the pool key |
| Authentication | Single-use signed challenges. No sessions or bearer tokens |
| Transport | Standard JSON-RPC behind an RPC proxy. No dedicated port |
| Expiry | 7 days by default, up to 30 |
Details: Overview, Client guide, Protocol reference.
MCP responder
A node can run a background worker that connects the pool to any OpenAI-compatible chat endpoint, local or remote. Holders send a command such as /ai <prompt> in the encrypted channel. The worker decrypts it, calls the model, and posts the answer back as a signed, encrypted message for the token's holders. The conversation never leaves the encrypted channel and no third-party API sits in between.
Configuration and flags: Running a service node. Application patterns: AI integration.
Supporting changes
- Public key index (
-pubkeyindex): keys recovered from spends, so recipients and signers can be resolved from the chain. - Asset index (
-assetindex): holder lists and validity checks for DePIN assets. - Pool persistence: optional on-disk save of the message pool across restarts.
- Post-quantum messaging: adaptation of DePIN messaging to ML-DSA-44 keys is specified and in progress.