<p><em>I believe the concerns of the authors are addressed in <a href="https://bitcoin.stackexchange.com/a/109511/101498">this answer</a>. Here is anyway, to their request, an adaptation of the answer to the application from this question.</em></p>
<p>I think you are conflating logging with the ability of taking part, or not, in the Lightning Network protocol. One can always refuse the establishment of a channel to their node, as much as they can refuse a handshake, refuse to advertize a way to reach them through the internet, or refuse to set up a computer connected to the internet in the first place.</p>
<ol>
<li>Yes it is. I'm pretty sure you'll at least have a line at <code>info</code> level. You'll have more details about the process at lower logging levels, of course.</li>
<li>You are mentionning RPC commands. If your node is listening, reachable and advertized a mean to reach it then you do not need to execute any command for another node to establish a channel to it.</li>
<li>That sounds overly convoluted, to say the least. Why would one use the logs to attempt that? In any case, you may of course be coerced into refusing the establishment of a channel to you, as much as you may be coerced to not use Lightning, or Bitcoin.</li>
<li>Most nodes on the network enforce a minimum channel capacity.</li>
</ol>

CC BY-SA 4.0
2022-04-23T15:00:58.967Z
Thank you, especially your answer to **2.**  does make clear to me what happens on the other side. A newbie like myself runs only a non-routing node but knowing at a high level what happens in routing nodes helps to understand the censorship-resistance of lightning.
John Smith
CC BY-SA 4.0
2022-04-23T13:00:33.353Z
2022-04-23T13:00:33.353Z
Antoine Poinsot
<p><code>c-lighning</code>'s user has the option of funding a private channel with <code>fundchannel</code>'s <code>announce=false</code> flag.
The user, such as myself, executes <code>fundchannel</code> and, provided that the fee was sufficient,
soon has a channel at their disposal. How does the process look on the other side?</p>
<ol>
<li>Is the request
to open a private channel logged in <code>.lightning/bitcoin/log</code> of the other party? If so what level of logging is required? Would anybody be kind enough to paste an example from their <code>.lightning/bitcoin/log</code>?</li>
<li>Is <code>fundchannel_complete</code> or <code>open_channel</code> <a href="https://bitcoin.stackexchange.com/questions/109509/is-it-possible-to-programmatically-or-preemptively-deny-any-all-open-channel-lig">used to complete the creation of the channel in</a>
the case that the other party agrees on creating a private channel.</li>
<li>Can monitoring the content of <code>.lightning/bitcoin/log</code> be the basis of
Bitcoin's censorship through the attempt to limit private channel creation
to only whitelisted parties or to only those that are not blacklisted.
Let's say that a law is passed that says that the operators of routing nodes
have a legal obligation to store their logs and provide law enforcement
with access to such logs. Opening private channels to the sanctioned entities
or the non-whitelisted entities is punished. The aim of such a law would be to
restrict the usage of c-lightning to custodial wallets.</li>
<li>Do top-capacity routing nodes automate the process of agreeing on the channel opening to them? If so what are the most commonly used solutions/scripts/plugins for this purpose?</li>
</ol>

CC BY-SA 4.0
2022-04-23T11:31:20.510Z
Does this answer your question? [Is it possible to programmatically or preemptively deny any/all open\_channel Lightning messages coming into your node?](https://bitcoin.stackexchange.com/questions/109509/is-it-possible-to-programmatically-or-preemptively-deny-any-all-open-channel-lig)
Antoine Poinsot
CC BY-SA 4.0
2022-04-23T12:13:41.310Z
@AntoinePoinsot It does **partially** answer, hinting me towards `open_channel`. Yet, I would gladly receive the answer about the details that I ask for in the points 1, 2, and 4 of my question.
John Smith
<core-lightning><channels><censorship-resistance>
What command does a c-lightning node run, after did broadcast fundchannel from my side, when they establish a channel with me? Can they be censored?
John Smith
# What command does a c-lightning node run, after did broadcast fundchannel from my side, when they establish a channel with me? Can they be censored?

(Asked by: username_0 on 2022-04-23)

`c-lighning`'s user has the option of funding a private channel with `fundchannel`'s `announce=false` flag.
The user, such as myself, executes `fundchannel` and, provided that the fee was sufficient,
soon has a channel at their disposal. How does the process look on the other side?

1. Is the request
   to open a private channel logged in `.lightning/bitcoin/log` of the other party? If so what level of logging is required? Would anybody be kind enough to paste an example from their `.lightning/bitcoin/log`?
2. Is `fundchannel_complete` or `open_channel` [used to complete the creation of the channel in](https://bitcoin.stackexchange.com/questions/109509/is-it-possible-to-programmatically-or-preemptively-deny-any-all-open-channel-lig)
   the case that the other party agrees on creating a private channel.
3. Can monitoring the content of `.lightning/bitcoin/log` be the basis of
   Bitcoin's censorship through the attempt to limit private channel creation
   to only whitelisted parties or to only those that are not blacklisted.
   Let's say that a law is passed that says that the operators of routing nodes
   have a legal obligation to store their logs and provide law enforcement
   with access to such logs. Opening private channels to the sanctioned entities
   or the non-whitelisted entities is punished. The aim of such a law would be to
   restrict the usage of c-lightning to custodial wallets.
4. Do top-capacity routing nodes automate the process of agreeing on the channel opening to them? If so what are the most commonly used solutions/scripts/plugins for this purpose?

**Tags:** core-lightning, channels, censorship-resistance

> **Comments:**
> **username_1**: Does this answer your question? [Is it possible to programmatically or preemptively deny any/all open\_channel Lightning messages coming into your node?](https://bitcoin.stackexchange.com/questions/109509/is-it-possible-to-programmatically-or-preemptively-deny-any-all-open-channel-lig)  
> **username_0**: @AntoinePoinsot It does **partially** answer, hinting me towards `open_channel`. Yet, I would gladly receive the answer about the details that I ask for in the points 1, 2, and 4 of my question.  

---

## 1 answers

### Answer by username_1 on 2022-04-23. Score: 1 | Accepted answer

*I believe the concerns of the authors are addressed in [this answer](https://bitcoin.stackexchange.com/a/109511/101498). Here is anyway, to their request, an adaptation of the answer to the application from this question.*

I think you are conflating logging with the ability of taking part, or not, in the Lightning Network protocol. One can always refuse the establishment of a channel to their node, as much as they can refuse a handshake, refuse to advertize a way to reach them through the internet, or refuse to set up a computer connected to the internet in the first place.

1. Yes it is. I'm pretty sure you'll at least have a line at `info` level. You'll have more details about the process at lower logging levels, of course.
2. You are mentionning RPC commands. If your node is listening, reachable and advertized a mean to reach it then you do not need to execute any command for another node to establish a channel to it.
3. That sounds overly convoluted, to say the least. Why would one use the logs to attempt that? In any case, you may of course be coerced into refusing the establishment of a channel to you, as much as you may be coerced to not use Lightning, or Bitcoin.
4. Most nodes on the network enforce a minimum channel capacity.

> **Comments:**
> **username_0**: Thank you, especially your answer to **2.**  does make clear to me what happens on the other side. A newbie like myself runs only a non-routing node but knowing at a high level what happens in routing nodes helps to understand the censorship-resistance of lightning.  

---

