Merkler

The problem

An airdrop puts one Merkle root on chain and gives every eligible wallet a proof it can present to claim. Producing those is a scripting job: install a toolchain, run something locally, and hope the output matches what the contract expects.

That is a real barrier for anyone running the distribution who is not the person who wrote the contract.

What it does

Give it the wallet list and it returns the root to publish and a proof for every address.

No install, no command line, and no account.

The list never leaves the browser

Tree construction runs client side. The wallet list is not uploaded, so there is no server holding the eligibility list for an airdrop that has not been announced yet, and no log of it to leak later.

It also means there is nothing to run. The app is a static Next.js build; the only thing the host does is serve files.