How to get sign-in code on Pi Node Linux CLI version?

[shun58]

Hello Pi Community,

I successfully installed Pi Node on my Linux VPS (Ubuntu) using the official CLI tool from https://minepi.com/pi-blockchain/pi-node/linux/

Current Status:

• Pi Node version: 0.2.2
• Status: Synced! ✅
• Peer connections: Active (Incoming: 1, Outgoing: 10+ peers)
• Container: Running normally

My Problem:
When I open the Pi mobile app and go to Node → "Sign in to Pi Node", it asks for a sign-in code. However, I cannot find a way to get this sign-in code from the Linux CLI version.

On Windows/Mac desktop versions, the sign-in code is displayed in the GUI. But the Linux CLI version (pi-node command) does not seem to have this feature.

What I've tried:

• Checked pi-node --help - no login/auth related commands
• Searched logs with pi-node logs - no sign-in code found
• Searched online documentation - no solution found

My Questions:

1. Is there a way to get the sign-in code from the Linux CLI version?
2. If not, will this feature be added in a future update?
3. Can I link my Pi account to the Linux node by signing in on Windows first, then continuing to run the node on Linux VPS?

My Environment:

• VPS: ConoHa VPS (Japan)
• OS: Ubuntu 24.04
• CPU: 4 cores
• Memory: 4GB
• Pi Node: Installed via official APT repository

Thank you for your help!

[ziyouniaoseo]

This is a Windows-exclusive feature and hasn't made it to Linux.

[Flashulica]

awaiting update also :D

[techvudu]

Is this for a specific reason or simply not implemented yet?

[medivb]

Has anyone tried the trick with using the same seed on a windows node (or generate a new one there) and then migrating it to a linux node? I don't have windows running anywhere, but willing to setup some vm if this is a proven workaround ;-)

[elie1316]

i need the code i am using cli

[asaddon]

I'm looking for the same, whats the point of running a node if we can't get rewards for it :\

[techvudu]

agreed. i shut mine down for now. i did not retain my windows node so not interested in going back.

[kapkan777]

In my case the situation is the same. I ran the node on Windows on a laptop for about 6 months, then I switched to a desktop PC on Linux and logged in using the same old seed that I used on Windows.

Until now (February 26), I still do not receive any node bonus. I have powerful hardware: DDR5 64 GB RAM and an NVMe SSD 990 Pro, and I bought it specifically for running the Pi Node.

I will let it run for some more time while the network goes through updates, because I believe it is currently needed. But if the reward issue on Linux is not fixed, I will be forced to stop it. I do not want to go back to Windows, but I also do not want to keep my PC running for nothing. It has already been running for almost 3 months without any node bonus

[itsEmDoubleyou]

I have the same Problem, still searching for a solution, i installed the pi node app on my Windows VM connected it with the Pi Phone app, placed the UUID to my user-prefernces.json on my linux pi node and restarted it but still no reward. maybe i did something wrong? maybe the .json file isnt used by the node? i have alot of questions. I hope someone can assist or give instructions how to do that. I leave the node online just for the projects network but soon there should be a official soloution for new nodes to get rewards.

[techvudu]

no rewards for linux based/cli node. that is basically what we are requesting.

[bitcryptic-gw]

Comment for: pi-node/instructions Issue #515

"How to get sign-in code on Pi Node Linux CLI version?"

Post at: #515

---

Same problem here — Linux/Docker node synced and healthy, no way to generate the sign-in code from the CLI.

I'm running the Pi Network Node via Docker on Unraid (I maintain a Community Applications template for this: https://github.com/bitcryptic-gw/unraid-pi-network-node), and this is the single remaining blocker for full account linkage and node reward eligibility on headless Linux deployments. The CLI FAQ confirms it's acknowledged but unscheduled — "Account linking, Pi Desktop, and port checking will be added in future Linux releases."

I'd like to propose a concrete path forward that the Pi Core Team could implement, and that the community could prototype in the meantime as a Pi Browser dApp.

---

Proposed Solution: Cryptographic Node Ownership Attestation via Pi Browser

The current pairing flow is tightly coupled to the Electron desktop app's local UI. A headless-compatible alternative would decouple the linkage from any specific OS or GUI, using the node's existing NODE_SEED keypair (a standard Stellar Ed25519 keypair) to prove ownership.

How it would work

