Reasons the relay will refuse to open a ceremony session for an account.
A session is created for a Salt account, and the relay resolves that
account's signer set before it will mint one. These are the ways that can go
wrong for the hosting party:
NOT_ACCOUNT_SIGNER — the signer set was read, and the authenticated
address is not in it, or is in it at a different index than the partyId
this party registered with.
ACCOUNT_NOT_FOUND — the accountId names no account the Salt API can
resolve: malformed, or well-formed and unknown. Note this says nothing
about the caller — no signer set was ever read to check them against.
ACCOUNT_LOOKUP_FAILED — the signer set could not be read at all, so the
relay cannot tell whether this party is allowed in and fails closed. The
account may be perfectly valid and this party perfectly entitled to it.
MISSING_ACCOUNT_ID — this client sent no accountId while the relay
requires sessions to be account-bound. It predates account binding and
needs upgrading.
The relay can also refuse a host attempt with NOT_REGISTERED or
INVALID_SESSION_TYPE. Those are deliberately absent here: each means this
SDK sent something malformed — it registers the party on connect and passes
the session type itself — so they are bugs to fix rather than conditions an
application can act on, and they propagate untyped.
Reasons the relay will refuse to open a ceremony session for an account.
A session is created for a Salt account, and the relay resolves that account's signer set before it will mint one. These are the ways that can go wrong for the hosting party:
NOT_ACCOUNT_SIGNER— the signer set was read, and the authenticated address is not in it, or is in it at a different index than thepartyIdthis party registered with.ACCOUNT_NOT_FOUND— theaccountIdnames no account the Salt API can resolve: malformed, or well-formed and unknown. Note this says nothing about the caller — no signer set was ever read to check them against.ACCOUNT_LOOKUP_FAILED— the signer set could not be read at all, so the relay cannot tell whether this party is allowed in and fails closed. The account may be perfectly valid and this party perfectly entitled to it.MISSING_ACCOUNT_ID— this client sent noaccountIdwhile the relay requires sessions to be account-bound. It predates account binding and needs upgrading.The relay can also refuse a host attempt with
NOT_REGISTEREDorINVALID_SESSION_TYPE. Those are deliberately absent here: each means this SDK sent something malformed — it registers the party on connect and passes the session type itself — so they are bugs to fix rather than conditions an application can act on, and they propagate untyped.