MintHop

TRANSPARENCY

Contracts and permissions

Inspect the deployed source code, fees and control over tokens created with MintHop.

Verified factory source

Sourcify reports an exact match for both creation and runtime bytecode at the addresses below. Source verification makes the deployed code inspectable; it is not an independent security audit or a guarantee of safety.

Verified on September 12, 2026. Explorer verification on Etherscan, BaseScan and BscScan is separate and is not claimed here.

Who can do what?

RolePermissions
Platform factory ownerCan change fees and the recipient for future launches, or pause new token creation. Token fees are capped at 5%; the contract has no native-fee ceiling or change timelock. These factory permissions do not grant control over customer token balances.
EVM token creatorOwns the newly created token. Optional capped minting is off by default. New website launches cannot grant transfer pause authority. Previously deployed tokens, or tokens created by calling the factory directly, may still have that authority. Check each token’s actual settings and current owner.
Vesting beneficiaryReceives the assigned tokens according to the immutable vesting schedule. There is no administrator cancellation function. Pausing the underlying token can prevent releases.
Token holderCan transfer when transfers are enabled and burn their own tokens if burning is enabled. MintHop’s factory owner cannot confiscate holder balances or mint through factory-owner privileges.

The EVM factories and token contracts are not upgradeable proxies. The website checks the reviewed fee hash when submitting a launch. If fees change, the transaction must use a fresh quote; a reverted transaction can still cost network gas.

Launch and ownership safeguards

The creator shows exact allocation amounts after token fees. It blocks allocations that round to zero and vesting plans that leave an unlocked rounding remainder. Immediate distributions may send a displayed rounding remainder to the creator.

Before requesting a renounce-ownership signature, the website rereads the owner and pause state and simulates the call. Resume transfers first: renouncing a paused token can freeze it permanently.

These are website safeguards. Direct contract calls can bypass them, and chain state can change before confirmation. They do not change the already deployed contracts. No independent third-party security audit is claimed.

Solana

Solana creation uses the standard Token-2022 program, not these EVM factories. This release revokes mint authority and metadata update authority during creation and has no freeze authority. Metadata and token websites hosted by MintHop remain dependent on the hosting service.