Every signed contract, debt confirmation and identity verification is cryptographically anchored. You don't need to trust the platform — you can verify the proofs yourself with standard open-source tools.
PGP Signatures
Every user can generate a PGP keypair directly in the browser. The private key never leaves the device. Contracts and debts are signed with this key before being submitted to the server.
- —Private key stays in your browser only
- —All contracts and debts carry dual PGP signatures
- —Signatures verifiable against the public keyring at gitea.parahub.io/audit
Bitcoin Anchoring
Every 10 minutes all pending events — signed contracts, confirmed debts, WoT verifications — are bundled into a git commit and stamped with OpenTimestamps. One Bitcoin block covers all events through a git Merkle tree.
- —Stamped every 10 minutes via systemd timer
- —One Bitcoin anchor covers all events — no per-event network cost
- —Proof is verifiable via opentimestamps-client with no account required
Export for Court
Any signed contract or confirmed debt can be exported as a ZIP package. The archive is self-contained and verifiable without access to Parahub.
- ›Full contract JSON with both signatures
- ›OTS proof file (.ots) anchored in Bitcoin
- ›Git commit reference and event log path
- ›README with step-by-step verification instructions
How to Verify Independently
pip install opentimestamps-clientots verify batch_ots_proof.otsgpg --import pubkey.asc && gpg --verify signature.ascPGP signatures qualify as Advanced Electronic Signatures (AES) under eIDAS Regulation (EU 910/2014). OpenTimestamps provides cryptographic proof of existence anchored in Bitcoin — accepted by Portuguese courts under Código Civil Art. 363º.