Sent money to loop address by mistake #2

[valiantgroves-design]

Good day,
I made a loop request for ‎‎0.27250000 but accidentally instead of using my address for forward I paste loop address that responsible for loop btc distribution.
txid: bc1p7y3xz8zw4cs7daut0qnl86fvmp5kz58t6vx900kck85aau4zh4xqvqrlma
address I used by mistake:
bc1px7ym9uvzsrrnyxhs97s2y3s03h89jjyjf42x2vw3wx3xd8shz5msq3z245

similar issue link: https://github.com/lightninglabs/loop/issues/1062

my current loop version:
loop version 0.31.8-beta commit=v0.31.8-beta commit_hash=

address for return: bc1q23vf4cchvdrtd9qzv7kpewu8twxsy4qs4ele0d

swap info:

{
    "amt": "27200000",
    "id": "0523d0f1d0a00657c73e0cccb35f7d15ce2b9d5e14916bccc60741208856d250",
    "id_bytes": "0523d0f1d0a00657c73e0cccb35f7d15ce2b9d5e14916bccc60741208856d250",
    "type": "LOOP_OUT",
    "state": "SUCCESS",
    "failure_reason": "FAILURE_REASON_NONE",
    "initiation_time": "1776991900147744777",
    "last_update_time": "1776994028287386302",
    "htlc_address": "bc1p7y3xz8zw4cs7daut0qnl86fvmp5kz58t6vx900kck85aau4zh4xqvqrlma",
    "htlc_address_p2wsh": "",
    "htlc_address_p2tr": "bc1p7y3xz8zw4cs7daut0qnl86fvmp5kz58t6vx900kck85aau4zh4xqvqrlma",
    "cost_server": "27243",
    "cost_onchain": "113",
    "cost_offchain": "111755",
    "last_hop": "",
    "outgoing_chan_set": [
        "1036478825238167553"
    ],
    "label": "",
    "asset_info": null
}

[hieblmi]

Thanks for raising an issue, will take a look.

Could you please explain how it happened that you specifically used address bc1px7ym9uvzsrrnyxhs97s2y3s03h89jjyjf42x2vw3wx3xd8shz5msq3z245 by mistake? Why did you select it?

[valiantgroves-design]

@hieblmi
There is was high network load and I was waiting and watch previous block from loop out to come out, that one address was copied to watch through chain explorer

[alexbosworth]

this is tricky for us to support, do you have any ideas about how you can change your process to avoid this kind of error? anything we can do to help you avoid it?

[valiantgroves-design]

@alexbosworth
I fell really sorry. It's hard for me to feel so dumb and asking your team for help every time. I'm going to automate my actions with lightning and this would end my mistakes.
Anyway I hope this is my last issue ticket.

[levmi]

Hi valiantgroves-design, don't beat yourself up or feel dumb! We just want to help you avoid the mistake in the future and/or help you have a better experience with Loop. Anything that you could tell us about your setup or use case would be helpful for us so that we can better build Loop to meet your needs. For instance, we do have built in automation flows. Potentially we could work on fitting those to your needs. Any context is appreciated.

[valiantgroves-design]

@levmi there is nothing especial in my actions from other loop users so there is nothing that would help me or your team to make changes. The best you could do is to create loop function that would return btc without your participation.
That's it I have nothing more to add.

[alexbosworth]

ok the sweep command is again

loop out sweephtlc --outpoint 61f786f36f4faa3dea43f6cf83ac7eca31291111ab389b6223f13078624b8b70:0 --htlcaddr bc1p7y3xz8zw4cs7daut0qnl86fvmp5kz58t6vx900kck85aau4zh4xqvqrlma --feerate <fee_rate_sat_per_vbyte> --destaddr <your_dest_addr>

please don't make more mistakes and do not delay safeguarding your process, it may no longer be possible to return the funds as the service evolves

[valiantgroves-design]

Understandable, have a good day.
Sweep has been done.

[hieblmi]

@valiantgroves-design would you be interested in an instant loop out mode?

It would allow you to pre-commit to on-chain funds, and then when the need for a swap arises execute it instantly.
So you wouldn't have to wait for on-chain confirmations after swap execution.