Repository navigation
ReliaMesh 0.2.0 adds an optional Solana Devnet report-commitment adapter and a read-only Solana RPC agent example to the Apache-2.0 reliability core. Collection, detection and self-hosting remain independent of any blockchain. Developed by Prefiler Labs Private Limited.
The managed service is live at reliamesh.com, with API health reporting 0.2.0. This release runs only in GCP project reliamesh.
python -m pip install reliamesh-server==0.2.0 reliamesh-sdk==0.2.0
# Optional operator-only Devnet tools:
python -m pip install 'reliamesh-server[attest]==0.2.0'The SDK still has zero runtime dependencies. The adapter publishes only an explicitly selected, salted report commitment through the existing Memo program. It pins Devnet, checks fees, saves the transaction signature before sending once, and verifies the expected signer, exact transaction bytes and finalized inclusion. The RPC example instruments readiness checks without trading, transfers, account-content collection or a wallet requirement.
Two actual commitments to labeled synthetic 0.2.0 regression/recovery reports are finalized:
Each cost 5,000 Devnet lamports, funded by the official free faucet. No mainnet spending or custom program deployment occurred. The attached evidence contains exact bundles, signatures, receipts, independent JavaScript verification, published Python CLI checks and reproduction commands. The immutable source tag predates final ledger verification; these dated release assets supplement it.
Verification includes 392 passing tests and one optional emulator skip on each of Python 3.12 and 3.13; deployment reran the suite. All four attached distributions match PyPI hashes and their provenance attestations bind the company repository, exact commit and release tag. Fresh published-package installation passed synthetic regression/recovery, SQLite backup/restore and attestation tamper checks. The deployed service separately passed 201-event privacy, isolation, deduplication, scopes, revocation and cleanup checks; the Solana-tool exercise accepted 200 synthetic events with no SDK drops.
The deployed container runs as UID 10001 with no Python package installer or set-ID files. Its scan has zero critical, zero fixable high/critical and zero high/critical Python findings. 44 high OS-package records across eight unfixed Debian CVEs remain; see the exposure assessment and attached complete scan. This is not an independent security audit.
The ledger proves matching bytes, signing-key possession and RPC-reported inclusion; it does not prove telemetry truth, completeness, real-world observation time or independent adoption. Devnet can reset or prune history. Network intelligence remains disabled; detection is tenant-local, and no calibrated accuracy or SLA is claimed.
- Grant-readiness dossier
- Machine-readable verification
- Devnet evidence and runnable commands
- CI · deployment · Trusted Publishing
- SDK 0.2.0 · server 0.2.0
Assets include exact wheels/source distributions, SHA256SUMS, runtime license inventory, complete container scan, verification JSON, the technical dossier, Devnet evidence archive and a website screenshot.