Reference
Documentation
Where everything isDOC-0271
| file | contents |
|---|---|
proto/PUENTE.md | The contract between ONYX and its connectors |
url/index.js | Address analysis and lookup identifiers |
canal/index.js | The encrypted channel |
canal/entropia.js | Random number generation |
config/sitio.js | Domain and site details |
Each piece is explained inside its own file, not in a separate folder.
APIAPI-0272
| route | purpose | access |
|---|---|---|
GET /v1/prefix/:p | The addresses in one group | public |
GET /v1/keys | Public verification keys | public |
POST /v1/scan | Submit an address for analysis | with credential |
These routes do not exist yet. The contract is fixed and the implementation arrives with ONX-13.
What it does not solveLIM-0273
- A single issuer. Credentials are signed by ONYX. Splitting that role across independent issuers is still an open problem.
- Walking the groups. Given time, someone can query groups one by one and rebuild part of the list. A per-client limit is missing.
- Size and timing. The channel encrypts content. How many queries you make, and when, is still visible from the network.
- Pages that disguise themselves. A malicious site can detect our address range and serve a clean page.
These four are here and not in the small print. What ONYX offers is not that something is impossible, but that it cannot be done without leaving a trace.