syleo.
WebCrypto v0.4.2
ORBITAL SHARD CORE // 128 BLOCKS LOCKED
[SYLEO] ZERO-KNOWLEDGE SHARD VAULT · SOLANA

Every secret
is 128 shards.

Slice any file, key, or raw payload into 128 SHA-256 cryptographic blocks directly in your browser. Seal with threshold shares, inspect raw hex offsets, or zero-fill shred in 3 passes.

How sharding works Protocol specs
$SYLEO CA: TBA (Official Pump.fun Launch)
⬢ syleo://sha256:9f86d081..0a08?shards=128&k=3of5
[01 / PIPELINE] LOCAL SHARD ARCHITECTURE

Slice. Seal. Verify. Shred.

Centralized cloud vaults upload your files before encrypting them. SYLEO executes the entire sharding and SHA-256 Merkle pipeline inside your local browser memory via window.crypto.subtle.

STAGE 01

Local Buffer Ingestion

Drop any document, keyfile, or archive into the client. The raw byte stream is read into an isolated ArrayBuffer without touching any external server.

FileReader → ArrayBuffer
STAGE 02

128-Block SHA-256 Tree

The payload is partitioned into 128 deterministic blocks (`#000` to `#127`). Each block is hashed via WebCrypto SHA-256 to form an immutable root digest.

crypto.subtle.digest('SHA-256')
STAGE 03

Threshold Key Sealing

Export a portable .syleo.json manifest or split vault access across $k$-of-$n$ threshold shares so no single node can reconstruct the payload alone.

threshold: k=3 of n=5 shares
STAGE 04

3-Pass Memory Shred

When your inspection session ends, trigger a 3-pass zero-fill and CSPRNG overwrite (`crypto.getRandomValues`) to sanitize all 128 blocks in RAM.

3-pass CSPRNG sanitization
[02 / REDUNDANCY] SHAMIR THRESHOLD ENGINE

Mathematically unbreakable split.

Configure how many guardian key shares are required to reassemble your 128-block vault. Even if an attacker compromises $k-1$ shards, zero bytes of the original payload are exposed.

● INTERACTIVE THRESHOLD SIMULATOR CIPHER: SHA-256 + AES-256-GCM
Total Guardian Shares (N) 8 Shares
Required Recovery Quorum (K) 5 of 8 Shares
MAX COMPROMISED TOLERANCE Up to 4 Shares Lost
KEYSPACE SECURITY 2^256 (128 Blocks)
syleo-crypto-engine — WebCrypto SHA-256 LOCAL ACTIVE
[03 / INTEGRITY] DETERMINISTIC HEX PROOF

Inspect every byte offset.

Click any shard cell in the 64-block verification matrix below to inspect its exact byte boundary and SHA-256 sub-chunk signature in real time.

INTERACTIVE 64-CELL SHARD MATRIX SHA-256 VERIFIED
INSPECTING SHARD: BLOCK #000 (0x000000)
DIGEST: 9f86d081884c7d659a2feaa0...
CRYPTOGRAPHIC ENGINE PARAMETERS ZERO-TRUST
Digest Standard FIPS 180-4 SHA-256 via window.crypto.subtle
Shard Granularity 128 Fixed-Offset Blocks per Vault Payload
Sanitization Mode 3-Pass 0x00 + CSPRNG Random Overwrite
Execution Context 100% Client-Side Browser Sandbox (No Wallet)
[04 / MANIFESTS] PUBLIC VAULT TEMPLATES

Pre-mounted shard vaults.

VAULT MANIFEST CATEGORY PAYLOAD SIZE SHARD TREE CIPHER STATE ACTION
[05 / DOCUMENTATION] TECHNICAL SPECIFICATION

Engineered for zero-leakage.

[06 / QUESTIONS] FAQ

Frequently asked questions.

What is SYLEO and how does it work in the browser? +

SYLEO (syleo.fun) is a browser-native cryptographic shard vault and 128-block payload inspector. When you drop any file or secret text into the client, your browser reads the byte buffer locally, calculates the real SHA-256 digest via WebCrypto, and maps the payload across 128 verifiable hex blocks.

Are my files or text payloads ever uploaded to a server? +

Never. All file slicing, SHA-256 hashing, hex header inspection, .syleo.json manifest generation, and 3-pass memory shredding execute 100% locally inside your browser tab.

Do I need to connect a Solana wallet to use the SYLEO Vault Client? +

No. Clicking "Open Vault Client" boots the full desktop-grade sharding interface immediately with zero wallet prompts, sign-ins, or permissions.

What is the role of the $SYLEO token? +

$SYLEO is the native ecosystem token for the SYLEO vault protocol on Solana, launched fairly via Pump.fun with no presale or private allocation.