[runtime, tesseract]: incentivise request from hyperbridge by dharjeezy · Pull Request #822 · polytope-labs/hyperbridge

dharjeezy · 2026-05-12T14:20:23Z

This PR adds a per destination BRIDGE reward for relayers that deliver hyperbridge originated requests. Closes #532.

The pallet gains a new claim variant claim_outbound_request_delivery_reward paid from the existing treasury, idempotent on the request commitment, and valid or both EVM and substrate destinations. The shape mirrors the existing claim_outbound_consensus_delivery_reward so verification reuses the same state proof and signature primitives.

The tesseract messaging task gains a sibling claim pipeline. After dest.submit(), receipts whose query.source_chain equals the hyperbridge coprocessor get persisted to the local DB and pushed onto a new claim channel. A new task consumes that channel, waits for hyperbridge's view of the destination to catch up, builds the state proof, signs outbound_request_delivery_message(commitment, destination, payee), and submits the claim. Responses are filtered out at the trigger because the incentive is request only.

seunlanlege · 2026-05-13T12:12:35Z

Not all requests from hyperbridge should be incentivized, we should make it take an allow list eg: pallet-host-executive, pallet-bandwidth etc

…rbridge-request # Conflicts: # tesseract/messaging/messaging/src/outbound.rs

…rbridge-request

…rbridge-request Resolve conflicts against main's refactors while preserving the outbound request-delivery incentive work: - relayer pallet: adopt main's module split (accumulate/outbound_consensus) and add the request claim as a new outbound_request module; re-home our storage, errors, events, calls (index 5/6) and validate_unsigned arm into main's slim pallet module. Adapt process_outbound_request_delivery_claim to main's 3-arg verify_withdrawal_proof (validate_state_machine precursor). - events.rs / outbound.rs: drop PostResponse handling (removed in #840) and adapt to the request-only TxReceipt struct; keep retain_incentivized_requests and the on-chain allowlist filter; keep the router-id removal from this branch. - testsuite: convert SubstrateStateProof::OverlayProof to bare StateMachineProof (enum removed on main). - gargantua spec_version -> 7_200 (above main's 7_000). Verified: pallet-ismp-relayer, gargantua-runtime, messaging, subxt-utils all compile; 15 outbound_request_delivery pallet tests and 10 messaging outbound tests pass; cargo metadata --locked clean.

Update the design doc to match the merged shape: reward keyed by module_id, the claim living in the outbound_request module, the three argument verify_withdrawal_proof, request-only TxReceipt, the BTreeSet allowlist snapshot, and the refreshed error list and test counts.

…/incentivize-hyperbridge-request # Conflicts: # parachain/runtimes/gargantua/src/lib.rs

Wizdave97

Let's not have duplicate implementations of the same thing

…/incentivize-hyperbridge-request # Conflicts: # tesseract/messaging/substrate/src/calls.rs

The `destination == request.dest` check in process_outbound_request_delivery_claim was untested; the rest of the verification pipeline had explicit rejection tests but this one did not. Add a case that registers a valid, allowlisted, unclaimed commitment for an EVM destination and then submits a claim whose state proof is for a substrate destination instead. Asserts the pallet rejects with MismatchedStateMachine before reaching state-proof verification.

Cuts a new release after the outbound request delivery reward claim pipeline (#822) lands. Minor bump reflects the new outbound-request claim task, the sibling DB-backed claim persistence, and the `incentivized_outbound_request_modules` allowlist fetch — additive features with no breaking changes to existing relayer behaviour.

incentivise request from hyperbridge

4f6e099

dharjeezy requested review from Wizdave97 and seunlanlege May 12, 2026 14:20