JUPITER FAUCET

About

Jupiter Faucet is a perpetual cycles top-up protocol for the Internet Computer - built to help canister smart contracts keep running indefinitely. The Internet Computer is designed for tamperproof, "unstoppable" on-chain services; Jupiter Faucet focuses on the practical part: making sure canisters don’t run out of cycles, even if nobody is maintaining the project.

The perpetual top-up workflow is intentionally designed to be so simple that anyone can carry it out as a one-off operation directly from the NNS dapp using the enhanced transfer and memo flow - no further setup required.

Jupiter Faucet is built to propel big burners, including cycle-intensive on-chain AI workloads such as WORDY, helping projects get the most out of ICP→cycles conversion over the long run.

Jupiter Faucet is open source, reproducibly buildable and designed to decentralize control over time. The source code, reproducible build references and governance information are available via the fixed corner links at the bottom of the page. The core component will be blackholed, with a worst-case scenario lifeline built into the canister. That lifeline can temporarily hand control to the SNS DAO if a breaking change in a network dependency prevents disbursals, and can blackhole itself again once disbursals resume.

Status: Jupiter Faucet is in the final phases of development, with a planned launch within Q2 2026.

Source Code

Jupiter Faucet is composed of a suite of smart contracts that are all open source.

Anyone can verify that the system components have been built from this source code by cloning the repository and running the reproducible build script. The build hashes produced should match the Wasm module hashes currently deployed on mainnet.

The Wasm module hashes below are retrieved on-chain from the IC management canister (`aaaaa-aa`) via `canister_info`.

Once Jupiter Faucet is governed by an SNS DAO, changes to these mainnet components will need to pass through consensus.

jupiter-disburser

Canister ID: uccpi-cqaaa-aaaar-qby3q-cai

Module hash: Loading…

Source code

Controls the Jupiter NNS neuron, disburses maturity, and routes ICP into the faucet and reward flows.

jupiter-faucet

Canister ID: acjuz-liaaa-aaaar-qb4qq-cai

Module hash: Loading…

Source code

Converts routed ICP into cycles top-ups for eligible canisters declared through memo-based contributions.

jupiter-historian

Canister ID: j5gs6-uiaaa-aaaar-qb5cq-cai

Module hash: Loading…

Source code

Indexes contributions, rewards, output and tracked-canister activity to power the public observability surface.

jupiter-lifeline

Canister ID: afisn-gqaaa-aaaar-qb4qa-cai

Module hash: Loading…

Source code

Minimal recovery canister that broken canisters can automatically assign control to temporarily (allowing the DAO to apply a fix).

jupiter-sns-rewards

Canister ID: alk7f-5aaaa-aaaar-qb4ra-cai

Module hash: Loading…

Source code

Placeholder recipient for the primary age-bonus ICP flow until the full reward logic lands.

jupiter-faucet-frontend

Canister ID: jufzc-caaaa-aaaar-qb5da-cai

Module hash: Loading…

Source code

Serves the certified frontend assets and dashboard UI (this website).

Governance

SNS launch coming soon...

Prior to the SNS DAO launch this system is being developed by Alex Lorimer, the controller of the LORIMER ♾️ 🐶 known neuron, and well-known ecosystem participant.

How it works

The top-up process is intentionally simple: transfer at least 1 ICP directly into the staking account of Jupiter Faucet's canister-controlled neuron and set your target canister ID as the transaction memo in plain ASCII text (see Ctrl + K 'memo' tip below). You do not need to be the owner of the canister. The 1 ICP minimum is intentional: historian keeps a durable beneficiary registry so later top-up activity can be monitored efficiently, and a much lower minimum would make registry spam far too cheap.

Staking account

22594ba982e201a96a8e3e51105ac412221a30f231ec74bb320322deccb5061d

Transfer ICP to this staking account, then paste your target canister ID into the NNS dapp memo field as plain ASCII text. The faucet accepts short ASCII principal text in `icrc1_memo`; entering the target canister ID is the supported UX, and ordinary self-authenticating user principals do not fit.
(Ctrl + k, and search 'memo' if the field is not yet visible).

That’s it. With your memo declaring a canister, that canister becomes the recipient of perpetual cycles top-ups, funded by the stake’s ongoing rewards (proportional to your ICP contribution and any further contributions made for that canister). A monitoring workflow will soon be introduced for visualising the impact of your perpetual top-ups.

While stake contributions can be made today, we recommend waiting for protocol completion (estimated Q2 2026).

