This website requires JavaScript.
Explore
Help
Sign in
igneum-network
/
igneum
Watch
1
Star
0
Fork
You've already forked igneum
0
Code
Issues
Pull requests
Releases
Activity
update-return-21
igneum
/
app
/
igneum-app
History
igneum-labs
d834055eac
MF-11 update-return (0.3.21), the app half on release-0.3.21: the Windows update helper owns the return (the exe set kept beside the app, the app launched by the helper, api/state polled 120 s, the kept set restored when nothing answers, one intake line either way; the installer stays silent under /IGNOTA=2), the window host restarts a dead engine and answers the Restart Manager, the first act after an update is the read-back line and a FAULT pc-restart line when the PC came up from a power loss; the tuner never asks above a card's measured efficient point (the 5090 at 308 W, floored at the vendor's 400 W) unless Power control is on and the user raised the cap, and a refused cap is asked again at 2 and 10 min then reported as FAULT power-cap; the job-channel ping on every wake request (7 October 2026, PC 2 lost power at 10:46Z; the relay half stays on update-return)
...
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-07 14:29:41 +00:00
..
resources
0.3.21: version strings (the tree after 0.3.20's cut: driver-check
f43c9d4d
first; miner-reliability's app half, the under-12 GB prove-instead routing and the per-architecture prover server follow)
2026-10-07 13:10:44 +00:00
src
MF-11 update-return (0.3.21), the app half on release-0.3.21: the Windows update helper owns the return (the exe set kept beside the app, the app launched by the helper, api/state polled 120 s, the kept set restored when nothing answers, one intake line either way; the installer stays silent under /IGNOTA=2), the window host restarts a dead engine and answers the Restart Manager, the first act after an update is the read-back line and a FAULT pc-restart line when the PC came up from a power loss; the tuner never asks above a card's measured efficient point (the 5090 at 308 W, floored at the vendor's 400 W) unless Power control is on and the user raised the cap, and a refused cap is asked again at 2 and 10 min then reported as FAULT power-cap; the job-channel ping on every wake request (7 October 2026, PC 2 lost power at 10:46Z; the relay half stays on update-return)
2026-10-07 14:29:41 +00:00
ui
Prove instead of mining (main's routing, 7 October 2026): on a machine whose every NVIDIA card is under 12 GB the Settings switch prove_instead lets the prover run with those cards' miners held off (Cmd::ProveHold through the cards path, the restore choices kept, given back when proving or the switch goes off); the Prove page's row shows only on such a machine with the sentence naming the choice; provedefault::prove_instead_cards and prove_instead_line with their test, proving.under_12gb on the state, api/prove/instead, the view test; the fleet's 3080 hour: a 10 GB card completes the compressed step alone at 8.6 GB and never beside its miner
2026-10-07 14:16:23 +00:00
.gitignore
One-click miner app: Rust engine (node, miner and worker supervisor with a local dashboard), Mac WKWebView window with a menu-bar item, design screenshots
2026-10-04 10:00:22 +00:00
build.rs
Windows exes carry the coin icon and a version block (the project lead's rule, 4 Oct 2026)
2026-10-04 10:44:20 +00:00
Cargo.lock
0.3.21: version strings (the tree after 0.3.20's cut: driver-check
f43c9d4d
first; miner-reliability's app half, the under-12 GB prove-instead routing and the per-architecture prover server follow)
2026-10-07 13:10:44 +00:00
Cargo.toml
0.3.21: version strings (the tree after 0.3.20's cut: driver-check
f43c9d4d
first; miner-reliability's app half, the under-12 GB prove-instead routing and the per-architecture prover server follow)
2026-10-07 13:10:44 +00:00