Show Posts
|
Pages: [1] 2 3 4 5 6 7 »
|
Thank you for your reply. I think that I got it now, just one small remark to my initial post: In my post I wrote that the transaction will go back to the mempool after the chain that included my TX "lost". I think this is not 100% correct, because for the "winning chain" it never left the mempool. So in worst case for me it will look like it was send back to the mempool and in worst case "1 confirmation" will change to "unconfirmed" but in reality nothing changed, it was just not included into the next block. I think I got it now
|
|
|
There is something, I don‘t fully understand about closing a lightning-channel and I would like to ask you guys, for some help/clarification.
Lets assume the following situation: I open up a Lightning-Channel and load it with some Satoshi. After a while, I want to close that channel. Closing a LN channel requires an on-chain-transaction. Lets assume, exactly at that moment, there is a chain split. Two miners find a block at the same time. One miner adds my transaction to his block, the other doesn't. At this moment, I will see 1 confirmation of this transaction in my wallet, right? Lets assume, the other miner „wins“ at the end and the blockchain will be reorganized. This means, my transaction will go back to the mempool, right? So in my wallet, I will see this transaction as „unconfirmed“, I guess. Normally, my transaction will be included in one of the next blocks. But lets assume the TX fee was too low. I guess, then the TX will stay for a certain time in the mempool but after some weeks will be wiped out. Does that mean the settlement transaction will be undone and the coins re-appear in my lightning channel? Can I always do a RBF (replace by fee) in this case?
|
|
|
Nee Peter Toddler hat s eigentlich ganz gut erklärt und es ist eher ein Problem für LN usw. , 2nd layer apps die nicht x blocks warten können , wolln usw. Um einen LN Channel zu schließen und auf den Mainlayer zurückzuspringen braucht es aber auch paar Bestätigungen. Ich sehe da für LN überhaupt kein Problem. Wenn sich die Mainchain aufspaltet, ist das oft innerhalb von 1-2 Blöcken wieder reorganisiert.
|
|
|
CEO einer IT Firma, der auf so billigen FUD reinfällt und sich öffentlich blamiert. immerhin 200k profit, obwohl am lokalen bottom verkauft. wenn dann im laufe diesen jahres der kurs auf 200k pro btc gestiegen ist, wird diese Pressemitteilung sicher noch mal ausgegraben werden... die werden sich noch ganz schön ärgern, 100 btc für nur 200k profit verkauft zu haben. Ich glaube er ist noch nicht so lange dabei. Die, die schon länger Bitcoin besitzen sind da schon abgehärtet gegen diesen täglichen FUD. Aktuell auch jetzt gerade was CSW wieder abzieht, es wird nie langweilig.
|
|
|
Just one last follow-up on this topic. Finally, it worked and I was able to transact those 30000 sats. Conclusion: BlueWallet was working just fine. I think that the assumption of @Rath_ was correct If the receiver has more than one channel, your wallet might have found a path to a channel which had only outgoing capacity. The receiver opened some more receiving-channels and my transaction went through. Thank you all for your help!
|
|
|
Are you saying you don't have an email address with a fake name? You think my name is Loyce Valenzuela? What? This is NOT your real name No its just ... I can do that but ... I'm too lazy, shame on me
|
|
|
No, sorry. I'm not a fan of telegram. As you say, too many PM's and scammers. I was also considering sending them an e-mail but i don't want to doxx myself.
|
|
|
I've had a discussion yesterday in another forum about this issue and we found out, that BlueWallet in combination with iOS produces this error. BlueWallet on Android was working fine. Weird.
|
|
|
It's a private user with his own node
|
|
|
Oh thanks, but the receiver is asking for 30000 sats and my BlueWallet refuses to send and I cannot guarantee that I will be able to send you those sats back in small chunks.
|
|
|
@LoyceV: Success! Don't spend all at once So I know it's the liquidity on the path.
|
|
|
Thank you for your help I believe that BlueWallet has a separate error code for lack of routes. I think in that case it says "Payment in transit" Quote: "This state happens when your payment was sent to the network, but it didn't get a response back." But I like the idea that maybe the liquidity on route to the recipient was not sufficient. That is one possible explanation. @Rath_, @LoyceV: If you agree, feel free to drop me a PM with an invoice of lets say 500 sats and I will try to send it to you as a test and a gift
|
|
|
Hello,
I have an issue with BlueWallet for iOS and don't know how to fix it.
Every time, I want to send a small amount of sat's on the lightning network, I get the following message: "API error: Payment failed. Does the receiver have enough inbound capacity? (code 10)" I know for sure, that the receiver has enough inbound capacity so this can be ruled out.
I'm not running my own node so the LN channel is custodial (standard settings after installation).
I have no idea what I can do now to move my funds. Did someone experience this before? Any advice for me?
Thank you guys.
|
|
|
Check the block explorer carefully: INPUT on 4/13/2019 9:03:22 PM +00:00 was a reward based on strong hands programme. But then you transferred your funds to some other addresses on 4/19/2019 5:47:30 PM +00:00.
|
|
|
Ich benutze die Bitcoin Core Wallet und habe in die Wallet einige Adressen importiert, um eine Watch-Only Wallet zu bekommen. Leider gibt es Probleme mit dem Zeitstempel: Wenn ich mir die Historie über den Button "Transaktionen" anzeigen lasse, wird für alle mit den Adressen verbundenen Transaktionen dasselbe Datum und Uhrzeit angezeigt. Das Datum und Uhrzeit entspricht dem letztmaligen Eingang von einer der importierten Adressen. Komischerweise: Wenn ich über die Konsole gehe und mir die Transaktionen über anzeigen lasse, sind die Zeitstempel korrekt bzw. unterscheiden sich gegenüber einem Vergleich mit z.B. blockchain.info nur um weniger Minuten. Jetzt habe ich im Netz mal nach diesem Fehler gesucht und da auch was gefunden was in diese Richtung geht: https://github.com/bitcoin/bitcoin/pull/12024, allerdings ist das aus 2017! Nur um sicher zu gehen: Ist das ein Bug in Core?
|
|
|
Oh dear, there is a bug in the Electrum-Wallet for macOS. When I try to export the private key of an address, there pops up an error message: "bytes must be in range(0, 256)"This is very sad, because I wanted to transfer the coins from the web wallet to a more secure offline generated address (paper wallet)
|
|
|
Thank you guys. It all cleared up, it was my fault, my PGP Key for e-mail encryption had expired.
|
|
|
Sorry for replying to an old thread but I have the exact same problem right now.
I'm not receiving a confirmation link. Its also not in the spam folder. I contacted Bitfinex, they told me to change the e-mail address but this will lock my account for withdrawals for 5 days. I know the issue is not on my side.
Do you guys have issues with withdrawals at Bitfinex right now?
|
|
|
It's getting exciting, go BTR!
|
|
|
|