How owasp-blt/blt-bacon works
Project type and purpose
• From the README and file tree, BACON is a backend‐heavy integration service that ties together Bitcoin Core, the Runes token protocol, GitHub/BLT issue events, USPTO trademark data, and a mobile frontend (the BLT iOS app). Its goal is to mint and distribute BACON tokens on Bitcoin, provide trademark alerts, and maintain a blockchain-backed company scoreboard.
File structure
• Top-level files only.
• BACON_Funding_Requirements.md – project planning.
• LICENSE, README.md – documentation.
• setup_bacon_node.sh – deployment script for the BACON node.
• No separate “src” folder shown, implying that the core service (“BACON node”) is likely packaged/deployed by the shell script.
• No direct frontend code; the primary frontend is the existing BLT iOS app (external to this repo).
README for architecture clues
• Components mentioned: Bitcoin Core, Runes protocol, POA consensus engine, BLT bug logging tool (GitHub issues), USPTO trademark API, company scoreboard, BLT iOS app.
• Integration points: JSON-RPC to Bitcoin Core, HTTP/webhooks from GitHub/BLT, REST calls to USPTO, push notifications to iOS.