RWA Tokens WatchCLAIM BY CLAIMevery issuer claim, checked

Admin keys: pause, freeze and blacklist functions

Published 2026-10-30 · Updated 2026-10-30 · Reviewed 2026-10-30

Admin keys authorize particular contract controls, including pausing operations or restricting selected addresses. Circle’s published code and policies illustrate three different mechanisms: a contract pause, address blocklisting and the removal of a blocklisting. Those controls operate at different levels and do not turn a completed USDC or EURC transfer into a reversible payment.

A pauser role controls contract state

In Circle’s published Pausable code, pause and unpause can be called only by the address assigned the pauser role. The functions set the paused state to true or false and emit the corresponding event. This is a contract-state control, with a named role determining who can invoke it. Circle Pausable code

The code distinguishes the pauser from the owner. Changing the pauser uses updatePauser and is restricted by onlyOwner. Permission to change the role is therefore represented separately from permission to call the pause functions. The source describes the role checks; identifying the controller of a particular live deployment also requires that deployment’s configuration.

Blocklisting targets an address

Circle’s USDC terms reserve powers to prevent specified addresses from sending or receiving tokens and to freeze them under applicable legal orders. Its help page describes blocklisting as restricting a selected address’s ability to send or receive USDC or EURC. The focus is the address’s interaction with those tokens. USDC terms

A contract pause changes a contract state; a blocklist entry applies an address restriction. In Circle’s examples, the first is expressed through the paused variable and pauser permissions, while the second concerns whether a specified address can send or receive the affected stablecoin. The mechanisms have different objects even when both limit token activity.

Removing a restriction is different from reversing a transfer

Circle expressly distinguishes blocklisting from reversing a completed transaction. Its blocklisting mechanism cannot retrieve a completed USDC or EURC transfer by undoing that transfer. Restricting future sends or receipts and reversing an already completed movement are different operations. Circle blocklisting explanation

Circle says it may remove a blocklisting when the relevant legal obligation ends or when a security incident no longer requires the restriction, subject to its policy assessment. Removal changes the address’s restricted status. It is a separate policy decision from the historical fact that a transfer has already completed.

Related questions

Who can change the pauser in Circle’s published Pausable code?

The owner. updatePauser is restricted by onlyOwner, while pause and unpause use the separate pauser role.

Can Circle lift a blocklisting without undoing an earlier payment?

Yes. Circle describes circumstances for removing an address restriction and separately explains that blocklisting cannot reverse a completed USDC or EURC transfer.

Sources

  1. Pausable.sol — Circle GitHub source repository accessed 2026-10-29
  2. USDC Terms — Circle accessed 2026-10-29
  3. Understand Circle stablecoin blocklisting process — Circle Help Center accessed 2026-10-29

For information only. Not investment, legal or tax advice, and not an offer or solicitation.

Spotted an error? Write to contact@rwa.ngo — corrections are logged publicly.