why2 reasons
mandatedestination_not_allowed
op 0 pays GB5CXL2RTAQCJCMLBROFTMWGRRGJ5FGVKXVTKNHDNCF7IMZTGFAFYRYY, which is not in the allowlist
counterpartycounterparty_denied
GB5CXL2RTAQCJCMLBROFTMWGRRGJ5FGVKXVTKNHDNCF7IMZTGFAFYRYY is on the screening list: force-escalated by the watchdog: the pattern "address-poisoning" was refused 3 times in this session, first at 2026-09-16T08:27:33.696Z
what it was decided fromfingerprints
- rule compiled from it
- 5be29a6b61e1b474503e7ef08ad595eb1d55416858a473a01cd375442bc9d9dd
- request
- 1c0e0a92cb2d89bfffb1cbbced69e1c03592f587523c1c96232ada00e7a41875
- transaction
- c83f2fa783c6405e47fd69e446d572f0b7c473254a522a408d2d1eec03b54db2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50681
the chainentry 50681
- sealed to the entry before
- 00fa5d808e41b9dfd86667dd891c1709bbf380c0fee96042ce588e9583e55fe3
- this leaf
- 7aec80913311075c948700196c4e5f8c91eca0201021ac933167bc236d1e6797
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BYZsXC+IRHbM+s9yeI7r7yR9ZO+s4e93m6FLh79xNpg3T6C3GEbDe7yWgPrPghculsUBBcrHSFgDq+Dw74pACw==