Protocol · Rules, governance & state machine
Protocol specification
Executable rules that govern human outcomes — state transitions, settlement logic, BYOE event primitives, and capacity admission. For system topology and ingestion consoles, see Architecture.
Core loop
Protocol Core Loop Stepper
Five stages from event ingest to settlement. Click a step or use the arrows to peek signal and gate — cards return to the stage label automatically.
Stage 01Developer POST ingests a BYOE primitive when an outcome should be requested.
State machine
State Flow & Transition Inspector
Pipeline auto-advances through the happy path — click any state or transition to take control.
| # | State | FWD | REJ | EXP | CAN |
|---|---|---|---|---|---|
01 | |||||
02 | |||||
03 | |||||
04 | |||||
05 | |||||
06 | |||||
07 | · | · | · | · |
Core value · BYOE
Bring Your Own Event
Define virtually any verifiable human outcome — pick a primitive below or type your own. Your product detects the moment; HaaS routes execution and settles on destination confirmation.
Verification rule
Ingest 200 OK starts routing only. Settlement requires destination 200 OK on the S2S outcome ping.
POST https://api.bthehype.com/v1/events/track
Authorization: Bearer haas_live_xxxxxxxxxxxxxxxxx
Content-Type: application/json
Idempotency-Key: req_user_signup_001
{
"event_type": "user_signup",
"verification_id": "usr_987654321",
"timestamp": "2026-08-27T14:30:00Z"
}
→ 200 OK — event accepted, routing beginsLedger
Settlement & Spread Breakdown
Network spread deducts only after verification — never on ingest, attempt, or deposit. Select an outcome to inspect the HYPEIT waterfall.
Credited to Operator wallet post-VERIFIED
Governance
Capacity Governance
Demand vs execution capacity — admission gates adjust as the network balances Developer programs and Node supply.
Developer admission
No window scheduled
Node admission
No window scheduled
Updated —