Base maturity: 100% of the base (non age-bonus) maturity generated from committed stake for topping up cycles 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%–19% distributed to SNS jUP stakers in the form of newly minted IO (a liquid staking protocol that will be launched alongside Jupiter Faucet)
• 0%–1% restaked into the D-QUORUM neuron to help fund decentralized due diligence of NNS proposals, because a prerequisite for truly unstoppable canisters is a secure and decentralized network.

Rewards: jUP SNS tokens will be minted to patrons who have committed ICP to the staking account of Jupiter Faucet's neuron (following the rules described). Contributions must meet the requirements in order to be counted (transactions of at least 1 ICP featuring a memo that declares a canister ID or neuron ID). While the Jupiter Faucet SNS rewards components are still being finalized the ICP will accumulate in the rewards account (reserved until SNS launch). See Governance for more info.

Advanced Usage

Jupiter Faucet supports three memo-directed flows. A plain declared canister ID keeps the default perpetual cycles top-up behavior. Advanced users can instead route ICP minted from maturity directly to either the default account of a declared canister or the staking account of a declared public NNS neuron.

To enable raw ICP transfer mode for a canister, add a full stop character ('.') after the declared canister ID in the ICP commitment memo. To target a public neuron instead, use the neuron ID in the memo. In either mode, the full stop may be followed by optional text; Jupiter Faucet uses that optional text as the outgoing memo on the perpetual ICP transfer. Declared neurons must be 'public' in order for Jupiter Faucet to derive their staking accounts.

The full ICP commitment memo must be ASCII and at most 32 characters. For canister targets, hyphens in the principal may be omitted to save space. Use the memo builder to build a valid memo.

Developer tip: You can adjust the canister/neuron, title, and label parameters in the following URL to customize the memo helper form for a smoother user experience: #memo-builder?canister={protocol canister ID}&title={custom title}&label={custom label} Copy URL

Relay Canisters

A relay canister provides one stable destination for ICP transfers. It aims to maintain a steadily growing cycles balance for configured target canisters by topping up 1% more cycles than needed to restore the previously sampled balance for each configured canister (provided enough ICP is perpetually supplied into the relay canister).

Target requirement: Every Relay target canister must make its cycles balance publicly observable so the Relay can measure consumption and calculate each top-up. See Cycles Observability on the next slide.

Example: The full suite of Jupiter Faucet protocol canisters are managed by a single relay canister. Anyone who wishes to contribute an ICP commitment can use the Relay Canister Memo Builder, optionally supplying their name as a memo suffix (identifying them for their good deed).

This flow depends on raw ICP top-ups described in the Advanced Usage section. This ensures Jupiter Faucet perpetually transfers raw ICP rather than directly topping up the relay canister with cycles. The relay canister then uses that raw ICP to keep itself topped up along with configured canisters. Surplus ICP (if any) can then be routed to a configured DAO treasury or other account. The Jupiter Faucet protocol's own relay canister routes 50% of any surplus ICP back into the Jupiter Faucet neuron itself (forever increasing the rate of future maturity-minted ICP back into the relay). The relay routes remaining surplus ICP into the IO neuron's staking account (described below).

Anyone can deploy their own relay canister (specifying their own selection of target canisters they wish to be kept topped up). There are two options:

• The easiest path to deploying a relay canister is to use the Relay Setup tool (any surplus ICP will automatically be routed to the IO neuron staking account, increasing the minimum APY for all IO holders and therefore increasing the value of rewards for jUP stakers).
• Alternatively, developers can pull the source code and deploy an instance manually specifying their own selection of surplus accounts.

Developer tip: A relay canister also accepts ICP transfers into its '1' subaccount (e.g. u2qkp-aqaaa-aaaar-qb7ea-cai.1). This is intended to support ICP senders who do not have support for ICRC memos, or who wish to grow their Jupiter Faucet commitment with many small ICP transfers (each below the 1 ICP minimum Jupiter Faucet threshold). The relay canister allows many small ICP transfers to accumulate before it transforms these into a single ICP commitment that meets or surpasses the minimum 1 ICP threshold. The relay canister's own ID is used in the ICP commitment memo such that it will perpetually receive raw ICP from Jupiter Faucet maturity.

Cycles Observability

Registering a canister through a qualifying memo commitment tells the Memo Tracker what to track. Its cycles balance can be displayed through one of these routes:

• Recognized blackhole: An ordinary target is observable when either the 13-node blackhole or the Fiduciary blackhole is one of its controllers. Both are immutable, run the same independently reproducible blackhole Wasm documented by DFINITY, and can only make canister status public. Adding either as an additional controller introduces no trusted operator and does not remove existing controllers; it simply lets the Memo Tracker read the target's cycles balance.
• SNS routes: Deployed SNS canisters and dapps governed by an SNS can be observed through that SNS. These targets do not need a recognized blackhole controller.

TL;DR: Non-SNS target canisters require a recognized blackhole controller if you want cycles history displayed in the Memo Tracker; cycles for SNS-governed dapps are observable by default. Newly tracked canisters may remain pending until their initial probe or the next cycles sweep completes. While Jupiter Faucet perpetually tops up target canisters whether or not their cycles are publicly observable, Jupiter Relay target canisters must expose their cycles so the Relay can calculate how much each needs.