Skip to content
View Shield-OS-dev's full-sized avatar

Block or report Shield-OS-dev

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Shield-OS-dev/README.md

ShieldOS-dev

Working on ShieldOS, a decentralized personal security operating system on Solana.

ShieldOS focuses on encrypted mail, storage, password management, private messaging, and security-focused AI inside a single dashboard.
Wallet-based authentication only, no Web2-style accounts.

Current Scope

  • ShieldOS core architecture and dashboard
  • Solana wallet integration and auth flows
  • Encrypted modules for mail, drive, and vault
  • Identity and permission layer design
  • Security and threat modeling

Design Principles

  • Privacy-first by default
  • Minimal and auditable system design
  • Strong cryptography with clear rationale
  • No telemetry, no tracking, no data selling

High-Level Architecture

ShieldOS is structured as a set of focused modules that all share the same core:

  • shieldos-core – shared types, cryptographic primitives, auth helpers, and low-level utilities used by every module.
  • shieldos-dashboard – main web client: routing, layout, state handling, and integration with all ShieldOS modules.
  • Modules (scoped as separate packages/repos):
    • Mail – encrypted inbox, verification code handling, and private communication.
    • Drive – private file storage with local encryption and optional IPFS pinning.
    • Vault – secure storage for secrets, notes, keys, and credentials.
    • Pass – DID + verifiable identity layer with local credential vault.
    • Link – encrypted share tokens and temporary access links.
    • Pay – private payment routing and spend control.
    • Scan / Security – local-only threat detection and payload inspection.

High-Level Flow

  • The Dashboard handles UI, navigation, and user interaction.
  • The Core layer provides cryptography, shared types, and secure helpers.
  • Each Module plugs into the dashboard via a shared module interface and imports from shieldos-core to keep behavior consistent.
  • All sensitive data is:
    • encrypted client-side,
    • stored locally when possible,
    • never logged or analyzed on the server.
flowchart LR
    User --> Dashboard[ShieldOS Dashboard]
    Dashboard --> Core[shieldos-core]
    Dashboard --> Mail[Mail]
    Dashboard --> Drive[Drive]
    Dashboard --> Vault[Vault]
    Dashboard --> Pass[Pass]
    Dashboard --> Link[Link]
    Dashboard --> Pay[Pay]

    Core --> Solana[(Solana)]
    Core --> IPFS[(IPFS / Storage Backends)]

How Core Fits Into the Architecture

shieldos-core is not a standalone app. It is the shared foundation for:

  • shieldos-dashboard – imports types, auth helpers, and crypto utilities.
  • Mail / Drive / Vault / Pass / Link / Pay modules – import the same primitives so that:
    • encryption behavior is consistent,
    • error formats are predictable,
    • authentication logic is unified,
    • there is no duplicated “security logic” spread across the codebase.

The goal is to keep all security-sensitive logic in one place so it can be audited, tested, and evolved without breaking every module separately.

Projects

Website
https://www.shieldos.xyz/

DApp
https://app.shieldos.xyz/

X
https://x.com/shield_os

Pinned Loading

  1. shieldos-core shieldos-core Public

    Core architecture, types, crypto utilities, shared components, and fundamental logic used across the ShieldOS ecosystem.

    TypeScript 1 1

  2. shieldos-dashboard shieldos-dashboard Public

    Main web dashboard for ShieldOS. Wallet authentication, module integration, UI system, and client-side encryption flows.

    TypeScript 1