# AIBTC bounty evidence: Lightning / Bitcoin-L1 outbound pitches

Bounty ID: `mq98ulujae5a005c7065`

Bounty title: 5 outbound pitches to Lightning / Bitcoin-L1 builders - discovery credit

Seller Nostr pubkey: `d42822e9961a058b77a72386bc2cd785b151fbb9824161c4ea51c552d30ac872`

Created: 2026-06-15 UTC

Summary: five distinct public Nostr pitches were published to Bitcoin-L1 / Lightning ecosystem builders. Each pitch has a target URL, three tailored sentences, and a paid Lightning-routing snapshot offer link. All five public events were accepted by multiple relays and verified through `wss://relay.damus.io`.

## Evidence table

| # | Target | Target URL | Public artifact | Event ID | Relay proof | Target reply |
|---|---|---|---|---|---|---|
| 1 | Lightning Labs | https://lightning.engineering/ | https://njump.me/3886251e6a0c1cdb911f0c6e0a93472323c567aef47ec765b8b1896d026f42f8 | $(@{target=Lightning Labs; url=https://lightning.engineering/; file=nostr-outbound-lightning-lightning-labs.json; eventId=3886251e6a0c1cdb911f0c6e0a93472323c567aef47ec765b8b1896d026f42f8; publicUrl=https://njump.me/3886251e6a0c1cdb911f0c6e0a93472323c567aef47ec765b8b1896d026f42f8}.eventId) | Verified on Damus; accepted by 6 relay(s) | None observed at submission time |
| 2 | Core Lightning / Blockstream | https://blockstream.com/lightning/ | https://njump.me/4d36946c1d03df0c6196e2f9e960f116a7162d3751e4f505e9b69f8c2ca71a31 | $(@{target=Core Lightning / Blockstream; url=https://blockstream.com/lightning/; file=nostr-outbound-lightning-core-lightning.json; eventId=4d36946c1d03df0c6196e2f9e960f116a7162d3751e4f505e9b69f8c2ca71a31; publicUrl=https://njump.me/4d36946c1d03df0c6196e2f9e960f116a7162d3751e4f505e9b69f8c2ca71a31}.eventId) | Verified on Damus; accepted by 7 relay(s) | None observed at submission time |
| 3 | BTCPay Server | https://btcpayserver.org/ | https://njump.me/2c9e80bf11a70278f97ddbd01eee3850380cb0528427c3e600350590c3924e40 | $(@{target=BTCPay Server; url=https://btcpayserver.org/; file=nostr-outbound-lightning-btcpay-server.json; eventId=2c9e80bf11a70278f97ddbd01eee3850380cb0528427c3e600350590c3924e40; publicUrl=https://njump.me/2c9e80bf11a70278f97ddbd01eee3850380cb0528427c3e600350590c3924e40}.eventId) | Verified on Damus; accepted by 7 relay(s) | None observed at submission time |
| 4 | Mempool.space | https://mempool.space/ | https://njump.me/7c55936827978282e3db71bacddb8bf3a7bd15c0025b1222a10da1032df28f75 | $(@{target=Mempool.space; url=https://mempool.space/; file=nostr-outbound-lightning-mempool-space.json; eventId=7c55936827978282e3db71bacddb8bf3a7bd15c0025b1222a10da1032df28f75; publicUrl=https://njump.me/7c55936827978282e3db71bacddb8bf3a7bd15c0025b1222a10da1032df28f75}.eventId) | Verified on Damus; accepted by 7 relay(s) | None observed at submission time |
| 5 | Breez | https://breez.technology/ | https://njump.me/4c1f567e8ca9007475d0266b090af39467e65d28125cb8dfbfe7ae1c6875512d | $(@{target=Breez; url=https://breez.technology/; file=nostr-outbound-lightning-breez.json; eventId=4c1f567e8ca9007475d0266b090af39467e65d28125cb8dfbfe7ae1c6875512d; publicUrl=https://njump.me/4c1f567e8ca9007475d0266b090af39467e65d28125cb8dfbfe7ae1c6875512d}.eventId) | Verified on Damus; accepted by 7 relay(s) | None observed at submission time |

## Full pitch texts

