dApps & permissions

Check revocation progress and failures

Confirm each permission removal rather than assuming a completed queue means every item succeeded.

Oath team1 min readUpdated Oct 16, 2026

Oath 4.0.3

Where to find it

Permissions → Recent changes

How to do it

  1. Open Permissions for the wallet used in the revocation.
  2. Open the history/progress entry for the removal or batch.
  3. Read each item’s network, asset, submission status and access result.
  4. For pending items, wait and refresh or reopen Oath after connectivity returns.
  5. For failures, read the reason, fix fee or network problems and prepare a new review for that item only.
  6. Rescan the access list and compare the exact permission after confirmation.

Submission, chain confirmation and verification that access is removed are distinct stages.

A batch can continue after one error and therefore produce successful and failed rows together. Review all selected entries, not just the last notification.

Closing the app may pause work; reopening and unlocking allows supported pending work to resume.

Follow along in Oath

Real app screens with illustrative demo data. No live funds were sent, swapped or revoked for these examples. Never send funds to an example address. Tap an image to inspect it at full size.

Token-access revocation review
1Inspect the asset, approved address and fee before authorizing removal. This is an unsigned demo revocation. See step 1.
Permissions overview
2Choose Token access, Collectible access, Account control, Connected DApps, Scan coverage or Recent changes as appropriate for the selected wallet.

Still need a hand?

Contact support about this article

A little more help

We’re here if you need us.

Tell us what happened. Keep recovery words, private keys and passwords private.

Contact Oath