A ledger that can’t lie.
Everything that happens on the farm — every payment, attendance day, worker action and camp event — is sealed into an append-only, cryptographically chained ledger, anchored hourly to the Bitcoin blockchain. If anyone alters history, ForceAgri detects it and raises the alarm.
Every wage dispute is the same question: whose record do you believe?
A paper book, a spreadsheet, a plain database — all of them can be quietly edited after the fact, and nobody can prove it either way. On ForceAgri, the record proves itself: if any past entry is altered — even by a database administrator — verification fails immediately and loudly.
For the farmer
Defensible records for audits, inspections and disputes. When a claim lands on your desk, you answer with a chain of proof — not a shoebox of slips.
For the worker
Earnings and attendance that can’t be silently rewritten — by anyone. What was recorded stays recorded, and any change leaves a trace.
Mistakes still get fixed — as visible corrections, never silent edits. The original, its reversal, and the corrected entry all stay on the record, linked together.
Four layers. Each closes the gap the last one leaves.
Plain language here — the precise cryptography is further down for those who want it.
Nothing is ever edited or deleted.
Entries can only be added — the database itself refuses every update and delete, from any app or any account. It isn't a policy; it's physically impossible. Mistakes are fixed with a new, linked correction entry, and the original stays visible.
enforced by database security rulesEvery entry is locked to everything before it.
Each sealed entry carries a fingerprint of its own content — and embeds the fingerprint of the entry before it. Change anything in the past and the link snaps: every entry from that point forward fails verification.
SHA-256 fingerprintsOnly the trusted server can seal a record.
Apps submit entries; a trusted cloud function seals them — sequence number, link to the previous entry, and a digital signature with the farm's own private key held in a secure vault. Each farm's public key is world-readable, so anyone can check the signatures without asking us. Sealing happens on arrival, so offline-first recording in the field still works.
Ed25519 · per-farm keys · secure vaultFrozen against everyone. Including us.
Every hour, the chain's head fingerprint is published to the Bitcoin blockchain — a public record nobody can retroactively alter, ForceAgri included. Because the head fingerprint chains everything before it, one anchor freezes the entire ledger to date. No tokens, no fees — and no farm data ever leaves the platform, only a fingerprint.
hourly · OpenTimestamps · multiple calendar serversGo ahead — try to rewrite history.
Play the crooked bookkeeper. Below is one of everything the ledger records — money, attendance, worker actions, camp events. Shave a wage, then run the same integrity check every farm runs automatically each night.
Six sealed entries — a wage, an attendance day, a worker action, a camp event, a deduction — fingerprinted with real SHA-256 in your browser. Verify the honest chain, or try to cook the books first.
Proof you can see — and hand to your accountant.
This isn’t a roadmap item. These are the surfaces on every farm right now.
The Ledger integrity page — every anchor ships a downloadable .ots proof file, verifiable with standard open-source OpenTimestamps tools. No ForceAgri involvement required.
Every export carries its own provenance
PDF, Excel and CSV reports end with a ledger-integrity footer — chain head, verification status, and whether any alarm is active. A payroll report handed to an accountant or labour inspector proves itself.
Corrections, never cover-ups
Reversed and corrected entries stay visibly linked to their originals, with a required reason. The history never lies about having a history.
On the record today.
Everything that happens on the farm is written to a chain — money, attendance, worker actions, camp events. If it’s in ForceAgri, it’s on the record, and the record proves itself.
Money chain
LiveEvery worker credit and debit — wages, deductions, purchases, settlements. Amounts are stored as exact integer cents (no floating-point rounding, ever), and balances are derived only from sealed entries.
Attendance chain
LiveOne entry per worker per day — present, absent or leave, clock-in and clock-out, and who recorded it from where. Re-marking a day adds a superseding entry; the old one stays visible.
Worker chain
LiveEvery action on a worker’s record — hiring, operation transfers, rate changes, terminations — with who did it and when. Employment history is tamper-evident too: no one can quietly rewrite how, or why, a worker left.
Farm & camp events
LiveOperational events recorded against camps and operations — the farm’s working diary. What was done, where, by whom — sealed with the same proof as the money.
Nightly self-checks re-walk every chain; daily signed checkpoints keep verification fast forever. New record types run on the same engine — without touching existing chains.
The precise claims.
What exactly gets sealed?
Each farm runs its own chains. A trusted cloud function seals every entry: it assigns the sequence number, embeds the previous entry's hash, computes a SHA-256 fingerprint of the content, and signs it with a per-farm Ed25519 private key held in Google Secret Manager. Client apps can never write the seal fields — and the database rules deny all updates and deletes outright.
What does "anchored to Bitcoin" mean?
Every hour, the chain's head fingerprint is published to the Bitcoin blockchain via OpenTimestamps, submitted to multiple independent calendar servers for redundancy. Only a hash ever leaves the platform — no farm data, no wallet, no gas fees. Because the head hash chains everything before it, one confirmed anchor freezes the entire ledger to date.
How would tampering actually be caught?
A nightly job re-walks each farm's chains: it recomputes every fingerprint, checks every link, verifies signatures against the farm's public key, and confirms the head still matches the latest Bitcoin-confirmed anchor. Daily signed checkpoints chain together, so verification stays fast forever — one period plus a short checkpoint chain, never a full re-scan. Admins can also run a check on demand and get a pass/fail with the exact broken sequence number.
What happens when a check fails?
The system fails loudly: a persistent red "Ledger integrity alert" banner appears across the portal for every farm user, and every admin on the farm is emailed. The alarm can only be cleared by a named admin acknowledging it — and that acknowledgement (who, when) is itself recorded.
Can ForceAgri itself rewrite history?
Layers 1–3 stop outsiders; anchoring closes the insider gap. Once an anchor is confirmed on Bitcoin, any rewrite of earlier history — even by us, holding the signing keys — is caught by re-checking against Bitcoin, without trusting ForceAgri or any intermediary. The honest residual: entries newer than the last hourly anchor (roughly the last hour) are not yet frozen.
Is this a blockchain?
No — and that's deliberate. There are no tokens, nodes, or mining. It's an append-only, hash-chained, signed log that is anchored to Bitcoin. You get the integrity guarantees people associate with a blockchain, with none of the cost, complexity, or volatility.
We choose our words carefully.
The engineering team deliberately doesn’t overclaim. Neither do we.
Alterations are detected and provable — not physically impossible. Entries newer than the last hourly anchor are the honest residual window.
The ledger itself is not a blockchain — no tokens, no nodes, no fees. That’s a feature, not a weakness.
Anchoring proves recorded history existed and is unaltered; it cannot prove an event was never omitted.