Lightning Piggy
Lightning Piggy should be read as a hardware and education project first. Its Nostr relevance comes through Nostr Wallet Connect and Nostr community sharing, while the practical risk sits in wallet choice, device flashing, batteries, QR setup, workshop supervision, NWC permissions and LNbits hosting.
What Lightning Piggy really is
Lightning Piggy is a physical Bitcoin savings device for children and families. The official site describes it as an open-source electronic piggy bank that accepts Bitcoin over the Lightning Network and displays savings in satoshis. That sounds playful, but the project is not just a mascot. It is a small hardware build, a firmware stack, a wallet-connection flow and an education program around saving in sats.
The device shows a receive QR code, a satoshi balance, recent transactions and payment messages. A child can watch a balance grow when relatives send small Lightning payments for chores, birthdays, homework goals or pocket money. The important detail is where the money lives: not inside the piggy. The FAQ says funds stay in the wallet you connect to it. If the device is stolen and configured as watch-only or receive-oriented, the attacker may see balance and recent activity, but the wallet remains the security boundary.
That makes Lightning Piggy a hardware interface to a Lightning wallet, not a new custodial wallet provider. It is meant to make small-value Bitcoin saving visual and teachable. You still need to choose a wallet, set up NWC or LNbits, handle QR configuration, flash firmware and supervise the build like real electronics. The friendly shape lowers the emotional barrier, but the technical responsibility does not disappear.
Why it belongs in Hardware
Lightning Piggy belongs in Hardware because the public experience begins with a device on a desk, shelf, classroom table or workshop bench. You source a board, flash firmware, connect Wi-Fi, add wallet credentials, place it in a case and scan a QR code from the screen. The software matters, but the object is the product.
The project itself reinforces that category. The build page separates Classic and p1 hardware. Classic uses LILYGO T5 e-paper boards and Arduino-based firmware. The newer p1 path uses a Waveshare ESP32-S3 touchscreen board running MicroPythonOS. The cases repository offers enclosure designs that can be 3D printed, laser cut or made from cardboard. Those are not marketing details. They tell you this is a maker project with physical assembly choices.
Nostr and NWC are still central to understanding the device. The official guides tell users to choose an NWC-capable wallet, copy a NWC link and keep a Lightning Address. The getAlby awesome-nwc list includes LightningPiggy in the Hardware section. The GitHub organization also maintains `nostrduino`, an Arduino and ESP32 library that includes NIP-47 support. Hardware is the category; NWC is one of the key ways the hardware talks to a wallet.
The official footprint
The official domain is `lightningpiggy.com`, without a hyphen. That distinction matters because similar-looking domains can appear in search. The official site carries the product story, build guides, market, community pages, FAQ, troubleshooting, serial monitor, donation page and links to the LightningPiggy GitHub organization, Primal profile, X account and Telegram community.
The GitHub organization is active and broad enough to support the open-source claim. The organization profile listed 13 public repositories when checked on June 13, 2026. The main repositories include `LightningPiggyApp` for MicroPythonOS, `lightning-piggy` for the Classic e-paper firmware, `website` for the Astro site, `lightningpiggy.github.io` for the web installer, `cases` for enclosures, `nostrduino` for Nostr/NWC on microcontrollers, `TouchColorPiggy` for a Waveshare touchscreen build and a small PWA called `lightning-piggy-mobile`.
The activity pattern matters. `LightningPiggyApp` had a push on June 13, 2026, the same day this review was written. The mobile PWA was pushed on June 11, 2026, and the website was pushed on June 3, 2026. Classic firmware was pushed in February 2026. This is not an abandoned one-page idea. It is an active family of repositories, with the usual maker-project caveat that activity does not equal audit quality.
Classic and p1 are different devices
Lightning Piggy has two main hardware generations. Classic is the original e-paper edition. It runs Arduino-based C++ firmware on LILYGO T5 boards with 2.13-inch and 2.66-inch e-paper displays. Its appeal is low power, simple display behavior and a build path that grew from the early Lightning Piggy codebase.
The p1 line is the newer recommended path. It uses a Waveshare ESP32-S3 board with a two-inch color touchscreen and optional camera. Instead of the older Arduino-only firmware flow, p1 runs MicroPythonOS and installs the Lightning Piggy app from the MicroPythonOS app store. The official build page frames this shift as an accessibility decision: MicroPython is easier for learners to read, change and understand than a larger C++ sketch.
Do not mix instructions between the two. Classic flashing, configuration and LNbits host-name rules are not identical to p1. The troubleshooting page says Classic refers to the original e-paper C++ firmware, while MicroPythonOS refers to the newer touchscreen version. It also warns that MicroPythonOS should be updated before installing or updating the Lightning Piggy app, because newer app versions may rely on newer OS APIs.
The wallet model
Lightning Piggy offers two wallet connection paths: Nostr Wallet Connect and LNbits. The build guides present NWC as the simpler option for many users because it can be copied from a compatible wallet. They present LNbits as the more controlled option for people willing to host or use an LNbits instance. Both can be self-custodial or custodial depending on how the underlying wallet is run.
The NWC path is useful because it separates the display device from the wallet. A NWC connection string can let an app request wallet information or actions over Nostr without exposing the wallet's private keys. In a Lightning Piggy context, that means the device can display a Lightning Address QR, fetch balance or recent payment state and interact with the wallet according to the permissions the wallet grants.
The LNbits path is more server-like. LNbits can run on a personal node, a hosted instance or a bundled home-server environment. Lightning Piggy's troubleshooting page recommends setting up LNbits on a node such as RaspiBlitz, Start9 or Umbrel if you want that backend. The extra control comes with extra work: server availability, TLS, extensions, invoice keys, LNURLp configuration and backups.
NWC in practical terms
For a reader, NWC should not be treated as a magic wallet sticker. It is a permissioned connection between a wallet service and an application over Nostr. The NIP-47 specification describes wallet-service and client messages, while the NWC site explains the user-facing promise: apps can add Bitcoin payment functionality without taking custody of funds.
Lightning Piggy uses that promise in a constrained hardware setting. The build guides ask you to choose a wallet that supports NWC, copy the NWC link and keep the Lightning Address. They name Alby Hub, Cashu, Coinos, Primal and Zeus as popular options in the guide, but the troubleshooting page adds an important correction: Primal NWC currently does not work with Lightning Piggy because Primal uses a Spark backend that Lightning Piggy does not yet support. Use the guide's wallet list as a starting point, not as a guarantee.
The safest setup is a dedicated low-limit wallet connection. If the device only needs to receive and display, do not grant broader spending power casually. If a later version asks for `pay_invoice`, inspect why. Revoke stale connections after a workshop. If you are using a child's device, assume curious hands will scan, reboot and press things. Keep the NWC connection boring, limited and replaceable.
LNbits in practical terms
LNbits is a flexible Lightning account and tooling system. In Lightning Piggy, it can provide the backend wallet and LNURL payment link that the device displays. The Classic firmware README says the LNURLp extension should be activated, a new pay link created, fixed amount disabled and minimum and maximum payment amounts set. Those are not optional UX details; they shape what someone can send to the piggy.
LNbits has a different risk profile from NWC. You need a reachable server, a working Lightning node or wallet backend, a correct invoice/read key and a TLS setup the ESP32 can actually use. The troubleshooting page calls out a real compatibility issue: ESP32's mbedTLS does not support ECDSA certificates in the scenario described there, so a Caddy reverse proxy may need RSA certificates for an LNbits server.
For a family, LNbits can be excellent when a parent already runs a node and wants separate accounts for children. For a classroom or event, it can be fragile if the network, TLS, server hostname or LNURLp extension is wrong. Test the whole chain before people arrive: LNbits page, LNURLp pay link, QR display, payment receipt, balance refresh and reboot behavior.
The flashing flow
Classic firmware is installed through a browser-based web installer at `lightningpiggy.github.io`. The installer asks you to connect the device over a USB data cable, choose the firmware flavor, select the serial port, start installation and wait until flashing completes. It is powered by ESP Web Tools and depends on Web Serial support in the browser.
The installer documentation is unusually practical. It warns that many USB cables only provide power, that the serial port is often labeled CP210, that Google Chrome has been tested on Linux, macOS and Windows, that Linux or macOS users may need serial permissions and that ad blockers can cause JavaScript errors during flashing. It also provides a logs and console path for debugging.
For p1, the first step is the MicroPythonOS installer at `install.micropythonos.com`, followed by installing the Lightning Piggy app from the MicroPythonOS app store. That is a different update channel. Before a workshop, prepare the exact board model, browser, data cables, driver instructions and fallback time. The friendliest hardware project can become frustrating if flashing fails in front of a room.
Configuration and QR behavior
After flashing, Classic devices expose a temporary Wi-Fi configuration access point. The build guide says the device screen shows the web address and login credentials. The troubleshooting page gives the default username as `piggy` and password as `oinkoink`. Those defaults are useful for onboarding, but they are also public. Treat the configuration phase as something to supervise.
The device needs Wi-Fi details and either NWC credentials or LNbits details. The guides also provide tools for Wi-Fi QR generation, LNbits ZapRewards QR generation and NWC plus Lightning Address QR generation. This is a sensible design for a display device, because scanning a QR code is easier than typing long credentials on a small screen.
There are edge cases. The troubleshooting page says Classic expects only the hostname in one LNbits configuration field, while MicroPythonOS uses the full `https://` URL. It also notes that if both LNbits and NWC credentials are configured, the display may keep showing the old LNbits QR code rather than the Lightning Address QR. If a QR does not change, clear the unused backend credentials rather than assuming the wallet is broken.
Safety and child use
The project is designed for children, but the hardware is not a toy. The Classic and p1 build guides both warn about small parts, choking and ingestion hazards, sharp edges and use at your own risk. The Classic guide also warns that improper assembly or faulty batteries can present a fire hazard, especially around LiPo battery polarity and connector wiring.
This is the right tone for a maker project. A finished piggy bank can sit on a child's shelf, but the build process includes circuit boards, USB flashing, batteries, enclosures, soldering in some variants and device configuration. Children can learn from it; they should not be left alone with loose electronics, charging batteries or admin credentials.
If you are running a family build, separate the fun from the risk. Let children decorate the case, scan a receive QR and watch sats arrive. Let adults handle battery sourcing, firmware flashing, wallet limits, configuration passwords, server credentials and backups. The best educational version is not the one with the most autonomy; it is the one where the child can understand the money flow without being handed the blast radius.
What the child actually sees
The product experience is simple on purpose. The child sees a balance in sats, a QR code that others can scan to send Lightning payments, recent transactions and messages. That is very different from giving a child a full mobile wallet, a seed phrase, a social feed or a trading app. The device makes saving visible without making every financial control visible.
This is why Lightning Piggy is interesting beyond the novelty. A piggy bank has always been a teaching object. It turns abstract savings into a visible ritual. Lightning Piggy preserves that ritual while changing the unit from coins to sats. A grandparent can send a small payment. A parent can reward a chore. A child can see that the number changed.
The limit is that Lightning is not a savings vault by itself. The FAQ says the project chose Lightning first because it is fast, low-cost and good for small routine payments and messages. It also says on-chain Bitcoin support would be desirable for more secure long-term savings. For now, think of the device as a front pocket for learning and small sats, not the family's long-term cold storage.
Education and workshops
Lightning Piggy calls its approach STEMM: Science, Technology, Engineering, Mathematics and Money. That fifth word is important. The project is not only teaching soldering or Python. It is using a concrete object to teach monetary scarcity, saving habits, QR payments, open-source software, hardware iteration and custody tradeoffs.
The site lists education partners and appearances at Bitcoin and community events. It also has pages for educators, Bitcoin kids and community builds. That makes Lightning Piggy more like a workshop kit than a normal consumer gadget. The open-source repos let a motivated builder inspect code, modify UI assets, change cases or use the device as a starting point for other microcontroller projects.
The p1 move to MicroPythonOS strengthens the education angle. The `LightningPiggyApp` README describes a MicroPythonOS display wallet package that supports LNbits, NWC and on-chain xpub via Blockbook wallet types. It also points to docs for appearance, assets and even a hidden mini-game. That does not make the device more financially safe, but it does make it more hackable and teachable.
Nostr beyond the connection string
Nostr appears in two ways. The first is NWC itself, where Nostr relays carry wallet-client and wallet-service messages for a Lightning wallet connection. That is the direct protocol relevance. If you only remember one Nostr fact about Lightning Piggy, remember that the NWC connection is a wallet permission surface.
The second Nostr surface is community. The build guide invites people to post photos of their piggy on Nostr with the `#zapmypiggy` hashtag for inclusion on the website. The site has a ZapMyPiggy community page, and the footer links to a Primal profile. This is a natural fit: a physical Bitcoin project is more useful when builders can show cases, share fixes and get zapped for contributions.
Those two Nostr uses should not be blurred. A public hashtag post is social sharing. A NWC string is wallet access. A Primal profile is identity and community. They all use the Nostr ecosystem, but they carry different risks. Never paste a NWC connection string into a public note, screenshot or support thread.
Known rough edges
The troubleshooting page is a gift because it shows real edges instead of hiding them. Primal NWC is listed as not working currently because of the Spark backend. Coinos connection issues were fixed in firmware version 6.1.0. The MicroPythonOS app store installation issue was fixed in app version 0.0.11. Classic Wi-Fi wake behavior, blank camera screens in the companion app and display QR behavior all have documented troubleshooting paths.
Hardware setup has its own failure modes. Data cables get mistaken for charge-only cables. Serial permissions block flashing. Browser extensions interfere with the installer. Drivers may be missing on Windows or macOS. A LILYGO 2.66-inch board may need a USB-to-TTL connector. Batteries can be miswired. Web Serial is not universal across browsers.
These are normal maker-project problems, not reasons to dismiss the project. They do mean a reader should plan for support. If you are buying or building one for a child, the child should not be the person diagnosing TLS certificates, USB serial drivers or Caddy key types. The adult admin burden is part of the device.
Security boundaries
Lightning Piggy's best security property is that it does not want to custody funds. The FAQ says the device simply connects to the wallet you choose and recommends self-custody wherever possible. That is a good baseline. It means the project is not asking families to deposit money with a new company just to see a piggy-bank display.
The remaining risk is configuration. A NWC connection can still authorize actions. An LNbits invoice key can expose invoice and balance behavior. A misconfigured LNbits server can leak data or fail payments. A public Lightning Address can be spammed. A device on Wi-Fi has network metadata. Default config credentials are known. Firmware and dependencies need update discipline.
Keep balances small. Use dedicated wallets. Avoid mixing a child's teaching device with a parent's main node account. Back up the underlying wallet, not just the device. Write down which backend is configured. If a device is lost, revoke the NWC connection or rotate LNbits credentials. The piggy is a display and interaction layer; the wallet remains where security decisions happen.
Privacy boundaries
Lightning Piggy is a public-receive object by design. A QR code on the screen is meant to be scanned by friends and family. That means the receive identifier, Lightning Address or LNURL can circulate. For small pocket-money use, that may be fine. For a child, it still deserves thought: who can send messages, what names appear in comments, and where payment events are displayed?
NWC adds relay metadata. The NWC protocol does not require a normal Nostr social account, but it does use relay communication. Wallets and apps may see timing, requests and connection identifiers. LNbits adds server metadata. A self-hosted LNbits instance gives more control, but it also makes the family responsible for logs, TLS, uptime and updates.
The FAQ says Tor is not currently supported on the device and would not be trivial or performant on ESP32. That is an honest limitation. Do not present Lightning Piggy as an anonymity device. Present it as a learning and small-payments device whose privacy depends on wallet choice, network setup, public identifiers and how carefully adults handle screenshots and support logs.
How to test before real use
Start with a tiny test wallet. If using NWC, create a dedicated low-limit connection in Alby Hub, Coinos, Zeus or another wallet you have verified with Lightning Piggy's current compatibility notes. If using LNbits, use a child-specific account or wallet, activate LNURLp and keep the invoice/read key separate from unrelated admin credentials.
Then test the device lifecycle. Flash firmware. Reboot. Join the configuration Wi-Fi. Change or record configuration access. Add Wi-Fi details. Add NWC or LNbits credentials. Confirm the QR appears. Receive a tiny Lightning payment. Confirm the balance refreshes. Power-cycle. Confirm the state survives. If using battery power, test charging and heat under supervision.
Finally test the recovery plan. If the device is lost, can you revoke the connection? If the SD or board fails, can you rebuild another piggy and connect the same wallet? If the child accidentally shares a photo, does it expose a NWC secret or only a receive QR? If LNbits stops responding, do you know whether the problem is server, TLS, extension, invoice key or network? Small answers now prevent large confusion later.
What it is not
Lightning Piggy is not a full Bitcoin node, not a hardware wallet vault and not a custodial savings account. It is a display device and learning object connected to a wallet. The underlying wallet may be custodial or self-custodial. The device does not make that choice for you.
It is also not a general Nostr client. You are not choosing it to write notes, manage relays, publish long-form posts or build a social identity. Its Nostr relevance is concentrated in NWC and community sharing. That is enough to explain its place in a Nostr ecosystem map, but it should be described accurately.
It is not a toy despite its child-friendly theme. The official guides say that directly. The device can be part of a playful savings ritual, but the build includes electronics and wallet permissions. Adults need to own the operational setup.
Where it fits in the ecosystem
Lightning Piggy sits beside projects like Wesatoshis, BTClock and BoltCard NWC in the hardware edge of the NWC map. It is less about general-purpose payments than Wesatoshis, less about display-only Bitcoin data than BTClock and less about card-present NFC payments than BoltCard. Its niche is children's savings, workshops and a visible Lightning receive surface.
It also touches the operating-system line because the best LNbits setup may live on RaspiBlitz, Start9, Umbrel or another home server. That does not make Lightning Piggy an operating system. It means its reliability often depends on one. A family using LNbits should understand the node or server behind the piggy.
The project is strongest when treated as a teaching bridge. It turns NWC, LNbits, Lightning Address, LNURL, browser flashing and open-source hardware into something a child can point at. The bridge is valuable precisely because it is concrete.
The practical close
Lightning Piggy is one of the warmer ideas in the Bitcoin and Nostr-adjacent stack: a small object that lets a child see sats arrive instead of hearing adults talk abstractly about sound money. It gives parents and educators a way to make Lightning payments tangible.
The quality of the project is in the details. The official site explains custody clearly. The build guides distinguish Classic and p1. The troubleshooting page documents rough edges. The GitHub organization has active repositories. The NWC and LNbits choices are real rather than vague. That is enough to make it worth opening and testing.
Use it with the right ceiling. Keep balances small, connect a dedicated wallet, supervise the hardware, test the firmware flow, understand the backend and never confuse a friendly display with a security model. As a vault, it is the wrong object. As a hands-on way to teach sats, Lightning and wallet permissions, it is unusually concrete.
Sources worth opening
Open the official Lightning Piggy site, About page, build guides, FAQ and troubleshooting page first. Then check the GitHub organization, the MicroPythonOS app repository, the Classic firmware repository, the web installer, getAlby awesome-nwc and NIP-47. The best read is hands-on: the project is understandable only when you see how hardware, wallet backend, QR setup and NWC permissions fit together.
- Lightning Piggy official website
- Lightning Piggy About page
- Lightning Piggy Build page
- Lightning Piggy Classic build guide
- Lightning Piggy p1 build guide
- Lightning Piggy cases page
- Lightning Piggy LNbits guide
- Lightning Piggy WiFi QR tool
- Lightning Piggy LNURL QR tool
- Lightning Piggy NWC QR tool
- Lightning Piggy Market page
- Lightning Piggy Nostr handles page
- Lightning Piggy community page
- Lightning Piggy in the wild
- Lightning Piggy educators page
- Lightning Piggy Bitcoin kids page
- ZapMyPiggy community page
- Lightning Piggy credits
- Lightning Piggy FAQ
- Lightning Piggy troubleshooting
- Lightning Piggy serial monitor
- Lightning Piggy donate page
- Lightning Piggy Web Installer
- Lightning Piggy GitHub organization
- LightningPiggyApp repository
- Lightning Piggy Classic firmware repository
- Lightning Piggy web installer repository
- Lightning Piggy cases repository
- TouchColorPiggy repository
- Nostrduino repository
- Lightning Piggy Geyser project
- getAlby awesome-nwc Hardware listing
- NWC official site
- NWC documentation
- NIP-47 Nostr Wallet Connect
- NIP-01 basic Nostr protocol flow
- NIP-04 encrypted messages
- LNbits website
- LNbits documentation
- LNbits GitHub repository
- MicroPythonOS website
- MicroPythonOS installer
- ESP Web Tools
- Web Serial API documentation
- BTCPay Server
- Waveshare ESP32-S3 Touch LCD 2
- LILYGO T5 product line
- Lightning Piggy Primal profile
- Lightning Piggy X profile
- Lightning Piggy Telegram community
