Project Structure Proposal: 3 Distinct Parts

[sbounmy]

🧩 Project Structure Proposal: Three Distinct Parts

As the project develops, it’s becoming clear that it naturally splits into three distinct components, each with different trust assumptions and deployment strategies:

---

🖼️ 1. Image Generation (Banknote Design) – Online

This part handles the creative and visual experience of generating themed “paper wallets” using AI.

• Runs online from the main site (e.g. hongbaob.tc)
• Allows users to:
  • Upload a portrait
  • Choose a banknote theme (Euro, Dollar, Dinar, etc.)
  • Receive a realistic paper wallet design
• Could include a credit-based system for accessing more generations or premium features
• Needs server-side rendering (e.g. via Sora or similar backend)

This could actually be become a private repo

🔐 2. Bitcoin Keygen + Print + Top-Up – Offline

This is the secure side of the system. It does not need to be online or trusted.

• Runs as a standalone HTML app (can be saved and run completely offline)
• Handles:
  • Bitcoin key generation
  • Overlaying keys on top of a chosen paper wallet image
  • Printing
  • Optional manual or automated top-up
• No backend or connection required — fully local, self-contained, and verifiable : Open Source
• Can be embedded as iframe too

Only top up via FIAT (credit card/wire) Mt Pelerin would require online

---

🔍 3. Wallet Scanner + Balance Check / Withdraw – Optional, Lightweight

A third piece of the experience could be a simple wallet scanner. It allows users to interact with their wallet (after creation) to:

• Scan public address to:
  • Check balance
• Scan private key to:
  • Withdraw funds
  • Transfer to another wallet
• Can follow the same principles as part 2:
  • Offline-capable
  • Standalone
  • Lightweight HTML/JS app (optional internet access only for querying balance or broadcasting a transaction)
• Could be deployed as a separate page (e.g. scan.hongbaob.tc) or embedded in part 2

---

🔧 Proposed URL-Based API for Rendering

To bridge part 1 and part 2, we can use a simple URL-based config to load the image and place the wallet data using coordinate parameters:

bitcoin.hongbaob.tc?image=https://hongbaob.tc/papers/1.jpg &public_address_qrcode=100,200&public_address_text=120,230&private_key_qrcode=100,400&private_key_text=120,430

URL Parameters:

Parameter	Description
image	URL to the paper wallet image (generated from part 1)
public_address_qrcode	x,y coordinates for the public address QR code
public_address_text	x,y coordinates for the public address text
private_key_qrcode	x,y coordinates for the private key QR code
private_key_text	x,y coordinates for the private key text

---

✅ Summary

Part	Description	Hosting	Trust Model
1. Image Generation	AI-generated banknote visuals	Online	Requires hosted backend (e.g. Sora)
2. Keygen + Print	Bitcoin wallet creation, printing, top-up	Offline	Fully trustless & verifiable
3. Wallet Scanner	Check balance, withdraw, transfer	Offline / Lightweight Online	Optional, lightweight, semi-trusted or local

By keeping the three parts modular and decoupled, we maximize security, usability, and scalability across both user types (casual and power users).

---

IMHO 2 & 3 can be together, so 2 distinct parts makes sense in a first move.

Let me know what you think — happy to refine the architecture or API further based on feedback!

[sbounmy]

We are often asked

how do I know the code deployed is the one from the repository?

it is not trivial : https://opensource.stackexchange.com/questions/7206/how-do-we-verify-if-the-code-deployed-in-same-as-the-one-published

But if we do the standalone part it could be hosted on github page.
And repo's page = repo's code
If we want to keep rails for this part we need to export the page as html/js into that github page repo)
Otherwise this part can be rewrite in react or any front only framework

cc @SalmaTalbi

[sbounmy]

we could investigate https://jekyllrb.com/ to turn into a static website the standalone app