Nick Slaney is the Lead at c=, which is the name of Block’s new Lightning Service Provider subsidiary.

In our conversation, we explored the reason Block is setting out to build an LSP, Block’s corporate structure and the ways in which different entities interact, and the path to achieving global Lightning adoption.

→ c=: https://cequals.xyz/

Sponsors

→ Voltage: https://stacksats.how/voltage

→ Stakwork: https://stacksats.how/stakwork

This show is a Lightning podcast. That means instead of asking for likes or shares, I ask for sats.

The best way to show your support is to download Fountain from the App Store, load your wallet with some sats, and send them over the Lightning Network to kerooke@fountain.fm.

→ Fountain: https://www.fountain.fm/

→ More Episodes: https://www.stacksats.how/podcast

→ Lightning Address: ⚡kerooke@fountain.fm

Links

→ Stack Sats: https://www.stacksats.how/

→ Twitter: https://twitter.com/kerooke

→ Books: https://www.kevinrooke.com/book-recommendations

→ Bitcoin News: https://stacker.news/r/kr

Timestamps

00:00 - Intro

02:19 - Nick Slaney Intro

08:12 - What is c=?

15:35 - Why Block Decided To Build a Lightning Service Provider

22:27 - Understanding Liquidity on the Lightning Network

23:48 - Why Is c= Important to Block?

26:28 - How Will Block Deploy Their Bitcoin on the Lightning Network?

31:42 - Where Are The Opportunities for Earning Revenue as an LSP?

35:05 - Square Merchants & The Lightning Network

37:57 - How LN Interoperability Influences Product Decisions

42:38 - Open LSPs

53:35 - Payment Reliability on the Lightning Network

1:01:18 - The Role of Hobbyist Lightning Node Operators

1:06:34 - Integrations Between Nostr & Lightning

1:17:08 - The Lightning Round