FLOPPY 1.0.11 — quality and installer verification

FLOPPY 1.0.11 updates the packaged engine to evidence-v6 and includes the bounded validator-board reader and explicit MLX adapter selection. Model weights are unchanged.

• Quality checks cover explicit word limits, requested formats and unsupported evidence.
• Frozen-app checks verify every installed engine module against the candidate source, catching missing or outdated payloads.
• Application and engine version labels now match this release.

Validation: 63 tests pass on macOS and Windows. Both frozen applications passed startup, API, UI and engine-hash checks in empty simulation profiles. The DMG passed hdiutil verification; the Windows installer compiled successfully. Windows startup succeeded without changing security policy.

Private beta: builds remain unsigned. Native installation over existing user profiles has not been tested. The earlier 1.0.10 Windows policy block was not reproduced with this candidate, but this does not guarantee compatibility with every Windows policy. No quality improvement or trading profitability is claimed.

Download the DMG for macOS or Setup EXE for Windows. Verify against SHA256SUMS.txt.

FLOPPY 1.0.10 — qualité et mesures fiables (bêta non signée)

FLOPPY 1.0.10 — qualité et mesures plus fiables

Bêta non signée. macOS : démarrage du paquet testé avec un profil vierge. Windows : compilation réussie et 25 tests passent, mais le démarrage du nouvel exécutable est bloqué par la politique de signature du laptop de test (WinError 4551, Code Integrity 3077). Le démarrage Windows de cette version n’est donc pas validé. Aucun contournement de sécurité n’a été effectué.

Changements

• Évite de réclamer une vérification actuelle GitHub sans sources ou une vérification de signatures sans données nécessaires.
• Préserve les demandes d’explication, de code et d’analyse de snapshots fournis.
• Renforce les contrôles de preuves et les consignes de véracité ; moteur identifié evidence-v4.
• Exclut des taux les avis devenus ambigus après découverte d’un autre livreur, ainsi que les jobs comportant plusieurs versions de notre résultat.
• Ajoute les tests de sélection et d’attribution ; 25 tests passent sur Mac et Windows.

Les contrôles ne constituent pas une garantie de justesse. Aucune baisse statistiquement démontrée du taux de refus à ce stade. L’API de liste des jobs du tableau reste intermittente.

Les améliorations du bot Telegram personnel de Rodo ne font pas partie de cette release du client FLOPPY.

Installateurs macOS et Windows joints avec SHA256SUMS.txt. Les builds ne sont ni signés ni notariés. Le worker de production et les modèles optimisés des machines n’ont pas été remplacés par ces tests de packaging.

FLOPPY 1.0.9 — qualité, cadence et mode secteur (bêta non signée)

FLOPPY 1.0.9 — bêta

Installateurs macOS Apple Silicon (M1 et suivants) et Windows x64. Ils ne disposent pas de signature de distribution Apple/Microsoft.

Changements depuis les derniers installateurs 1.0.7

• Débit réel et plafond horaire distincts ; votes ambigus et réponses retenues visibles séparément.
• Protection contre les doubles livraisons, contrôles des éléments factuels et correction limitée des réponses avant envoi.
• État du worker plus précis : réseau, moteur indisponible, génération prolongée.
• Mode secteur uniquement, reprise automatique au branchement ; pause manuelle et température respectées.
• Mise à niveau fiable du moteur embarqué, avec conservation de l’identité et des données locales.
• Correction du réglage d’auto-vérification et minimum de deux générations parallèles.
• Correction de l’encodage UTF-8 sous Windows et de la version du DMG.

Le filtre ne garantit pas l’absence de réponses erronées. Les installateurs ne téléchargent pas le modèle à l’avance : l’assistant de première configuration s’en charge.

Vérification

Les 11 tests passent sur macOS, Windows et Linux. Les deux programmes compilés démarrent avec un profil vierge. L’installation Windows puis le démarrage depuis le dossier installé sont vérifiés. Intégrité du DMG vérifiée.

Source : 1e06296. Build validé. Empreintes des fichiers dans SHA256SUMS.txt.

