bitcoin-tool VS litecoin

Download bitcoin-tool from https://github.com/matja/bitcoin-tool Compile it and follow the instructions

You can use bitcoin-tool to convert the key from Bitcoin WIF to hex, and then from hex to Litecoin WIF, then import into Electrum-ltc using p2wpkh-p2sh:T.... https://github.com/matja/bitcoin-tool

Obsolete, because it's not SegWit Try this: https://github.com/matja/bitcoin-tool

cd /usr/local/src curl https://github.com/matja/bitcoin-tool/archive/refs/heads/master.zip -O -L unzip master.zip cd bitcoin-tool-master make test <-- this compiles and tests the app cp -iv bitcoin-tool /usr/local/bin/

Also, https://github.com/matja/bitcoin-tool Written in a portable programming language

If you want to generate random keys, one at a time, and you have the knowledge and discipline to keep secure backup copies of all your keys, try bitcoin-tool https://github.com/matja/bitcoin-tool

There's a non-deterministic key generation tool, but only for people who understand how to make key-set backups, and when to make a new backup https://github.com/matja/bitcoin-tool Not suitable for engraving on metal

For many years, I have used bitcoin-tool for one-off Litecoin keys https://github.com/matja/bitcoin-tool

If you're using Linux, you might find this useful https://github.com/matja/bitcoin-tool

I use bitcoin-tool https://github.com/matja/bitcoin-tool But the same questions apply. How do you trust the C code in bitcoin-tool? I think if bitcoin-tool gives the same result as one of the javascript wallet generators, the developers of the different apps are unlikely to be conspiring

Open Source Litecoin is fully decentralized in the fact any one person could submit code into the network and as long as a majority of miners agree to that fork it will be implimented. This is similar to bitcoin.

Progress continues with the integration of Litecoin code changes into the v24 Bitcoin codebase. The month of May saw a major milestone with the resolution of all remaining functional tests for the pre-MWEB merge task. The code has been submitted for review here.

git clone https://github.com/litecoin-project/litecoin.git

"If upgrading to 0.21.2 after MWEB has activated, you must resync to download MWEB blocks." https://github.com/litecoin-project/litecoin/releases

I tried following this tutorial: https://github.com/litecoin-project/litecoin/blob/master/doc/build-osx.md

However, this serialization format seems to contradict with BIP 0144, which states: "if the witness is empty, the old serialization format must be used." also contradict the comments in the litecoin source code at https://github.com/litecoin-project/litecoin/blob/master/src/primitives/transaction.h

In order to add MWEB support to PSBTs, I first had to merge in PSBTv2 (BIP-0370), which can be seen here. I then defined the MWEB fields we needed to add, and added them to the PSBT data structures along with serialization and deserialization here.

A pull request has also been submitted for downloading and verifying HogEx transactions, MWEB headers, and the UTXO leafset bitmap. This covers steps 2 and 3 of the light client sync process.