Security

See it first.
Sign it yourself.

Nerby Protocol reads the chain and previews transactions. It never holds keys and it never sends anything on your behalf.

01 · No keys

Nothing here can sign or send.

The safest way to protect a key is never to hold it. Nerby Protocol is built so that it cannot move funds even if it wanted to.

By design

No wallet on the server

The server has no private key, no seed phrase and no signing code. It never asks for yours.

By design

Read-only tools

All eleven tools only read chain state. None of them submits a transaction to the network.

By design

You sign elsewhere

When you want to act, you get an unsigned transaction to review. Signing happens in your own wallet, on your own device.

02 · Simulation

What a dry-run tells you.

Before you sign anything, your AI can run the transaction against the chain as it is right now.

You learn

Will it go through?

Success, or the exact revert reason the contract gives — for example an insufficient balance or a blocked address.

You learn

What will it cost?

A gas estimate and the fee at the current gas price, in the network’s native currency.

Keep in mind

A snapshot, not a promise

The chain keeps moving. Prices, balances and gas can change between the dry-run and your signature, so check the details in your wallet too.

03 · Your data

What is stored: nothing.

Stateless

No accounts, no sessions

There is no sign-up and no login. Each request is answered and forgotten; the application keeps no database.

Transparent

Where requests go

Your question is turned into a standard RPC call to a public node for the network you named. That node operator, and the hosting provider, can see the addresses being queried — as with any block explorer.

Public data

Only what is already on-chain

Everything returned is public blockchain data. Nothing private about you is needed to use it.

04 · Known limits

Read this before relying on it.

Nerby Protocol is new. These are the honest edges of what it does today.