What Changed Inside the Gnosis Bridge?
A recent change in the Gnosis bridge is easy to miss because the destination has not changed: USDS has replaced DAI as the default Ethereum-side asset in the native xDAI bridge. xDAI is still minted on Gnosis, but the bridge is no longer best understood as a simple DAI lockbox. That matters when a transfer appears complete on one chain while the balance update is happening through the other chain’s consensus machinery.
The mint is a consensus action
On Ethereum, the user first approves the foreign bridge and calls relayTokens(recipient, value). The contract emits UserRequestForAffirmation, carrying the recipient, amount, and a nonce. Validators watch that event rather than trusting the front end’s preview. The bridge uses a 4-of-7 validator majority; once enough validators affirm the request, they call executeAffirmation on Gnosis.
That call does not merely transfer an ERC-20 balance. It invokes Gnosis’s block reward contract, which records the receiver and amount. The consensus engine then credits native xDAI in the next block. This is why a normal token-transfer trace can look incomplete: the useful evidence may be an AddedReceiver log, followed by a changed native balance at the relevant block, rather than a conventional token Transfer event.
The reverse route has a different shape. Sending xDAI to the home bridge burns the equivalent amount and emits UserRequestForSignature. Validators sign the withdrawal message on Gnosis; after the threshold is collected, anyone can submit the signatures to the Ethereum bridge with executeSignatures. The destination contract then releases the corresponding Ethereum-side asset. With the current migration, that can mean USDS as the bridged asset, with conversion to DAI handled on the Ethereum side where applicable.
There are two operational details worth keeping in muscle memory. First, xDAI is native currency, while wxDAI is its ERC-20 wrapper; protocols that need token semantics usually want wxDAI, not a second bridged asset. Second, a raw transfer to the foreign xDAI bridge is no longer the reliable initiation path for minting on Gnosis. Use the bridge’s relay call so the request is encoded and indexed correctly.
Where the interface fits
The interface is deliberately thin. The Gnosis Bridge page is a compact front end that previews the Ethereum-to-Gnosis DAI/xDAI route, displays the Gnosis Chain balance and a 0.5% slippage setting, and passes the swap action to the bridge application. That preview is useful for checking the intended asset and recipient, but it is not the settlement mechanism: the contracts, validator affirmations, nonce, and destination execution are.
The 0.5% number belongs to the swap quote, not the validator threshold or bridge fee; changing it cannot accelerate a pending affirmation. It only changes how much price movement the interface accepts before the quoted action is rejected.
For routine operations, I watch the request event and nonce first, then the validator execution, then the native balance. If the first transaction is final but xDAI is absent, the question is not “did the UI succeed?” It is whether the affirmation threshold has been met, whether daily or per-transaction limits blocked execution, or whether the balance was credited through the block reward contract and is only missing from the wallet’s display. Those distinctions turn a vague bridge delay into a short, inspectable state machine.