Praxis sign in

Sign in with Sphere

Preparing the Sphere sign-in…

What does this do, and what should I check before approving?

If you keep your Praxis owner key in a Sphere wallet rather than in a local praxis-signer key file, you can sign in here without touching a terminal. Praxis opens your Sphere wallet in a second browser window and asks it to sign one short sign-in challenge; your private key never leaves the wallet and is never seen by this page.

  1. A Sphere wallet window opens at https://sphere.unicity.network. Approve the connection there — allow the popup if your browser blocks it.
  2. Praxis reads your wallet's public key and asks this server for a challenge addressed to it.
  3. Your wallet shows you the exact challenge text and asks you to approve signing it.
  4. Praxis checks the signature against the key enrolled for that challenge and opens your session.

Before you approve: only approve this signature when you started it yourself from a tab at https://praxis.blocky-dev.dev, and only in a window whose own address bar reads https://sphere.unicity.network. A signing request that appears while you are on any other site is not this sign-in, whatever it says.

Sign in with a local key instead
! Sign-in with a local praxis-signer key is unavailable: sign-in challenge issuance requires the request's origin and remote address plus a guardian-admitted write (packages/auth-http/src/server.ts's handleChallenge, mounted at POST /api/v1/auth/challenge) -- neither is reachable from a login page-read builder of shape (cspNonce) => Promise<LoginModel>. See packages/app/src/roles/app-pages.ts. Current issuance policy: 'origins'.. This is a deployment fact, not a rejection of any proof — nothing was submitted or checked.