🔗 SoWasIt - Documentation Technique

Architecture et modèles de données de la plateforme blockchain

Technical Concepts & Guarantees

SoWasIt is a cryptographic anchoring infrastructure designed to guarantee the absolute integrity of your data through immutable and mathematically verifiable proofs of existence.

Why SoWasIt is reliable:

Chained Immutability : Each block contains the double hash of the previous one (SHA-256). Modifying a single bit in the history mathematically invalidates all subsequent blocks.
Certified Timestamping : Creation time is recorded and sealed within the block's double hash.
Proof Independence : The proof (hash + content) is exportable. Its integrity can be verified with standard tools, without depending on our platform.

Anchoring Mechanism

The uniqueness of SoWasIt lies in its double-layer architecture:

[ Votre App ] -> [ Chaîne Privée ] -> [ Chaîne d'Ancrage Publique ]
      |               |                       |
   Données      Ordre & Contexte        Preuve Globale

Each event from your application is first recorded in your private chain (to keep your data confidential), then immediately anchored in the shared public chain.

Shared Registry : All SoWasIt clients anchor into the same public chain. This creates a cryptographic interdependence: to falsify your data, one would have to falsify the history of all the platform's clients simultaneously.

Atomicity & Reliability

To ensure a proof exists as soon as an operation is confirmed, SoWasIt uses advanced transaction mechanisms.

Atomic Transactions

Writing to your chain and public anchoring occur within a single, atomic transaction.

Guarantee : If public anchoring fails, the private record is rolled back. You never have a 'partial proof'.

Lock Management

The use of system-level locks ensures a perfect sequence of succession for blocks, preventing any race conditions even under high concurrency.

Security & Isolation

Although the infrastructure is shared (Multi-tenant), isolation is hermetic.

Logical Isolation : Each request is filtered by a tenant_id at the database engine level. A user from tenant A can never, by design, address a chain from tenant B.
Hashed Secrets : API keys and session tokens are never stored in plain text. Only their SHA-256 hash is kept.
Idempotence : The system supports idempotency keys. If you resend the same request, SoWasIt detects the duplicate and returns the original proof.

API Reference

The API is RESTful and communicates exclusively in JSON over HTTPS.

Complete Documentation : Interactive Swagger (OpenAPI) documentation is available at /api-docs

Authentication

Use the X-API-Key header for your server calls.

GET /api/v1/chains
Host: api.sowasit.io
X-API-Key: your_api_key_here

Chain Management

A chain is a logical container for your proofs.

Method	Endpoint	Description
`GET`	`/chains`	List your chains
`POST`	`/chains`	Create a new chain

Block Anchoring

This is the primary operation for creating a proof.

POST /chains/{chainId}/blocks
{
  "data": {
    "event": "document_signed",
    "hash": "e3b0c442...",
    "user_id": "user_42"
  }
}

Response : You immediately receive the block's hash and its prev_hash, constituting your proof of existence.