Technical Standard

Protocol Integrity & Security Deep Dive.

Explore how KeyFT leverages Trust-as-a-Service (TaaS) to secure field data through cryptographic validation and multi-layered sensor attestation.

Core 01 ☁️

Edge Infrastructure

Built on Cloudflare Workers and D1 Database for global zero-latency performance. Ensures data is processed in a distributed manner without any Single Point of Failure (SPOF).

Tech Stack

Runtime: Cloudflare Workers Storage: D1 SQLite (Edge) Security: JWS Attestation
Core 02 🔏

JWS Integrity Seal

Every mission report is cryptographically signed using JSON Web Signature (JWS). This ensures that data remains tamper-proof and immutable during transit.

Crypto Header

{ "alg": "HS256", "typ": "JWT", "kid": "worker_v4_anchor" }
Core 03 🤳

Face-API Liveness

Integrated biometric detection ensures physical human presence. The system verifies facial landmarks and liveness in real-time before the submission sequence is unlocked.

AI Audit

Verify: NeuralMatching(Face_Hash, Profile_DB) === true;
Core 04 🗑️

Auto-Purge Policy

For privacy and efficiency, the protocol automatically deletes raw reports 5 days after mission completion, retaining only the permanent verification hashes.

Data Lifecycle

if (currentDate > expiryDate + 5d) { purge(raw_data); keep(hash); }
Core 05 📍

Bounding Box Logic

Beyond standard GPS, KeyFT calculates radial distance server-side to prevent "Fake GPS" or coordinate spoofing on the client/worker browser side.

Geo-Fence

const dist = serverSideHaversine(client_loc, target_loc); if (dist > radius) throw Error("UNAUTHORIZED_LOC");
Core 06 🌳

NGO Settlement

Engineered to verify tree planting or social initiatives. Funds or payroll are only released if all sensor requirements (Photo + GPS + Biometric) are fully met.

Verification Flow

Status: (Sensor_Check && Biometric_Check) ? "VERIFIED" : "REJECTED";