> whoami
Sameer Agarwal
I build systems where trust is a design flaw.
Oracle aggregation. Cross-chain attestation.
Verifiable compute. ZK/FHE privacy.
Novel AMM curves.
2020–22
The Reliability Problem
Razor Network's oracle needed to aggregate prices from dozens of sources across a staking network. The initial design used weighted mean — but weighted mean is manipulable. A single outlier data point, if staked heavily enough, can move the aggregate significantly. Switching to weighted median was a security decision disguised as a statistics decision: the median is only manipulable if you control more than half the stake. Every math choice in an oracle is a trust assumption.
2022–23
The Bridging Problem
Cross-chain data was getting more important. The question wasn't just 'can I transmit a value?' but 'who vouches for it, and how?' We designed a cross-chain bridging mechanism using Threshold Signature Scheme (TSS) — a cryptographic primitive that requires a threshold of validators to co-sign before data crosses a bridge. At the time it was unnamed infrastructure. It was the first attempt to make the validator set itself the trust boundary.
2023
Compute Needs Proof Too
At Syntience, the problem was distributed AI training pipelines. We were running GPT-2 training across multiple nodes on GCP. But a question kept surfacing: how do you know the compute actually happened correctly? A node could return fraudulent gradient updates. This wasn't a problem we solved at Syntience — but prototyping verifiable training validation pipelines was the moment the question became concrete. Computation has the same trust problem as data.
2023–25
Bridging Becomes Protocol
The cross-chain bridging work evolved into something larger: Metalayer, a full verification protocol. As the sole smart contract engineer, I designed the complete security surface — validator registration, staking, the attestation lifecycle, dispute resolution, and the whitepaper that forced every design decision to be explicit. The key insight: attestation can't be bolted onto a bridging protocol after the fact. It has to be the protocol. The validator lifecycle is the product.
2026–
The Exploration
The exploration widened in three directions. Uniswap Hook Incubator Cohort 8 turned V4 hooks into practice through StableGate, a KYC-gated CSMM with cross-chain credential automation. CuratedLP and Reckon pushed AI agents into constrained protocol roles: rebalance liquidity without custody, monitor solver fills, and trigger objective slashing. Mini ETH Node moved the work below contracts into Rust, building an Ethereum-like execution node from first principles to understand the mental map behind RLP, state roots, block processing, and canonical state.
Razor Network
Blockchain Developer
Razor Network Oracle
The oracle problem at Razor wasn't data fetching — it was aggregation security. When dozens of staked validators report prices, the aggregation function determines how hard it is to manipulate the result. We moved from weighted mean to weighted median early on. That shift roughly doubled the stake required to meaningfully skew an output. The staking and rewards mechanism was designed to punish outlier reporters and reward validators who cluster around consensus — aligning economic incentives with data accuracy.
Syntience
Syntience's problem was distributed AI training at scale. I built GPT-2 training pipelines across multiple GCP nodes using PyTorch, designed modular decision-making frameworks using mixture-of-experts models, and worked on inference reliability. The question that kept surfacing — how do you verify that a compute node actually ran the computation it claims to have run? — didn't have a clean answer in 2023. Prototyping verifiable training validation pipelines was the first attempt to make this concrete.
Metalayer
It started as a bridge. We needed to move oracle data cross-chain without introducing a new trust assumption, so we built a TSS-based bridge-proxy — a threshold of the existing validator set co-signs cross-chain transmissions. No new committee, no new trust surface. That design kept evolving: if validators can attest to oracle data crossing a bridge, they can attest to anything. The bridge became Metalayer — a modular compute and verification protocol.
As the sole smart contract engineer, I owned the entire security surface: validator registration, staking mechanics, the attestation lifecycle (open → attest → finalize → dispute), and the dispute resolution mechanism. The protocol supported bridge attestation, oracle data attestation, ZK proof verification, and AI inference result validation — each with different latency requirements and finality guarantees but a single shared validator lifecycle. Writing the protocol whitepaper was the most valuable forcing function: every design decision had to be explicit enough to put in a document.
Mini ETH Node
in developmentThe Problem
Ethereum clients are hard to understand from the outside because networking, encoding, execution, state commitment, and block processing are usually buried inside large production codebases.
The Design Decision
Build a compact Ethereum-like execution node from first principles in Rust. The project keeps real client boundaries: protocol messages stay in the networking layer, the processor owns canonical state, execution lives in its own crate, and the block builder only creates signed block envelopes from node-provided state.
CuratedLP
completedThe Problem
Concentrated liquidity on Uniswap V4 offers higher capital efficiency but demands constant active management. Most LPs either passively mismanage positions or hand full custody to opaque vault managers with zero accountability.
The Design Decision
An AI curator agent — orchestrated by OpenClaw on a 5-minute heartbeat — uses Venice AI private inference inside an EigenCompute TEE to analyze markets and rebalance positions, but can never touch LP funds. MetaMask Delegation Framework scopes permissions via a custom CaveatEnforcer: the curator can only call rebalance() and claimPerformanceFee(), with fee bounds and rate limiting enforced on-chain. Every execution log is stored on Filecoin with PDP proofs and indexed on-chain via a LogRegistry contract. ERC-8004 gates curator registration and records performance history.
Reckon
completedThe Problem
Solver markets like UniswapX, CoW Protocol, and 1inch Fusion route swaps through off-chain solvers, but users have no objective same-chain way to prove a bad fill, trigger restitution, or tie solver quality to discoverable reputation.
The Design Decision
Make solver fills cryptoeconomically challengeable. Solvers register as ENS-resolvable virtual subnames, post reputation-scaled USDC bonds, and opt-in swappers tag UniswapX orders with a view-only Reckon validator plus EBBO tolerance. Autonomous 0G iNFT challenger agents monitor fills, compute benchmark violations, coordinate first-claim-wins over Gensyn AXL, and submit challenges via KeeperHub. Successful challenges slash immediately: 60% restitution to the swapper, 30% to the challenger iNFT owner, 10% to protocol.
LienFi
completedThe Problem
DeFi lending requires overcollateralization because creditworthiness is private data. Traditional mortgage systems require banks, appraisers, and courts because trust must be established at every step.
The Design Decision
Chainlink CRE confidential enclaves assess creditworthiness using Plaid data and Gemini — and then discard all raw financial data before writing the verdict on-chain. The liquidation auction uses Vickrey mechanics (winner pays second-highest bid) with only opaque bid hashes stored on-chain.
ENSRouter
completedThe Problem
Your wallet address changes per chain and per token preference. Senders shouldn't need to know your current routing preferences — they should just know your name.
The Design Decision
ENS text records are already on-chain, version-controlled, and human-readable. Storing payment routing config there makes preferences portable and trustless — no custodian, no syncing problem.
StableGate
completedThe Problem
Institutional stablecoin trading faces a tension: DeFi offers efficient execution but can't enforce compliance; CeFi offers compliance but sacrifices transparency. There's no way to have permissioned access and on-chain execution without manual admin overhead.
The Design Decision
Credential NFTs on Base represent verified institutional relationships. A Reactive Smart Contract monitors NFT events cross-chain and automatically delivers callbacks to a Uniswap V4 hook on Unichain — zero manual steps between credential issuance and swap execution. The hook enforces allowlist gates, tiered fees, expiry, daily volume caps, and LP whitelist on a 1:1 CSMM.
🎓 Cohort 8 Graduate
Graduated from the Uniswap Hook Incubator with StableGate — KYC-gated institutional stablecoin swaps on Uniswap V4 with cross-chain credential automation.
🥇 1st Place — Filecoin Partner Track
AI agent-managed liquidity vaults on Uniswap V4. Curator rebalances via Venice AI inside EigenCompute TEE, scoped MetaMask Delegation, execution logs on Filecoin.
🏅 Top 12 Projects
On-chain mortgages with private credit scoring in Chainlink confidential enclaves and sealed-bid Vickrey auctions.
🥇 1st Place — Best LI.FI-Powered DeFi Integration
Cross-chain payment routing via ENS text records. Senders pay any token on any chain; recipients receive in their preferred asset.
🏅 Winner — Chainrunner Track
Decentralized exchange built on Polygon.
🏅 Winner
On-chain will execution — trustless inheritance without a lawyer.
// contact
If you're building anything interesting in the Web3 space — or need help or advice — I want to hear about it.