feat(nats): content-addressed object storage, so an answer can be named instead of carried #84
Owner
- Added Ability to store bytes under their own SHA-256 digest and fetch them back by that digest, making the address a function of the content and repeated stores idempotent
- Added Ability to verify content against its address on read, so storage that returned substituted or corrupted bytes fails instead of being passed off as the answer
- Added Function to ensure an object-store bucket exists, idempotent like the existing KV helper, with bucket naming and retention left to the caller
- Added Ability to store bytes under their own SHA-256 digest and fetch them back by that digest, making the address a function of the content and repeated stores idempotent
- Added Ability to verify content against its address on read, so storage that returned substituted or corrupted bytes fails instead of being passed off as the answer
- Added Function to ensure an object-store bucket exists, idempotent like the existing KV helper, with bucket naming and retention left to the caller
peersky
added 1 commit 2026-08-27 05:07:27 +00:00
All checks were successful
CI / Dependency Age Check (pull_request) Successful in 17s
Details
CI / Lint & Audit (pull_request) Successful in 1m22s
Details
CI / Spell Check (pull_request) Successful in 6s
Details
Commit Lint / Validate PR Title (pull_request) Successful in 3s
Details
Publish Release / Create Tag & Sync (pull_request) Has been skipped
Details
Publish Release / Publish to crates.io (pull_request) Has been skipped
Details
Publish Release / Publish dry-run (no side effects) (pull_request) Has been skipped
Details
Publish Release / Create GitHub Release (pull_request) Has been skipped
Details
CI / Test (pull_request) Successful in 5m2s
Details
Merge pull request 'feat(nats): content-addressed object storage, so an answer can be named instead of carried' (#84) from feat/content-addressed-object-store into dev
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/content-addressed-object-store"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?