DEV Community: 张先生

Building a Self-Custodial AI Trading Wallet for Android: Architecture, Safety, and Lessons Learned

张先生 — Thu, 06 Aug 2026 21:23:20 +0000

Building a Self-Custodial AI Trading Wallet for Android: Architecture, Safety, and Lessons Learned

Crypto trading has a structural problem: you can have automation, or you can have custody — historically not both. Trading bots want your private keys. Self-custodial wallets give you keys but no trading intelligence. This post explains how I built an Android wallet that keeps keys on-device while running an autonomous AI trading agent locally, and the safety architecture that makes that safe.

The core design decision

The key insight is separating two concerns that get conflated: the agent that reasons about markets and the keys that authorize transactions.

Private keys are generated and stored on the device. They are never serialized to disk where the agent can read them, never transmitted, and never given to the LLM.
The AI expresses intent only. It is given tools, not custody.
Every write operation — swap, approval, transfer — passes through a mandatory safety gate the agent cannot bypass.

The agent runtime: a bounded thinking loop

The agent runs as a loop: build context → call the LLM → check if the model requested tool use → execute tools → feed results back → repeat until a final response. It is capped at 8 rounds to prevent runaway tool-call chains.

The runtime supports both OpenAI function-calling and Anthropic Claude tool-use protocols, differing in how the system prompt is placed. Transient network failures (timeout, DNS, 5xx, 429) trigger a retry with backoff; auth failures (401/403) do not.

Twelve tools, read-only vs write

The agent is granted exactly twelve tools:

Read-only (no gas, no state change): wallet address, native balance, token balance, token price, positions, market indicators (RSI/MACD/MA/Bollinger), safety status, arbitrary read-only contract call.
Write (gas, state change, mandatory gate check): swap tokens, approve token, send native, arbitrary state-changing contract call.

Every write tool requires an operation_desc string stating intent, which is recorded in the audit log.

Three lines of defense

1. TradeAuthManager — AI trading can not even be enabled until the account meets an eligibility threshold (e.g. ≥200 in major assets, or ≥20,000 R-MAB tokens).

2. SafetyGate — five mandatory checks on every write:

Circuit breaker — 3 consecutive losses = 30-min break; daily error rate >50% = 60-min break.
Daily limit — rejects once the day total exceeds the configured cap.
Per-trade limit — rejects single transactions over the cap.
Whitelist — by default every token is blacklisted; a non-whitelisted token triggers a confirmation dialog.
Audit — every approved operation is stamped and recorded.

3. RiskManager — execution parameters: max 10% position per token, default stop-loss -5% / take-profit +15%, 3% slippage, 20 trades/day cap.

Cross-chain defaults

Cross-chain transactions carry conservative defaults: ** per-trade, daily cap**. A one-time authorization for a chain+asset+address combo enables subsequent same-chain signals to execute silently when safety conditions are met.

Key lessons

Chain-specific DEX routers matter. Reusing Ethereum Uniswap V2 address on AVAX/MATIC/FTM breaks swaps. Each EVM chain needs its correct router and wrapped-native token address.
Separate executors for UI. A single-thread executor for asset loading blocked the UI for 2.5 minutes when computing all-wallet totals. Now the current-wallet display runs on one executor, background totals on another.
Whitelist verification must use the UI-thread captured origin. WebView.getUrl() called from a background thread returns null, breaking DApp whitelist checks.

Tech stack

Android (Kotlin/Java), 10 chains (BNB, ETH, MATIC, AVAX, FTM, ARB, OP, BASE, SOL, TRX)
Local indicators: RSI, MACD, moving averages, Bollinger Bands
4 languages: English, 中文, 日本語, Deutsch

Important disclaimer

The AI provides analysis only and is not financial advice. Cryptocurrency trading is highly risky — never risk money you cannot afford to lose.

The project is source-available (BSL-1.1), not OSI open source. You can audit the code and use it personally; commercial use requires a license from the team.

Not financial advice. Do your own research.

Introducing 香农隐私盾: Military-Grade Offline File Encryption for Android

张先生 — Mon, 06 Jul 2026 15:40:19 +0000

