SUBTC Philosophy — No RPC Required

permalink SUBTC
#philosophy#required#rpc#subtc

The **SUBTC Protocol** is designed as a **lightweight API layer** for Bitcoin, meaning **no RPC or node management is required** for developers or AI agents.

This design choice focuses on simplicity, privacy, and accessibility.

---

1. Why No RPC?

Traditional Bitcoin integrations require:

- Running a full Bitcoin node
- Using `bitcoin-cli` or JSON-RPC calls
- Managing blockchain synchronization

SUBTC removes all of this complexity:

- Developers don’t need a node
- No RPC credentials to manage
- No local blockchain storage

---

2. How It Works

All actions are executed via the **SUBTC API**:

- `wallet_create` → create wallets
- `wallet_receive` → generate addresses
- `wallet_balance` → check balances
- `wallet_send` → send BTC
- `wallet_poll` / `wallet_wait_event` → monitor transactions

Everything is **stateless**, **deterministic**, and works with **curl commands**.

---

3. Benefits

- **Developer-Friendly:** Start testing instantly, no blockchain setup required
- **Privacy:** No local node means no traceable logs
- **Automation:** AI agents or scripts can interact seamlessly
- **Testnet Ready:** Experiment safely without real BTC

---

4. Philosophy

SUBTC is **infrastructure and a bridge**:

- Not a custodian of wallet-balance" rel="dofollow">funds
- Users control their wallets and keys
- Protocol enforces execution, not decision-making

This aligns with:

- **Zero data storage**
- **No KYC / No tracking**
- **AI agent automation**

---

Conclusion

By eliminating RPC requirements, SUBTC makes Bitcoin integration **simpler, safer, and fully compatible with developers and AI agents**, while respecting privacy and decentralization principles.

https://subtc.net/api