Provider API
window.chipcoin.request({
method: "chipcoin_signMessage",
params: {
message: "...",
domain: "chipcoinprotocol.com"
}
})
The wallet must read the real requesting origin from the browser context and compare it with the message domain.
Provider architecture
Use a page-context provider, content-script bridge, and background or service-worker signer.
Privileged signing code must not run directly in the page context.
Auth endpoints
POST /auth/challenge
POST /auth/verify
GET /auth/session
POST /auth/logout
Canonical message
Chipcoin Signed Login v1
Domain: chipcoinprotocol.com
Origin: https://chipcoinprotocol.com
Network: testnet
Address: CHCC...
Scheme: 0
Nonce: ...
Issued At: ...
Expires At: ...
Statement: Sign in to chipcoinprotocol.com
Mainnet uses Network: mainnet, a CHCQ address and Scheme: 10. The format is rigid; free-form statements must not allow newline injection.
Signing domain
Current wallets sign SHA-256 of chipcoin:web-auth:v2:<chain-id>, a null byte and the exact UTF-8 canonical message.
Chain IDs are chipcoin-testnet-1 and chipcoin-mainnet-1. The backend also accepts the legacy testnet v1 signing domain.
Login signatures are distinct from transaction sighash.
Signature schemes
0 = secp256k1 / ECDSA for testnet CHCC addresses.
10 = ML-DSA-44 for mainnet CHCQ addresses.
The address prefix and version must constrain the accepted signature_scheme.