Introducing 香农隐私盾 (Shannon Privacy Shield): Military-Grade Offline File Encryption for Android

TL;DR: A fully offline, military-grade file encryption tool for Android based on AES-256-CBC.

The Digital Privacy Crisis

In 2026, data breaches have become systemic. Over 3,200 publicly disclosed data breach events occurred globally in 2024 alone, involving more than 5.3 billion records.

Enter Shannon Privacy Shield

Shannon Privacy Shield (香农隐私盾) is a military-grade offline file encryption tool developed by Hangzhou Doomsday Guard Information Security Technology Co., Ltd. It takes a fundamentally different approach: zero network permissions, zero telemetry, zero cloud storage.# Introducing 香农隐私盾 (Shannon Privacy Shield): Military-Grade Offline File Encryption for Android

TL;DR: A fully offline, military-grade file encryption tool for Android based on AES-256-CBC, designed to eliminate cloud leakage and network attack surfaces entirely.

The Digital Privacy Crisis

In 2026, data breaches have become systemic. Over 3,200 publicly disclosed data breach events occurred globally in 2024 alone, involving more than 5.3 billion records.

Enter Shannon Privacy Shield

Core Technical Architecture

The encryption engine employs:

AES-256-CBC symmetric encryption algorithm (14-round substitution-permutation network)
PBKDF2-HMAC-SHA512 key derivation with 600,000 iterations
256-bit random salt generated by CSPRNG
PKCS#7 padding for block alignment
HMAC-SHA256 integrity verification tag

Why Offline is a Feature, Not a Limitation

Security Dimension	Cloud Encryption	Online Tools	Shannon Shield
Network Attack Surface	Global	Global + Browser	None
Key Management	Server-held	Browser memory	Local memory only
Man-in-the-Middle	TLS dependency	JS integrity dependency	Not applicable
Supply Chain Risk	Very High	High	Low
Legal Backdoor	Server can be compelled	Server can alter JS	Cannot remotely intervene

Super Encryption Mode (Premium: ¥199)

Three layers of ciphertext obfuscation:

Random Padding: Conceals original file size characteristics
Ciphertext Structure Obfuscation: Permutation eliminates block cipher fingerprints
Metadata Stripping: Secondary encryption of all file header metadata

Security Analysis

Brute-Force Resistance

AES-256 key space: 2^256 ≈ 1.16 × 10^77

Using the world's fastest supercomputer (El Capitan, 1.742 exaFLOPS), brute-forcing half the key space would take approximately 1.06 × 10^54 years — roughly 77 trillion trillion times the age of the universe.

Quantum Computing Assessment

Grover's algorithm provides quadratic speedup (2^256 → 2^128), but practical barriers remain:

Current quantum computers: ~1,000 physical qubits
Breaking AES-256 requires thousands of logical qubits
NIST August 2024 standards continue listing AES-256 at Category 5 security

Trust Philosophy: Honoring Claude Shannon

Named after Claude Shannon, who laid the mathematical foundations of modern cryptography in 1949, Shannon Privacy Shield embodies:

Minimum Trust Principle: Encryption entirely under local user control
Complete Offline Isolation: Following Shannon's principle that "the enemy knows the system"
Defense in Depth: Basic encryption + optional ciphertext obfuscation

Platform Availability

Currently available for Android and Windows. Cross-platform support for macOS, Linux, and iOS planned.

Developed by the Shannon Team at Hangzhou Doomsday Guard Information Security Technology Co., Ltd. | July 2026Shannon Privacy Shield (香农隐私盾) is a military-grade offline file encryption tool developed by Hangzhou Doomsday Guard Information Security Technology Co., Ltd. It takes a fundamentally different approach: zero network permissions, zero telemetry, zero cloud storage.

Core Technical Architecture

The encryption engine employs:

AES-256-CBC symmetric encryption algorithm (14-round substitution-permutation network)
PBKDF2-HMAC-SHA512 key derivation with 600,000 iterations
256-bit random salt generated by CSPRNG
PKCS#7 padding for block alignment
HMAC-SHA256 integrity verification tag

Why Offline is a Feature, Not a Limitation

