A payment has
a bigger picture.

01. Start with what matters.

1. Open Quorail inside an up-to-date Nimiq Pay wallet and connect.
2. Choose the address whose balance you want to plan around. This does not choose the wallet's transaction signer.
3. Add upcoming payments with a Nimiq recipient, an amount, a fee and a due date.
4. Set your reserve target and a planning window in Settings.
5. Review a payment's impact. When recorded commitments remain covered, approve the transaction in Nimiq Pay.
6. Check the receipt in Activity. Quorail matches the sender, recipient, network and amount before marking the payment confirmed.

02. Understand the calculation.

Room to move is your account balance minus recorded commitments within the planning window and your reserve target. The payment preview subtracts the selected payment and its fee, plus the other commitments. It never subtracts the same planned payment twice.

Overdue commitments remain included. Confirmed payments leave the outstanding plan. Pending and uncertain payments remain reserved until their receipts are checked, which can temporarily make the forecast conservative. Unrecorded spending, future income and exchange-rate changes are not predicted.

All calculations use integer Luna. One NIM equals 100,000 Luna. Quorail supports amounts with up to five decimal places. There is no dollar valuation or promise of yield.

03. Your wallet is in control.

Quorail has no private keys, custody account, background signer or autonomous payment agent. The native wallet asks you to approve each payment. Always verify the sender, recipient, amount, fee and network there.

Your reserve is a planning target, not a vault. Quorail blocks its own payment flow if a payment would cross that target. It cannot prevent direct wallet spending or enforce restrictions outside this app. Only ordinary spendable NIM accounts are supported. Contract balances may not be spendable.

04. Follow the receipt.

A transaction hash means the wallet returned a submission identifier. It does not prove successful execution. Activity uses the network-specific RPC service to verify inclusion and execution, and it distinguishes pending, confirmed, failed and mismatched receipts.

Confirmed means successful inclusion reported by the configured RPC, not an independent cryptographic finality proof. Use the explorer for independent inspection. If a request fails after it may have been submitted, Quorail keeps it uncertain and pauses new sends. Recover its transaction hash from Nimiq Pay history and check it in the payment details. Never blindly retry.

If no transaction hash can be found, keep the record and investigate the wallet history before taking further action. The app deliberately provides no automatic reset for ambiguous payments.

05. Privacy, without surprises.

Your plan and payment records are stored unencrypted in this browser's local storage, separated by address and network. They do not sync across devices. Anyone with access to this browser profile may be able to inspect them. Address sharing is not authentication and is not presented as proof of ownership.

Export a JSON backup in Settings or Activity. Import merges new records for the same address and network, preserves existing entries, and requires re-verification of imported payment attempts. Clearing browser data can remove your plan and payment-attempt history.

Receipt checks send a transaction hash and your IP address to a public Nimiq RPC operator. Google Fonts receives a font request and your IP address. Hosting providers may keep ordinary access logs. Quorail adds no advertising trackers. Optional Quorail AI sends your question to Anthropic through our server only after consent. You may additionally share a previewed summary of balance, reserve and forecast totals. Titles, addresses and receipts are excluded from that automatic summary. Avoid entering secrets in your question. Payment details are public on the blockchain.

06. Recurring plans, shared boards and AI.

Weekly and monthly commitments appear in the 30, 60 and 90 day projections. Confirmation creates the next occurrence. Each payment still needs wallet approval. There is no automatic debit.

Shared boards are optional snapshots stored on the deployment's Redis service for 30 days. Anyone with an invite can read titles, addresses, amounts, due dates and responsibility labels. Share links only with trusted people. Labels are not verified identities. Private plan edits do not sync into a board. Keep payment execution in one place to avoid duplicate payments.

Collection boards divide a contribution request into exact shares. Each share has a public transaction reference. Confirmed shares update the board total. Collecting a contribution does not pay the original outgoing commitment. A matching reference, amount, recipient and network are required to verify a receipt. No funds are held by Quorail.

AI explains your plan and cannot execute transactions. Responses may be inaccurate; use the deterministic preview for the calculation. The service uses request limits and temporarily stores salted client hashes for rate limiting. Shared board records expire; keep a local JSON backup. A blockchain reference alone cannot restore a plan.

07. An example is an example.

The example workspace lets you explore payment planning without a wallet. Its balance and commitments are illustrative. It cannot send payments or create transaction receipts. Connect your wallet to start a separate real plan.

08. Built by Jayking.

Quorail-Nimiq adapts the original Quorail consequence-planning concept into a Nimiq Pay Mini App. The implementation replaces the earlier chain-specific execution model with user-approved NIM payments.

GitHub: paulos-ui · X: @__official__1

Open source under the MIT License. Independently built, with no claim of official Nimiq endorsement.