-
-
Notifications
You must be signed in to change notification settings - Fork 0
Core Concepts
To effectively use Svalinn, you must understand its foundational principles.
The primary abstraction in Svalinn is the "Shielding Boundary". This is a cryptographic perimeter that data cannot cross without being either encrypted, signed, or accompanied by a validity proof. Everything inside the boundary is considered a Trusted Execution Environment (TEE).
Svalinn relies on mathematical contracts—formal specifications of what a piece of code is allowed to do. These contracts are verified at compile-time and run-time to prevent buffer overflows, timing attacks, and memory leaks.
When data enters the boundary, Svalinn generates a ZK-SNARK proof of its provenance. This allows downstream services to verify that the data originated from a trusted source and passed all boundary checks without needing to re-examine the raw data or trust the intermediate transit layers.
For distributed deployments, Svalinn nodes form a consensus topology. They use a Byzantine Fault Tolerant (BFT) protocol to agree on the state of the boundary and any policy updates.