Bitcoin Forum
May 16, 2024, 06:00:38 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 »
1  Bitcoin / Bitcoin Technical Support / Re: Sniffing LN traffic with Wireshark on: October 29, 2023, 11:20:39 PM
Hi,

Thanks for all your answers.
I finally solved it using a Wireshark pluguin: https://github.com/nayutaco/lightning-dissector
It fails on some packets, but id does his job anyway.
2  Bitcoin / Bitcoin Technical Support / Re: Default Lightning Network Features on: October 25, 2023, 09:14:44 AM
Hi. Can you clarify what you mean by "features"? For example, are you interested in knowing whether they all use Watchtowers? Does Watchtower count as a feature? Or is your question more generic? Like which wallets support which implementation etc?

Hi. Sorry if my question wasn't clear. I mean the features that are shown when you use "describegraph" command.

From LND (note that CLN show the features in a binary string format):

Code:
{
            "pub_key": "03f81d429455dcc08ebbe00c9961db42e907a6571a657637533ac2e92cc9c936f4",
            "alias": "alice",
            "implementation": "LND_v0.15.1",
            "features_LNDv0.15.1_view": {
                "0": {
                    "name": "data-loss-protect",
                    "is_required": true,
                    "is_known": true
                },
                "5": {
                    "name": "upfront-shutdown-script",
                    "is_required": false,
                    "is_known": true
                },
                "7": {
                    "name": "gossip-queries",
                    "is_required": false,
                    "is_known": true
                },
                "9": {
                    "name": "tlv-onion",
                    "is_required": false,
                    "is_known": true
                },
                "12": {
                    "name": "static-remote-key",
                    "is_required": true,
                    "is_known": true
                },
                "14": {
                    "name": "payment-addr",
                    "is_required": true,
                    "is_known": true
                },
                "17": {
                    "name": "multi-path-payments",
                    "is_required": false,
                    "is_known": true
                },
                "23": {
                    "name": "anchors-zero-fee-htlc-tx",
                    "is_required": false,
                    "is_known": true
                },
                "27": {
                    "name": "shutdown-any-segwit",
                    "is_required": false,
                    "is_known": true
                },
                "31": {
                    "name": "amp",
                    "is_required": false,
                    "is_known": true
                },
                "45": {
                    "name": "explicit-commitment-type",
                    "is_required": false,
                    "is_known": true
                },
                "2023": {
                    "name": "script-enforced-lease",
                    "is_required": false,
                    "is_known": true
                }
            },
Hope with this example this is clear.
3  Bitcoin / Bitcoin Technical Support / Default Lightning Network Features on: October 25, 2023, 08:43:32 AM
Hi all,

Does anyone know which are the default features enabled on the main three Lightning Network node implementations (LND, C-Lightning and Eclair)?
Or where can I find a list?


Best Regards,

SS
4  Bitcoin / Bitcoin Technical Support / Sniffing LN traffic with Wireshark on: October 11, 2023, 08:34:16 AM
Hi all,

I've seen on the Internet that Wireshark can detect protocol packages like Bitcoin and Lightning Network. They are identified in the protocol column.
The problem is that my Wireshark is not classifying those packages, it just says tcp/ip or http/json.
Does anyone know how to solve that?

Note: I know there's a package called lightning dissector but I don't need to read the packages, just identify them. (In the end, I ended up using it)

Thanks in advance!

-SS
5  Bitcoin / Bitcoin Technical Support / Re: Help with python code on: October 04, 2023, 09:49:12 PM
I don't post my seed at anyplace I have it on paper writed by hand, I'm totally noob programing I do it correcting what a AI do for me.

There're tools that can help you with that. But some tips:

1. NEVER use a script that sends your seed to some web page. THEY CAN STEAL YOUR FOUNDS!
2. Don't try to program anything if you don't know how to.
3. Don't use code generated by an IA. Just look for some tools already done.
6  Bitcoin / Bitcoin Technical Support / Re: [Solved] Connect LND and Core on different machines on: September 28, 2023, 01:23:32 PM
Finally it's working!
There were different issues. First of all the bindings of bitcoind services must be on 0.0.0.0 if not external IP cannot connect.
Also, there was a traffic filtering on the bitcoin core firewall and it was blocking LND traffic.

- SS
7  Bitcoin / Bitcoin Technical Support / Re: [Issue] Connect LND and Core on different machines on: September 28, 2023, 12:05:09 PM
After changing some config as binding to 0.0.0.0 and listening to 0.0.0.0/0 on bitcoin.conf now I get a different error:

Code:
2023-09-28 14:06:41.431 [DBG] RPCS: [/lnrpc.WalletUnlocker/UnlockWallet] requested
2023-09-28 14:06:41.986 [INF] LNWL: Opened wallet
2023-09-28 14:06:42.026 [INF] CHRE: Primary chain is set to: bitcoin
2023-09-28 14:06:42.039 [ERR] LTND: unable to create partial chain control: -28: Loading P2P addresses…
2023-09-28 14:06:42.039 [ERR] LTND: Shutting down because error in main method: error creating wallet config: unable to create partial chain control: -28: Loading P2P addresses…
2023-09-28 14:06:42.040 [INF] LTND: Shutdown complete

error creating wallet config: unable to create partial chain control: -28: Loading P2P addresses…

8  Bitcoin / Bitcoin Technical Support / Re: [Issue ]Connect LND and Core on different machines on: September 28, 2023, 10:34:45 AM
At very least, number on verificationprogress is just estimation and one of Bitcoin Core member said there's no problem if it's slightly below 1.0[1]. It's proven by 0.9999983770795251 doesn't refer to total of verified block since the value equal to 6249989856747 / 6250000000000 [2].

[1] https://bitcoin.stackexchange.com/a/85973
[2] https://www.calculator.net/fraction-calculator.html?c2d1=0.9999983770795251&ctype=2&x=79&y=24#decimal2fraction

Yes, I absolutely discard that as the issue. I think there's some network config issue on bitcoin.conf and lnd.conf files but I'm unable to see it.
I've modified rpcallowip parameter to 0.0.0.0/0 but still not working :/

If I just wait I get the following message on LND:

Code:
2023-09-28 12:37:13.820 [ERR] LTND: unable to create partial chain control: invalid http POST response (nil), method: getblockhash, id: 1, last error=Post "http://x.x.x.x:8332": dial tcp x.x.x.x:8332: connect: connection timed out
2023-09-28 12:37:13.820 [ERR] LTND: Shutting down because error in main method: error creating wallet config: unable to create partial chain control: invalid http POST response (nil), method: getblockhash, id: 1, last error=Post "http://x.x.x.x:8332": dial tcp x.x.x.x:8332: connect: connection timed out
2023-09-28 12:37:13.822 [INF] LTND: Shutdown complete

error creating wallet config: unable to create partial chain control: invalid http POST response (nil), method: getblockhash, id: 1, last error=Post "http://x.x.x.x:8332": dial tcp x.x.x.x:8332: connect: connection timed out

9  Bitcoin / Bitcoin Technical Support / [Solved] Connect LND and Core on different machines on: September 28, 2023, 09:20:46 AM
Hi,

I'm trying to connect my LND node to my Core, both on different machines, but my LND is stucked after unlocking the wallet and I cannot make RPC calls as it shows the following error:
Code:
user@ubuntu:/usr$ lncli getinfo
[lncli] rpc error: code = Unknown desc = the RPC server is in the process of starting up, but not yet ready to accept calls

Error from lnd side:
Code:
2023-09-28 11:19:26.524 [DBG] RPCS: [/lnrpc.WalletUnlocker/UnlockWallet] requested
2023-09-28 11:19:27.087 [INF] LNWL: Opened wallet
2023-09-28 11:19:27.132 [INF] CHRE: Primary chain is set to: bitcoin
2023-09-28 11:19:32.512 [DBG] RPCS: [/lnrpc.Lightning/GetInfo] requested
2023-09-28 11:19:32.512 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: the RPC server is in the process of starting up, but not yet ready to accept calls

With a quick search on the Internet, I found that this could be because Core is not completely sync but it's:
Code:
{
  "version": 220000,
  "blocks": 809706,
  "headers": 809706,
  "verificationprogress": 0.9999983770795251,
....
Checking mempool.space 809706 is the last block.

The bitcoin.conf and lnd.conf are the following ones:

[Bitcoin.conf]
Code:
server=1
daemon=1

# Allows LND to connect to the Bitcoin node via an RPC user & pass
rpcuser=*********
rpcpassword=**********

# Allows LND & Bitcoin Core to communicate via ZeroMQ
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333

# Allows other machines apart from localhost to connect to rpc server
rpcallowip=x.x.x.x/24
rpcbind=127.0.0.1


dbcache=20480

shrinkdebugfile=0


[LND]

Code:
[Application Options]
externalip=x.x.x.x

[Bitcoin]
bitcoin.active=true
bitcoin.mainnet=true
bitcoin.node=bitcoind



[Bitcoind]
bitcoind.rpchost=CoreIP (same network as externalip)
bitcoind.rpcuser=*******
bitcoind.rpcpass=********

bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332
bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333


Thanks in advance,
-SS
10  Bitcoin / Bitcoin Technical Support / Re: Operate Bitcoin Core on a laptop with restricted storage capacity on: September 23, 2023, 09:54:19 AM
Are there some recommended approaches for running Bitcoin Core on a laptop with constrained storage capacity? Is it possible to use an external hard drive as the data directory (datadir)? How does this setup work, and would I need to pay attention to?

Thank you in advance to everyone who responds to this question.

All what you said is possible, you can run it with a low storage capacity and you can use an external hard drive to have more capacity.

If you use your first option, then you need to prune your BitcoinCore, that means that you will only store a certain amount of blocks according the configuration that you specified.
In order to prune it, you just have to add the following line on bitcoin.conf file:
Code:
prune=10000
This would allow to store all blocks possible in 10Gb if you have 5Gb then use 5000, etc.

For the second option, using an external hard drive, you just have to add the parameter -datadir=$pathToStorage when running the Btc Core:
Code:
bitcoind --datadir=/mnt/data
You can also add that parameter on the bitcoin.conf file so you'll not have to specify it every time. (Use your own /data path)
This article does it with a rapsberry:  https://ishaana-misra.medium.com/using-raspberry-pi-to-run-a-full-bitcoin-node-a30c6339b06e
The setup is the same so you can follow the part where she uses the parameter datadir:
 - Setting Up The External Hard Drive
 - Installing & Running The Bitcoin Core

Hope this helps Smiley
SS
11  Bitcoin / Bitcoin Technical Support / Re: Is it possible to accelerate this transaction? on: September 23, 2023, 09:37:59 AM
Maybe you already tried but, try to talk to the customer support team of that services and see if they can do a CPFP as I see that RBF is not enabled on that tx.
I would be very surprised if that worked, but it doesn't hurt to try. I am yet to meet a knowledgeable support rep on a crypto casino that has something more than a very basic understanding of how Bitcoin and crypto works. It would require Gamdom to play around with private keys, which they might not be happy about. It's hard to get centralized exchanges to do it for the same reason. And the question is, can they even do it? They might be working with a custodial service or payment gateway on their end as well.

Yeah I agree is not easy, but to try it, is free, even more if it's their fault because they have miscalculated the fees required. I think how they do is irrelevant, at the end, their service "complexity" should be transparent for the customer.

And another point, if it's not OP fault, if it's company fault I think they MUST do it as they "lost" or "block" their customer money because an error.

Note: I know it's not lost but let's be realistic 6sats/vb without CPFP and RBF and more than 450k tx in the mempool.... An infinite queue on the meempol == lost.
12  Bitcoin / Bitcoin Technical Support / Re: Is it possible to accelerate this transaction? on: September 22, 2023, 07:24:01 PM
I recommend you to just spend that transaction. Create a new transaction using the one that is stucked and use a hight fee (enough to pay for both tx), this is called CPFP.
He can't do that because he is using Cash app, a custodial service. CPFP doesn't work in this situation because Cash App doesn't give him access to the private keys. On top of that, another centralized service (the casino Gamdom) sent the transaction, so he doesn't control the change address either.

The fees for this transaction can only be increased by Gamdom, and I don't think that's something they do. Nevertheless, it's a pretty bad estimate of Gamdom to use such low fees when they sent the transaction weeks ago. 

Oh, thanks for the clarification, I did not read all the posts.
Well, he said he's new on crypto. Lesson learned, NOT YOUR KEYS NOT YOUR COINS.

Maybe you already tried but, try to talk to the customer support team of that services and see if they can do a CPFP as I see that RBF is not enabled on that tx.


Ah and... don't get frustrated, we all make mistakes in the beginning and we have all been through similar things so... take it easy Smiley .
13  Bitcoin / Bitcoin Technical Support / Re: Is it possible to accelerate this transaction? on: September 22, 2023, 04:12:32 PM

https://mempool.space/tx/3a88b7e9edb449562f6a62e05e763d3890b7ffb52b5e8d0c21a19a2f1b2bd042

And are any of the so called accelerators legitimate things or is that all just a scam? New to crypto sorry

I recommend you to just spend that transaction. Create a new transaction using the one that is stucked and use a hight fee (enough to pay for both tx), this is called CPFP.
14  Bitcoin / Bitcoin Technical Support / Re: Decrypt Lightning Node Client Traffic on: September 21, 2023, 05:04:21 PM
It looks like it's a non-standard authentication method, not using TLS but it is using keys on the secp256k1 curve and a form of ECDH called Noise_XK.

In order to get the session key that is generated by this algorithm which encrypts the traffic, you'll have to find a utility which allows you to replicate the Noise_XK key exchange process.

Thank you!

It looks like it. If anyone knows how to do it it will really help.

SS
15  Bitcoin / Bitcoin Technical Support / Re: Decrypt Lightning Node Client Traffic on: September 21, 2023, 07:40:27 AM
I just read though and did a quick search of
https://github.com/lightning/bolts/blob/master/07-routing-gossip.md
and did not see anything mentioning encryption.

Odd, but you have to have some certificate someplace that you send your side to when they connect.

Didn't check, IS it even encrypted? I mean it's 'sudo public' information being sent.

-Dave



I guess it is, for privacy and security reasons.

https://github.com/lightning/bolts/blob/master/08-transport.md

As far as I understand from here, it uses the node ID (a pubkey) to encrypt the traffic.

SS
16  Bitcoin / Bitcoin Technical Support / Re: Decrypt Lightning Node Client Traffic on: September 20, 2023, 07:24:27 PM
Assuming you are running the node and using LND as an example in the lnd.conf file you can specify the TLS certificate used:
https://docs.lightning.engineering/lightning-network-tools/lnd/lnd.conf

Not perfect and you won't get everything but anything connecting to your node can then be read.
As a cheat, if you just want to see what is going on in general you can setup a bunch of nodes that just talk to each other and read all of their traffic.

-Dave

Hi Dave,

Thanks for your answer!

Checking the link you provided, I'm only able to see configuration for the TLS certificate on RPC connections.
I don't know if the node will use the same certificate, but I'm looking to read the p2p network messages (gossip protocol). I mean, the messages that are sent between the nodes.
17  Bitcoin / Bitcoin Technical Support / Decrypt Lightning Node Client Traffic on: September 20, 2023, 08:57:33 AM
Hi,

I need to sniff traffic from the p2p Lightning Network and check it using Wireshark or some other package capture program.
The issue here is that the traffic is encrypted. Is there any node implementation that has some option to extract the key used for encrypting that traffic?

If you know of any other solution to take that traffic and be able to read it without extracting the key from the node for example doing some man in the middle between the Node and the P2P network please, let me know.


Thank for reading!


Best Regards,
SS
18  Bitcoin / Development & Technical Discussion / Re: [NOT A DISCUSION ABOUT INCREMENTING BLOCK SIZE] Bitcoin blocks size on: June 25, 2023, 09:15:21 AM
The maximum block size is defined in src/consensus/consensus.h.
Code:
/** The maximum allowed weight for a block, see BIP 141 (network rule) */
static const unsigned int MAX_BLOCK_WEIGHT = 4000000;

If you search for WITNESS_SCALE_FACTOR (which is also defined in the above file as 4), you'll notice it also appears in other parts where there are bytes that need to be measured. In other words there isn't a parameter equal to 1 MB, there's just the above, and the code takes into account the fact that 1 byte is equal with 4 weight units.
Your question has already been answered here: Block size limit in source code

Hi thanks both for your answers. I appreciate it.


Regards,
SS
19  Bitcoin / Development & Technical Discussion / [NOT A DISCUSION ABOUT INCREMENTING BLOCK SIZE] Bitcoin blocks size on: June 21, 2023, 07:40:37 PM
Hi,

Could someone point me to the code file where the block size is defined?
I need to know the theoretical max block size if we ignore SegWit, etc.

Thanks in advace.


Regards,
SS
20  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core RPC remote not Working on: June 18, 2023, 12:22:36 PM
Replace value of your rpcbind to 0.0.0.0 which makes RPC accessible from other device. And IIRC value of bind should be changed as well.

Changing rpcbind to 0.0.0.0 worked. Thanks!
Pages: [1] 2 3 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!