AI-powered blockchain analytics and financial intelligence for Web3 teams. Tracks users onchain behaviour and contracts spendings as connected to traction gained during a campaign or marketing window.
MetaGauge is an AI-powered blockchain intelligence platform that helps Web3 teams turn on-chain data into actionable business intelligence.
Teams connect a smart contract and MetaGauge indexes its blockchain activity, transforming raw transactions into insights about users, growth, retention, engagement, protocol activity, risk, competitive performance and financial activity.
MetaGauge also includes an AI analyst that is trained to act as a CFO for the business. It allows users to track where their financials are lacking and always get automated prompt to fix and stay ahead of their competitor. With a live competitors feedback, metagaguge helps business owner to be aware of what changes competitors are doing to stay ahead. Also investors can track real onchain value gotten by business owner frome their investment, tracking funds given to smart contract owner and onchain business value gained within the period.
The platform includes protocol analytics, user lifecycle analysis, whale detection, transaction and gas analytics, competitive intelligence, on-chain risk analysis, GitHub and sentiment intelligence, and financial intelligence that converts EVM activity into classified financial records and financial reports.
Ethereum, Arbitrum and Robinhood are currently our primary production environment. We are actively testing the product with DeFi users and using their feedback to refine the product.
Our longer-term goal is to make MetaGauge a reusable intelligence layer across blockchain ecosystems, accross all blockchains.
Here's the full progress narrative
Chain integration (Arbitrum + Robinhood Chain)
Brought both chains to full parity with MetaGauge's existing Ethereum support, not just RPC access, but the whole analytics stack: RPC routing with verified-live fallback endpoints, on-chain risk analysis, deployment-block lookup via each chain's block explorer, market-share and competitor tracking, and wallet-analytics. For Robinhood Chain specifically, this meant adding it from scratch: chain ID 4663 (mainnet) / 46630 (testnet), both verified live via direct RPC calls before any code was written against them, plus a custom wagmi chain definition since it's too new to be in wagmi/chains yet.
Outcome Escrow, a new on-chain financial primitive
Built a marketing-campaign escrow system into MetaGauge's core product: a funder locks tokens against on-chain KPIs (user registrations, activations, retention, volume), a marketer applies and gets accepted, and payout releases automatically once targets are met and a hold period passes , no manual settlement. On top of the contract, built a marketplace layer inside MetaGauge: cross-project job browsing, marketer profiles with reputation tracking (campaigns/hits/misses), and an invite flow where a project owner can curate who they want, while the real security boundary stays on-chain , the invite carries no authority until the marketer signs the apply transaction themselves.
Live, proven end to end
Deployed the OutcomeEscrow contract to both Arbitrum Sepolia and Robinhood Chain testnet, then ran the complete real lifecycle on each: allocation created, marketer invited, marketer applied with their own wallet, funder accepted, a qualifying user action recorded, and settle() called, ending with the marketer's wallet holding the exact token payout on-chain. Not simulated: every step is a real transaction with a real hash on a real network.
Real bugs found and fixed along the way
The live-indexing pipeline (the part that runs after a user's initial onboarding scan) was never calling the Outcome Escrow event decoder at all — meaning any campaign activity happening after onboarding would have silently never been indexed. Found by timing a real transaction to land after onboarding completed; fixed in three separate code paths that had each drifted independently.
The historical scan's lookback was a fixed block count (200,000 blocks), which works out to ~23 days of real history on Ethereum but only ~5.6 hours on Robinhood Chain's much faster blocks — found via a real onboarding that indexed "successfully" with zero transactions. Fixed to scale with each chain's actual block time.
A CORS gap meant the frontend (port 3002) couldn't reach the backend at all in this environment — found because a feature that looked broken turned out to be a blocked network request.
Two frontend pages were calling wallet-connection hooks with no WagmiProvider in their component tree — would have crashed in a real browser the moment anyone touched a connect-wallet button; caught by a production build attempting to statically render those pages.
Product polish
Rebranded the color system to the project's chosen palette (#01579B / #29B6F6) across every token used throughout the app, fixed a broken Arbitrum logo asset, and cleaned the onboarding chain picker down to the chains actually meant to be supported.
MetaGauge has not raised institutional capital yet.
We are currently focused on product validation, user feedback and establishing clear product-market fit before raising.
The team is building and validating the product with Ethereum as the primary production environment, while exploring expansion into additional blockchain ecosystems.
We are open to strategic ecosystem support and venture investment as MetaGauge reaches the next stage of validation and deployment.