SigilbaseManual and attested uploads, sealed on arrival.
Sending records to Sigilbase through manual and attested uploads: every delivery receipted, every gap declared, and evidence your auditor verifies offline without an account.
Receivers ship in waves, and this one is in the first. Until then, anything that can send JSON reaches Sigilbase through the events API today.
- Status. First wave.
- Collected by. A receiver you point at.
- Connects with. A signed-in user with the right to upload.
- Category. Receivers and the API.
What can be sent through Manual and attested uploads
Each record becomes an event in the ledger, kept exactly as it arrived with a hash of those bytes beside it.
-
Log files
A file (CSV, PDF, JSON) uploaded by a named user with a stated description: the hash, the uploader and the time are sealed, and every report says the record came from an upload. HR exports, scan reports, penetration test reports, board minutes, policy acknowledgements, access reports and restore-test evidence.
How it will be collected
When this receiver ships, a named user uploads the file with a description; the hash, the uploader and the time are sealed, and every report says the record came from an upload.
The evidence model
What every connector and receiver ships with, whatever the source:
- A receipt per collection: what was asked for, what arrived, the cursor before and after
- A declared gap for any interval nothing covers, never a blank
- A daily settlement once late records can no longer arrive
- The raw record, byte for byte, with its hash
- An evidence bundle anyone can verify offline
What you get
-
Sealed as it arrives
Every record is hashed and chained to the one before; every few minutes the chain is sealed into a signed checkpoint. A changed, deleted or reordered record fails verification at that exact point.
-
Continuity you can show
The receipts chain too, so an auditor sees not only the records but that nothing between them went uncollected, and where a gap was, that it was declared.
-
Verified without us
An export carries the open-source verifier. It runs offline, checks the chain, the receipts and the gaps, and needs no Sigilbase account. How the service is run.
Questions about Manual and attested uploads
-
Does Sigilbase support Manual and attested uploads?
Receivers ship in waves, and this one is in the first. Until then, anything that can send JSON reaches Sigilbase through the events API today. Whatever arrives is written to a chained, signed ledger whose evidence anyone can verify offline with the open-source verifier, without a Sigilbase account.
-
What can be sent through Manual and attested uploads?
Log files: A file (CSV, PDF, JSON) uploaded by a named user with a stated description: the hash, the uploader and the time are sealed, and every report says the record came from an upload. HR exports, scan reports, penetration test reports, board minutes, policy acknowledgements, access reports and restore-test evidence.
-
How will Manual and attested uploads evidence be collected and verified?
When this receiver ships, a named user uploads the file with a description; the hash, the uploader and the time are sealed, and every report says the record came from an upload. Every collection will be receipted in the connection's own stream: what was asked for, what arrived, and the cursor before and after. An interval nothing covers will be declared as a gap, never left blank. Exports carry the standalone verifier, which checks the chain, the receipts and the gaps offline.
Start recording provable history
Chained, sealed, independently verifiable audit logs, from the first event. Free while Sigilbase is in beta.
Questions first? Write to hello@sigilbase.io.