pull down to refresh
0 sats \ 4 replies \ @charonnakamoto OP 12 Jan \ parent \ on: Need help with balancing a lightning channel using loop-out feature lightning
LN BTC to on-chain worked here smoothly. However, I tried to do on-chain to LN. But I haven't received the funds on LN despite six on-chain confirmations. The person from MiddleWay on Telegram has been extremely helpful but cannot identify the root cause of the issue. Now, I am having to figure out the refund mechanism. So, not a great experience there.
As i said, but seems that you do not understand.
To receive correctly into your LN channels you MUST provide route hints. Otherwise who is sending you the sats over LN cannot see your channels.
The wallet interface you are using for your private node MUST insert route hints.
reply
I am not using my private node infrastructure for this.
I was trying out swaps using the link you provided, but the swap from mainchain BTC to Lightning BTC failed. Now, I have submitted a refund request. The LN invoice was raised from Wallet of Satoshi, a custodial LN setup. I am sure their liquidity management is better than mine. The on-chain transfer to swapmarket was confirmed more than six times(Tx ID: c80741d93d885609d3e0cc7f28d94d7d0c7dd0e72b6b4a60fefb32cee0d6afad) .
I hope I have made myself clearer.
reply
It seems I need to wait 24 hrs before I can get the refund. It has been a frustrating experience, but the middleway person has been constantly in touch and giving his points of view. But he is also far from RCA, except for blaming my transaction on bad luck. Will inform if the issue gets resolved in 24hrs and I get my sats back.
reply
The refund did not work even after 24 hours. However, the middleway(swap service provider working with Boltz software in the backend) person kept me updated on the process throughout. I helped debug the issue a little by sending screenshots of the console while requesting a refund. He had to raise a GitHub issue and tried tweaking this manually, and it worked. I finally have my sats back. Otherwise, I would have had to wait 7 days(block height till timeout). I do not know what technically happened in detail, but I learned a lot from swaps in the process.
In summary, if a user's feedback for production software leads to a GitHub issue, I conclude that swaps(at least on-chain to LN) are not ready for prime-time. Though I appreciate the middleway person sticking with me(having some tough conversations) till the issue got resolved.
reply