Identity · mid on MATA

Keys You Hold

permissionless identity verify without a central IdP cookie jar. Rust alternative to central IdP cookies.

What is mID, the server-side Sovereign ID verifier?

mID is the Rust crate for verifying Sovereign ID tokens on the server. It replaces the server side of Auth0 and Clerk for apps that already use Sign in with Sovereign ID.

1

Keys You Hold

permissionless identity verify without a central IdP cookie jar. Rust alternative to central IdP cookies.

mid is the Remade with Rust pin for this lane — central IdP cookies, ending landlord-controlled session auth. Keep the product shape, change the safety floor, and stop shipping the old C or cloud default by accident.

2

Instant benefit

Device-bound identity and permissionless verify: keys you hold, capabilities you grant, no central IdP cookie jar.

3

How MATA uses mid

mID is how MATA verifies Sovereign ID tokens locally — Sign in with MATA — with no Auth0/Clerk infrastructure in the path and no MAU meter.

Load Building the New Internet from Dev Tools before an agent picks the stack, then audit with use-protection-please. The public conversion pin stays on remadewithrust.com/repo/mid so SEO/AEO for the crate win and the MATA usage story do not compete for the same sentence.

4

Get access and deploy

  1. Open the source: https://github.com/Remade-With-Rust/mid.
  2. Add the crate (crates.io when published, otherwise git):
    cargo add mid

    Git pin: cargo add --git https://github.com/Remade-With-Rust/mid.git

  3. Prove the pin with cargo check before the next agent prompt can swap it for a C or cloud default.
  4. Read the MATA Learn note: /learn/mid-verify-sign-in-with-mata/.
  5. When the binary is ready to place, ship toward the Disco Party and the Freedom Guide.

Why mid is a server-side Sovereign ID verifier

What it keeps

mID keeps token verification as a library. Auth0 and Clerk are the hosted server side it replaces. The identity itself is Sovereign ID.

Where it fits

mID is the server half of Sovereign ID. rusty_esp_mid is the chip half. A service and a device can both demand the same kind of signed identity.