Skip to content

test: pin owner-signed renewal lease vector - #546

Draft
samgbafa wants to merge 3 commits into
feat/tc-renewal-contract-vectorsfrom
feat/node-renewal-lease-vector
Draft

samgbafa wants to merge 3 commits into
feat/tc-renewal-contract-vectorsfrom
feat/node-renewal-lease-vector

Conversation

@samgbafa

@samgbafa samgbafa commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Vector-only follow-up stacked on #545. Pins the owner-signed UCAN renewal lease and the signed original grant, deriving the canonical urn:cid:<original CID> target from the original bytes. Adds a renewer-signed first stamp linked to the actual lease CID (leaseCid == previousStampCid), and pins its bytes, signature, and CID. The period is derived from the owner's signed original exp - nbf (30 days); the lease's 365-day expiry is a separate upper bound. nodeDid is the stable node identity; the dedicated renewer DID/key signs the stamp.

No runtime implementation or production behavior. Fixed keys and timestamps are public test vectors only.

Validation: cargo test -p tinycloud-node --test renewal_lease_v1_vectors --test renewal_stamp_v1_vectors --offline passed (2 suites); cargo fmt --all --check passed. The linked-stamp regression was first observed failing against the unlinked fixture, then passed with the pinned vector.

Please confirm this lease vector together with frozen stamp vector #545 before runtime code depends on either.

Next-slice fixture appendix: freezes the proposed owner-authenticated stop/re-enable/state-read contract and its three synthetic signed request samples. This is documentation and public synthetic fixture data only. Do not consume these proposed strings in runtime until the next slice is authorized.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant