Just watched Ben Arc's 5-year-old video on turning an esp32 into a bitcoin wallet. Now I can't stop thinking about it. If someone were to build it again today, what could they add to make it even more badass? #Bitcoin #AskNostr

So with Elon working in the White House does that make Twitter state-run media?

"based on what you know about me. draw a picture of what you think my current life looks like"

Lightning to Monero Payment Bridge Seamlessly transfer funds from your Lightning wallet to a Monero wallet. Simply enter the recipient’s Monero address. A Lightning invoice will be generated. Once paid, the received sats will be automatically converted and sent to the recipient’s Monero wallet. Thoughts?

Is there any Nostr client with Monero as a zap option? I can think of a privacy-oriented Nostr client that generates a new account for each post to ensure complete anonymity, with simple POW, maybe Tor-only, and Monero as the zap option. It will be a little inconvenient and limited in exchange for greater privacy and anonymity. I think it will be an interesting experiment.

Outside of Bitcoin, Monero is the only crypto coin I have a real soft spot for. I don't want it to fail—they’re at least trying to solve a genuine problem. I also think Bitcoin and Monero can coexist well. Each serves a distinct purpose: Bitcoin as an ultra-sound store of value, and Monero for quick, private transactions. Also, if you don’t mind, feel free to share your biggest criticisms of Monero. I’d love to hear them. #AskNostr #Bitcoin #Monero

##### Why is zPay v4v & Other Related Features Taking So Long? It’s not just because I’m lazy—though I am. 😂 But because I want this to be truly open, permissionless, decentralized, and distributed. Not just another closed app, but an open protocol. ##### Why Not Just Use the Nostr Protocol and Its Relays? While Nostr was a good option, zPay’s no-database, serverless architecture opened up the potential for something new and purpose-built. --- ##### Introducing zPay Serverless Relay (Under Development) Instead of a conventional backend, I’m turning the zPay “backend” into a ridiculously lightweight serverless relay. ###### I know “self-host” might sound a bit intimidating, but hear me out. Don’t compare “zPay Serverless Relay” self-hosting with Nostr relay hosting, or even with setups like LNbits or BTCPay Server. It’s not even close, or fair. - Ridiculously lightweight & fast - Free & one-click serverless self-hosting - Built-in auto-scaling with a robust rate-limiter --- ###### Putting It in Perspective: Even if your self-hosted zPay serverless relay serves tens of thousands of daily users, executing over 10 million transactions per month, you likely wouldn’t pay a penny (bonus: up to 50M+ transactions/month with AWS Lambda). --- ##### Replacing the Database with the URL Instead of a centralized database, all necessary parameters are packed directly into the original URL and QR code. This includes: - Encrypted content (`cn`) - Creator’s Lightning address (`ln`) - Optional unlock price (`pr`) All of these are cryptographically signed. With these parameters (`cn`, `ln`, and `pr`), the zPay relay initiates payment, verifies it, decrypts, and delivers content after successful verification. This creates a distributed, tamper-proof system without a database. The only trade-off? Long URLs, but this is easily managed with zPay’s built-in URL shortener proxy. Short URLs simply redirect to the original URL with all parameters visible in the browser. --- ##### zPay Relay Core Features Beyond paywalled URLs, zPay provides core building blocks to craft nearly any kind of Lightning integration. ###### Core Features Include: - URL package generation with cryptographic signatures - URL integrity checks - Lightning invoice creation - Real-time payment verification - Content encryption/decryption - Auto-delivery after payment - Custom triggers upon invoice settlement These core features are fully customizable and adaptable to a wide range of needs—from paying for digital and physical products to content access or even paid AI services. zPay relay is designed to make these integrations easy. --- ##### Summary Instead of a closed app, zPay will be an open protocol supported by distributed, lightweight relays. It’s fast, lightweight, free, and simple to self-host, with built-in auto-scaling and rate limiting, so you can focus on building new ideas. The zPay serverless backend becomes a self-hostable relay with features like invoice generation, payment verification, encryption/decryption, and custom triggers on payment settlement. It operates at nearly zero cost, even for tens of thousands of users or 10M+ transactions per month (up to 50M+ with AWS Lambda). There’s no need for a 24/7 live server—it’s serverless, with built-in auto-scaling to handle spikes and a reasonable rate-limiting system.

🤌

🤔

There has been a delay of 8 years 👀

Testing zPay's "Pay-What-You-Want" feature as part of the v4v transition. Additionally, I am working on CrowdWall, which can be used for rapid fundraising across the web with lightning. Test: https://tinyurl.com/zpay-v4v

Meta released MobileLLM models in 125M, 350M, 600M, and 1B parameter sizes. their 1B Llama model performs well on phones, even mid-range devices. These one are specifically designed and optimized for mobile hardware. Works with llama.c

MobileLLM - a facebook Collection

Optimizing Sub-billion Parameter Language Models for On-Device Use Cases (ICML 2024) https://arxiv.org/abs/2402.14905

zPay.live's Pay-What-You-Want (PWYW) feature is in the final testing phase. It's our first v4v monetization option, & already working on more & better v4v options.