Mihenk Pay
Condition-based USDC payments between crypto projects and KOLs (influencers). Part of Mihenk AI.
Mihenk AI measures which crypto KOLs really move the market: real reach (median views per post, not followers), bot-screened audiences, and every coin call scored against BTC. Mihenk Pay uses those measurements to settle KOL deals on-chain. The project locks the fee in USDC, the KOL accepts from the payout wallet, and the contract releases the money only when Mihenk verifies the post. Whatever isn't earned goes back to the project.
Live on Arc, Base, Monad, Sei, Avalanche C-Chain and Arbitrum One mainnet with native USDC. Current version: v2 (22 Oct 2026, addresses below).
How it works
- Lock. The project (or its agency) locks the fee for one KOL in a supported stablecoin (USDC, or any standard ERC-20 the owner allows). Terms are agreed off-chain; only their hash goes on-chain.
- Accept. The KOL accepts from the payout wallet. This proves the wallet belongs to the KOL before any money moves.
- Verify and settle. After the post has stayed live for the agreed period, Mihenk posts the result. The project sets a minimum time on-chain, counted from the KOL's acceptance, before which Mihenk cannot settle. One part of the fee is earned on delivery, the rest when the real-reach target is met. Only a hash of the measurement report goes on-chain.
- Dispute window. Either side can dispute within the window (24 hours to 14 days, 3 days by default). The owner resolves with a corrected payout.
- Close. Anyone can finalize after the window. The KOL receives the earned amount minus Mihenk's fee; the project gets back everything not earned.
If Mihenk never settles before the deadline, the project can reclaim the full amount. An unresolved dispute falls back to Mihenk's result after 30 days. If the token refuses a payout (for example to a USDC-blacklisted address), the other payouts still go through and the refused amount is credited to that address, which can claim it later itself. Funds can never be stuck.
Design choices
- Payouts are never tied to a token's price. Paying KOLs for price moves would reward pumping. Mihenk pays for delivery and real reach only.
- Commercial terms stay confidential. No social handles on-chain; the chain holds only hashes of the terms and of the result.
- Fee rate and fee recipient are fixed per campaign at creation; the rate is hard-capped at 10%, so neither can change after a project has funded.
- Separate roles. The owner, the verifier and the fee recipient are separate addresses;
Deploy.s.sol can hand ownership to a Safe multisig (OWNER).
- Fee-on-transfer tokens are rejected, and every token must be allow-listed.
- Two-step ownership, reentrancy guards, SafeERC20, custom errors.
Setup
git clone https://github.com/MihenkAI/mihenk-pay-contracts && cd mihenk-pay-contracts
git clone --depth 1 https://github.com/foundry-rs/forge-std lib/forge-std
git clone --depth 1 --branch v5.1.0 https://github.com/OpenZeppelin/openzeppelin-contracts lib/openzeppelin-contracts
forge test
Tests
37 Foundry tests, including a fuzz test proving that every unit locked always ends up with the KOL, the project or the fee recipient (paid out, or credited for claim when an address is blacklisted), and nothing is stuck in the contract.
Deploy
DEPLOYER_KEY=... VERIFIER=0x... FEE_RECIPIENT=0x... TOKEN=0x... OWNER=0x<safe> \
forge script script/Deploy.s.sol --rpc-url <RPC> --broadcast
If TOKEN is empty, a testnet-only TestUSD with an open faucet is deployed and allow-listed. DISPUTE_WINDOW defaults to 3 days (minimum 24 hours). script/DemoLive.s.sol runs the full flow on a live network with a real stablecoin.
On Arc, USDC is the native gas token and its ERC-20 interface (0x3600…0000) is backed by a precompile that Foundry's local EVM does not implement, so forge script cannot simulate token calls there. Deployment works with forge script; the Arc demo campaign below was sent with cast send, letting the node estimate gas.
Deployments
v2 (live since 22 Oct 2026)
Deployed with script/Deploy.s.sol from this code. Owner 0x9e366c62f1310115e5832af0d46c6f26f8a1e0b4; verifier and fee recipient 0x845B9cff41Eb67e56673375D842b7C5b949Cc7aA; fee 3%; dispute window 3 days (1 day on Sei); native USDC allow-listed. Source verified on Sourcify (exact match) on all six networks.
What changed from v1, after issues were reported to us once v1 was live:
- A payout the token refuses (for example a USDC-blacklisted KOL, project or fee recipient) no longer blocks the other payouts. In v1 one such address could leave a settled campaign with no way out once the dispute window had passed; in v2 the refused amount is credited to that address and only that address can
claim(token) it.
- The fee recipient is fixed per campaign at creation, like the fee rate.
createCampaign takes minLive: the verifier cannot settle earlier than minLive seconds after the KOL accepts, and settlement must still fit before settleDeadline.- The dispute window is at least 24 hours (v1 deployments ran with 1 hour).
- On Monad the owner is now a separate key from the verifier.
- Campaigns are read with
getCampaign(id).
v1 (closed to new campaigns)
The first mainnet deployments each ran one 2-USDC demo campaign, all finalized. On 22 Oct 2026 USDC was removed from their allow-list, so no new campaign can be created there; they hold no funds.
The v1 demo campaigns follow.
Arc mainnet v1 (chain ID 5042)
Live with native USDC (0x3600000000000000000000000000000000000000). Source verified on Sourcify (exact match). The USDC used here was moved from Base to Arc with Circle CCTP V2 and the forwarding service (burn on Base, mint on Arc).
Demo campaign #1 with 2 USDC: a real, organic KOL post measured by Mihenk AI, replayed as a paid campaign (no actual sponsorship took place). 50% earned on delivery, 50% on reaching 20,000 real views, 1-hour dispute window. Delivery and reach were both met.
Base mainnet v1 (chain ID 8453)
Live with USDC (0x8335…2913). Source verified on Sourcify.
Same demo campaign with 2 USDC:
Base Builder Code: transactions sent from these scripts on Base mainnet carry Mihenk AI's Builder Code (bc_s415ugdv, ERC-8021) at the end of the calldata, so Base attributes the activity to Mihenk AI. See script/BuilderCode.sol; the contract ignores the suffix, and test/BuilderCode.t.sol runs a full campaign with tagged calldata. The demo campaign above was sent before the Builder Code was added.
Monad mainnet v1 (chain ID 143)
Live with USDC (0x7547…b603). Source verified on Sourcify.
Robinhood Chain testnet v1 (chain ID 46630)
On every network, only keccak256 hashes of the terms file and the measurement report are stored (termsHash, resultHash). The files themselves name the KOL, so they stay off-chain and are shared only with the parties.
Bridging USDC to Arc (CCTP)
bridge/cctp_base_to_arc.mjs moves USDC from Base to Arc with Circle Bridge Kit (CCTP V2) and the forwarding service, so the receiving wallet needs no gas on Arc. It funded the Arc demo campaign (burn on Base, mint on Arc). Run npm install in bridge/, then SPONSOR_KEY=0x... AMOUNT=5.40 node cctp_base_to_arc.mjs for an estimate, adding SEND=1 to bridge.
Status
The contracts have not had an external audit yet. Live deployments are used for demo campaigns with small amounts; client campaigns at scale come after an audit. Security reports are welcome at [email protected].
Roadmap
- Connect settlement to Mihenk's live measurement pipeline (post detection, time live, bot-screened reach).
- "Approve and pay" inside Mihenk's existing proposal builder: the client approves a KOL list and funds the campaign in one step, paying with USDC from any chain through CCTP.
- Agent payments: let AI agents fund and settle KOL campaigns in USDC (x402-style flows).
- Write each campaign's result on-chain as a portable KOL track record.
License
MIT
