ECP Proof Card

Why does it take 669 bytes to tell a computer there is a fire?

ECP encodes the core alert fields in 8 bytes. Fire, flood, security, IoT threshold, fleet beacon — same compact format.

CAP XML 669 bytes
JSON 270 bytes
ECP UET 8 bytes
98.8% less data
Same core fields, many scenarios.
Run ID: #pending
Proof hash (CLI canonical): 8a5340fce836
Compare protocols live → Verify in CLI (ProofCard)

UET (8 bytes) is the compact unsigned token. For cryptographic signing, use an Envelope (typically 42 bytes with HMAC). These values are live-measured in the CLI ProofCard tool. This page shows the canonical FIRE scenario for instant sharing. Clone the repository to verify independently, including the raw payloads via -- --show-payload.

git clone https://github.com/Egonex-Code/ecp-protocol cd ecp-protocol/samples/ProofCard dotnet run dotnet add package ECP.Core