Stan Kladko [ARCHIVE] on Nostr: 📅 Original date posted:2017-12-13 📝 Original message: Thank you Presumably many ...
📅 Original date posted:2017-12-13
📝 Original message:
Thank you
Presumably many nodes will be behind firewalls. Are there any
firewall traversal mechanisms included (or some type of an overlay
network)?)
On Wed, Dec 13, 2017 at 2:53 PM, ZmnSCPxj <ZmnSCPxj at protonmail.com> wrote:
> Good morning Stan,
>
>>How to I discover nodes - is there any UI to see nodes currently
>>running on the network ?
>
> There are no UIs to my knowledge. Current LN programs keep track of this in
> their databases, although each one varies in detail. Presumably their
> individual main developers know how to extract this information.
>
> My understanding is that network bootstrap involves some LN nodes being
> discoverable via DNS, then your node will connect to them, request node
> gossip, then it (if you use some kind of auto-pilot channeling system like
> what lnd has) will select from the node information it acquires to select
> some nodes to connect and channel to.
>
> Note a precision, there is a difference between "connect" and "channel". To
> connect, means only that you contact them over the network and consumes only
> bandwidth and some small amount of CPU power on your node. To channel,
> means to commit some bitcoins to a payment channel between you.
>
>>>>How do I find out if someone wants to connect to me?
>>>The node connects to yours and sends channel funding messages.
>>
>>In this case there is some kind of an UI where I can accept or reject -
>> correct?
>>Or I auto-accept everyone that connects to me?
>
> None. You auto-accept incoming channel requests. You might, if you are up
> to it, program your node to reject some nodes via any heuristic you choose,
> but you would have to implement that yourself. I know of no current LN
> software that has or intends to have such a feature, as there are little
> downside to accepting all channels --- you only spend less than a kilobyte
> of storage for each newly-opened channel --- while the upside is that a
> channel to you is a potential route which you can charge for, or a route you
> can receive funds through.
>
>>>If you intend to connect for the purpose of becoming a hub and earning
>>> routing fees, if you have some onchain bitcoins you can afford to invest,
>>> then it is to your interest to
>>channel with relatively new and low-connectivity nodes.
>>
>>If I become a hub, how much to I earn, approximately in routing fees?
>>Is it a percentage of transactions? Are routing fees the same for all
>>hubs?
>
> Each node indicates as part of its information a "fixed fee" and a
> "proportional fee". The "fixed fee" is imposed per successful routing
> attempt, while the "proportional fee" is a ratio of the value traveling
> through the node when it is on the route. It is expected that there will be
> many nodes through which people can route, so there will be much
> competition and eventually the system will settle to a state where most
> nodes charge the same low fee.
>
>>If I am connecting to the network and see many hubs - how can I select
>>which hub to connect to? Is there any performance/reputation info
>>available for any hub?
>
> There are none. Presumably your auto-channeling program will gather
> statistics and other information to make some guesses on which nodes have
> good performance.
>
> Note that, there is nothing that specially privileges hubs, and this is
> deliberate. Any node can become a hub without permission or special
> treatment of the network, if by "hub" we mean "node with high number of
> channels". Indeed, even the DNS bootstrap, to my knowledge, should only be
> used to gather initial node gossip to acquire some *other* nodes that can
> potentially be channeled to.
>
> Regards,
> ZmnSCPxj
Published at
2023-06-09 12:48:01Event JSON
{
"id": "4be7bee489bf4895104b43540863407ef034e0a36070d5d53eb148c9bb85fc9d",
"pubkey": "bb6a5aab45ee6665cfa35d9cdfbb10ea8cce5d69ef1372d8395f055dd667d022",
"created_at": 1686314881,
"kind": 1,
"tags": [
[
"e",
"71de09222201d9843898341412b076e30b471910d9c7453f365ef2ecaeeb2d27",
"",
"root"
],
[
"e",
"0a5fc021e396bc41fce8a8ef4a55ae0f442fc052f46a14f966028d52022d2691",
"",
"reply"
],
[
"p",
"4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861"
]
],
"content": "📅 Original date posted:2017-12-13\n📝 Original message:\nThank you\n\n\nPresumably many nodes will be behind firewalls. Are there any\nfirewall traversal mechanisms included (or some type of an overlay\nnetwork)?)\n\n\n\nOn Wed, Dec 13, 2017 at 2:53 PM, ZmnSCPxj \u003cZmnSCPxj at protonmail.com\u003e wrote:\n\u003e Good morning Stan,\n\u003e\n\u003e\u003eHow to I discover nodes - is there any UI to see nodes currently\n\u003e\u003erunning on the network ?\n\u003e\n\u003e There are no UIs to my knowledge. Current LN programs keep track of this in\n\u003e their databases, although each one varies in detail. Presumably their\n\u003e individual main developers know how to extract this information.\n\u003e\n\u003e My understanding is that network bootstrap involves some LN nodes being\n\u003e discoverable via DNS, then your node will connect to them, request node\n\u003e gossip, then it (if you use some kind of auto-pilot channeling system like\n\u003e what lnd has) will select from the node information it acquires to select\n\u003e some nodes to connect and channel to.\n\u003e\n\u003e Note a precision, there is a difference between \"connect\" and \"channel\". To\n\u003e connect, means only that you contact them over the network and consumes only\n\u003e bandwidth and some small amount of CPU power on your node. To channel,\n\u003e means to commit some bitcoins to a payment channel between you.\n\u003e\n\u003e\u003e\u003e\u003eHow do I find out if someone wants to connect to me?\n\u003e\u003e\u003eThe node connects to yours and sends channel funding messages.\n\u003e\u003e\n\u003e\u003eIn this case there is some kind of an UI where I can accept or reject -\n\u003e\u003e correct?\n\u003e\u003eOr I auto-accept everyone that connects to me?\n\u003e\n\u003e None. You auto-accept incoming channel requests. You might, if you are up\n\u003e to it, program your node to reject some nodes via any heuristic you choose,\n\u003e but you would have to implement that yourself. I know of no current LN\n\u003e software that has or intends to have such a feature, as there are little\n\u003e downside to accepting all channels --- you only spend less than a kilobyte\n\u003e of storage for each newly-opened channel --- while the upside is that a\n\u003e channel to you is a potential route which you can charge for, or a route you\n\u003e can receive funds through.\n\u003e\n\u003e\u003e\u003eIf you intend to connect for the purpose of becoming a hub and earning\n\u003e\u003e\u003e routing fees, if you have some onchain bitcoins you can afford to invest,\n\u003e\u003e\u003e then it is to your interest to\n\u003e\u003echannel with relatively new and low-connectivity nodes.\n\u003e\u003e\n\u003e\u003eIf I become a hub, how much to I earn, approximately in routing fees?\n\u003e\u003eIs it a percentage of transactions? Are routing fees the same for all\n\u003e\u003ehubs?\n\u003e\n\u003e Each node indicates as part of its information a \"fixed fee\" and a\n\u003e \"proportional fee\". The \"fixed fee\" is imposed per successful routing\n\u003e attempt, while the \"proportional fee\" is a ratio of the value traveling\n\u003e through the node when it is on the route. It is expected that there will be\n\u003e many nodes through which people can route, so there will be much\n\u003e competition and eventually the system will settle to a state where most\n\u003e nodes charge the same low fee.\n\u003e\n\u003e\u003eIf I am connecting to the network and see many hubs - how can I select\n\u003e\u003ewhich hub to connect to? Is there any performance/reputation info\n\u003e\u003eavailable for any hub?\n\u003e\n\u003e There are none. Presumably your auto-channeling program will gather\n\u003e statistics and other information to make some guesses on which nodes have\n\u003e good performance.\n\u003e\n\u003e Note that, there is nothing that specially privileges hubs, and this is\n\u003e deliberate. Any node can become a hub without permission or special\n\u003e treatment of the network, if by \"hub\" we mean \"node with high number of\n\u003e channels\". Indeed, even the DNS bootstrap, to my knowledge, should only be\n\u003e used to gather initial node gossip to acquire some *other* nodes that can\n\u003e potentially be channeled to.\n\u003e\n\u003e Regards,\n\u003e ZmnSCPxj",
"sig": "017fcc2116e06f2be4c91b79b1bcdff8c009ab82a2342538761e303c3183ae24d4333bfa59ed3f01eb7be296c7bb6361f2c621bbd256f0e83a30d884f8d9b4ba"
}