@paramira/auth-sdk
License: MIT
Source: packages/auth-sdk · on npm as @paramira/auth-sdk
What it does
Lets a third-party ("relying party") app verify that its visitor controls a paramira community identity (did:iwacu:...) — without that app ever touching the identity's private key. The key stays in whichever paramira app the person already trusts (abantu, isoko, iwacu); your app just asks that app to vouch for them.
Once you have a verified DID, you can gate features by whatever community protocol the person has adopted — see Checking a feature below. No sign-in is needed for that part; the adopted-protocols endpoint is public by design.
A minimal working example — "Sign in with abantu" gating a feature in a small community app — is in demo/.
Used by
Apps: abantu
Services: directory
Uses
agreements
The canonical payload for signing an agreement-type protocol: a hash of the exact clauses and version, built identically by the app that signs and the directory that verifies.
blind-tokens
Anonymous, rate-limited, publicly verifiable membership tokens: an issuer signs a blinded message once per member per epoch (RFC 9474 blind RSA, via @cloudflare/blindrsa-ts), the member unblinds a token the issuer can't link back to them, and anyone can verify it against the epoch's public key. Plus an issuance ledger that refuses a second token and repeats a lost one.