FAQ

TNTS signed-envelope messaging FAQ

How does TNTS reduce content-based blocking?

Delivery state transitions are based on envelope validity and route policy, not payload sentiment or language scoring.

What does deterministic message routing mean?

The sender and recipient node path is resolved using explicit routing logic and can be audited through lifecycle events.

What are TNTS lifecycle states?

SENT, ROUTED, DELIVERED, OPENED. Each transition can be represented by signed event records.

What is envelope proof?

A cryptographic signature block (ed25519 in draft examples) attached to envelope and receipt events.

Does TNTS provide realtime transport visibility?

Yes. Event streams expose state changes without requiring platform inspection of message content.

Where is the API shape documented?

See /developers/api for endpoint contracts and envelope schema snippets.