pull down to refresh
0 sats \ 2 replies \ @aliceandthewonderland OP 10h \ parent \ on: A question from a complete paranoiac person privacy
I'm seriously considering switching to Graphene
I don't understand what error does it show, is your wallet fully loaded, by "fully loaded," I mean if you have the same address in electrum?
41 sats \ 1 reply \ @aliceandthewonderland 16 Jan \ parent \ on: The Future Of Bitcoin Lending? bitcoin
Turing-complete smart contracts, enabling the creation of various DeFi applications on top of it
imo, very negative. extremely negative. It only ends up creating massive attack surfaces, unnecessary complexity, and systemic risks that undermine the core value proposition of sound money. simple, reliable Bitcoin script is all you need for secure value transfer - anything more complex just introduces vulnerabilities.
I view Bitcoin not as a purchase, but as a way to store my energy's value outside of the corrupted fiat currency system.
when sending sats from Phoenix to Zeus with a routing hint included, Zeus is able to receive the sats. I'm not sure why thanks anyway
Have a look in your Phoenix wallet > settings > payment channels. Have a look at the Funding TX and see if it spliced out on that LN payment.
Yep, you were right, I did splice out some funds, and it led to dropping channel size. Thanks it helped me a lot to study.
If Phoenix had less inbound liquidity when LNproxy tried to forward the payment, it could have caused the transaction to get stuck. LNproxy might not have been able to fulfill the payment due to Phoenix’s reduced capacity, causing the HTLC to timeout and triggering the refund.
I exported the Phoenix wallet log from the event on Jan 10, 2025, UTC, to see whether it attempted to process the payments. The log indicates that it indeed tried to execute payments through MPP for amounts of 175,000 sats and 2 of 87,500 sats. But it appears that the LN proxy failed to complete these transactions, resulting in keep Phoenix purging incoming payments multiple times like image below, which ultimately led to the rollback of the transactions and the subsequent release of the HTLC by Strike.
Indeed it seems you are right. Not sure if this is accurate, but this is my reasonable scenario thus far.
So, the sudden drop in your inbound liquidity (from 470k to 250k sats) could have been due to Phoenix closing and reopening channels to manage fees or balance liquidity. This isn’t unusual, but it can catch you off guard if you're not expecting it.
as mentioned by @OT, I found out that I did splice out some funds to on-chain, which explains the sudden drop in inbound liquidity.