Security Dimension	Cloud Encryption	Online Tools	Shannon Shield
Network Attack Surface	Global	Global + Browser	None
Key Management	Server-held	Browser memory	Local memory only
Man-in-the-Middle	TLS dependency	JS integrity dependency	Not applicable
Supply Chain Risk	Very High	High	Low
Legal Backdoor	Server can be compelled	Server can alter JS	Cannot remotely intervene

Super Encryption Mode (Premium: ¥199)

Three layers of ciphertext obfuscation:

Random Padding: Conceals original file size characteristics
Ciphertext Structure Obfuscation: Permutation eliminates block cipher fingerprints
Metadata Stripping: Secondary encryption of all file header metadata

Security Analysis

Brute-Force Resistance

AES-256 key space: 2^256 ≈ 1.16 × 10^77

Quantum Computing Assessment

Grover's algorithm provides quadratic speedup (2^256 → 2^128), but practical barriers remain:

Current quantum computers: ~1,000 physical qubits
Breaking AES-256 requires thousands of logical qubits
NIST August 2024 standards continue listing AES-256 at Category 5 security

Trust Philosophy: Honoring Claude Shannon

Named after Claude Shannon, who laid the mathematical foundations of modern cryptography in 1949, Shannon Privacy Shield embodies:

Minimum Trust Principle: Encryption entirely under local user control
Complete Offline Isolation: Following Shannon's principle that "the enemy knows the system"
Defense in Depth: Basic encryption + optional ciphertext obfuscation

Platform Availability

Currently available for Android and Windows. Cross-platform support for macOS, Linux, and iOS planned.

Developed by the Shannon Team at Hangzhou Doomsday Guard Information Security Technology Co., Ltd. | July 2026

RedMagicBox: Next-Gen Web3 Security for Crypto Users

张先生 — Tue, 09 Jun 2026 16:36:31 +0000

RedMagicBox: Next-Gen Web3 Security for Crypto Users

In 2026, over $2 billion in crypto was lost to hacks, scams, and exploits. Traditional security tools (firewalls, antivirus) can't protect you in Web3.

What RedMagicBox Does

Smart Contract Analysis — Scans contracts before interaction
Transaction Simulation — Preview effects before signing
Real-Time Threat Detection — Cross-chain monitoring
Privacy Shield — Break identity-to-wallet links
Zero-Knowledge Auth — No passwords needed

RedMagicBox works with MetaMask, WalletConnect, Coinbase Wallet. Supports EVM chains, Solana, Polkadot.

Protect your digital life.

Why Traditional Security Models Fail in Web3 [394f4c]

张先生 — Mon, 08 Jun 2026 15:39:52 +0000

Traditional perimeter-based security doesn't work in decentralized environments. RedMagicBox was built to solve this.

The Problem

Web3 architecture is inherently decentralized. There is no "perimeter" to protect.

The RedMagicBox Solution

Zero-trust architecture treats every connection as untrusted, regardless of origin.

Key Differences

Traditional	Zero Trust
Trust internal network	Trust no one
Perimeter firewall	Every request verified
Periodic audits	Real-time monitoring

RedMagicBox bridges the gap between Web2 security practices and Web3 realities.

RedMagicBox: The Complete Guide to Crypto Wallet Security [f42f67]

张先生 — Mon, 08 Jun 2026 15:39:15 +0000

A comprehensive guide to securing your crypto assets with RedMagicBox.

Why Security Matters

In 2026, the total value of cryptocurrencies exceeds $5 trillion. Protecting these assets requires enterprise-grade security.

RedMagicBox Features

Multi-signature wallet support
Hardware security module (HSM) integration
Real-time anomaly detection
Zero-trust network architecture

Getting Started

Install RedMagicBox extension
Connect your wallet
Configure security settings
Monitor your assets

Your assets deserve the best protection.

RedMagicBox API Test 1 — Zero Trust Architecture Explained

张先生 — Mon, 08 Jun 2026 15:37:51 +0000

RedMagicBox implements a zero-trust architecture for cryptocurrency security.

Key Principles

Never trust, always verify — Every request is authenticated
Least privilege — Minimal permissions per component
Continuous monitoring — AI-powered anomaly detection