Step 1 — CLI generates a challenge token

A new pi-node generate-attestation command (or equivalent) outputs a JSON payload containing:

• The node's public key (derived from NODE_SEED)
• A timestamp / nonce
• A SHA-256 hash of both

{
  "node_pubkey": "GABCDEF...",
  "nonce": "2026-03-29T00:00:00Z:random_hex",
  "hash": "sha256(node_pubkey + nonce)"
}

Step 2 — Pi Browser dApp signs the attestation

The user opens a Pi Browser app (a lightweight dApp, buildable today under the PiOS licence), pastes or scans the payload, and is prompted to authorise. The Pi SDK signs the hash with the user's wallet private key, producing a signed attestation binding:

{ node_pubkey, nonce, hash, user_pi_signature, user_uid }

No wallet seed is ever exposed to the node software or the dApp backend.

Step 3 — Attestation submitted to Pi backend

The signed payload is submitted to Pi Network's API (same infrastructure that handles existing node registration). The backend verifies:

1. The user signature is valid for the claimed user_uid
2. The nonce is fresh (replay protection)
3. The node_pubkey is not already linked to a different account

On success, the node is linked — equivalent to the current QR/PIN flow, but entirely headless-compatible.

Why this is sound

• No new trust assumptions. The node's keypair is already the authoritative identity for consensus participation. Linking it to a user account is the natural extension.
• Replay-resistant. The nonce + timestamp prevents an intercepted attestation from being reused.
• Works on any OS. The CLI side is a single command; the user side is a Pi Browser dApp — both headless nodes and Docker deployments are first-class citizens.
• Pi SDK already supports signing. The authentication flow in the Pi SDK issues signed tokens; the mechanism for signing an arbitrary payload is the same primitive.
• Precedent in other networks. Ethereum validator withdrawal credential linking, Solana vote account authority changes, and Cosmos validator commission updates all use an equivalent signed-message ownership proof.

Community PoC

While waiting for official CLI support, this approach can be prototyped entirely within the existing Pi developer ecosystem:

1. A small Node.js script that reads NODE_SEED, derives the public key using stellar-sdk, and outputs a signed JSON attestation (signing with the node keypair, not the user wallet).
2. A Pi Browser dApp (PiOS-licensed) that presents the attestation, calls Pi.authenticate() to get the user's accessToken, and submits both to a lightweight verification endpoint.
3. If Pi's backend accepts a manageData Stellar operation as an on-chain attestation record, this could work without any backend changes at all — the dApp submits a signed transaction to Horizon with the node pubkey as the data value, and Pi's infrastructure reads it from the ledger.

I'm happy to build and open-source the PoC dApp under PiOS if there's community interest and/or any indication from the Core Team that the backend attestation verification path is feasible.

Requested from Pi Core Team

1. Short term: pi-node generate-signin-code or equivalent CLI command that outputs the existing code format — even if it requires a one-time online call to Pi's backend to register the code, this unblocks Linux/Docker operators immediately.
2. Medium term: A documented API endpoint for node-account linkage that accepts a signed attestation as described above, enabling fully offline / automated deployments.
3. Clarification: Does submitting a manageData Stellar operation to Pi Horizon with a specific data key constitute a valid linkage signal that the rewards infrastructure reads?

Happy to collaborate on any of the above. Running the node on Unraid via Docker; template and setup notes at https://github.com/bitcryptic-gw/unraid-pi-network-node.

[kapkan777]

There is definitely interest from Linux node operators. This is a certainty, especially since we don't receive even 1 Pi in return while still incurring expenses. I believe it's a necessity to resolve this issue as soon as possible. Additionally, a dedicated Telegram group for Linux node operators would be very useful.

[SeanMXD]

Are you serious? I just set up what would be a Super Node on a hosted server and it is completely useless to me. I was hoping to cash in on that massive mining bonus... Am I going to have to fork this repo and resolve this issue myself?

[SeanMXD]

Are you serious? I just set up what would be a Super Node on a hosted server and it is completely useless to me. I was hoping to cash in on that massive mining bonus... Am I going to have to fork this repo and resolve this issue myself?

Haha never mind, the node is closed source... Get on it Pi Team!!! Don't make me spend Fable credits, I bet Anthropic could find a way to sign me in anyways :)

[flashulica85]

Workaround works...you need to install it in Windows first. You may use bottle to do that