New answers tagged

0

Configuring npm to install global packages to your user directory goes a long way to make these pesky permission issues go away. See: https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally#manually-change-npms-default-directory


1

There are currently no specifications for interoperable text/file formats between lightning network node implementations. The lightning BOLT specifications deal with standardization of the network protocols so that different lightning implementations can talk to one another, but all other details which are not part of this protocol are left up to the ...


3

Elliptic curve private keys are just scalar integer values between 1 and n (The order of G). These can be encoded by any means, but usually they are just represented as 256-bit integers with whatever endianness the platform uses. If interpreted as an array of bytes, it is simply a 32 byte sequence. The WIF (Wallet Import Format) of Bitcoin takes the 32 byte ...


7

I don't think there is a Public dataset online with an answer to your question. This would also be extremely hard to create as the results could change a lot depending on which node is doing the experiment. I know people are probing payment channels you could do the same. Just do payments to random payment hashes and collect the data for your node. You will ...


0

I figured out the issue: there were some directories that were owned by root that needed to be owned by my user. I made myself owner of some npm-related folders, for instance: sudo chown -R `whoami` /usr/local/lib/node_modules ...and that seems to have fixed the issue.


4

The situation is less worse than you seem to assume. If node C disappears the channel A,B won't be affected. Also there is no direct need to affect the channel B, C and C, D. So most channels will stay open. The payment process is a two stage process and it depends during which stage of the process node C disappears to see what happens and how nodes react. ...


0

There is nothing special that lightning nodes will have to do. All the advice is basic information security practices. Don't open ports on your node that you don't have to. Use a strong password to access your node. Disable remote logins if you have physical access. Keep the software that is running patched and up to date. Decrease your attack ...


0

Though not possible by the funding transaction, it could get figured out with 'multiple non-finalized payments' as described in the following paper: https://eprint.iacr.org/2019/328


1

As a rule of thumb it is probably best to let lnd generate the preimage for you. If someone can guess your preimage they have the chance of steeling the payment. It is somewhat similar to guessing your Bitcoin private keys but probably not as bad as they can only get the current payment and technically even that might be tricky. If you want to do it alone ...


2

These implementations use some form of the Dijkstra algorithm which is implemented in the open source networkx python lib https://networkx.github.io/documentation/stable/reference/algorithms/shortest_paths.html also electrum wallet is working on lightning. I think they followed pretty much the lnd code base so one could check their pathfing implementation at ...


0

I don't know if that possibility ever existed as an api call 8n lnd. but you can certainly call the describegraph api call to get all nodes and channels that are publically known. This json blob can easily be imported with a few lines of code as a graph in any graph library such as neo4j or networkx once the network is there you can run any pathfinding ...


0

I'd argue it is possible to get some estimate, when doing a time series analyses of 2-to-2 multisig spendings. Number of occurrences (or gowth rate) likely changed, when lightning got live. Question is how accurate such an estimate can be.


1

The Bitcoin scripting language allows for a decent variety of transaction constructions, but only a subset of those are considered "standard". In particular, Bitcoin Core will only relay transactions by default that pass the isStandard() check. However, miners are still free to include (valid!) non-standard transactions in their blocks. Transactions larger ...


1

What is a "maximum standard weight"? It is a property that nodes follow to prevent processing large transactions with number of rules and signatures. It is standardness not consensus. If a node receives a transaction greater than 400,000 WU, it will discard the transaction and not relay it further. I can however, definitely create a transaction greater than ...


4

Running lightning node over TOR is no different than running it over normal IP connection. Sending payment, fulfilling incoming payment, sending error messages etc. would happen in the exact same way in both cases. The only difference is that the above messages that you send to your peer will now happen over TOR network rather than a direct IP package. If ...


2

Yes. You always have two accounts on LND (ZAP interfaces over rpc with your self hosted lnd node). One account is your lightning wallet where channel management is done, and the other is your on chain wallet. Depending on where your balance is there are different processes for moving the balance to your on chain wallet (which is what I assume you want). ...


1

The following produces the wrong private key! (but is probably a step in the right direction) In c-lightning the per commitment point / secret is derived using per_commit_point / per_commit_secret from: The node id / public key (can be found with listfunds, until the channel is purged some time after closing) The channel database id (can be found with cat ~...


2

They can only be detected when force closed and there are still pending htlcs otherwise they look like a spend from a 2-2 multisig wallet. I've been told some people try to do chain analysis and machine learning to predict private channels. I highly doubt that this is reasonably possible. Although there is one thing to consider. If a node has public and ...


5

Basically as fast as a regular payment. The encrypted onion is being transported from node to node and will most likely leave the TOR network pretty quickly as many connections in lightning happen with direct IP connections. The path calculation is happening locally on your node and does not need communication with your peers at the time when the payment is ...


1

This is implementation dependent of course. Afaik every implementation will try to reconnect, so your first case works (note that your paranoid friend's Tor hidden service isn't used at all). This is common in practice, for any non-public node. In the second case, for c-lightning the address hint will be forgotten on reconnect, so they'll try to reconnect ...


0

Most of the articles that I have read refer to channels/nodes that haven't sent channel_update or node_announcement message for a long time (often weeks) as zombies. They say, a node who wants to route a lightning payment cannot rely on a path containing these nodes (hence zombies). But that is a fuzzy notion since nodes will not send these update messages ...


3

I am not aware of a clear definition for the term zombie channels. At least I don't recall the term being used in the lightning rfc. Also I didn't hear lightning devs in conversations to talk about them. Thus I think the semantics are more along your suggestion that they refer to channels which are for some reason obsolete / inactive / unusable. Disclaimet: ...


2

A funding transaction is one where some money is paid into a P2WSH transaction output, where the redeeemScript is a 2-of-2 multisig between the two participants. No other information is provided. Technically, even the redeemScript for the funding is not revealed until the funding transaction output is spent (channel closed), which makes it less obvious that ...


0

How would the adversary know that your transaction is linked to the lightning network ? it can be toward a friend, an exchange or even stolen When a Lightning channel is created or closed, it leaves a footprint on the Bitcoin blockchain. (Note that this footprint tells a third party very little about how you routed your payments while on the Lightning ...


2

This might not be a satisfying answer but if you look at the eclair git repo and their Wiki you will find that the eclair API is a JSON API and is exposed via http and web sockets and can be queried with regular http requests. If you look at the c-lightning python client it is a tool that talks via a unixDomainSocket to the exposed lightningd api. So I ...


0

Maybe the directory doesnt have the proper rights, try this command sudo chmod 777 If it still doesnt work try these flag before your install sudo npm install -g --unsafe-perm or sudo node-gyp rebuild -g --unsafe-perm then try again


1

Why is the description field limited to 639 bytes? Every field in lightning invoice is of the form: type (5 bits) data_length (10 bits, big-endian) data (data_length x 5 bits) The data_length indicates the size of the data that is to be followed. Since data_length itself has a size of 10 bits, it can represent a number up to 1023 (210 -1). Thus the size ...


Top 50 recent answers are included