Manager: HhampuzNazwa kampanii: MyCryptoMixer.com Signature CampaignIle do zarobienia: Senior Member - $50 w BTC/tydzień, Hero Member/Legendary - $60 w BTC/tydzień Jakie rangi: 8x Senior Member, 10x Hero Member/Legendary Dodatkowe informacje: Minimum 20 postów tygodniowo. |
|
|
|
Okay so do most ppl also have two pins then?
Probably. It's more convenient. It's a pain to enter a complex passphrase on such a small device. I want to do the 25th Word with my current seed at the moment. Best way to do this? Do i want two pins or not?
The passphrase will be stored in the Secure Element just like your private keys if you decide to use the secondary PIN. If you are comfortable with that then go for it. |
|
|
|
Has this been addressed before and I don't seem to find it, or is it just me having trouble with my computer?
It seems that Suite saves label related data to a different folder on Dropbox. I am not sure but you might get all of your labels back if you move/copy all the label data to that folder. The default location is "Applications/TREZOR/" while Suite saves to "Applications/TREZOR/Apps/TREZOR/". |
|
|
|
I'm curious but has anyone here done this? [...] It could be capital or lowercase as well?
Yes, you can use both capital and small letters. Quite a few people here use passphrases. Now if someone has your seed, and then need to crack the last word... wouldn't that be very hard?
That's the whole point. In fact, it is impossible to tell if you are using a passphrase. You could leave some small part of your funds on the non-passphrase protected account to mislead potential attacker. Now could I actually add a 25th Word right now to my nano ledger s? But im concerned about making a mistake though... but its simple right? Or I would need a completely new seed to do this?
You don't need a new seed to set up a passphrase. Here's a guide for Ledger Nano S. You can either enter the passphrase every time you connect your device or attach it to a separate PIN. If you ever need to recover your coins using, for example, Electrum, you will have to enter your passphrase as an additional word of your seed; not your PIN. The additional PIN is just for the convenience. |
|
|
|
So, I was supposed to be able to receive sats, at least, up to the amount of outbound liquidity the other node has to me, right?
Correct. That would be the maximum you could receive through that channel. And if someone else, other than the person who opened the channel with me, tries to send sats to me, it's never granted that the route can be done. That might happen if, for some reason, between the sender and me, there is some break in the routing, yes? Is this accurate?
There could be no route at all between your nodes or some node in the path might suddenly stop responding or the payment could be too large for a single channel to handle. The last one can be mitigated using multipart payments, but most wallets don't support them. What if there is a route but it needs to go through many many nodes, does that has any influence in the time the sats takes to be available on my side?
Yes, it does. Most of my Lightning payments were instant while others took under 10-15 seconds. Some payments took even longer time, but it didn't happen too often. |
|
|
|
First of all, is the term liquiddity the same as capacity?
You can use them interchangeably in this context (inbound/outbound liquidity/capacity). 1 - Do I get inbound capacity/liquidity when someone simply opens a channel with me?
Yes, but it's also more complicated. See the last answer. And an extra question is if this work exactly the same way for outbound capacity. If so, the above 2 questions also answer to the case of outbound capacity/liquidity.
You get outbound capacity when: 1) you open a channel with someone 2) someone opens a channel to you and sends you some coins or routes a payment through you. I have someone that opened a channel of 100k sats with me (his reserve is 1k sats) but he didn't send any sats to me neither I did to him and I can't send sats from my wallet in my phone into the wallet I have on my laptop connected to my node. The error is always the same: "Does the destination has inbound capacity??"...
While your channel has some inbound capacity now, all incoming payments have to go through the node which opened the channel to you. You are also limited by the liquidity of other nodes in the route. |
|
|
|
Manager: ZweiNazwa kampanii: WOLF.BET Signature CampaignIle do zarobienia/tydzień: Hero Member - 0.00015 BTC/post, Legendary - 0.00020 BTC/post Jakie rangi: 15x Hero Member, 15x Legendary Dodatkowe informacje: Maksimum 40 postów na tydzień; minimum 15 postów tygodniowo, w tym maksymalnie 5 postów w lokalach. |
|
|
|
But you are saying good chance after updating the firmware now to 1.6.1, then won't be another one for at least 6 months right?
No one knows. If a critical vulnerability is found, Ledger will probably release another update as soon as possible. But if you don't do an update you are still pretty safe from like what happened with that person who years ago didn't do any update for two years and could no longer update the firmware anymore because it was too old?
Such a situation shouldn't happen anymore. Old firmware was not able to work with Ledger Live which replaced the Chrome extension. Users were not able to update their firmware to the version compatible with Ledger Live once the Chrome app was shut down. Ledger offered replacement devices afterwards. So I should first update ledger live first... without my nano ledger s connected to it... right? [...] Or its always better to do ledger live first?
There is no reason why you should disconnect your Ledger during Ledger Live update. It shouldn't matter which one you update first. |
|
|
|
Manager: TalkStarNazwa kampanii: CoinBene Signature CampaignIle do zarobienia/tydzień: Full Member - 0.0013 BTC/tydzień, Senior Member - 0.0023 BTC/tydzień, Hero Member/Legendary - 0.0035 BTC/tydzień Jakie rangi: 5x Full Member, 5x Senior Member, 5x Hero Member/Legendary Dodatkowe informacje: Minimum 25 postów na tydzień, w tym maksimum 10 w sekcjach lokalnych. |
|
|
|
|
Regarding the darkv0rt3x's case - it turned out that he had only an outbound channel to friend B. That channel required both sides to have a 546 satoshi reserve which means that he should have been able to receive about 454 satoshi through that channel since he had sent a 1000 sat payment through friend B. He tried to receive as little as 50 satoshi without success. It seems to be a problem with friend's B node. Any other suggestions are welcome.
|
|
|
|
Can I send you a PM with my friend's node ID and channel ID?
Sure, go ahead. Do you want me to let the other people here know what might be possibly wrong after I have checked it? |
|
|
|
If I show you the channel he opened with me, can you tell if all the conditions are met or not?
I might be able to see the details of your friend's channels on the 1ml.com explorer once you provide me with your channel's id. I don't know if all information will be up-to-date. We can give it a go if you don't mind sharing it here. |
|
|
|
What am I missing and what is that reserved value I know it gets kinda locked when channels are opened?
There is an unspendable channel reserve. You need to spend about 2-3% of the channel's capacity before you will be able to receive anything. Theoretically, you should be able to receive slightly less than 30k sats through friend's B second channel since all funds are on his side of the channel at the moment. There might be some problem with friend's B channels. He might not have enough inbound capacity because of the reserve. |
|
|
|
So basically I have no choice but to accept this fee just because of the previous small transactions?
You can lower the fee to 1 sat/byte if the transaction is not urgent, but the fee will still be quite high due to the number of inputs. You can't do anything else about it. |
|
|
|
but the same payment with the same settings on Android app (4.0.2) has 0.00001968BTC fee!!! The app warns me that that the fee is too high!
Is your Android wallet different than your desktop one? If so then you must have received a few small payments to your Android wallet. Now, all of these UTXOs need to be combined which increases the weight of the transaction. |
|
|
|
A beta version of Trezor Suite is now available for anyone to download. There is also a web version (Trezor Bridge is still required). Here's an official blog post. There isn't much information about upcoming features. |
|
|
|
Ten manager od 777 jest jakis niepowazny ehh; pamietam ze byla jeszcze jakas bliźniacza kampania do 7
77? Kojarzycie moze?
Chodzi Ci o Bitvest? Manager jest dokładnie ten sam, więc nie będzie to dobra alternatywa. Skoro manager w tym poście nie napisał, że zostałeś przyjęty, to można spokojnie uznać, że odrzucił Twoją aplikację. Co do ignorowania prywatnych wiadomości, powodów może być kilka. Albo jest zasypany wiadomościami albo ignoruje wiadomości od osób, które dopominają się o rozpatrzenie aplikacji. |
|
|
|
It would probably be a good idea to have LN clients be able to split up invoices so a payment can go through multiple routes, and the transaction will only go through if all invoices are paid.
LND, c-lightning and Eclair already support multipart payments which allow to pay a single invoice through multiple routes without any additional effort needed from the user. |
|
|
|
What i do not understand is that for every incoming transaction LL displays a very large fee?
If you look up that transaction in a block explorer, you will see that Slushpool processed quite a few withdrawals in a single transaction. Each destination address (output) increases the weight of the transaction which makes it more expensive to spend. |
|
|
|
|
Show Posts
