All Veriox worker settings are managed from the portal — there’s nothing to configure in the worker code or wrangler.toml. Changes take effect within a few minutes without redeploying.
Portal configuration
Go to your worker in portal.veriox.io → Configuration to manage all of the following settings.
| Setting | Default | Description |
|---|
| Network | Testnet | Whether this worker verifies against Concordium testnet or mainnet. Switch to mainnet when you are ready to go live. |
| Age Threshold | 18 | The minimum age visitors must prove. See age thresholds. |
| Session Duration | 24 hours | How long a verified session lasts before the visitor must verify again. See session duration. |
| Excluded Paths | (none) | Pages that bypass verification entirely (e.g. your homepage, login page). See popup behaviour. |
For developers — Wrangler CLI
The behavioural settings above are not worker variables — they live in the portal and are applied to your worker automatically. The only thing the worker itself needs is your private key, set as a secret.
Secrets
| Secret | Required | Description |
|---|
VERIOX_PRIVATE_KEY | Yes | Your ECDSA private key (PKCS8, base64). Signs every request to the Veriox Platform API and is never transmitted. Set via wrangler secret put VERIOX_PRIVATE_KEY. |
Built-in values
Your Worker ID is baked into the worker code when you download it from the portal — there’s no variable to set. (For local development only, you can override it with a VERIOX_WORKER_ID value in .dev.vars.)
Example wrangler.toml
name = "my-site-age-verification"
main = "veriox-worker.js"
compatibility_date = "2024-05-01"
compatibility_flags = ["nodejs_compat"]
To change any verification setting, update it in the portal — it takes effect within a few minutes with no redeploy.
