Reducing Attack Surface on SUBTC

When building **payment gateways** on the SUBTC Protocol, it is critical to minimize the attack surface to protect keys, wallets, and funds.

---

1. Key Guidelines

- Use **Docker containers** to isolate processes and dependencies
- Store secrets like `SUBTC-KEY` and wallet IDs (`WID`) in **.env files**, not databases or GUI dashboards
- Avoid persistent storage of sensitive credentials whenever possible

> Note: This reduces the attack surface—it is **not a security guarantee**.

---

2. Multi-Layer Protection

- Integrate **WireGuard** or similar VPN/proxy layers for network isolation
- Restrict access to containers and hosts
- Limit exposure to only required endpoints

This approach provides **multi-layer defense** and helps prevent accidental leaks.

---

3. Philosophy

- Keep secrets **ephemeral** and **scriptable**
- Reduce reliance on web interfaces, which can be exploited
- Enable automation without compromising privacy

---

4. Next Steps

- Learn more about advanced network security setups
- Check our **internal search engine** for guides on WireGuard integration
- Implement container-based testing and deployment pipelines

---

Conclusion

By combining containers, secure environment variables, and network isolation, developers can **significantly reduce the attack surface** when building on SUBTC, ensuring safer and more reliable payment operations.

https://subtc.net/api