-snip
Wygląda na to, że Hhampuz zaczął już tagować uczestników. Widzę, że zdecydowałeś wycofać się z kampanii. Nie zapomnij napisać do yahoo, że wycofujesz się z niej, bo nie masz na razie możliwości usunięcia swojego posta z aplikacją. @cygan też się najwidoczniej wycofał. Powodzenia panowie ze znalezieniem kampanii. Pamiętajcie, że nie dostaniecie się do tych lepszych, jeżeli nie będziecie pracować "w okresie bezrobocia". Dziękuję za gratulacje i również gratuluję  |
|
|
|
Really interesting, but still a rather "useless" security protocol if your private key has already been compromised. The thief could wait the blocktime out, and you wouldn't even know you were compromised until he broadcasts the redeemscript.
It's still a good security enhancement if you realise that your wallet is compromised. It gives the victim some time to react. There is no other effective method of defense if the key is compromised. The only thing that comes to my mind is a multisig setup but that's more complex and needs to be prepared properly before the attack. |
|
|
|
2 tematy o tej kampanii. Myślę, że warto być na bierząco będąc w livecoin 2.0. Gadają o tagowaniu uczestników, o banowaniu managera za plagiat, o włączeniu na czarną listę uczestników przez yahoo i wiele innych.
Tagowanie uczestników raczej nie będzie miało miejsca, ale yahoo opublikował listę osób, które trafią na jego czarną listę, jeżeli nie wycofają się z kampanii w ciągu 72 godzin. @cygan, @wwzsocki co zamierzacie zrobić? Pytam z czystej ciekawości. |
|
|
|
If he has the private key, he can simply sign another transaction without locktime and broadcast that one instead.. ?
What I thought was a way to freeze a specific tx, not the private key, in the OP's case blocking the 1 btc transaction he made from being spent.
It is possible to create a time-locked address from which no one will be able to spend before a specific date or block height is reached. It looks like only Coinb.in supports this feature. Take a look at this guide or read TryNinja's TL;DR. |
|
|
|
Glad to see Ledger have finally caught up with Native SegWit, but in all honesty, it's pretty disappointing it has taken them this long.
Trezor still doesn't support receiving to native SegWit addresses in their web wallet. I'm surprised that Ledger has introduced it before Trezor, but it seems that they haven't tested it well enough. |
|
|
|
Have the watch towers not yet activated to prevent this stealing of funds?
Watch towers have to be configured manually for each node on a separate machine. They have been recently introduced in the latest LND update so that's why they haven't been mentioned in the article. It also looks like the sending capacity in Eclair isn't that accurate: I can't send all at once, but I could send multiple smaller payments.
Sending capacity = Current channel balance - total can receive - minimum channel reserve (that's how I would calculate it, but I am still missing something). Each time you send a transaction multiple routes are calculated and the most efficient one is chosen. Total possible amount to send differs for each destination node. The problem you described is a liquidity issue; it's not Eclair's fault. |
|
|
|
-snip
What wallet had you been using before you lost your seed? Did you use a passphrase? What kind of address was it? (legacy, nested or native SegWit). While importing a seed, you have to choose a type of address and derivation path. That's why I'm asking those questions. There is no point in sweeping the current seed if importing it doesn't re-create the original wallet. |
|
|
|
-snip
The previous command might have also affected the latest version's files. Try re-installing it by following the same guide. Old files have been removed so there shouldn't be any conflicts anymore. |
|
|
|
-snip
Take a look at the following image.  The second address is not displayed because it belongs to you (it's clearly a bug). According to the block explorer, you combined two inputs and sent 1 BTC to 3KodMvBcdXdUfNMV5v8Fe1rvrzRibPzoZw. The change has been sent to bc1qssyu9sxgczgvtdxt3jctf7kxf4gh50qx2zxp0d. Due to some bug, you can't see the balance of your change address. It should be fixed by Ledger soon. I heard that there is a risk involved of exposing the private key. Never tried it though.
You don't have to expose your private key. Electrum allows you to create a new wallet using a hardware device. If you don't connect the device then Electrum will act as a watch-only wallet. |
|
|
|
-snip
Are you sure that you have sent 1.52 BTC? It looks like bc1qssyu9sxgczgvtdxt3jctf7kxf4gh50qx2zxp0d is a change address which belongs to you. It means that you might have sent only 1 BTC by an accident. Check the account or wallet from which you sent coins; they should be there. |
|
|
|
Anyway, updating the ledger live will be enough or we need to do anything else to generate the native SegWit?
According to this page, you have to create a new account. I can't give you any further details since I don't own any Ledger device anymore. But anyway, you don't even need ledger live, as you can generate native segwit addresses using Electrum+ledger nano. Much better control over your funds also.
Some people don't want to use Electrum for some reason. This thread is targeted at people familiar only with Ledger Live. |
|
|
|
|
Try the following command to remove the old version of electrum
sudo python2 -m pip uninstall electrum
It might not work if you installed it using a different method. What command did you use to install the latest version?
|
|
|
|
Ledger has just released a new update in which support for native SegWit addresses has been introduced. What are the benefits of using such addresses? - lower transaction size, - smaller QR code, - case-insensitivity. Note that some services might not be able to send to native SegWit addresses. If you need full compatibility and still want to save some money on fees then use nested SegWit addresses (they start from 3). |
|
|
|
So, prior to posting it would be nice to see what your post actually looks like, once posted, specially if you are including links, images, tables.. so on.
Keep in mind that as a newbie you won't be able to some of the text formatting features (including images). You can lift some of these limitations by buying a Copper rank. |
|
|
|
In a MultiSig address to spend from a specific address, the only way I see is that - to go to the coin tab and spend from there but problem is how do I spend all the coins in one transaction from that address instead of picking each input one by one?
I don't see any reason why you would be forced to pick each input one by one. Can't you just go to the Coins tab, press CTRL+A, right-click and select Spend? It seems to be working for me. Alternatively, you can select a few inputs by holding CTRL and pressing the left mouse button. |
|
|
|
BitMex Research published an interesting article in which they examine all possible Lightning Network channel closure scenarios. -snip
I don't mind. I was thinking of re-creating the Lightning Network Discussion thread but it would have to be self-moderated. I don't want to be accussed of keeping the discussion biased. |
|
|
|
After January of 2018, wearing an avatar is an indicator of constructive users.
It isn't. It would have been if merit airdrop had not occured. There are still plenty of old accounts which are in control of users who are spamming in Altcoin boards and Bitcoin Discussion. |
|
|
|
2.5.Encryption
You can encrypt the wallet with BIP38, if you want. However, if you do not carry it around with you everywhere so you might lose it, it should not be necessary.
Encryption should be recommended even if one does not intend to carry around the paper wallet. There is always a slight chance that it might be found by someone else. Of course you can also try to memorize your private key to save ink and paper  Remembering a 12 word seed with a passphrase would be much easier. |
|
|
|
That being said, I'm not trusting Eclair with any significant amounts, as I have no way of knowing how secure it is.
You should be fine as long as you set up backups to Google Drive. They are automatically encrypted. Mobile wallets can be considered more secure than dedicated nodes since they are not reachable at all times (funds are not stored in a hot wallet). As for the timelocks, I have already explained them here. |
|
|
|
1c. I seen that Electrum support send to multiple addresses at once and even manage to make that kind of transaction in testnet ( without leaving any dust ) but I am not brave enough to do it with my money.
This would be the the best choice. There is nothing to be afraid of as long as you control both addresses. Press Send and fill the Pay to box like this: Address1, amount
Address2, amount Don't forget about comma between the address and the amount and make sure to enter Address2 in a separate line. Don't overpay for a transaction. Check the current recommended transaction fee here (look at sat/byte) 3. As of transfer forks can I do it later or even leave them as it is until I research things further.  ? Yes, you don't have to spend them right after moving BTC. |
|
|
|
|
Show Posts
