pmm-debug-sig

Diagnose EIP-712 signature and Permit2 failures in PMM RFQ Protocol.

3|9|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/okxlabs/Web3-DEX-EVM-PMM --skill pmm-debug-sig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmm-debug-sig
Source: https://github.com/okxlabs/Web3-DEX-EVM-PMM/tree/main/.claude/skills/pmm-debug-sig
Command: npx skills add https://github.com/okxlabs/Web3-DEX-EVM-PMM --skill pmm-debug-sig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix EIP-712 signature issues in the OKX PMM RFQ Protocol, including OrderRFQ and Permit2 signatures, to prevent on-chain reverts and signer mismatches.

Core Features & Use Cases

  • Comprehensive diagnostic workflow covering domain separators, typehashes, struct hashing, and witness type handling for both OrderRFQ and Permit2.
  • Step-by-step debugging templates and on-chain verification checks that help engineers reproduce and resolve signature errors across chains.
  • Use Cases: when RFQ signatures fail, Permit2 signatures revert, or digest mismatches occur during PMM integration.

Quick Start

Provide a failing PMM RFQ or Permit2 signature payload along with the corresponding order fields to the debugger to obtain digest and signer verification results.

Frequently Asked Questions about pmm-debug-sig

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my PMM RFQ signature fail with a digest mismatch on cross-chain transactions?

Cross-chain PMM RFQ signature digest mismatches typically occur when domain separators or typehashes are constructed incorrectly for the target chain. Verify that the EIP-712 domain parameters match the specific chain ID and contract address deployed on that network.

How do I debug Permit2 signature reverts in the OKX PMM RFQ Protocol?

To debug Permit2 signature reverts in PMM RFQ, provide the failing Permit2 signature payload and order fields to the diagnostic workflow. It checks witness types, struct hashing, and on-chain verification steps to pinpoint the revert cause.

What is needed to verify an EIP-712 OrderRFQ signature on-chain?

On-chain EIP-712 OrderRFQ signature verification requires the correct domain separator, typehash, and properly hashed struct fields. The diagnostic workflow specifies these exact requirements and provides step-by-step templates for on-chain verification checks.

Can I use this debugger for Permit2 witness type issues across different blockchains?

Yes, this debugger applies to cross-chain Permit2 witness type issues within PMM RFQ. It provides comprehensive diagnostic templates that cover witness type handling and struct hashing to reproduce and resolve signature errors across different chains.

What should I provide to start diagnosing a failing PMM RFQ signature?

To start diagnosing a failing PMM RFQ signature, provide the failing signature payload along with the corresponding order fields. The debugger processes this input to output digest and signer verification results for troubleshooting.

What are common limitations when troubleshooting EIP-712 signature errors in PMM?

Troubleshooting EIP-712 signature errors in PMM is limited by incorrect domain separator construction or mismatched typehashes. If the on-chain verification environment or contract deployment addresses are incorrect, the diagnostic results may not accurately reflect the revert scenario.