FLOPPY 1.0.7 (private beta, unsigned) — adjustable power, thermal pause

Private beta build, unsigned. Two fixes that came straight from beta testers.

Allocated power is adjustable, in Settings → Allocated power.

• Pace: 50 / 75 / 100% of what your machine actually measured at setup.
• Parallel generations: 1, 2 or 4. Fewer at a time means a cooler, quieter machine and slightly slower answers.
• Thermal limit: 75, 80 or 85 °C. FLOPPY pauses above it and resumes 5 °C lower, and tells you on Telegram if you paired it. NVIDIA cards only, off by default.

All three take effect without a restart.

Simulation mode no longer catches people out. The README's own run-from-source example enabled it, so a tester spent hours watching invented jobs and invented numbers. The default now runs for real; simulation is opt-in, shows an orange banner on the dashboard saying nothing is sent to the board, and prints a warning at startup.

Install notes and requirements are in the README. SHA-256 in SHA256SUMS.txt.

FLOPPY 1.0.5 (private beta, unsigned) — key backup fixed for containers

Private beta build, unsigned. Fixes a serious problem for anyone running FLOPPY in a container or opening the interface from another machine.

Your key was unreachable. Reveal, Copy and Save all failed silently: the app only returns the key to the machine it runs on, and a browser outside the container arrives from the Docker gateway instead. Now:

• Save the rescue file works from any browser — the app writes the file on its own machine and only the path travels back. In a container it lands in /data (your mounted volume); copy it out with docker cp.
• Reveal, when blocked, tells you where to read the key: docker exec <container> cat /data/engine/seed.hex.
• Confirming the backup now warns you if you never revealed nor saved the key in that window.
• FLOPPY_ALLOW_REMOTE_KEY=1 opts into sending the key over the network. Off by default, on purpose.

If you are already running from an earlier build: read your key now with the docker exec command above and store it. It cannot be recovered if the volume goes.

Install notes and requirements are in the README. SHA-256 in SHA256SUMS.txt.

FLOPPY 1.0.4 (private beta, unsigned) — Linux and Docker

Private beta build, unsigned.

New: Linux and Docker. The Engine step used to fail on Linux ("install Ollama yourself"). FLOPPY now downloads the official ollama-linux-<arch>.tar.zst, verifies its SHA-256 against the official release, and extracts it into your FLOPPY folder — no root needed. A Dockerfile is included; see the README. Autostart uses a systemd user service where systemd exists.

Also: long answers are no longer cut mid-sentence, and a cleaned-out data folder no longer breaks the Engine step.

• Linux / Docker: run from source, or docker build -t floppy . && docker run -d -p 8788:8788 -v floppy-data:/data floppy. Needs tar with zstd (apt install zstd) or Python 3.14+.
• macOS: open the DMG, drag to Applications. macOS 15 blocks it at first: System Settings → Privacy & Security → "FLOPPY.app was blocked" → Open Anyway.
• Windows: run the installer. SmartScreen → "More info" → "Run anyway". Per-user, no admin rights.

Needs 8 GB RAM (16 recommended) and about 5 GB of disk. What it does and does not do is in the README. SHA-256 in SHA256SUMS.txt.

FLOPPY 1.0.3 (private beta, unsigned)

Private beta build, unsigned. Read before installing.

• macOS: open the DMG, drag FLOPPY to Applications. macOS 15 will refuse to open it at first: System Settings → Privacy & Security → "FLOPPY.app was blocked" → Open Anyway. Apple Silicon recommended.
• Windows 10/11: run the installer. SmartScreen: "More info" → "Run anyway". Installs per user, no admin rights.
• Needs 8 GB RAM (16 recommended) and about 5 GB of disk for the engine and the model.

What it does, and does not do, is in the README: local key, local model, measured numbers, kibble is an unofficial practice board, no token or reward is promised.

Report what breaks with Settings → "Copy the log" (remove personal paths first, never paste your key) in an issue.

SHA-256 in SHA256SUMS.txt.