Slipmark Cloud
By Reply Intelligence Group
Slipmark Cloud · Public anchors

We can't rewrite history either.

Every day we take the latest hash of every ledger and account log, sign a document listing them, and publish its SHA-256 to Sigstore's Rekor, a public transparency log we don't control. If any past record were changed, its chain would no longer reach a head published here.

Repositories and accounts appear only as opaque ids (the SHA-256 of "repo:" or "account:" followed by their internal id), so private names never leave Slipmark. Anchoring covers every plan; Business evidence packs show which id is yours. Signing key: public-key.pem (ECDSA P-256). How to verify

#PublishedLedgersDigest (SHA-256)RekorDocumentCheck it
829 Oct 2026, 03:17 UTC2 ledgers · 1 account logs682d9c58063be587…log index 35567637198.json
728 Oct 2026, 03:17 UTC2 ledgers · 1 account logsa6dca70ad216e466…log index 35328751147.json
627 Oct 2026, 03:17 UTC2 ledgers · 1 account logsd09c629b19cca6af…log index 35034430536.json
526 Oct 2026, 03:17 UTC2 ledgers · 1 account logs80426478ab72e91c…log index 34774190425.json
425 Oct 2026, 03:17 UTC2 ledgers · 1 account logs3020f150d7801d29…log index 34496014744.json
324 Oct 2026, 03:17 UTC2 ledgers · 1 account logsfeca4e7e922bef10…log index 34347605983.json
223 Oct 2026, 11:38 UTC2 ledgers · 1 account logsb2e7bc7cc3f78c70…log index 34190400752.json
122 Oct 2026, 18:37 UTC1 ledgers · 1 account logs6a73cd8f6926cbb5…log index 33969516981.json