🛂Architecture & Security Design

“Security isn't an add-on. It's the foundation.”

Every piARM module is built from the ground up with hardened logic and minimal surface area for attack. Our entire ecosystem follows zero-trust principles and is carefully architected to prevent:

  • Man-in-the-middle attacks

  • RPC spoofing or phishing endpoints

  • Dusting attacks, fake honeypots, and sybil bait

  • Session hijacking and stale signing exploits

How we enforce this:

  • 🔒 Airgapped execution logic: critical wallet functions never run with internet-facing permissions

  • 🔁 Session memory wiped: unless pinned by the user, keys and wallets are erased every refresh

  • 🧱 Sandboxed data layers: user-added chains and tokens are isolated from trusted defaults

  • 🧊 Cold signing stays cold: secure signing flows never touch online components

  • 🧬 Custom-built RPC stack: redundant, fallback providers prevent single-point spoofing

  • 🧃 USB or QR handshake: two-factor triggers required before any sensitive operation


🌍 Chain Support

Out of the box, piARM is equipped for all major EVM chains:

  • Ethereum

  • Arbitrum

  • Base

  • Optimism

  • Polygon

  • Fantom

  • Avalanche

  • BNB Chain

  • Cronos

  • Pulsechain

  • Sepolia (Testnet)

✅ Custom RPCs are supported. You can import any EVM-compatible network, configure gas tokens, and manage visibility per-chain.

🔢 Supported Token Types:

  • ERC-20 (standard)

  • Native chain gas tokens

  • Custom or unknown tokens (manual or discovered via piarm-token-discover)


⚙️ Setup & Deployment

“Deployment should be frictionless, auditable, and secure.”

🔐 Cold Vault Setup (Airgapped Mode)

  1. Clone the secure boot image from our Git repo

  2. Flash to SD card or USB via piarm-flasher

  3. Boot into hardened shell environment

  4. Run onboarding: secure phrase setup, 2FA config, and vault entropy generation

  5. Begin using the vault — completely offline


🛠️ Tooling: Blue Guava & Dragonfruit

🔹 Blue Guava – Blockchain Signal Engine

piARM’s multichain analytics and signal intelligence engine. Enables advanced on-chain insights and logic modules:

  • Router previews and token simulations

  • Contract verification signals

  • Smart trigger logic for user agents (bots, notifications, tooling)

  • Foundation for PiARM’s future plugin ecosystem

Runs locally or via PiARM node clusters. Rajika framework integration begins Q3.


🔸 Dragonfruit – Sovereign Sniper & Launch Toolkit

A self-hosted toolkit for advanced builders and automation users.

Focused on freedom, privacy, and control — no keys sent to third parties, no auto-update traps, and no built-in dependencies on centralized APIs.

Includes:

  • Mempool listeners & token creation watchers

  • Auto-routing, auto-snipe, or conditional liquidity triggers

  • Configurable via .yaml or .json strategy profiles

  • Optional Telegram bot output or SMS notifications

  • Supports Raspberry Pi, VPS, local, and container deployments

  • Leverages Blue Guava for verified contract filtering, router decoding, and simulated outcomes

❗Note: Dragonfruit is an open toolkit — not a revenue-generating product. Performance depends entirely on user configuration and market dynamics.


💼 Use Cases

🧊 For Privacy-Conscious Retail Users:

  • Cold store your assets with no $300 hardware requirement

  • Simulate token interactions without touching RPC endpoints

  • Prevent dust traps, rug tokens, and DNS attacks

🛠️ For Builders:

  • Deploy Blue Guava for analytics, dashboards, and swap simulations

  • Run token discovery, router previews, and bridge simulations

  • Create your own tooling on top of piARM’s modular RPC layer

🌏 For Emerging Markets:

  • Run an entire crypto suite on $35 hardware

  • Sync offline with PiRelays, even on unstable internet

  • 100% local, self-sovereign, and KYC-free


🔥 Why We’re Different

"Every cold wallet says trust us. We say: don’t."

  • Runs on anything: From old ThinkPads to Raspberry Pi 5

  • Fully modular: Use only the components you need — vault, wallet, Guava, token scanner

  • Transparent build: Source available. Audit everything. No hidden firmware

  • No black boxes: CLI-first, user-owned, and offline-first

  • Offline-first design: Built for the real world — where internet is optional, not assumed

Last updated