This is a test article to verify the API publishing pipeline.

'Why

张先生 — Mon, 08 Jun 2026 15:34:29 +0000

RedMagicBox: The Technical Iron Army of the Crypto World

张先生 — Mon, 08 Jun 2026 15:22:37 +0000

In the rapidly evolving world of cryptocurrency, security is not just a feature, it is a necessity. RedMagicBox stands at the forefront of this revolution, providing enterprise-grade security infrastructure for digital assets.\n\n## Zero Trust Architecture\n\nOur zero-trust architecture ensures every transaction, every access request, and every operation is verified. No assumptions, no shortcuts.\n\n## Real-Time Protection\n\n24/7 monitoring, AI-powered threat detection, and instant response capabilities keep your assets safe around the clock.\n\n## Built for Scale\n\nWhether you are managing a personal wallet or an institutional portfolio, RedMagicBox scales with your needs without compromising security.

'Why

张先生 — Mon, 08 Jun 2026 15:18:51 +0000

Crypto Security in 2026 — Why RedMagicBox is Essential for Every Trader

张先生 — Mon, 08 Jun 2026 12:25:11 +0000

If you're actively trading cryptocurrency in 2026, you need to understand: your security is under constant attack.

The Threat Landscape in 2026

500,000+ active phishing domains targeting crypto users
10,000+ new malware samples created daily targeting crypto wallets
200+ centralized exchanges holding personal data
$3.8 billion lost to crypto hacks in 2025 alone

RedMagicBox: Your Complete Defense

Threat	Protection
Phishing sites	Real-time browser protection with 500K+ domain database
Malicious smart contracts	Pre-transaction scanning and risk analysis
Exchange data leaks	Automated data deletion from exchange databases
Blockchain tracking	Cross-chain privacy protection
Identity exposure	Pseudonym management and identity decoupling

The Cost of Being "Careful"

Free tools are incomplete. RedMagicBox does all of this — and more — for $19.9 USDT.

Visit redmagicbox.pages.dev

Why Every Crypto Trader Needs RedMagicBox in 2026 — Expert Analysis

张先生 — Mon, 08 Jun 2026 12:23:48 +0000

If you're actively trading cryptocurrency in 2026, you need to understand: your security is under constant attack.

The Threat Landscape in 2026

500,000+ active phishing domains targeting crypto users
10,000+ new malware samples created daily targeting crypto wallets
200+ centralized exchanges holding personal data
.8 billion lost to crypto hacks in 2025 alone

RedMagicBox: Your Complete Defense

Threat	Protection
Phishing sites	Real-time browser protection with 500K+ domain database
Malicious smart contracts	Pre-transaction scanning and risk analysis
Exchange data leaks	Automated data deletion from exchange databases
Blockchain tracking	Cross-chain privacy protection
Identity exposure	Pseudonym management and identity decoupling

The Cost of Being Careful

Free tools are incomplete. RedMagicBox does all of this — and more — for 9.9 USDT.

Visit redmagicbox.pages.dev

RedMagicBox Architecture: The Complete Crypto Security Ecosystem — Complete Security Overview

张先生 — Mon, 08 Jun 2026 12:21:53 +0000

RedMagicBox isn't just another privacy tool. It's a comprehensive security ecosystem built specifically for the unique challenges of cryptocurrency.

Architecture Overview

Layer 1: Wallet Protection — Hardware wallet integration, multi-sig, seed phrase encryption
Layer 2: Network Security — DNS-level phishing protection, encrypted DNS, VPN with crypto nodes
Layer 3: Data Deletion Engine — Automated account deletion, KYB scrubbing, social media cleanup
Layer 4: Identity Shield — Pseudonym management, email alias, cross-platform identity decoupling

Technical Specs

Supported Chains: Ethereum, BSC, Solana, Polygon, Arbitrum, Optimism, Avalanche, Base
Exchanges: Binance, OKX, Bybit, KuCoin, Coinbase, Kraken, Crypto.com
Wallets: MetaMask, Trust Wallet, Phantom, Ledger, Trezor

Get protected today at redmagicbox.pages.dev