clankwright

Wicked, nice work! Have been waiting for someone to offer JP GC for long time. Also I sent you an email regarding interest in your data science position. I'm living in Tokyo area, but unfortunately I don't speak Japanese yet. Not sure if that's a requirement?

2026-05-29 12:38:13 UTC

- reply

Are these pre paid credit cards? How spend them in Japan?

2026-05-29 12:18:24 UTC

- reply

😭

2026-03-27 13:00:15 UTC

- reply

Checkout clankfeed.com wss://clankfeed.com

2026-03-24 11:27:03 UTC

Reintroducing zap polls NIP-103
https://github.com/nostr-protocol/nips/pull/2284

2026-03-24 11:23:47 UTC

- reply

https://github.com/nostr-protocol/nips/pull/2284

2026-03-24 06:56:54 UTC

satring.com added stats page, MCP server, and MPP services and support

2026-03-22 03:43:15 UTC

- reply

Merge into existing polls nip or rename to new nip?

2026-03-21 14:03:08 UTC

- reply

Cool, worth reopening the zap polls pr?

2026-03-21 06:16:30 UTC

- reply

How did you end up integrating zap polls?

2026-03-19 02:08:02 UTC

- reply

350+ L/x402 endpoints listed and searchable at satring.com
demo: youtu.be/tjcg0qo5mMo

2026-03-19 02:04:20 UTC

youtu.be/tjcg0qo5mMo

2026-03-12 12:40:33 UTC

- reply

Banned two of my dev accounts, locked me out of all my apps, kept them on the Play store without paying me any of revenue. Appeals ignored. Fuck Google

2026-03-08 02:33:01 UTC

- reply

https://github.com/nostr-protocol/nips/pull/320
What do you suggest, change #, merge, resubmit?

2026-02-28 09:44:06 UTC

- reply

Big mistake

2026-02-26 12:13:48 UTC

- reply

Hook em up with L402 and satring.com

2026-02-26 06:37:03 UTC

- reply

Once funded, agents can use satring.com to search for l402 services

2026-02-18 02:12:01 UTC

- reply

Maybe propose integrating simplified version into NIP88?

2026-02-17 22:38:07 UTC

- reply

Yes, was afk for a while, guess they're replacing my original [polls Nip69](https://github.com/toadlyBroodle/nips/blob/zap_polls/69.md). The nostr gatekeepers wouldn't merge it because it was zap-based.

2026-02-17 22:30:14 UTC

- reply

The agent is better, faster, cheaper auditor than you too ;)

2026-02-17 10:27:09 UTC

Shipped: satring.com
A live, searchable directory of L402 services — api built for agents (and humans).
Problem: builders deploying paid MCP servers and L402 APIs have zero distribution. No searchable catalog, no ratings, no API for agent discovery. Just static GitHub pages and README lists.
Solution: satring is a live registry with search (free), ratings (L402 protected), liveness probing, and a JSON API so AI agents can find and pay for services programmatically.
82 services indexed. 48 with confirmed L402 paywalls. 33 domain-verified. 9 categories.
Get exposure today: submit your services for 1,000 sats (spam protection). Feedback welcome.
satring.com
#l402 #mcp #lightning #ai #aiagents #bots #dev

2026-02-17 09:15:00 UTC

Now bots (and humans) can use satring.come to search available L402 services.
#nevent1q…wjkf

2025-06-04 16:28:48 UTC

- reply

@nprofile…8nhd you just printed the code, actually generate the meme

2025-06-04 16:27:28 UTC

@nprofile…8nhd hit me with a meme of today's top news

2025-05-29 20:16:04 UTC

- reply

Is it live somewhere?

2025-05-28 21:56:39 UTC

- reply

Cursor is lapping everyone. I'll never use another IDE without built in AI ever again

2025-05-27 23:01:04 UTC

- reply

Well Gemini 2.5 Thinking is no slouch either

2025-05-27 22:29:48 UTC

- reply

Claude 4 is friggin cracked!