Base maturity: 100% of the base (non age-bonus) maturity generated from contributed stake is used to perpetually burn ICP, mint cycles, and top up the declared canister over time.

Age bonus maturity: the age-bonus component (between 0% and 20% of total maturity depending on stake age) is split into:
• 0%–16% distributed to SNS JUP stakers in the form of newly minted nICP
• 0%–4% restaked into the D-QUORUM neuron to help fund decentralized due diligence of NNS proposals.

Coming soon: detailed step-by-step instructions. Jupiter Faucet is in the final stages of development.

Also coming soon: SNS launch, and periodic JUP airdrops for users who have contributed ICP to Jupiter Faucet's canister-controlled neuron, front-loaded to encourage earlier contributions

Jupiter Stake

Direct ICP ledger balance plus public NNS neuron details.

Neuron ID: 11614578985374291210
Current stake
Age
Publicly readable
Created
Voting power refreshed
Follows
Staking account

Total Output

Historian tracks protocol-routed ICP from the disburser to the faucet payout account.

Total Output counts ICP routed from the disburser staging account to the faucet payout account. It does not attempt to measure downstream burn or spending.

Total output

Total Rewards

Historian tracks protocol-routed ICP from the disburser to the SNS rewards account.

Total Rewards counts ICP routed from the disburser staging account to the SNS rewards account. It is a Jupiter routing metric rather than a downstream burn metric.

Total rewards

Target Canisters

Loading next historian run…

This registry is historian's durable set of tracked target canisters. The registry itself is not pruned, but the per-canister histories and recent feeds shown elsewhere are bounded; full transfer history remains queryable from the ICP ledger and its archive canisters.

Target canister	Commitments	Total ICP	Latest cycles
Loading…

Page 1

Commitments

Loading next historian run…

A commitment qualifies when the memo names a target canister ID as ASCII principal text in `icrc1_memo` (max 32 bytes) and the contribution is at least 1 ICP. The minimum is intentionally high to make beneficiary-registry spam expensive: historian keeps a durable beneficiary registry so it can efficiently monitor and display later cycle top-up activity. The table below is a bounded recent view: newest 500 qualifying items, newest 100 below-threshold memo items, and newest 100 invalid-memo items. Invalid memo text is not echoed back here. Full transfer history remains durably queryable from the ICP ledger and its archive canisters.

Timestamp	Amount	Target canister	Category
Loading…

Page 1

Partners

Jupiter Faucet is helping to propel big burners: projects with meaningful, continuous cycles demand (on-chain AI and other high-throughput workloads). By making perpetual top-ups "set-and-forget", we aim to reduce operational friction and help these applications scale on the Internet Computer.

Life On Ledger has so far been a stealth mode project and is still under development. It has a strong relationship to Jupiter Faucet's early contributors, and a huge demand for cycles. In short, Life On Ledger is a massive multi-player online game in the form of an unstoppable cellular automata. It supports up to 100K simultaneous players (potentially more with some further work) each competing to claim more territory than their competitors in a perpetual war. To support its long-term growth, the upcoming LOL SNS DAO will be the recipient of a 10% allocation of JUP genesis tokens.

We're confident LOL's high burn rate and affinity for a VERY large community of CA fanatics will help put the IC on the map for good.

We also recognize that unstoppable smart contracts depend on the safety and resilience of the network they run on. That’s why we support D-QUORUM, and why a small portion of age-bonus maturity (0 - 4% of total maturity depending on age) is restaked into the D-QUORUM neuron to help bootstrap protocol-funded, decentralised due diligence of NNS proposals, to strengthen Internet Computer governance over time.

The future is arriving faster than many are ready for, and onchain governance will revolve just as much around capable onchain AI as it does around human participation and off-chain tooling. A stealth-mode AI project that is currently under development (and goes by more than one name) will be the recipient of an additional 15% allocation of JUP genesis tokens. This project stands to become the largest burner on the IC, while helping to secure the network and inform human voters of network activity in a trust-minimised way. This project demands significant resources which will be ongoing. Jupiter Faucet will help it get there.

Stimulating the adoption of liquid staking tokens is also an important goal. We believe nICP will help insulate ICP from price volatility. Issuing JUP rewards as nICP also helps users maximise long-term gains with minimal effort or opportunity cost. As the IC's leading liquid staking protocol, WaterNeuron's nICP is the go-to choice.

We believe these strategic alliances will help decentralize Jupiter Faucet at genesis and beyond, while also helping to elevate and secure the Internet Computer - for the benefit of everyone building on it, everyone staked on it, and everyone holding valuable on-chain assets.