自定义Substrate节点提交extrinsic至Polkadot前端遇1002验证错误

I’ve run into this exact issue after renaming a Substrate node template, so let’s break down what’s going on and how to fix it. The error message makes it clear: your frontend’s metadata and your node’s runtime have a mismatch in how they define the MultiSignature enum—either the frontend expects a variant your node doesn’t recognize, or vice versa.

Step-by-Step Fixes: #

1. Verify your runtime’s MultiSignature definition
   Head to your runtime/src/lib.rs file and locate the MultiSignature type alias. It should look exactly like this (or explicitly reference Substrate’s default enum):

   pub type MultiSignature = sp_runtime::MultiSignature;
   

   If you used a renaming script or manually edited types, make sure you didn’t rename the variants inside MultiSignature (like Sr25519, Ed25519, Ecdsa). These variant names are hard-coded in the Polkadot.js frontend’s type system—changing them will break compatibility immediately.

2. Recompile your node and export fresh metadata
   After confirming the MultiSignature setup is correct, recompile your node in release mode:

   cargo build --release
   

   Then export the latest metadata from your node. You can do this via the command line:

   ./target/release/your-custom-node-name export-metadata --raw > metadata.json
   

   Or pull it directly from the frontend later if your node is running.

3. Update the frontend with fresh metadata
   Open the Polkadot/Substrate frontend and:

   • Navigate to Settings > Metadata
   • Click Upload metadata and select the metadata.json file you just exported
   • Alternatively, if your node runs on the default port (9944), click Reload metadata to pull the latest directly from your node

4. Reset frontend cache and node connection
   Old cached metadata can linger even after updates. Fix this by:

   • Clearing your browser’s cache for the frontend site
   • Going to Settings > General and clicking Reset all settings (this wipes saved node connections and stale metadata)
   • Re-adding your custom node connection (double-check it points to your renamed node, not the original template)

Common Pitfalls to Avoid: #

• Renaming scripts sometimes modify deep type references in pallets or runtime files. Do a quick search for MultiSignature across your codebase to confirm no variants were accidentally renamed.
• Ensure all your pallets are compatible with your Substrate version—outdated pallets can introduce type mismatches that trigger this error.

If you’re still stuck, check your node’s runtime logs when submitting the extrinsic—they’ll often have more details about which variant is missing or mismatched.

内容的提问来源于stack exchange，提问作者sea212