Add BOLT 12 payer proofs blog post with diagram assets - #322
Open
vincenzopalazzo wants to merge 5 commits into
Open
Add BOLT 12 payer proofs blog post with diagram assets#322vincenzopalazzo wants to merge 5 commits into
vincenzopalazzo wants to merge 5 commits into
Conversation
Add a blog post covering exportable, verifiable Lightning receipts (lnp) built on BOLT 12, with four diagrams rendered from the design handoff. Co-Authored-By: Vincenzo Palazzo <vincenzopalazzo@users.noreply.github.com>
✅ Deploy Preview for lightningdevkit ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Co-Authored-By: Vincenzo Palazzo <vincenzopalazzo@users.noreply.github.com>
benthecarman
reviewed
Aug 6, 2026
benthecarman
left a comment
benthecarman
left a comment
Contributor
There was a problem hiding this comment.
left some notes but overall this reads very AI-y
Correct the preimage rationale (offer is not bound to payment hash), introduce NIP-57 before referencing it, call out missing cryptographic verifiability for screenshots, and drop the opaque app capability descriptor phrasing. Light prose pass on the AI-y bits.
Member
Author
|
Addressed the inline notes in e71e5fd, and did a light prose pass on the more formulaic bits from the overall "reads very AI-y" feedback. Happy to keep sanding tone if anything still sticks out. |
Member
Author
What does not these days? :P |
Rewrite the post in a more first-person, conversational voice so it reads less AI-generated, while keeping the four diagram placements and the technical corrections from review.
Member
Author
|
Pushed a fuller rewrite aimed at the "reads very AI-y" cc @benthecarman :P |
Drop em-dashes; they read as AI tell.
vincenzopalazzo
force-pushed
the
blog/bolt12-payer-proofs
branch
from
August 7, 2026 11:40
b4b3098 to
5e84c52
Compare
Contributor
|
still reads pretty ai-y imo |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Review Notes
Decision Log
Hardest decision: Rendering the draw.io HTML design handoff into PNG screenshots rather than embedding the .dc.html directly. The handoff bundle is a React/dc-runtime canvas requiring window.React/window.ReactDOM at runtime — embedding it as a live component in VitePress would pull in a runtime dependency and break on the static build. PNG screenshots preserve the visual design exactly and match how every other blog post in the repo handles diagrams (e.g. bolt12-has-arrived.md uses ../assets/.svg/.png).
Alternatives rejected:
Least confident about: The date "2026-07-01" placeholder. The original .docx had 2026-07-XX; set a concrete date to satisfy the frontmatter schema, but the real publish date should be confirmed. Also, author Vincenzo Palazzo may need an entry in docs/blog/author/ for the byline page to resolve correctly.
Test plan