One Bridge is refusing every bridge request with 'the bridge is temporarily disabled due to errors, please contact the administrator'. This proposal calls admin_restart_bridging() on dpjyw-raaaa-aaaar-qbxlq-cai to clear that state and resume bridging. It moves no funds.

Background: a BNB bridging task got stuck when a user's incoming transfer reverted on chain, having asked to bridge more tokens than their deposit address held. The version deployed at the time could not tell a reverted transaction from one that was merely unconfirmed, so it kept polling for a receipt that would never come, spent the canister's cycles on RPC calls, and once those calls started failing the error counter climbed to its limit of 42, which is what disables bridging.

v0.5.0, released in proposal 485, ends such a task instead of retrying it forever, and did so on the first finalization round after the upgrade: pending_logs() is now empty and the task is archived with its error, its amount and fee left out of the totals because nothing was bridged. Only error_rounds is still at 42, since it is not cleared when the queue drains, and that is what this call resets.

Proposal to execute nervous system function:

Nervous system function:

NervousSystemFunction { id: 1308, name: "Restart bridging on the one_bridge_canister canister", description: Some( "Restart bridging on the one_bridge_canister canister.", ), function_type: Some( GenericNervousSystemFunction( GenericNervousSystemFunction { target_canister_id: Some( dpjyw-raaaa-aaaar-qbxlq-cai, ), target_method_name: Some( "admin_restart_bridging", ), validator_canister_id: Some( dpjyw-raaaa-aaaar-qbxlq-cai, ), validator_method_name: Some( "validate_admin_restart_bridging", ), topic: Some( ApplicationBusinessLogic, ), }, ), ), }

Payload sha256:

0fee102bd16b053022b69f2c65fd5e2f41d150ce9c214ac8731cfaf496ebda4e

Payload:

record { record { 3_308 : nat64; false }; 42 : nat64; 0 : nat64 }