Skip to main content

TideCloak 0.14.29

Summary​

TideCloak 0.14.29 lands the Payer and Midgard plumbing for the Stripe-backed billing story: subscription capacity endpoints, checkout line items, currency migration, wallet lifecycle state model, and Java/JNA wrappers for the new operations. It also introduces Policy v4 with optional signed policy expiry (v3 signatures continue to work), VRK authorizer-pack expiry renewal without wallet regeneration, and a 30-day grace period on the ORK side.

Key Features​

Payer / Midgard Plumbing : Midgard now exposes the Payer's endpoints for subscription capacity changes, currency migration, and capability checks. Checkout line-item support lets consumers purchase custom capacity bundles, and Payer ORK proxy exports cover pricing, subscriptions, and payment-method management. Currency support is now available on payment-method setup sessions.

Policy v4 Continued : Continues the Policy v4 signed-expiry rollout from 0.14.28, with the Midgard bridge surfacing v4 policy operations alongside the payer and lifecycle work. Existing Policy v3 signatures continue to verify.

VRK Authorizer-Pack Expiry Renewal : The VRK authorizer pack's expiry can now be renewed without regenerating the wallet, complementing the wallet-lifecycle work.

Wallet Lifecycle State Model : Added an explicit wallet lifecycle state model, with improved VRK regeneration and lifecycle handling.

Operation Status & Error Propagation : Operation status and error information now propagate across the Midgard bridge for the new payer and lifecycle operations.

30-Day Grace Period : ORK now applies a 30-day grace period.

Java / JNA Wrappers : Java and JNA wrappers added for the new payer and lifecycle operations.

Enclave SRI : sha256-k70kLV9gsftSFeU8yu5memp7cjJqF4QFtAOKzfTz+48=

Upgrade Notes​

  • Policy v3 signatures continue to work — no need to re-sign existing policies for v4.
  • Wallet lifecycle model is additive — existing wallets continue to operate; the new state model surfaces information without changing legacy behaviour.
  • VRK expiry renewal is optional — existing wallets keep working; the new endpoint is opt-in for operators who need to extend expiry without a full regeneration.

Detailed changelog​

For a granular per-repository breakdown of changes, see the detailed changelog.