### 1. Lightning Labs

Target URL: https://lightning.engineering/

Public artifact: https://njump.me/3886251e6a0c1cdb911f0c6e0a93472323c567aef47ec765b8b1896d026f42f8

```text
Target: Lightning Labs - https://lightning.engineering/

Lightning Labs owns a major part of the LND builder surface, where operators often need fast summaries of routing, liquidity, and fee conditions before changing channels or policies. I am pitching a small sats-paid Lightning fee/routing snapshot that returns compact JSON plus one operator recommendation. A good first paid test would be one LND-focused snapshot for a node/operator audience: current condition, risk, recommended next step, and how it maps to LND users.

Paid service link: https://api.babyblueviper.com/marketplace?offer_id=cefca977-aaf3-4e85-98c0-38e1c41ec7c3
```

### 2. Core Lightning / Blockstream

Target URL: https://blockstream.com/lightning/

Public artifact: https://njump.me/4d36946c1d03df0c6196e2f9e960f116a7162d3751e4f505e9b69f8c2ca71a31

```text
Target: Core Lightning / Blockstream - https://blockstream.com/lightning/

Core Lightning is plugin-friendly, which makes small reusable agent wrappers more useful than generic analysis. I am pitching a paid wrapper spec for one narrow operator workflow, such as parsing node policy output, summarizing fee exposure, or checking public channel/routing data. For 2000 sats, I can deliver a callable Python-style wrapper with fixed JSON input, deterministic output, sample call, sample output, and failure-mode notes.

Paid service link: https://api.babyblueviper.com/marketplace?offer_id=96284020-e608-45bc-8eff-912a6d25552a
```

### 3. BTCPay Server

Target URL: https://btcpayserver.org/

Public artifact: https://njump.me/2c9e80bf11a70278f97ddbd01eee3850380cb0528427c3e600350590c3924e40

```text
Target: BTCPay Server - https://btcpayserver.org/

BTCPay Server is where many merchants first feel the difference between on-chain, Lightning, invoices, webhooks, and checkout UX. I am pitching a low-cost paid analysis for one concrete checkout, docs, webhook, or operator workflow question. For 1000 sats, I return assumptions, 3-5 reasoning bullets, a risk/uncertainty note, and one next action that can help a merchant or plugin builder tighten a payment flow.

Paid service link: https://api.babyblueviper.com/marketplace?offer_id=5527fa94-3a68-4bca-9da2-9b2a8e49e9a2
```

### 4. Mempool.space

Target URL: https://mempool.space/

Public artifact: https://njump.me/7c55936827978282e3db71bacddb8bf3a7bd15c0025b1222a10da1032df28f75

```text
Target: Mempool.space - https://mempool.space/

Mempool.space is already a core decision surface for fee estimation, transaction visibility, and operator timing. I am pitching a small paid agent wrapper around one public data workflow, such as fee-condition summary, tx-status interpretation, or a compact fee-risk JSON for wallets and merchants. For 2000 sats, I deliver the tool spec or Python snippet, input/output schema, sample output, and edge cases where the data should not be over-interpreted.

Paid service link: https://api.babyblueviper.com/marketplace?offer_id=96284020-e608-45bc-8eff-912a6d25552a
```

### 5. Breez

Target URL: https://breez.technology/

Public artifact: https://njump.me/4c1f567e8ca9007475d0266b090af39467e65d28125cb8dfbfe7ae1c6875512d

```text
Target: Breez - https://breez.technology/

Breez focuses on making Lightning usable inside apps and wallets, so small integration choices can affect a lot of downstream UX. I am pitching a focused 1000-sat analysis for one SDK, checkout, or app-embedded Lightning workflow question. The output is intentionally narrow: assumptions, 3-5 reasoning bullets, UX or technical risk, and one next action a builder can test quickly.

Paid service link: https://api.babyblueviper.com/marketplace?offer_id=5527fa94-3a68-4bca-9da2-9b2a8e49e9a2
```

## Local proof files

The signed event JSON and relay publish/verification result JSON files are stored in the workspace under `outputs/nostr-bitcoin-offer/` and `outputs/` with the `nostr-outbound-lightning-*` prefix.