Community
Talk to the people building the network.
The conversations worth having now are architectural: what the primitives are, how they compose, and what is finished.
Channels
Where the conversation happens.
Three channels. No Discord server, no forum.
Telegramt.me/uninet_systemThe working channel. Protocol and node questions, answered by the people who wrote the layer.X@UniNet_DLTArchitecture notes and release-level updates. For a specific technical question, use Telegram.LinkedIncompany/uninet-technologyCompany updates, longer write-ups and hiring.
Scope
What to ask right now.
Some layers run, some run in part, some are not built yet.
Worth asking
Questions that get a real answer
- How agent identity and supervisors are modelled.
- What delegation can express in scope and expiry, and what it cannot.
- What each UNP relay sees.
- Where your design would break against any of this.
Not answerable yet
Questions we would answer badly
- Dates for subsystems still in development.
- Hardware-backed confidential computing or HSM key custody. Neither is implemented.
- Production cross-chain settlement.
- Price, listings and token mechanics.
Open questions
Where outside input still changes what gets built.
A concrete constraint from a system you run beats a general opinion.
01Authority models
Scoped, time-bounded, revocable delegation covers many cases. Tell us the one it does not.
02Governance structures
Bring the organizational structure that breaks the model.
03Privacy threat models
UNP is a routing architecture, not an anonymity claim. If your threat model includes the operator, describe it.
04Operator constraints
What your hardware makes cheap, and what it rules out. Reward parameters are not finalized.