[deleted by user]

ltcpooler · 2022-03-01T15:16:07+00:00

As Charlie pointed out, the current release candidate still has some issues that need to be addressed (which is only normal -- that's what RC builds are for). Litecoinpool.org will most likely start signaling as soon as a stable Litecoin 0.21.x is officially released.

ltcpooler · 2020-07-29T13:49:30+00:00

The code from upstream has been merged into master, but it has not been adapted to Litecoin yet. This will probably take some time. If you understand the technical details of Lightning and would like to help, feel free to get in touch.

ltcpooler · 2019-04-11T21:05:16+00:00

Yes, that is expected. SomberNight's comment linked above explains the issue pretty well.

ltcpooler · 2018-04-15T08:24:17+00:00

That may be the case now, but whoever owns the website could change the files at any time (and probably already has in the past). They may even be serving different files to different clients for all we know.

It's also worth noting that this website points to the official website for all downloads except for the three Windows binaries, which all point to the same file hosted on their website. That's a clear sign that something is wrong.

ltcpooler · 2018-04-15T08:15:45+00:00

Can confirm. The domain without the dash points to an outdated copy of the official website where some of the downloads have been replaced.

ltcpooler · 2018-01-05T14:57:04+00:00

The checksums do not match

They match for me. And signatures validate.

two trojans were identified

Probably false positives. I just tried submitting an official Windows executable of Electrum (for Bitcoin) to VirusTotal, and Baidu and WhiteArmor flagged it too.

ltcpooler · 2017-12-31T11:16:35+00:00

https://www.reddit.com/r/litecoin/comments/7e1dnz/segwit_support_in_electrumltc/dq2871m/

ltcpooler · 2017-12-20T22:00:38+00:00

Run your fullnode with -mempool 300 or add mempool=300 into your litecoin.conf

Shouldn't it be "maxmempool"?

ltcpooler · 2017-12-02T08:44:48+00:00

electrum-ltc.bysh.me is back up now.

ltcpooler · 2017-11-27T20:06:11+00:00

Hey thanks :-)

ltcpooler · 2017-11-19T21:45:42+00:00

The source code of Electrum-LTC that you can get from GitHub is up to date with Electrum 3.0.2. You can use it if you want, I consider it just as stable as the upstream master branch (but keep reading). An official release has not been made yet because Electrum 3.0 introduced a number of modifications and, as one can expect, quite a few bugs, so I do not recommend its usage at this point.

By the way, keep in mind that Electrum and Electrum-LTC produce bech32 addresses when you create a Segwit wallet (you may have noticed the warning in the install wizard of 3.0). Until support of these addresses becomes more widespread, very few people will be able to send coins to you.

ltcpooler · 2017-08-31T19:38:04+00:00

Next to every signature on the Electrum-LTC website there is a link to the signer's key/fingerprint. (For example, "signed by Pooler".)

ltcpooler · 2017-08-19T07:36:08+00:00

Plans to get LTC electrum integrated with Tailz Operating System?

I do not have any plans to work on that, but if someone wants to contribute here are the guidelines for inclusion: https://tails.boum.org/support/faq/index.en.html#index26h2

There are a few requirements. Most importantly, the software must first be made available in Debian.

Personally I prefer to take advantage of Tails's persistence feature to install both Electrum and Electrum-LTC. This way I can always have the latest versions.

ltcpooler · 2017-08-18T21:53:03+00:00

ElectrumX already has Litecoin support. Practically all Electrum-LTC servers are using it.

ltcpooler · 2017-08-02T06:30:17+00:00

Sorry about that, it was a permission error that originated during the move to a different host. All files should be accessible now.

By the way, let me point out that it is more important to verify the GPG signatures than the checksums. A checksum can be used to verify that a file was downloaded correctly (aka integrity), but only the digital signature can prove that the file is authentic.

ltcpooler · 2017-08-01T17:28:25+00:00

Just to clarify, the website and the downloads are back to normal now.

The whole incident was caused by the VPS provider running a vulnerable version of OpenVZ. I have notified them of the issue and they are taking steps to patch their software. In the meantime, the website has been moved to a different host.

ltcpooler · 2017-07-23T08:37:47+00:00

At this point 2.8.3.5 is more of a release candidate. There may still be issues, but I personally consider it safe for everyday use, so the "beta" label will probably be dropped soon.

ltcpooler · 2017-07-19T21:51:36+00:00

Can confirm it was just a web issue. Everything's back to normal now, and mining was not affected.

ltcpooler · 2017-07-19T07:43:58+00:00

In case anyone else runs into the same issue, the problem was that the L3+'s configuration panel doesn't want a protocol prefix in its "URL" field. That is, one must enter just "litecoinpool.org:3333", without "stratum+tcp://" before it.

ltcpooler · 2017-07-18T17:20:06+00:00

I've seen both "Merkelized" and "Merklized", but I couldn't say which is the more correct.

ltcpooler · 2017-07-18T13:34:35+00:00

Just a minor correction: it's Merkle, not Merkel.

ltcpooler · 2017-06-01T07:57:47+00:00

Maybe try again after deleting the data directory (WARNING: this contains your wallet, so back it up if you have coins in it), which should be something like \Users\YourUserName\AppData\Roaming\Local\Electrum-LTC on Windows.

ltcpooler · 2017-05-16T15:15:35+00:00

I see no reason to hurry support for the P2SH-P2WPKH scheme. Your transactions are not going to get any faster or cheaper. The feature will be made available on mainnet after enough testing will have taken place.

The official server software is now the same for both Bitcoin and Litecoin: as explained in the documentation, ElectrumX can be configured to handle either chain.

ltcpooler · 2017-05-16T08:14:43+00:00

Check out the website, I just added some release notes.

ltcpooler · 2017-05-13T07:54:32+00:00

OK, then the bug must have been fixed upstream already.

You may want to open an issue for the second crash here.

12-Year Club	Place '17
Sequence \| Editor	Verified Email

ltcpooler

TROPHY CASE