supratic

bitcoinplusplus

AGORA

lightning

Are you currently at the @btcplusplus conference in Nairobi?

A live offer is available on our trading platform from a fellow attendee who is looking to exchange Bitcoin for cash at the conference using the Lightning Network.

This could be a convenient opportunity to connect and trade directly with another participant. ⚡️

Take a look at the offer here: http://hodlhodl.com/offers/CGeLmWOINyZXS0En

[OFFER] P2P Bitcoin trade IRL @ bitcoin++ Nairobi

![Uploading Titelbild_Prag.png…]()

[BTC Prague](https://btcprague.com/) is Europe’s largest Bitcoin conference, and this year it held a special significance for us. @OPAGO_PAY was selected as the official Lightning Service Provider for BTC Prague 2026, a role that gave us the perfect stage to demonstrate what seamless digital asset payments at the point of sale truly look like.

### Thousands of Visitors, Thousands of Transactions

Over the course of the event, thousands of attendees used Bitcoin Lightning to pay for food, beverages, and merchandise, all processed seamlessly through our Digital Asset Payment Platform. Low fees, high security, and a payment experience that just works: for merchants and customers alike. That is exactly the standard we hold ourselves to.

![](https://m.stacker.news/145106)

opago at BTC Prague 2026 as Official Lightning Service Provider

lonniev/tollbooth: DPYC API service monetization via Lightning micropayments

Those APIs have been used as samples, it should apply to any API.

# tollbooth-sample

Educational Weather Stats MCP Service — the reference implementation for building Tollbooth DPYC monetized API services with Bitcoin Lightning micropayments.

This service wraps the free [Open-Meteo](https://open-meteo.com/) weather API and gates paid tool calls through the [Tollbooth](https://github.com/lonniev/tollbooth-dpyc) credit system using the `@runtime.paid_tool()` decorator. Domain tools contain only business logic; debit, rollback, balance warnings, and constraint evaluation are handled automatically by the `OperatorRuntime`. Standard DPYC tools (balance, purchase, Secure Courier, Oracle, pricing, constraints) are delegated to the wheel via `register_standard_tools()`.

**Version:** 0.2.0

## The DPYC Economy

**DPYC** stands for **Don't Pester Your Customer**. It's a philosophy and protocol for API monetization that eliminates mid-session payment popups, subscription nag screens, and KYC friction.

### How it works

1. **Pre-funded balances** — Users buy credits via Bitcoin Lightning *before* using tools. Each tool call silently debits from their balance. No interruptions, no "please upgrade" modals.

2. **Nostr keypair identity** — Users are identified by a Nostr public key (`npub`), not an email or password. One keypair per role, managed by the user. No account creation forms.

3. **UUID-keyed tool identity** — Every tool is a `ToolIdentity` object with a deterministic UUID v5 derived from a capability name. Pricing hints come from the `category` field:

   | Category | Pricing hint | Use case               |
   | -------- | ------------ | ---------------------- |
   | `free`   | 0 sats       | Balance checks, status |
   | `read`   | 1 sat        | Simple lookups         |
   | `write`  | 5 sats       | Multi-step operations  |
   | `heavy`  | 10 sats      | Expensive queries      |

   Actual prices are set dynamically by the operator's pricing model in Neon.

4. **Rollback on failure** — If the downstream API fails after a debit, credits are automatically rolled back via a compensating tranche. The user never pays for a failed call.

5. **Honor Chain** — The DPYC ecosystem is a voluntary community:
   * **Citizens** — Users who consume API services
   * **Operators** — Developers who run MCP services (like this one)
   * **Authorities** — Certify operators and collect a small tax on purchases
   * **First Curator** — The root of the chain, mints the initial cert-sat supply

website: https://tollbooth-dpyc.com

# Kurrent Protocol

Kurrent is a research implementation of a Kaspa-native latest-state channel protocol. It explores whether Kaspa covenant and transaction-introspection capabilities, as represented by the KIP-10/KIP-17/KIP-20 direction, can support Eltoo-style settlement semantics: participants negotiate updates locally, and the chain is used to enforce the latest accepted state when settlement or dispute is required.

This repository is deliberately evidence-driven. A passing local-devnet run must produce real Kaspa and Lightning Network artefacts: raw transactions, witnesses, txids, preimages, logs, typed model validation, and verifier reports.

Current status:

* Local devnet gate: `passed` in the prepared local environment.
* Production-readiness gate: `failed/blocked` until the production evidence pack is complete.
* Mainnet readiness: not claimed.
* Native Lightning route-hop integration: not claimed.

## Why Kurrent Exists

The [Eltoo paper](https://blockstream.com/eltoo.pdf), by Christian Decker, Rusty Russell, and Olaoluwa Osuntokun, frames a Layer 2 channel as a sequence of locally negotiated contract states. The key idea is that old states must become unenforceable after they have been replaced by newer states. Eltoo does this with enforceable state numbers and floating transactions, using `SIGHASH_NOINPUT` in its Bitcoin construction.

Kurrent borrows the latest-state principle, not the exact Bitcoin mechanism. Instead of implementing Bitcoin eltoo byte-for-byte, it investigates how a similar non-punitive settlement model can be expressed against Kaspa covenant and transaction-introspection capabilities.

In plain terms:

* participants update channel state off-chain;
* each new accepted state must advance the state number exactly once;
* stale or non-continuing spends must be rejected;
* the latest state can settle on Kaspa simnet;
* all claims are backed by replayable local evidence.

a19q3/Kurrent: the Kaspa-native state channel protocol

bitcoin_beginners

Organization Spotlight: India’s Bitcoin Bharat

hasherstacker

link changed https://www.fedi.xyz/blog/organization-spotlight-india-bitcoin-bharat

## What's Changed

* refund failed swaps by [@boufni95](https://github.com/boufni95) in [#591](https://github.com/shocknet/wallet2/pull/591)
* bump fee by [@boufni95](https://github.com/boufni95) in [#593](https://github.com/shocknet/wallet2/pull/593)
* fix not amt err by [@boufni95](https://github.com/boufni95) in [#596](https://github.com/shocknet/wallet2/pull/596)
* refund swap info by [@boufni95](https://github.com/boufni95) in [#594](https://github.com/shocknet/wallet2/pull/594)
* fix identity profile metadata per row by [@DSanich](https://github.com/DSanich) in [#602](https://github.com/shocknet/wallet2/pull/602)
* fix fetchMetrics spam calls by [@boufni95](https://github.com/boufni95) in [#604](https://github.com/shocknet/wallet2/pull/604)
* Fix Metrics dashboard button label contrast by [@shocknet-justin](https://github.com/shocknet-justin) in [#607](https://github.com/shocknet/wallet2/pull/607)
* feat(invitations): add QR codes and one-time invite UI by [@DSanich](https://github.com/DSanich) in [#606](https://github.com/shocknet/wallet2/pull/606)
* Fix channels UI avatars and add peer/channel buttons by [@shocknet-justin](https://github.com/shocknet-justin) in [#608](https://github.com/shocknet/wallet2/pull/608)
* fix/nip07 by [@shocknet-justin](https://github.com/shocknet-justin) in [#613](https://github.com/shocknet/wallet2/pull/613)
* Deprecation aware shockwallet by [@snake-eaterr](https://github.com/snake-eaterr) in [#612](https://github.com/shocknet/wallet2/pull/612)
* update clink / noffer by [@shocknet-justin](https://github.com/shocknet-justin) in [#615](https://github.com/shocknet/wallet2/pull/615)
* Fix noffer clipboard confirm by deferring parse to Send page. by [@shocknet-justin](https://github.com/shocknet-justin) in [#616](https://github.com/shocknet/wallet2/pull/616)

**Full Changelog**: [v0.0.27-beta...v0.0.28-beta](https://github.com/shocknet/wallet2/compare/v0.0.27-beta...v0.0.28-beta)

ShockWallet release v0.0.28-beta

![](https://m.stacker.news/144128)

[source](https://x.com/morphlin_com/status/2064010874285621646#m)

@paoloardoino shilling Bitcoin Lightning for AI payments

![## Buy and Spend Bitcoin Instantly. With Tapnob, moving your money is quick and stress-free. Convert or spend Bitcoin and supported digital assets into local currency with fast, secure transfers to bank accounts and mobile wallets, and handle daily payments without delays.](https://m.stacker.news/143857)



This company is offering an good service in Nigeria. If you are over there you can get your own Lightning address and spend Bitcoin locally.

It's a centralized service, buy hey, people need to start somewhere. Perhaps a good service to pay bills and other stuff,

Tapnob: Convert Naira to Bitcoin Instantly

Straight of Hormuz now accept Bitcoin (mainnet & Lightning) as payment method

Are you enjoining the show? grab some 🍿when US troops invasion?

The point I wanted to make is that if they are accepting it, means there is people willing to pay with it.

![putting workplace praise on a bitcoin standard. send real value, in real time, all within slack.](https://m.stacker.news/143852)

a slack-native bitcoin tipping app. 

run /zap, pick a teammate, set an amount, add a personal message and send your shoutout publicly or in private. as easy as it sounds.

Non-custodial, peer-to-peer, settled over lightning.

it's workplace praise on a bitcoin standard!

But what's under the hood?

zaptipr — send bitcoin on slack with /zap

![](https://m.stacker.news/143848)

more details in the FAQs  

![](https://m.stacker.news/143849)

Vodafone IoT ePOS infrastructure for merchants using Bitcoin Lightning

bitdevs

![](https://m.stacker.news/143528)


`Hôtel Emeraude · Bujumbura, Burundi · June 5–6, 2026`

Two days of hacking, three hands-on workshops, 30 developers. Let's build peer-to-peer Bitcoin exchanges — no intermediaries — powered by Vexl & the Lightning Network.

Bitcoin P2P Hackathons by the Free Tech Institute

nostr

![](https://m.stacker.news/143407)

And here the winner for the Hack4Freedom, a women-only initiative powered by [EVENTO*](https://evento.so/) and sponsored by [**Btrust**](https://btrust.tech/) and [**Vinteum**](https://vinteum.org/).

![](https://m.stacker.news/143405)

Zappr is a self-custodial Bitcoin social + payments hub that unifies your Nostr feed, a Lightning wallet, and an AI agent on a single screen — usable in any language. Instead of juggling a separate social app, wallet app, and a wall of English-only jargon, you read your feed, zap posts, check your balance, and send payments by simply talking to an agent in English, Nigerian Pidgin, Yoruba, Hausa, Swahili, and more.

A beginner can tap their fingerprint and get a working Lightning wallet plus a Nostr identity in one step — no seed phrase to copy, no keys to lose. Users can read their feed, zap posts, check their balance, send payments, and ask questions in the language they actually think in: English, Pidgin, Yoruba, Hausa, Swahili, and more.

***

## Problem

Getting onto Bitcoin and Nostr in the Global South means clearing several barriers at once:

* **Fragmented** — your social identity (Nostr) and your money (Lightning) live in separate apps that don't talk to each other.
* **English-only** — wallets and clients assume English fluency, leaving out most first-language Pidgin, Yoruba, Hausa, and Swahili speakers.
* **Jargon wall** — newcomers face seed phrases, nsec/npub, NWC, and invoices with no plain-language guide.
* **False choice** — users are pushed to either give up custody for ease of use, or keep custody and wrestle with seed-phrase backups.

The result: tools built *for* people in Nigeria and the broader Global South are often unusable *by* them.

***

## Solution

zappr collapses social, payments, and help into one surface:

* **Read** your Nostr feed in real time.
* **Zap** posts and send Lightning payments inline.
* **Ask** an AI agent — in your own language — to check your balance, zap a post, send sats, or explain what a "zap" even is.

Onboarding is seedless: a single WebAuthn passkey (Face ID / fingerprint) deterministically derives both a Nostr identity and a Breez Liquid Lightning wallet, so a first-time user is live in one tap. Power users keep their existing setup via NIP-07 extension or direct nsec + NWC. Keys never leave the browser — the server only ever proxies AI calls.

Payments stay accessible at the edges too: the agent can cash sats out to a Nigerian bank account in NGN via a MavaPay offramp (currently on staging).

***

## Team

* **Abdullahi Ummu Salmat** ([@Salmatcre8](https://github.com/Salmatcre8)): `Product Manager & Backend Developer`
* **Ibrahim Ashiah Adejoke**: `Product Designer`
* **Adegboye Oluwadarasimi Busayomi**: `Frontend Developer`

***

## Repository & Links

* **Source:** [https://github.com/Salmatcre8/zappr](https://github.com/Salmatcre8/zappr)
* **Demo:** https://zappr-indol.vercel.app
* **License:** MIT

Zappr: Nostr, bitcoin lightning payments & AI assistant into a multilingual app

![](https://m.stacker.news/143192)


# ZapCart

### Hack4Freedom Lagos 2026

***

## Overview

ZapCart is a simple, mobile-first point-of-sale (POS) system built for small businesses and everyday traders in Nigeria.

It helps merchants accept instant Bitcoin Lightning payments, track sales, and manage inventory in a way that feels as simple as writing in a notebook, but faster, more accurate, and less stressful.

ZapCart was born from a real problem we experienced firsthand through our mother’s local store.

Like many small traders in Nigeria, she relied on memory, paper records, and mental calculations to run her business. Over time, inaccurate bookkeeping, forgotten transactions, and calculation mistakes constantly pushed the business into confusion and debt.

Some customers claimed they had paid when no record existed. Some sales were never written down during busy periods. End-of-day calculations were stressful and often inaccurate. Inventory disappeared without clear tracking. Despite working hard every day, there was never full visibility into whether the business was truly making profit.

We realized this was not just our mother’s problem.

It is the reality for millions of small businesses across Nigeria.

ZapCart exists to solve that problem with simplicity first.

If a trader can use WhatsApp, they can use ZapCart.

***

## Problem

Nigeria’s informal economy is one of the largest in Africa, contributing significantly to employment and daily commerce.

According to the International Labour Organization (ILO), over 80% of employment in Nigeria exists within the informal sector. Millions of these businesses operate without proper digital tools for sales tracking, bookkeeping, or inventory management.

Most small traders still rely on:

* Paper notebooks
* Mental calculations
* Verbal debt tracking
* Manual inventory counting

This creates serious daily problems:

* Missing or forgotten transactions
* Frequent calculation mistakes
* Poor debt tracking
* Lost sales records
* Inventory inconsistencies
* Stressful end-of-day reconciliation
* Limited understanding of actual profit or loss

Existing POS and accounting solutions are often:

* Too complex for everyday traders
* Designed for formal businesses
* Expensive to maintain
* Dependent on traditional banking systems
* Difficult for low-tech users to learn

For many traders, technology today feels like additional stress instead of assistance.

Yet these same traders are the backbone of local commerce in Nigeria.

***

## Solution

ZapCart transforms the familiar market-selling experience into a simple digital workflow designed specifically for everyday Nigerian merchants.

Instead of replacing how traders work, ZapCart improves the system they already understand.

With ZapCart, merchants can:

* Add products quickly during checkout
* Receive instant payments using Bitcoin Lightning
* Generate simple QR-based payment requests
* Automatically save every transaction
* View daily sales totals instantly
* Track inventory without spreadsheets or accounting knowledge

The product is intentionally designed around one principle:

> “If your mother cannot use it without explanation, it is not ready.”

To achieve this, ZapCart focuses heavily on:

* Large touch-friendly interfaces
* Minimal checkout steps
* Extremely simple navigation
* Clear visual feedback
* Mobile-first usability
* Fast interactions for busy market environments
* Low-friction onboarding

ZapCart is not trying to turn traders into accountants.

It is helping them avoid preventable losses, confusion, and debt caused by poor record-keeping.

***

## Technology Stack

* React (Vite)
* TypeScript
* Tailwind CSS
* Zustand
* Node.js
* Breez SDK (Lightning Payments)

***

## Team

* Enyi Gloria - Fullstack Developer
* Enyi Hannah - Product Analyst
* Achusim Ebube - Product Manager

***

## Repository & Links

* Live Demo: https://zap-cart.vercel.app/
* GitHub Repository: https://github.com/gloria2807/ZapCart
* Demo Video: https://vimeo.com/1194957098?share=copy&fl=sv&fe=ci

ZapCart: mobile-first POS system built for small businesses and everyday traders

![](https://m.stacker.news/143190)


# KoboSats

Bitcoin Lightning payments for Nigeria's informal market traders — via smartphone app or USSD on any basic phone.

## Overview

KoboSats is a self-custody Bitcoin Lightning payment tool built for Nigeria's 40 million informal market traders — food vendors, fabric sellers, phone repair shops, and artisans. Traders can receive instant payments in naira, track customer debts with tamper-proof records, and access everything through a web app or by dialling a USSD code from any basic phone. No BVN. No bank account. No smartphone required. Bitcoin runs in the background; traders see naira.

## Problem

Nigeria's informal traders deal with three daily problems: Payments are broken. Bank transfers fail or take days. POS machines charge fees and go offline. Cash gets stolen or miscounted. A trader selling ₦50,000 on credit may never see that money. No infrastructure for debt tracking. Most traders use exercise books or memory to track what customers owe. Notebooks get lost, memories fail, and customers dispute debts with nothing to prove otherwise. Financial tools leave out the people who need them most. Every Nigerian fintech product requires a BVN, bank account, and smartphone — yet less than half of Nigerians own a smartphone. Millions of traders have been locked out of digital finance entirely.

## Solution

KoboSats gives every trader a self-custody Bitcoin Lightning wallet with two ways to access it: For smartphone users — a React web app: Enter an amount in naira, get a Lightning invoice QR code, customer pays in under 3 seconds. Includes a live balance dashboard, debt tracker with SMS reminders, transaction history with permanent receipt links, and support for English, Yoruba, Hausa, and Igbo. For feature phone users — USSD via Africa's Talking: Dial *384*7287# from any phone, on any network — no internet or app needed. Full menu in all four languages. Receive payments, check balance, and log debts from a ₦5,000 Nokia or a ₦300,000 iPhone. For both — permanent records on Nostr: Every payment and debt is signed with the trader's private key and published to decentralised relays worldwide. Tamper-proof and permanent — no company can alter or delete it.

## Technology Stack
React, Tailwind CSS, Python, FastAPI, SQLite/PostgreSQL, Breez Spark SDK, CoinGecko API, Africa's Talking, Nostr Protocol, BIP340 Schnorr, Render, Netlify.

## Team
- **Olowookere Busayomi** - `Backend developer` 
- **Timilehin Olajolo** - `Frontend Developer` 
- **Rita Okam** - `Backend Developer`

## Repository & Links

- Frontend: https://kobosat.netlify.app
- Repo: https://github.com/Team-Lumina/KoboSat-frontend.git

- Backend: https://kobosat-backend.onrender.com/docs
- Repo: https://github.com/Team-Lumina/KoboSat-Backend.git

KoboSats: Bitcoin Lightning payments for Nigeria's informal market traders

> A community-powered platform uniting real-time local discovery with integrated currency payments. Find trusted places, transact instantly, and get rewarded in Bitcoin sats for helping the network stay accurate.

![](https://m.stacker.news/143123)

![](https://m.stacker.news/143116)

![](https://m.stacker.news/143117)


## Designed for Discovery & Trust. Engineered for Local Economies

Discover trusted vendors, pay seamlessly, and earn real incentives in a single, community-driven ecosystem.

### Real-time discovery

See exactly what's around you instantly. Nearby services are dynamically displayed on a fast, responsive map built for high accuracy. Flexible regional configurations built over lightweight transaction rails, keeping things responsive as network scale grows.

### Built-in wallet, Pay in Local Currency

Integrated cashouts allow users to pay nearby businesses in their local currency without leaving the app. Fast and secure. Convert earnings and transact seamlessly in your local currency. Fast checkout with zero handoffs or redirect interfaces.

### Verify & contribute

Explore services around you with solid community verification, keeping directory details fresh and accurate so you save time. Keep the community map secure. Add new local storefronts, update operations, and verify reviews in real time to build local trust.

### Earn rewards

Bitcoin sats rewards align user incentives with absolute database health. Quality participation is naturally rewarded.. Your map accuracy matters. Earn Bitcoin micropayments (sats) as real, redeemable value for maintaining trust in the directory.

***

It was Randa before, recently went for a rebrand and some upgrades. rewards, comes probably from fees paid by businesses. Did not find any business in the [*OpenStreetMap*](https://www.openstreetmap.org/). Perhaps too early? +1 point for using open source maps.

I was initially unable to define what kind of build in wallet it offers, then after layers of interactions...

![](https://m.stacker.news/143122)

![](https://m.stacker.news/143119)

![](https://m.stacker.news/143120)

![](https://m.stacker.news/143121)


Requires email registration. Another warning that just screams "USE AT YOUR OWN RISK"...

Or just avoid it!

Kaze - Discover Local Merchants & Services. Pay Bitcoin Locally, Earn Sats

This PR wires neutrino's `chainimport` feature into lnd, enabling fast initial sync by importing pre-built block and filter headers from local files or HTTP URLs before falling back to P2P sync for the remainder of the chain. On mainnet, this can reduce initial sync from hours to minutes by downloading headers from a trusted source like [block-dn.org](https://block-dn.org/) instead of fetching them one-by-one from peers.

Two new config options are added under the `[neutrino]` section: `neutrino.blockheaderssource` and `neutrino.filterheaderssource`. Both accept either a local file path or an HTTP(S) URL. When configured, neutrino imports headers from these sources on startup, validates proof-of-work, and then continues syncing any remaining blocks via its normal P2P protocol. Both sources must be specified together or not at all.

The neutrino dependency is updated to include the `chainimport` package (PRs [#317](https://github.com/lightningnetwork/lnd/pull/317), [#320](https://github.com/lightningnetwork/lnd/pull/320), [#324](https://github.com/lightningnetwork/lnd/issues/324)) as well as a bug fix for the block manager's internal state after import ([lightninglabs/neutrino#335](https://github.com/lightninglabs/neutrino/pull/335)). Without this fix, the block manager would retain stale genesis-based locators after import and fail to sync additional blocks via P2P. The `Start()` method signature change to accept `context.Context` is propagated to all call sites.

An integration test exercises the full end-to-end flow: mining blocks, syncing a reference node to generate header files, copying those files with import metadata, starting a fresh node with the import config, and verifying it syncs to the chain tip and can continue syncing additional blocks mined after the import snapshot.

LND add neutrino: add fast initial sync via header import by Roasbeef

This release has been named by [@enaples](https://github.com/enaples)

### Release Candidate 2 for cln v26.06

This RC builds upon [RC1](https://github.com/ElementsProject/lightning/blob/v26.06rc1/CHANGELOG.md), with these changes:

* Removed fields no longer present in documentation / GRPC interfaces.
* Experimental payment proof implementation updated to latest draft
* gossipd made more robust against channel_update spamming.

See the [changelog](https://github.com/ElementsProject/lightning/blob/v26.06rc2/CHANGELOG.md) for full details

##

An enormous thanks to the core-Core Lightning team:
@rustyrussell, @ShahanaFarooqui, @sangbida, @cdecker, @nepet, @Lagrang3, @daywalker90, @nGoline and @niftynei And of course, our invaluable open-source community!

And of course, our invaluable open-source community!