Clearnet (SearXNG)
BlepoOS's clearnet layer aggregates results from the open web using SearXNG — the same architectural pattern as DuckDuckGo and Startpage, but operated as Empoorio community infrastructure.
Design
- Multiple SearXNG nodes — no single point of failure
- HTTP/JSON integration from the
aephoron-blepoosRust crate (the same crate serves the results page) - HTTPS mandatory for all clearnet endpoints
- Fallback chain when a node is unreachable
Provider trait
BlepoOS uses a unified Provider trait in the monorepo:
rust
// components/blepoos/src/lib.rs
pub trait Proveedor {
fn buscar(&self, consulta: &str, categoria: Categoria, pagina: u32) -> Result<Respuesta, Error>;
}Clearnet providers wrap SearXNG instances. Web3 providers use Tantivy. The merge layer combines both.
Privacy
- Queries are not logged for advertising profiles
- No Empoorio user analytics on search content
- Node operators see aggregated uptime metrics only (public
/metricaspage)
Multi-node roadmap
| Phase | Goal |
|---|---|
| 1.1 | Single SearXNG node (blepoos.aephoron.com) — live |
| 1.2 | Configurable node list in browser settings |
| 1.3 | Community node registry on EmpoorioChain |
| 1.4 | DMS rewards for nodes meeting uptime SLOs |
Fallback behavior
If the node does not answer the health probe (/healthz, remembered for one minute), the browser sends the same query to DuckDuckGo and tells the user once — search never hard-fails. The return to BlepoOS is automatic.