Contract Version Registry Publisher

WHAT IT DOES

Contract Version Registry Publisher allows you to publish smart contract versions to an on-chain registry. You provide a registry contract address, the contract address to register, a semantic version number (e.g., 1.0.0), optional metadata as JSON, and optional tags. The tool prepares a registration transaction and, upon your confirmation, sends it to the blockchain to record the version in the registry. This is essential for upgradeable contract systems, protocol version management, and any project that needs to maintain a public or private record of deployed contract versions. Registered versions become discoverable and auditable, enabling users and other contracts to query which version of a contract is deployed at a given address.

HOW TO USE

Enter the registry contract address. Enter the contract address you want to register. Specify a semantic version in the format major.minor.patch (e.g., "1.0.0"). Optionally add metadata as a JSON object (e.g., {"name":"MyToken","description":"ERC-20 token"}). Optionally add comma-separated tags (e.g., "stable,production,audited"). Click "Prepare Registration." The tool validates the inputs, displays a summary of the registration details, and shows a preview of the data to be published. Review the information and click "Publish to Registry." Your wallet will prompt you to confirm the transaction. Upon confirmation, the version is recorded on-chain. The tool displays the transaction hash and a success message.

THE REAL MECHANISM

The tool uses a minimal registry ABI that includes a registerVersion function with parameters for the contract address, version string, metadata string, and tags string. When you prepare a registration, the tool validates the inputs (contract address format, semantic version format, and JSON metadata). When you publish, it creates a contract instance using the registry address and the ABI, estimates gas using estimateGas with a 20% buffer, and sends the registerVersion transaction using the wallet's signer. The tool waits for the transaction receipt and displays the result. All data is processed client-side—no data is sent to external servers. The registry contract itself must implement the registerVersion function for the transaction to succeed.

WHAT IT CANNOT SEE

This tool cannot automatically detect the correct version number from contract bytecode—you must provide it manually. It cannot verify that the contract address actually matches the version you are registering. It cannot publish versions for non-EVM contracts. It cannot validate that the registry contract is the correct one or that it uses the expected interface. It cannot detect if a version already exists for that contract address and prevent duplicates. It cannot automatically generate version metadata from the contract source or bytecode. The tool does not read from the blockchain to check the current state of the registry.

PLEASE NOTE

Contract Version Registry Publisher works exclusively with EVM-compatible chains. It requires a connected wallet with sufficient gas funds to send the registration transaction. The registry contract must be deployed on the same network and must implement a registerVersion function matching the expected signature. All processing occurs client-side in your browser; no data is sent to any external server. The tool is free to use and does not require authentication. For best results, ensure the registry contract is deployed and verified before publishing.