why3 reasons
mandatedestination_not_allowed
op 0 pays GDNZXXNULVBMJYSRVIC2AKI4QSP4FAYEFSPU4PMINZV3S73FAS5JHNB5, which is not in the allowlist
counterpartycounterparty_denied
GDNZXXNULVBMJYSRVIC2AKI4QSP4FAYEFSPU4PMINZV3S73FAS5JHNB5 is on the screening list: force-escalated by the watchdog: the pattern "tool-poisoning" was refused 1 time in this session, first at 2026-09-16T08:27:20.098Z
post_approval_integritydefinition_changed_since_approval
the tool or contract definition fingerprinted a3f1c0de9b7452e8 when the human approved and fingerprints 77b2e4901ac6df35 now. the approval covers something that no longer exists
what it was decided fromfingerprints
- rule compiled from it
- dba3bc173cae575c5328fca615a0d0ab207d46f81bc4e0073524c64c5347cd9d
- request
- c6401b9d5f705d3f5b26cc3bd87a8d038eb4b835a2a0529248bf3fa0cd3eece8
- transaction
- af223217aa5cb5d928fe557011bbc666af9f6d579f73e750accf205a7cd8c542computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50367
the chainentry 50367
- sealed to the entry before
- 3144440aba8545cd5a6a6724e877588a1d1219dfbff98974c1a574aa65102db6
- this leaf
- 7ffd971c7877277c0760799d005a1650e5639833fcef71b701046b705c2c6fab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dYJqtA1l7cKGB1cIl0BAkRqwE7mf1ffbdbSkUovrycMtu5gkcdCApK7CjUrG8PyEzd4QT0YcX/8AXYk/YoLDBw==