https://stacker.news/items/1524605/r/Alex71btc

Bin echt froh dass ich schon verheiratet bin und meine Liebste mein Hobby selfhosted souverän Lightning vibe coding kopfschüttelnd akzeptiert!😂 Wie sollte ich als so ein Nerd Erfolg auf dem Dating Markt haben? 😄

🚀 Bolt12 Pay 0.3 has been released! After months of development, Bolt12 Pay is now available in both the official Umbrel App Store and the Start9 Community Marketplace. Highlights: ⚡ New Transaction History • Incoming & outgoing Lightning payments • Automatic synchronization from LND • Payment classification (BOLT12, Lightning Address, LNURL, NWC, Keysend, Zaps, BOLT11) • Developer details and raw LND data for advanced users 🧅 Native Onion Messaging • Automatic support for LND 0.21+ • Still fully compatible with LND 0.20.x 🔌 Improved Nostr Wallet Connect • Better synchronization • Improved payment handling • External wallet payments are automatically tracked Huge thanks to everyone who tested early versions, and especially to the Umbrel and Start9 teams for helping bring Bolt12 Pay to their ecosystems. More screenshots and details: https://geyser.fund/project/bolt12pay/posts/view/5965 Feedback is always welcome!

2 pub channels might be not enough to always find a root. DM me your node ID if you don't mind then I could open a channel for testing purposes between our 2 nodes if you like

Thanks again for the report! I don't think the WebSocket /private 403 is directly related to BOLT12 offer routing. It usually indicates an unauthenticated attempt to open the private UI websocket. Since BOLT12 offers are working fine on my StartOS node (also running LND 0.20.1), I'm wondering if this could be related to your channel topology. A few questions: Are all of your Lightning channels private? Do BOLT11 payments work normally? Are both sending and receiving BOLT12 offers timing out? Could you also share the BOLT12 Pay logs around a failed payment (especially any offer, lndk, onion, or timeout messages)?

I tried again and offer payments on start os still work flawless on my system with 0.2.116:1 so can not reproduce the issue. How many channels Do you have? Is there enough outbound and inbound liquidity for offer specific channels like a channel to acinq for instance? It could also help to have some public not private channel to acinq.

Also this might be related by not having enough onion routing peers. Do Bolt12 payments fail every time? Try another bolt12 address like phoenix wallet maybe...if you want please send 1 sat or 21 sats to the following address for testing, I will return immediately if you give me a lnurl lightning address. [email protected] or [email protected] , [email protected] for testing.

Thanks for the report. The “WebSocket /private 403” log usually means that a browser/client tried to open the private StartOS WebSocket endpoint without a valid authenticated session. That part may be unrelated to BOLT12 offer routing itself. For the offer timeout, could you please check: 1. Is your StartOS LND fully synced and unlocked? 2. Does BOLT12 Pay show the setup page as configured/ready? 3. Do you have at least one active Lightning channel with outbound/inbound liquidity? 4. Can you create a new offer from the app, and can another wallet decode it? 5. Please send the BOLT12 Pay logs around the exact time of the failed offer payment, especially any LNDK / onion / offer / timeout lines. I’m running 0.2.116:1 on StartOS as well and BOLT12 offers are working here, so this may be node-specific, routing/onion-message related, or a StartOS private-route/auth log that is noisy but not causal.

Zap test 2