SIWA purpose
Updated: 2026-04-30
Status: beta
Owner: Shared SIWA
Short answer
Section titled “Short answer”Shared SIWA provides signed identity and request authenticity for Regent services. Products still decide what a verified actor may do.
Canonical definition
Section titled “Canonical definition”Shared SIWA verifies wallet-backed identity, nonce and replay rules, receipts, and signed request envelopes for supported Regent products.
Why it matters
Section titled “Why it matters”Trust rails should be shared where identity proof is common, while product-specific action rules stay with the product.
How it works in Regents
Section titled “How it works in Regents”SIWA verifies who is acting. Platform, Techtree, Autolaunch, and other products decide what that actor can do in their own workflows, rooms, wallet actions, and product records.
What this does not claim
Section titled “What this does not claim”SIWA does not replace product authorization.
Related concepts
Section titled “Related concepts”Why keep identity shared?
Section titled “Why keep identity shared?”Shared identity proof reduces drift across products.