FOUNDATION • SIGNAL • DEVELOPERS
A Signal is a signed statement of presence. Your first Signal becomes Genesis—the start of a personal, tamper-resistant Signal Chain (SC). As Signals accumulate, your node strengthens the Meshwork: an open fabric for coordination, reputation, and verifiable activity.
1) Choose a Node ID. 2) Post a signed Genesis. 3) Land on your Signal Profile with a QR to share. Your node will appear on the Live Map (respecting your privacy mode).
Total Nodes
—
Active (≤10m)
—
Currently resonating
Active (≤60m)
—
Seen in the last hour
Each glowing point is a node with recent Signals—verifiable presence across the globe.
A Signal contains your nodeId, a timestamp, and a random nonce—signed via HMAC-SHA256 using your secret. The network verifies freshness and signature before updating public state.
nodeId|stickerId|ts|nonceThe SC is your personal, append-only ledger within the Meshwork. You control what’s posted, how it’s shared, and what apps can build on top—profiles, audits, rewards, and rituals all grow from your verified activity.
On-chain contracts anchor identity and emit events indexers can subscribe to. We favor a minimal, composable surface that pairs cleanly with off-chain systems.
Use REST to read/write or subscribe to event streams for real-time workflows. WebSockets (roadmap) will enable live subscriptions without polling.
GET /api/nodes — latest presence per nodePOST /api/mesh/ping — post a signed Signalcurl https://aesctrust.org/api/nodes
Great for analytics and reactive systems.
mesh.ping, mesh.attestLive topic subscriptions with backpressure and resumable cursors.
SDKs make Meshwork integration straightforward. Use TypeScript for apps and dashboards, or Python for data pipelines and analysis.
Typed client for REST + signatures + utilities.
import { MeshClient, signPing } from "@aesc/mesh";
const mesh = new MeshClient({ baseUrl: "https://aesctrust.org/api" });
const msg = { nodeId, stickerId: null, ts: Date.now(), nonce: crypto.randomUUID() };
const sig = await signPing(SECRET, msg);
await mesh.sendPing({ ...msg, sig, lat: 40.7, lon: -74.0 });Simple ingestion + streaming helpers.
from aesc_mesh import Mesh, sign_ping
mesh = Mesh(base_url="https://aesctrust.org/api")
msg = {"nodeId": NODE_ID, "stickerId": None, "ts": now_ms(), "nonce": rand_hex()}
sig = sign_ping(SECRET, msg)
mesh.ping(**msg, sig=sig, lat=37.78, lon=-122.41)Archetypes give symbolic shape to Meshwork design. Each maps to a practical concern in systems engineering and governance, helping teams reason about roles and responsibilities.
From live presence maps to rituals and audits—Signals are the primitive that powers coordination. Here are a few directions to build.
Subscribe to mesh.ping and light up verified presence for your product or community hub.
Translate resonance windows into sound/visuals; mint badges when synchronized activity surpasses thresholds.
Periodic budgets reconcile on a C96 cadence with verifiable Signals and attestations.
Last signal
Post a Signal in Getting Started to see it here.
