Changelog

BRS now settles on Polygon PoS in both environments: Polygon Amoy in sandbox, Polygon mainnet in production. It is the third EVM chain after Ethereum and Base.

• Token: the same contract address as Ethereum and Base for each environment. See the Addresses page for addresses and explorers.
• Intents: send chainId: "polygon" on onramp and offramp intents; the destination or burning wallet must be whitelisted on your Polygon whitelister.
• Wallets: register and authorize destination wallets through the Wallets API with chainId: "polygon". Calldata comes back with chainRef: "eip155:137" (mainnet) or "eip155:80002" (Amoy).
• Dashboard: Polygon is selectable in both environments. Add wallet now signs the grant in-browser on every EVM chain, Ethereum and Base included; it was API-only before.

The whole flow is the one in Ethereum end-to-end with chainId: "polygon". To enable Polygon for your organization, contact Nora to provision your whitelister.

BRS now settles on Base in both environments: Base Sepolia in sandbox, Base mainnet in production.

• Token: the same contract address as Ethereum for each environment. See the Addresses page for addresses and explorers.
• Intents: send chainId: "base" on onramp and offramp intents; the destination or burning wallet must be whitelisted on your Base whitelister.
• Wallets: register and authorize destination wallets through the Wallets API with chainId: "base". Calldata comes back with chainRef: "eip155:8453" (mainnet) or "eip155:84532" (Base Sepolia).
• Dashboard: Base is selectable in both environments.

Everything in Ethereum end-to-end applies unchanged with chainId: "base". To enable Base for your organization, contact Nora to provision your whitelister.

BRS now settles on Ethereum mainnet in production, alongside Solana. Sandbox keeps using Sepolia.

• Token: 0x0000006238e3C7797Ae71827da303560bae1B125, 6 decimals.
• Intents: send chainId: "ethereum" on onramp and offramp intents; the destination or burning wallet must be whitelisted on your Ethereum whitelister.
• Wallets: register and authorize destination wallets through the Wallets API. Owners that are contract wallets (Safe, smart accounts) can submit the wrapped transaction hash, or activate with sync when the hash is not at hand.
• Dashboard: Ethereum is selectable in production. Wallet setup for Ethereum remains API-only for now.

Start with Ethereum end-to-end: whitelist, mint and burn in one pass, with the responses the sandbox returns. See Wallet whitelisting → Path C → Reference: addresses, limits and owners for addresses, limits and the grant flow. To enable Ethereum for your organization, contact Nora to provision your whitelister.

Webhook delivery history is now available in Webhooks → Deliveries. Filter deliveries by endpoint, event type, or status, and open a delivery to see its response and each recorded attempt.

Eligible events can also be redelivered from the delivery details. The page shows the redelivery status while it is queued or processing.

For deliveries created before detailed history was available, the page identifies attempts that are not available individually.

You can now select Ethereum as a chain in the dashboard, alongside Solana. Use the chain selector in the Mint / Burn dialog to choose where BRS is minted or burned. Ethereum is available on Sepolia (Sandbox) first.

Ethereum wallet setup is API-only for now: register and authorize destination wallets through the Wallets API with chainId: "ethereum". The Wallets page lists them read-only — same layout as Solana, behind the chain selector — and an active wallet becomes selectable as a mint destination. Mints settle on-chain (Nora signs and broadcasts); burns are prepared by Nora and submitted from your own wallet.

To enable Ethereum for your organization, contact Nora to provision your whitelister for the chain.

Organization owners can now manage separate Sandbox and Production Pix-key allowlists from Sidebar → Pix Keys. Use the instance picker to select an environment. Each environment accepts up to 20 Pix keys, including CNPJ, EVP, email, and Brazilian phone keys.

Use the allowlists to prevent offramps to unapproved destinations. An empty allowlist blocks offramps unless the temporary empty-allowlist bypass is enabled.

Creating an organization now asks for its CNPJ, validated as you type. The number carries into KYB, so the company step arrives pre-filled instead of asking again.

Organizations created before this change show a prompt in Settings → Organization to add the missing CNPJ.

The /v2/wallets reference documents every endpoint, request field and response shape for registering and listing wallets.

A companion wallet whitelisting flow walks the whole path end to end: register the wallet, rebuild the returned instruction, sign and broadcast it yourself, then sync with the transaction signature.

Owners can now manage the list of emails that receive security alerts from Settings → Security. Add or remove recipients at any time; admins see the list read-only.

With no recipients configured, alerts keep going to the organization owner.