Skip to content

Add Lexe case study with architecture diagram#312

Open
ConorOkus wants to merge 2 commits into
mainfrom
lexe-case-study
Open

Add Lexe case study with architecture diagram#312
ConorOkus wants to merge 2 commits into
mainfrom
lexe-case-study

Conversation

@ConorOkus
Copy link
Copy Markdown
Contributor

@ConorOkus ConorOkus commented Jun 5, 2026

Summary

Adds a new case study: Lexe Uses LDK to Run Self-Custodial Lightning in Secure Enclaves (by Max Fang), covering how Lexe runs hundreds of self-custodial Lightning nodes inside a single Intel SGX enclave using LDK's modular Persist / Confirm traits and shared NetworkGraph / ProbabilisticScorer.

🤖 Generated with Claude Code

Add a case study covering how Lexe runs self-custodial Lightning nodes
inside Intel SGX secure enclaves using LDK, and wire its case study link
into the existing Lexe entry on the case studies page.

Recreate the "Lexe Architecture with LDK" diagram (from the Claude Design
handoff) as an inline-SVG Vue component embedded in the post. Adapted for
this site: theming follows the global light/dark switch (html.dark) rather
than a standalone toggle, and the dark figure blends with the theme
background with no outline.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@netlify
Copy link
Copy Markdown

netlify Bot commented Jun 5, 2026

Deploy Preview for lightningdevkit ready!

Name Link
🔨 Latest commit 4e7e4e3
🔍 Latest deploy log https://app.netlify.com/projects/lightningdevkit/deploys/6a22e52ad149aa000876d0e8
😎 Deploy Preview https://deploy-preview-312--lightningdevkit.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Swap Lexe in for Bitkit in the featured row (Bitkit stays in the full
grid). Lexe's logo is a white wordmark on a dark tile, which reads on the
light page but vanishes on the dark page, so add an invertOnDark flag —
reusing the home-page logo-strip convention — to invert it in dark mode.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@MaxFangX
Copy link
Copy Markdown

MaxFangX commented Jun 5, 2026

Would it be possible to use this version instead? This is the original version that I wrote and polished, and it's the version we host on our blog. It has more a direct, confident, sharp technical tone while the one on the Spiral blog reads as if it was rewritten and flattened out by an LLM, and loses my voice. Feel free to make edits as needed though, for example if you want to remove the --- em-dashes (yes, I do use them intentionally), add line breaks, or soften some PR / marketing language you feel is too bold to put on the Spiral website.

My original:

Spiral substack:

@MaxFangX
Copy link
Copy Markdown

MaxFangX commented Jun 5, 2026

@ConorOkus I DM'd you some rounded square logos on Discord which are more suitable to use than the one in the preview:

lexe_macOS_app_icon_512 image

@MaxFangX
Copy link
Copy Markdown

MaxFangX commented Jun 5, 2026

Cool architecture diagram; it's visually appealing and better than ours. Some nits:

  1. The diagram is slightly inaccurate; it's connecting the App to the user's cloud storage.
  2. The "HTTPS/TLS" label looks like it's labeling the "Lexe Cloud" box rather than the bottom connection. In general I think the labels for network connections (TLS, TLS-in-TLS, HTTPS/TLS, Noise) could be a bit more carefully placed.
  3. I think the second sentence in the caption is unnecessary: "The shared NetworkGraph and ProbabilisticScorer live once per enclave, while each user's keys and channel state stay isolated."
image

You can compare with the original one from our blog, which is not as pretty but is a bit more accurate.

image

If you'd like to work off of our original, (we built it in Google Slides), I shared a Google Slides presentation to your Spiral email @ConorOkus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants