Untilum
§04 · Developers

Implementable from the documents alone.

Read the spec, check the published vectors, open an issue against a section. Every Last Call comment gets a logged disposition — accepted, rejected with reason, or deferred.

View protocol on GitHubComment on a section
01

Ten RFCs, publicly reviewable

RFCTitleStatus
0001Protocol GoalsLast Call
0002Threat ModelLast Call
0003Trust ModelLast Call
0004Storage IndependenceLast Call
0005Beacon IndependenceLast Call
0006Identity ModelLast Call
0007Verification ModelLast Call
0008GovernanceLast Call
0009Compatibility PolicyLast Call
0010Capsule File FormatLast Call
02

Wire specifications

Normative — referenced by the RFCs, not restated by them.

Draft

Capsule Format v1 — Specification

Read spec →Draft

Untilum Protocol (TSP) — Version 1

Read spec →Draft

UDDP Container v1 — Autonomous Capsule File Format (.uddp)

Read spec →
§03

Two implementations. Byte-identical output.

RFC-0008 §4 requires two interoperating implementations of every mandatory feature before a version finalizes.

2
independent implementations — TypeScript reference SDK, independent Rust crate
4
critical tests, green in both — round-trip, no-time, no-password, forged-time
1:1
byte-identical UDDP containers across both generators, asserted in CI
0aff2c192db1502c29e175e7f3f4abd226de0cea1bc9cbdae1337a9d0c95f0d8 tsp-v2-mock-multibeacon.json 1bbd42cb60e05e14ee544b3f11f6ee498c6730d34295b59670a5a45bef6c813d tsp-v2.json 8d88181a46497f8afed2db9010fb1cb3d7c5dde19d5d8832fc10363e1c6ff72a uddp-cross-impl.json