multiversx-spec-compliance_skill

Overview

This skill verifies that MultiversX smart contract implementations match their whitepapers, technical specifications, and MIP standards. It helps auditors and developers map documented claims to code, detect deviations, and produce clear remediation guidance. The focus is on correctness of logic, tokenomics, and MIP compliance.

How this skill works

The skill extracts normative claims from specifications using keywords (MUST, SHOULD, MAY, etc.), maps each claim to the implementing code locations, and applies targeted verification techniques: formula checks, constraint enforcement, state-transition review, and MIP-specific validations. Findings are categorized by severity, documented with code references, and packaged into a compliance report with recommendations.

When to use it

• During security or specification audits of MultiversX contracts
• When validating tokenomics (supply, inflation, burn, distribution)
• To confirm compliance with MultiversX Improvement Proposals (MIPs)
• When reviewing upgrade proposals against the original spec
• To verify economic formulas, units, and precision handling

Best practices

• Use the exact spec version that matches the code commit/tag
• Extract and document claims explicitly using MUST/SHOULD/MAY language
• Check unit consistency (EGLD vs wei, seconds vs milliseconds, bps vs percent)
• Verify precision and scaled arithmetic for BigUint calculations
• Test boundary values and edge cases referenced in the spec
• Record assumptions and ambiguous spec interpretations in the report

Example use cases

• Confirm staking contract enforces the minimum stake and lock period specified in the whitepaper
• Verify reward/APY formulas match the documented formula and precision expectations
• Check NFT/SFT creation meets MIP-2 metadata, quantity and royalty requirements
• Validate inflation and epoch calculations against documented annual rates
• Produce a deviation report showing root cause and recommended code changes