Nano Gateway on the Internet Computer Protocol
Connect your IC canisters to the Nano network with +30 RPC actions – ready to serve your smart contracts on the IC. Non-custodial by design: NANOGATE never holds keys or funds, and you can even use your own private Nano node.
NANOGATE connects the Nano network with the Internet Computer Protocol. It allows ICP canister smart contracts to interact with Nano and vice versa — without wrapping, bridges or third party oracles. Canisters make inter-canister calls to the gateway, which communicates with Nano nodes via ICP's HTTP outcall infrastructure. Every call is executed by all replicas in the subnet simultaneously (13 in this case), and the result is only accepted if a supermajority agrees. Every Nano RPC response is therefore consensus-verified by the subnet.
Nano (XNO) is a digital currency (symbol Ӿ). It is built on a block-lattice architecture, where each account has its own blockchain. Transactions are feeless and settle in under half a second. There is no inflation — all coins were distributed via a CAPTCHA faucet between 2015 and 2017. The network's throughput scales with hardware rather than being limited by protocol design. Running a node costs as little as $20 per month, and the entire network uses less energy than a single wind turbine generates. These properties make Nano the most efficient decentralized payment network ever created, with more than 222 million blocks confirmed to date. It does one thing and does it very well. That is why Nano was deliberately designed without a smart contract layer.
The Internet Computer Protocol (ICP) is a sovereign, serverless cloud that runs smart contracts at web speed with on-chain consensus. Its canisters can make HTTPS outcalls, receive incoming requests, serve web content directly to browsers, store data on-chain, and run full applications. These are capabilities that traditional blockchains don't offer. The development experience is straightforward. The dfx SDK handles everything from local testing to mainnet deployment, and canisters can be made immutable by removing all controllers, making them publicly verifiable and tamper-proof. ICP is the most advanced blockchain project in the world, years ahead of its competition, capable of being anything by design. Anything except pure digital cash.
NANOGATE unlocks new capabilities for both networks. For Nano, this means smart contract conditions can trigger automated payments, used for decentralized finance of all kinds — on-chain treasury management, escrow services, programmable payment schedules, or conditional multi-party payouts. Nano's feeless, sub-second transactions will also be able to serve as triggers for ICP smart contracts, acting as a free signaling layer to initiate on-chain logic. When the world's most powerful smart contract platform connects with the only network where value transfer is nothing but information, entirely new categories of decentralized applications become possible. NANOGATE is that connection.
Non-custodial by design. NANOGATE never sees or accesses private keys — there's simply no need to.
The DAO changes who controls the canister. Custody stays unchanged: NANOGATE remains non-custodial by design.
Operator-controlled. A single owner can upgrade the canister code — the pragmatic setup today, before decentralization.
Controlled by the DAO. Code and parameters change only through token-holder proposals and votes — no single party can alter the gateway.
The ICP subnet (its honest 13-replica supermajority), the Nano node(s) queried for data, and the operator, who runs the infrastructure and can upgrade the canister code.
The ICP subnet and the queried Nano node(s) stay the same. The operator's upgrade power is replaced by DAO governance — no single party, only the honest majority of voting power.
Responsibility lies with the developer. Guided by applicable EU crypto-asset regulation.
Under the DAO, commercial and legal responsibility will sit with a German company established for that purpose. The DAO governs the technology; token holders vote on governance proposals — the token carries no share of revenue or profit and no dividend or payout right. Still guided by applicable EU crypto-asset regulation.
One Nano node per request — one you select, the gateway's pick, or your own private node. You can already query several nodes yourself and compare. Public nodes are operator-curated.
An open, DAO-governed node set: independent operators register their nodes, widening the choice. An optional built-in mode fans out a request across several nodes and cross-checks their answers.
The DAO is where NANOGATE is headed — and deliberately no further. It decentralizes control so no single party can run or change the gateway, while keeping the code upgradeable through governance proposals so it can keep improving.
Going further — to where the gateway itself holds Nano keys (a chain-key custody model) — is not our goal. Technically it isn't possible on ICP today anyway, and even if it were, it would make NANOGATE a custodian, with the legal obligations that brings. NANOGATE stays non-custodial by design.
Want to follow NANOGATE's transition to a DAO? Write to info@nanogate.run to be kept up to date!
We're also looking to collaborate with Nano services that have active user interaction.
Nanocontracts.run is designed as a hybrid Nano wallet — a regular web wallet with a contract mode hosted on ICP. On that foundation, further features such as decentralized payment and governance tools are planned. The governance side is designed to fuel gateway adoption by exploring the interactions between Nano and ICP in largely uncharted territory — identifying and managing as many of the emerging factors as possible on behalf of both communities. More details once the DAO transition of NANOGATE is complete.
Get up and running in 5 minutes. Make your first Nano RPC call from the Internet Computer.
sh -ci "$(curl -fsSL https://internetcomputer.org/install.sh)"
# Restart terminal or: source ~/.bashrcdfx identity new YOUR_IDENTITY_NAME
dfx identity use YOUR_IDENTITY_NAME
dfx identity get-principalDuring beta, choose one of the options below to get your first credits:
# Check Nano block count
dfx canister call 7jsss-6qaaa-aaaad-aegpq-cai send_simple_nano_request \
'(record { action = "block_count" })' \
--network ic
# Get account info for any Nano address
dfx canister call 7jsss-6qaaa-aaaad-aegpq-cai get_account_info_for_signing \
'("nano_3rrfgsjs653mefzpf81sqcty13cg5aseoccem5sajwjb1crqkxmdksdkhe14")' \
--network icWant to call Nanogate from your own canister? Follow the step-by-step guide to set up inter-canister calls.
Credits are used to pay for RPC calls. During beta, you can get credits through donations or request some via email to get started.
And help decentralize the gateway by running it as a public node.
Use your own private node and save credits on every request:
# Register your private node
dfx canister call 7jsss-6qaaa-aaaad-aegpq-cai register_private_node \
'("https://your-node.com/rpc", opt "your-api-key")' --network ic
# Enable your private node for your Nano requests
dfx canister call 7jsss-6qaaa-aaaad-aegpq-cai set_force_node '(true)' \
--network ic
# Your requests now use YOUR node (reduced credit cost)
dfx canister call 7jsss-6qaaa-aaaad-aegpq-cai get_account_info_for_signing \
'("nano_1...")' --network icICP subnets consist of 13 to 40 replicas, each making requests simultaneously. The current subnet uses 13 replicas, and for now this is unlikely to change. Your node must:
Once your node is stable, contact us at info@nanogate.run to register it as a public node. Public nodes serve all NANOGATE users and earn credits instantly for every request they handle.
Note: The same URL cannot be used for both private and public nodes. Use different endpoints if you want to run both.