# ZK-gossip for lightning channel announcements

**URL:** <https://delvingbitcoin.org/t/zk-gossip-for-lightning-channel-announcements/1407>\
**Category:** Protocol Design\
**Tags:** taproot, lightning, zkp\
**Created:** [January 28, 2025, 1:04pm UTC](https://delvingbitcoin.org/t/zk-gossip-for-lightning-channel-announcements/1407 "2025-01-28T13:04:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sanket1729](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/sanket1729/32/13_2.png) [@sanket1729](https://delvingbitcoin.org/u/sanket1729)\
**Post date:** [January 28, 2025, 10:28pm UTC](https://delvingbitcoin.org/t/zk-gossip-for-lightning-channel-announcements/1407/2 "2025-01-28T22:28:00Z")

</div>

First off, awesome work with this. I have been brainstorming this specific issue for quite sometime now. Great to concrete progress here.

I will try out the code and ask specific questions in a followup reply, but here is the main one that I struggled with initially.

How does this interact with lightning channel closures? I am not familiar with lighting routing messages for channel close, or if the node directly figures it out by observing the blockchain.

For effective payment routing, the graph also needs to be updated with the closed channels, removing them network. Will the ZK benefits go away if the channel\_id is leaked when we close the channel?

---

_[View the full topic](https://delvingbitcoin.org/t/zk-gossip-for-lightning-channel-announcements/1407)._