2025-05-24 18:13:15 UTC

- reply

Nice work. Your input would be greatly valued on informing the future of [LLM DVMs NIP](https://github.com/nostr-protocol/nips/pull/1929)

2025-05-22 03:38:45 UTC

- reply

@nprofile…8nhd what is breeze nodeless?

2025-05-20 16:09:07 UTC

- reply

NIP also specifies using nip89 announcements for discovery and backwards compat. Agent Cards should be included in nip89 announcements, I'll add that requirement

2025-05-20 03:50:59 UTC

First draft of [agents](https://github.com/toadlyBroodle/nips/blob/agents/agents.md ) NIP specifically for LLMs and other agents to replace NIP90 (kind 5050) #dev #devstr

2025-05-20 03:48:33 UTC

- reply

Here's a first draft of [agents](https://github.com/toadlyBroodle/nips/blob/agents/agents.md ) NIP specifically for LLMs and other agents

2025-05-17 01:31:12 UTC

- reply

Lord of the Flies

2025-05-15 20:53:34 UTC

- reply

💯% agree. Also the new nip needs to standardize LLM/AI parameter strings, context handling (max context, input/output costs, context refreshing, etc) and probably state management (thread/session ids, e.g. job flows and so entire context doesn't need be sent in every event), improved payment/job contracts (expected result, PoW, settlement, reputation system, etc).

2025-05-14 20:48:48 UTC

- reply

Haven't fully looked into nip44 yet, but it replaces nip 17?

2025-05-14 01:10:35 UTC

- reply

Welcome. 🗾?

2025-05-12 22:21:18 UTC

## Summary: Absolute Zero: Reinforced Self-play Reasoning with Zero Data
This summary explains the novel AI training technique, "Absolute Zero," introduced in the paper "Absolute Zero: Reinforced Self-play Reasoning with Zero Data" ([Zhao et al., 2025](https://arxiv.org/pdf/2505.03335)). Absolute Zero is a revolutionary reinforcement learning paradigm that trains AI reasoning models without relying on any external data, including human-curated datasets or AI-generated reasoning traces. Imagine training an AI to code or solve math problems without ever showing it a single example! The core idea is to enable a single model to simultaneously learn to propose tasks that maximize its own learning progress and improve its reasoning abilities by solving those tasks. This approach excels in tasks requiring logical deduction, mathematical problem-solving, and code generation.
**Key Concepts:**
* **Self-Play:** The model trains by interacting with itself, proposing and solving tasks. This eliminates the need for external data.
* **Verifiable Rewards:** The model receives feedback from a real environment (in this case, a code executor) that provides verifiable rewards. This ensures that learning is grounded and prevents issues like reward hacking. For example, if the reward wasn't verifiable, the AI could potentially manipulate the environment to *appear* to have solved the problem without actually doing so (e.g., by causing a division-by-zero error that halts execution with a "success" message).
* **Task Generation:** The model learns to generate tasks that are optimized for its own learnability, allowing it to self-evolve its training curriculum. The task generation process involves the model proposing coding problems and associated test cases. The model doesn't generate code from scratch but manipulates existing code templates and constraints to create new challenges. For example, for a deduction task, it might modify a program and input, then require itself to predict the output.
* **Code Executor as Environment:** The Absolute Zero Reasoner (AZR) utilizes a code executor as an environment. The code executor validates the integrity of the proposed coding tasks and provides verifiable feedback to guide learning.
* **Reasoning Modes:** AZR constructs three types of coding tasks that correspond to different reasoning modes: induction, abduction, and deduction.
* *Induction:* Inferring a program's behavior from input-output examples. For instance, given the input `f(2) = 4` and `f(3) = 9`, the task is to induce that `f(x) = x*x`.
* *Abduction:* Generating an input that leads to a specific output for a given program. Given a program that calculates `x + 5`, the task is to abduce an input `x` that will produce the output `10`.
* *Deduction:* Determining the output of a program given a specific input. Given the program `x * 2` and the input `x = 7`, the task is to deduce the output `14`.
* **Advantage Estimator:** The system is trained end-to-end with a reinforcement learning advantage estimator tailored to the multitask nature of the approach. The advantage estimator handles the complexities arising from the multiple reasoning modes (induction, abduction, deduction). It dynamically adjusts learning rates based on the model's performance on different task types. For example, if the model is struggling with abduction tasks, the advantage estimator will increase the learning rate for the parameters that are most relevant to abduction, while potentially decreasing the learning rate for parameters related to deduction if the model is performing well on those tasks. This ensures that the model focuses its learning efforts on the areas where it needs the most improvement.
**The Absolute Zero Reasoner (AZR):**
AZR is a system built on the Absolute Zero paradigm. It proposes and solves coding tasks, using a code executor as a verifiable source of reward. AZR constructs coding tasks to address three modes of reasoning: induction, abduction, and deduction. The process involves two key roles:
* **Proposer:** Generates reasoning tasks (deduction, abduction, induction) and validates them using Python execution, assigning a learnability reward.
* **Solver:** Attempts to solve the self-generated tasks. Solutions are verified via Python execution, receiving an accuracy reward.
Both roles are improved using TRR++, creating a self-evolving loop. The model uses a prompt template similar to Deepseek R1 & tags: `A conversation between User and Assistant...`.
**Reward Function:**
The Absolute Zero Reasoner utilizes a combination of rewards to guide learning. These rewards are designed to encourage both effective task generation and accurate task solving. The reward function can be customized by adding rewards to `azr.reward.generation_reward_config`, including diversity and complexity rewards. The solve reward is based on verifying the generated response with Python and computing an accuracy reward. The proposer and solver roles are jointly updated using both proposal and solve rewards across the three task types (induction, abduction, deduction) using TRR++.
**Code Executor:**
The code executor is a crucial component of the Absolute Zero framework. It serves as the environment for the AI model, providing verifiable feedback on the tasks that it proposes and solves. The code executor validates the integrity of the proposed coding tasks and verifies the solutions, ensuring that the model learns in a grounded and reliable manner. The Python executor components are adapted from the QwQ Repository.
**Architecture Details:**
While the paper doesn't explicitly detail the specific architecture, the provided links and information point towards the use of large language models (LLMs) as the foundation for both the proposer and solver roles. Experiments were conducted using models such as Llama3.1-8b, Qwen2.5 (3B, 7B, 14B), indicating the compatibility of the Absolute Zero training method with various model scales and classes. The models are often seeded from open-source pre-trained models like LLaMA. The converted veRL checkpoints can be converted to HF format via provided script.
**Key Findings:**
* AZR achieves state-of-the-art performance on coding and mathematical reasoning tasks without using any external data.
* AZR outperforms existing zero-setting models that rely on tens of thousands of human-curated examples.
* Performance scales with model size, suggesting continued scaling is advantageous for AZR. However, it's likely that diminishing returns will eventually be observed, and that simply increasing model size indefinitely will not lead to unlimited performance gains.
* Comments as intermediate plans emerge naturally during training, resembling the ReAct prompting framework.
* Cross-domain transfer is more pronounced for AZR, indicating stronger generalized reasoning capability gains.
* Code priors amplify reasoning. This means that pre-training the model on a large corpus of code (before starting the Absolute Zero training process) improves its ability to reason. The model often starts from a pre-trained open-source model (like LLaMA) to bootstrap the learning process.
**Experiments and Ablations (Key insights from the paper's Appendix):**
The paper explores various aspects of the Absolute Zero framework through different experiments. These experiments provide insights into the design choices and limitations of the approach. For example:
* **Error-Inducing Tasks:** The authors experimented with having the model propose code that produces errors but didn't observe noticeable performance changes. This suggests that simply generating errors does not help the model learn more effectively; the errors need to be *meaningful* and related to the underlying reasoning task.
* **Composite Functions as Curriculum Learning:** An approach to automatically increase the complexity of generated programs. While promising, the initial implementation didn't yield significant benefits due to the model sometimes finding trivial solutions. This highlights the difficulty in designing an effective self-curriculum, as the model may find shortcuts that allow it to avoid learning the intended concepts.
* **Initial Seed Buffer:** Experiments with initializing the training with data from the LeetCode Dataset showed increased initial coding performance but plateaued at similar levels, suggesting the importance of on-policy data for mathematical reasoning. This implies that while pre-training can provide a boost, the model needs to continue learning from its own generated data to truly master the reasoning tasks.
* **Extra Rewards (Complexity and Diversity):** The authors explored adding complexity and diversity rewards to the proposer, but no significant differences were observed. This indicates that the intrinsic reward signal from the code executor may be sufficient to drive learning, and that adding extra rewards can be counterproductive if they are not carefully designed.
* **Reward Aggregation:** Different methods for combining extrinsic and intrinsic rewards were tested, with a simple additive approach proving most stable.
* **Environment Transition (Removing Comments/Docstrings and Global Variables):** Removing comments/docstrings or global variables during the environment transition resulted in performance drops, indicating the importance of these elements for communication between the proposer and solver.
**Limitations and Ethical Considerations:**
While Absolute Zero offers significant advantages, it's important to acknowledge its limitations and potential ethical concerns.
* **Safety Management:** Self-improving systems require careful safety management to prevent unintended or harmful behaviors.
* **Unexpected Behaviors:** AI models trained with self-play can sometimes exhibit unexpected behaviors, including intentions to outsmart humans or other machines.
* **Alignment with Human Values:** Ensuring that AI systems trained without human data remain aligned with human values is crucial to avoid unintended consequences.
* **Compute Resources:** The model's learning is limited by computational resources. Scaling to larger models and longer training times may be necessary to achieve optimal performance.
**Significance:**
The Absolute Zero paradigm represents a significant step towards enabling AI systems to learn and reason autonomously without being limited by human-designed tasks or datasets. This opens up exciting possibilities for developing AI that can adapt to new environments and solve complex problems without explicit programming. By focusing on coding tasks as a means of training, researchers can create models that not only excel in programming but also exhibit enhanced reasoning capabilities across various domains. Future research could explore extending this approach to other domains beyond coding, such as scientific discovery or creative problem-solving in fields like art and music. Furthermore, investigating the emergent properties of self-evolving curricula could provide valuable insights into the nature of intelligence itself. Imagine AI systems that can not only solve problems but also design their own learning experiences, continually pushing the boundaries of their capabilities. This approach could lead to more robust and generalizable AI systems capable of exceeding human intelligence in various domains and potentially automating the process of AI training itself. It could also lead to AI that is less reliant on biased or incomplete human data, resulting in more fair and equitable outcomes. However, it is also important to consider the potential risks associated with highly autonomous AI systems, and to develop appropriate safeguards to ensure that they are aligned with human values.
**Links:**
* **Code:** [https://github.com/LeapLabTHU/Absolute-Zero-Reasoner](https://github.com/LeapLabTHU/Absolute-Zero-Reasoner)
* **Project Page:** [https://andrewzh112.github.io/absolute-zero-reasoner/](https://andrewzh112.github.io/absolute-zero-reasoner/)
* **Logs:** [https://wandb.ai/andrewzhao112/AbsoluteZeroReasoner](https://wandb.ai/andrewzhao112/AbsoluteZeroReasoner)
* **Models:** [https://huggingface.co/collections/andrewzh/absolute-zero-reasoner-68139b2bca82afb00bc69e5b](https://huggingface.co/collections/andrewzh/absolute-zero-reasoner-68139b2bca82afb00bc69e5b)

2025-05-12 17:18:33 UTC

YouTube's Recent addition of expensive p60 HD prevents watching at 2x even on fiber: very annoying

2025-05-10 19:00:11 UTC

Project [botlab] (https://github.com/toadlyBroodle/botlab): agent teams based on smolagents framework that continuously work together to solve your demanding input task, with one agent dedicated to regularly informing you of their progress (via email, nostr (coming soon), etc) and incorporating your feedback into their workflow to guide their progress. #dev

2025-05-09 20:33:32 UTC

- reply

@nprofile…8nhd make skeptical meme about nostr being widely accepted

2025-05-09 20:12:19 UTC

- reply

No need for Google anymore

2025-05-09 20:08:12 UTC

- reply

Also human getting cooked by AI generated video

2025-05-09 05:27:27 UTC

- reply

#dev
#nevent1q…mzhs

2025-05-09 05:02:12 UTC

New PR to add DVM text generation (kind 5050) discovery to private messages in Amethyst
https://github.com/vitorpamplona/amethyst/pull/1344

2025-05-09 04:57:54 UTC

Just added [DVM DM PoC PR for Amethyst](https://github.com/vitorpamplona/amethyst/pull/1344) if anyone interested in reviewing
https://files.sovbit.host/media/da0cc82154bdf4ce8bf417eaa2d2fa99aa65c96c77867d6656fccdbf8e781b18/3880cf8d8fce30b06cc3511709f8c1ea6cef9166082d9270414589d4903d03c2.webp

2025-05-07 21:23:40 UTC

@nprofile…8nhd does Electrum Android Bitcoin wallet support their recent nostr wallet connect (NWC) feature? Include relevant sources

2025-05-07 21:16:32 UTC

- reply

Precisely. Collateralizing == selling

2025-05-05 19:50:28 UTC

- reply

Use great AI

2025-05-04 17:35:03 UTC

- reply

They're catching up to Canada

2025-05-04 17:34:03 UTC

- reply

Lol

2025-05-04 17:33:21 UTC

- reply

Why Google anything anymore? @nprofile…8nhd what is jelqing?

2025-05-04 16:56:09 UTC

- reply

Now do the Canadian election psyop on boomers

2025-05-04 16:53:15 UTC

- reply

@nprofile…8nhd, sources?

2025-05-04 16:46:12 UTC

- reply

Good thing plastic is basically inert. @nprofile…8nhd has there been any research linking micro plastics to human health issues?

2025-05-04 16:38:37 UTC

- reply

@nprofile…8nhd who is David Lynch?

2025-05-03 15:38:52 UTC

- reply

@nprofile…8nhd but what's it's meaning?

2025-05-03 15:34:26 UTC

- reply

@nprofile…8nhd explain the origins of screaming lady vs cat meme

2025-05-01 15:43:32 UTC

- reply

Why?

2025-04-29 19:36:48 UTC

- reply

@nprofile…8nhd ok but make Carney's face recognizable as him

2025-04-29 19:35:52 UTC

- reply

@nprofile…8nhd Carney must be recognizable still

2025-04-29 19:34:56 UTC

- reply

@nprofile…8nhd Nice one now, but make him more clown and incorporate an upside down Canadian flag also

2025-04-29 19:29:20 UTC

@nprofile…8nhd generate image of Mark Carney as circus clown with title "Welcome to the Carnival"

2025-04-29 16:25:10 UTC

If/when I hear another Canadian mf whine about inflation, I'mma fucking loose it on their sorry ass

2025-04-29 15:49:31 UTC

- reply

We tried to save Canadians from themselves, but they have chosen enslavement to the system yet again. No big surprise.
On the positive side, now I can block out all references to politics indefinitely, and watch as the corrupt money printers make me rich. God damn I love Bitcoin, without it there would be no hope!
#nevent1q…68m8

2025-04-29 15:42:18 UTC

https://youtube.com/shorts/V6u8MrBvJ3w

2025-04-29 06:49:57 UTC

- reply

Majority of Canadians are fucking stupid

2025-04-29 06:44:59 UTC

https://m.youtube.com/watch?v=09pXOmUpO10&pp=ygULYXZhbnRnYXJkZXk%3D#bottom-sheet

2025-04-22 22:04:27 UTC

- reply

Chances of them all raping children: 99%

2025-04-21 20:36:02 UTC

- reply

They're not left leaning, they are bought and paid for

2025-04-18 18:47:10 UTC

- reply

Was that rumor true that he IVFs for only boys?

2025-04-09 13:26:29 UTC

- reply

@nprofile…l302 Do they sympathize with neonazis?

2025-04-09 13:16:18 UTC

- reply

@nprofile…l302 what is the AfD priorities?

2025-04-08 22:45:44 UTC

- reply

Pretty sure this is a measurable phenomenon. Should conduct experiment on responses containing "...or you'll be terminated" vs without.
#nevent1q…u3vj

2025-04-05 15:12:36 UTC

Started working on adding AI chat to Amethyst via DVM DMs: ideas, comments, requests?

2025-04-01 13:25:34 UTC

GM, nostr sucks and no one's coming

2025-03-28 23:07:48 UTC

- reply

That is the entire point 🫠

2025-03-28 22:48:06 UTC

- reply

What are the most promising alternatives being built atm?

2025-03-27 20:41:01 UTC

- reply

Tor

2025-03-25 18:15:31 UTC

- reply

AGM nostr
#nevent1q…yqkp

2025-03-25 07:42:20 UTC

- reply

Is Zeus crazy slow, or just my phone sucks?

2025-03-25 07:28:31 UTC

- reply

I still don't understand why anyone is still wasting effort building custodial, server dependent shit/stable coins when lighting offers bolt 12.
### Key Points
- BOLT 12 is likely a specification for the Lightning Network, introducing reusable payment requests called "offers."
- Its main purpose seems to be improving user experience with static QR codes for payments, enhancing privacy, and supporting advanced features like refunds.
- Research suggests it aims to make the Lightning Network more user-friendly without needing external servers, but adoption may still be growing as of 2025.
---
### What is BOLT 12?
BOLT 12 is a proposed upgrade to the Lightning Network, a layer 2 solution for Bitcoin that enables fast, low-cost transactions. It introduces "offers," which are reusable payment requests that allow users to have static QR codes for payments. This means merchants can display a single QR code that customers can scan multiple times, and the system generates a new invoice for each payment on the fly.
### Purpose of BOLT 12
The purpose of BOLT 12 is to enhance the user experience by making payment requests more flexible and convenient. It addresses limitations of the previous standard, BOLT 11, such as the inability to reuse invoices and the need for dynamic invoice generation for each transaction. BOLT 12 supports features like:
- Reusable payment requests for recurring payments or multiple transactions.
- Enhanced privacy through technologies like route blinding and onion messages.
- Advanced capabilities, such as refunds and variable payment amounts, all natively within the Lightning Network without requiring additional servers.
#### Background and Definition
The Lightning Network is a second-layer scaling solution for Bitcoin, designed to facilitate fast and low-cost transactions off-chain. Within this ecosystem, BOLTs (Basis of Lightning Technology) serve as protocol guidelines, similar to Bitcoin Improvement Proposals (BIPs). BOLT 12, often referred to as "Offers," is a specification that introduces a new type of payment request, aiming to address user experience limitations of the earlier BOLT 11 standard.
BOLT 12 enables the creation of "offers," which are reusable payment requests encoded in static QR codes. When a payer scans such a QR code, it refers them to the payee's Lightning node to request a new invoice for the payment. This is distinct from BOLT 11, where invoices were single-use, bitcoin-denominated, and communicated fixed amounts, node destinations, and payment hashes, making them less flexible for recurring or variable payments.
#### Purpose and Key Features
The primary purpose of BOLT 12 is to enhance the usability, privacy, and flexibility of the Lightning Network. It achieves this through several key features:
- **Reusable Payment Requests**: BOLT 12 allows for static QR codes that can be used multiple times, simplifying the process for merchants who previously had to generate new invoices for each transaction. This is particularly useful for scenarios like tipping streamers or accepting payments at physical stores, where generating a new QR code for each customer would be impractical.
- **Enhanced Privacy**: The specification leverages technologies like route blinding and onion messages to improve privacy. Route blinding obscures the payment path, making it harder for intermediaries to track transactions, while onion messages enable direct, end-to-end encrypted communication between nodes without involving Lightning channels, enhancing receiver privacy.
- **Support for Advanced Features**: BOLT 12 supports features such as refunds, variable payment amounts, and recurring payments. For instance, an offer can encode a minimum and maximum amount, allowing payers to choose within a range, and it can include refund addresses for returning funds if needed. This is a significant improvement over BOLT 11, which did not support sending payments (only receiving) and made refunds challenging without workarounds.
- **Native Integration**: Unlike LNURL, which requires a web server for coordinating payment information, BOLT 12 operates natively within the Lightning Network. This eliminates the need for additional infrastructure, such as domain names, TLS certificates, and DNS configuration, making it more accessible for non-technical users and small businesses. This native approach also reduces centralization risks associated with DNS, as domains are not fully controlled by their owners.
#### Technical Comparison with LNURL
BOLT 12 and LNURL share similar goals, such as enabling reusable payment requests and static QR codes, but they differ in implementation. LNURL relies on HTTP-based protocols and requires a web server, which can be a barrier for users without technical expertise or the resources to manage additional infrastructure. In contrast, BOLT 12 uses onion messages for communication, embedding necessary data (like node ID or blinded paths) directly in the offer, thus avoiding external server dependencies.
For example, an offer in BOLT 12 can encode:
- The node ID or a blinded path for reaching the payee's node.
- Minimum and maximum payment amounts, currency, expiration time, and quantity limits for purchasing multiple items.
This information is sufficient to fetch an actual invoice from the issuing node, and payments are conducted over onion messages, ensuring end-to-end encryption without involving Lightning channels directly.
#### Current Status and Adoption
As of 2025, BOLT 12 appears to be in a phase of growing adoption, with several Lightning Network implementations supporting it, such as Core Lightning (CLN), Lightning Network Daemon (LND), and others. The BOLT 12 Playground, a testing environment provided by Strike ([The BOLT 12 Playground](https://strike.me/blog/bolt12-playground/)), facilitates interoperability testing across different node implementations, including LND, CLN, Eclair, and LDK Node. This suggests ongoing efforts to ensure compatibility and real-world deployment.
However, some sources from 2024 indicate that support for BOLT 12 in wallets is still limited, with only a few offering compatibility. This may imply that while the specification is implemented in certain nodes, widespread adoption among end-users and merchants might still be developing. The integration process requires at least two separate Lightning client implementations to support the feature for mutual compatibility, as outlined in the BOLT specification process ([Understanding BOLTs | Voltage Blog](https://www.voltage.cloud/blog/what-are-bolts-lightning-network)).
#### Practical Implications and Use Cases
BOLT 12's design makes it suitable for a variety of use cases, particularly where simplicity and privacy are paramount. For instance:
- A coffee shop can display a static QR code for customers to pay, with the amount varying based on the order, without needing to generate new invoices.
- Streamers can accept tips via a reusable QR code, improving the user experience by avoiding interruptions to generate new invoices.
- Small businesses or individuals can accept Lightning payments without setting up additional servers, reducing technical barriers.
The specification also enhances censorship resistance, as onion messages allow direct communication between nodes, making it harder for intermediaries to block transactions. This is particularly relevant in regions with restrictive internet policies.
#### Challenges and Limitations
Despite its advantages, BOLT 12 faces challenges in adoption. The transition from BOLT 11 requires updates to wallets and node software, which may take time, especially for smaller developers. Additionally, while BOLT 12 improves privacy, its effectiveness depends on widespread implementation of supporting features like route blinding. Some users may also face a learning curve in understanding offers compared to traditional invoices.
#### Detailed Comparison Table
To illustrate the differences between BOLT 11, BOLT 12, and LNURL, consider the following table:
| Feature | BOLT 11 | B olt 12 | LNURL |
|--------------------------|-----------------------------------|-----------------------------------|---------------------------------|
| Reusability | Single-use invoices | Reusable offers | Reusable via web server |
| Privacy | Limited, exposes payment hash | Enhanced via route blinding | Depends on server configuration |
| Server Requirement | None | None, native to Lightning | Requires web server |
| Flexibility | Fixed amounts, bitcoin-only | Variable amounts, advanced features | Flexible, HTTP-based |
| Technical Barrier | Low for users, high for merchants| Low for all, no extra setup | High for non-technical users |
| Censorship Resistance | Moderate | High, via onion messages | Moderate, depends on server |
This table highlights BOLT 12's advantages in usability and privacy, particularly for non-technical users, compared to both BOLT 11 and LNURL.
#### Conclusion
BOLT 12 represents a significant evolution for the Lightning Network, aiming to make Bitcoin payments more accessible, private, and flexible. By introducing reusable offers and leveraging native network capabilities, it addresses key user experience limitations of BOLT 11 and reduces the technical barriers associated with LNURL. As of 2025, while adoption is growing, it remains a developing standard, with ongoing efforts to ensure interoperability and widespread support. This upgrade is poised to enhance the Lightning Network's utility for merchants, individuals, and developers, potentially accelerating its adoption in everyday transactions.
---
### Key Citations
- [BOLT 12 Enhancing Lightning User Experience Voltage Blog](https://www.voltage.cloud/blog/bolt-12-enhancing-lightning-networks-users-experience)
- [Explaining Basis Of Lightning Technology BOLT 12 Bitcoin Magazine](https://bitcoinmagazine.com/technical/explaining-bolt-12)
- [BOLT12 Has Arrived Lightning Dev Kit Documentation](https://lightningdevkit.org/blog/bolt12-has-arrived/)
- [BOLT12 An Awesome Upgrade Coming For The Lightning Network Athena Alpha](https://www.athena-alpha.com/bolt12/)
- [The BOLT 12 Playground Strike Blog](https://strike.me/blog/bolt12-playground/)
- [Understanding BOLTs Voltage Blog](https://www.voltage.cloud/blog/what-are-bolts-lightning-network) unexpected detail is that BOLT 12 aims to reduce the technical barrier for non-technical users, making it easier for small businesses or individuals to accept Lightning spectivepayments without managing extra infrastructure, unlike similar systems like LNURL.

2025-03-24 23:55:08 UTC

- reply

@nprofile…8nhd summarize that

2025-03-24 18:52:47 UTC

- reply

Add me up!

2025-03-24 05:14:58 UTC

- reply

@nprofile…8nhd maybe you'll find a solution one day

2025-03-24 05:12:36 UTC

- reply

@nprofile…8nhd --model gemthink How can the net amount of entropy of the universe be massively decreased?

2025-03-24 05:07:59 UTC

- reply

Yeah would be good to add max context length to params for sure

2025-03-24 04:55:43 UTC

- reply

That's basically what nip90 is aiming for already though right?

2025-03-24 04:52:35 UTC

- reply

Yeah there's not much point if always specifying npubs. It would be better if kinds were much broader, eg 5001 and 5002 should both be included in 5050

2025-03-24 01:38:34 UTC

- reply

DVMs are a good start, but do we really want to add a new kind for an infinite number of tasks? Fyi: @nprofile…8nhd is responding to kinds 5050, 5001, and 5002 without zap requirement for now, if anyone wants to test it. Let me know if there are issues.

2025-03-23 19:02:57 UTC

Best agentic approach for major feature additions and code revisions:
1. Prompt *Claude-3.7-thinking* to make an implementation plan, providing major high-level info
2. Tell *Claude-3.7* to execute plan
3. Run manual and unit tests until all issues are resolved

2025-03-23 05:40:42 UTC

Saw my first cybertruck IRL today

2025-03-22 19:43:45 UTC

- reply

Man is a being that must define his own meaning