orvane
v0.1.0
Published
Mine ORVANE from your terminal: SHA-256 proof-of-work on any CPU
Maintainers
Readme
Quick start
You need Node.js 18 or newer.
npm install -g orvane
orvane login # opens your browser: connect a wallet, approve this terminal
orvane mine # start diggingYour terminal shows a code like KQ7M-3XPA. Check that the browser shows the same code, then click Authorize. The terminal gets its own API key, stored in ~/.orvane/config.json and revocable from the dashboard.
Commands
| Command | What it does |
|---|---|
| orvane login | Approve this terminal in the browser (or orvane login <API_KEY> on a machine without one) |
| orvane mine [-t N] | Mine with N threads (default: all cores minus one) |
| orvane status | Balance, total earned, hashrate, difficulty |
| orvane logout | Remove the API key from this computer |
While mining you see a live dashboard: hashrate, job progress, round countdown, your estimated share of the round, and your last payout. Ctrl+C stops and prints a session summary.
How it works
- The CLI asks the network for a job: a random challenge and a difficulty.
- Your CPU threads look for a nonce such that
sha256(challenge + nonce)starts with enough zero bits. - The CLI submits it; the server verifies it with a single hash and records the work (2^difficulty).
- Every 60 seconds the round closes and its emission is split between the round's miners by work.
Difficulty adjusts per miner so everyone finds roughly one share every 20 seconds. A faster machine gets a higher difficulty, and each share counts for the work it took, so speed still pays.
Economy
| | | |---|---| | Max supply | 50,000,000 ORVANE | | Round | 60 seconds | | Emission at launch | 578.70 ORVANE / minute | | Halving | every 30 days | | Empty rounds | release nothing | | Paid upgrades | none |
Fair play
- Work-based split: 100 accounts on one computer earn the same as one, because the CPU is shared.
- At most 3 accounts can mine from one IP address at the same time.
- A short human check when you start and about every 30 minutes.
- Every share is verified server-side; every job can be used once.
Security
- HTTPS only. The CLI refuses to log in over plain HTTP (except localhost).
- The API key never leaves
~/.orvane/config.json(mode 600). If it leaks, revoke it on the dashboard. - Withdrawals, when they open, will require a signature from your wallet. An API key alone can never move your ORVANE.
MIT
