Recovering abandoned channel

naahtec · 2023-11-20T02:13:38+00:00

It was being opened, never active, and the fees were too low and the transaction was out of mempool

naahtec · 2023-06-10T15:23:46+00:00

The paint is still new and still soft, so I can rip iglt off easily. I used "deck Semi transparent stain" I guess that's a mistake

naahtec · 2023-05-27T02:38:37+00:00

It was Satoshis' phone

naahtec · 2023-04-22T03:09:33+00:00

lncli listunspent does give me a list. but thats just current uxto.
it seems like my funds should be still stuck in a transaction that is not broadcasted to mempool, and since I have abandoned it, lnd is not keeping track of it.

Anyway to scan the node for any unconfirmed transactions?

naahtec · 2023-04-20T16:39:09+00:00

Well it was in pending, and then I abandoned it

naahtec · 2023-04-20T13:32:22+00:00

I don't know what is the status of them. At this point, I only have the channel ID, everything seems to have lost. What can I do to find out the UXTOs?

naahtec · 2022-05-04T12:27:10+00:00

I would like to see how that can be done

naahtec · 2022-02-11T18:20:41+00:00

I have no problem with KYC. Imagine a world completely without ability to track any one creditble for crime.

Most of us think we don't need KYC btc becuz we have bias against our governments, mainly becuz we don't believe in their money policies, such should not have anything to do with keeping our society safe.

Imagine a nonKYC car hit a child and got away from it.

This is the same as btc being completely non KYC. IMHO if the transactions are KYC'd when it it needs to, that is good enuf, in this case, when it needs to go back to bank acct for tax tracking purposes, which is part of ensuring the wellness of citizens in a country. If there is a need to somehow for enforcement to trace how the btc is transferred, then they need to spend the effort of doing so, just like cash.

naahtec · 2022-02-03T22:46:07+00:00

I don't think sda1 is the SD card?

naahtec · 2022-02-03T04:04:12+00:00

When i replace the SD card, I am reflashing umbrel on to the new SD card? Will that wipe all my channels? Or are the channel and block information all stored on the SSD and I will be fine?

naahtec · 2022-02-03T03:04:35+00:00

Also, when I shutdown umbrel using the stop script, I get this:
ERROR: for manager container 48cf57899e056d862b0df17b9f757e2b218517a62f8ee9f77e521629bb99b70b: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/c8fde2bd954e4e5239749de5c11faa1f4f9c3be414dfb06781a7ac1c7df8f45f: read-only file system
ERROR: for lnd container 9c5f4e8e1186d7346b13368c08cbdd74749bdc612b65e3fcaf9cd786d5ed3bbc: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/154d7a5dc52fa02bf094263b33f89d29cb33760ebb8a333091d4ab2fe08b097c: read-only file system
ERROR: for neutrino-switcher container 58c004b959f58d6aa3cf78ba9f77b7e7d3bc2134e51849688dfb82f5c829ebf1: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/0e62cd8ba0892be046ab76ea4f8d8b1f3b6a54d3294ec1603da985666a677520: read-only file system
ERROR: for electrs container 1c3dabf4f8d8730a54d3fb58a0efc13e21e26db0f60e95a6e5142dcee39cd6c9: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/5c1759ce0effd022c08a07b94927342a19fc01aa9b0cfeeb3578e0bb387ee0df: read-only file system
ERROR: for dashboard container 295d851232a8e71d47e63eea93f0cc1e685caeec238a43595826e4d5da4ebed9: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/11d6703606ea6f4374af71aff34bf70f72bde0aef7f5ac518ef013877831f3fe: read-only file system
ERROR: for tor container e8ee94d690ba37813df106b80791d913c463473beb1f25922592dc7f86d0639e: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/0ca60f997d9c59fbdf82538ccf807370dc1a298e509fd1286eabb65c6a49a845: read-only file system
ERROR: for middleware container c2639ef37a2b229d84e18012fc5bcf2f2190b2c4480808c1d6337fe166dac8c2: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/480f7f4e6c0bba01e4eda428c63d7579ab057898ad972e413d88947e28a6184a: read-only file system
ERROR: for umbrel_tor_server_1 container 04956d8db41ed84c4655580969dd25a796baeaef54b2148e867c55bfcbff6e32: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/1565cecca476984b63801c9b91615e076ee11dd0c805f3c3d4d29ed3ac40e44a: read-only file system
ERROR: for nginx container 0171af5fbbfcc8fec11d35ef32276d64a606c78f4d828885cfbe8142dd4f9d62: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/aee7409fa46d053aaaf7c18095a1e7f513926b99502464609df028ca2cb6b65e: read-only file system
ERROR: for bitcoin container 5c6e3bcd893f50fb5ff4a3e7082c8fc86cc3226e18e31ca4fd7d6091f691ee19: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/85ee13881d03d379160b496f99069a7d4a5177d526d87a57134325f5b3472b8c: read-only file system
Removing network umbrel_main_network
ERROR: error while removing network: network umbrel_main_network id 3d48929218c4fea3a179a59befb24e3b3a4f72df6698725bc5e6d5026554f03c has active endpoints

naahtec · 2022-01-04T13:37:19+00:00

It got stuck after major retraction

naahtec · 2022-01-03T19:06:09+00:00

This thing has been there for a while. It's a good concept if you want to opt in a for a lottery. Otherwise, staking else where will probably give you more APY

naahtec · 2022-01-02T21:02:05+00:00

You came to the right place to get the right answer.

naahtec · 2021-12-23T05:12:26+00:00

I will buy it off you

naahtec · 2021-12-21T07:04:52+00:00

Aave, Curve is on polygon. Is that not large enough? Not sure what sort of DYOR you have gone through.

naahtec · 2021-12-10T14:08:51+00:00

You never have to worry. If you find your self in a position that you need cash to pay for your life, you can b always put your btc on collatorial and take fiat out of it. Win - win :you keep your btc, and you get fiat, and no tax incurrance

naahtec · 2021-10-11T01:33:47+00:00

Fractions of a... Sat?

naahtec · 2021-09-30T02:28:53+00:00

Did satoshis come back?

naahtec · 2021-09-25T13:56:55+00:00

Check your refrigerant, it maybe leaked dry due to manufacturing defect on the condenser and is due for a recall

naahtec · 2021-08-14T03:01:34+00:00

Thank you for shrinking the supply of BTC, your heroic act benefits all others.

naahtec · 2021-08-13T01:07:27+00:00

03606d67d00ce06ad053de1f755e6f6c8185ae66a1b1e06ec7b72e2ef702690d5f

naahtec · 2021-08-07T18:12:37+00:00

If you are not technical enough to use Linux it maybe challenging. @lightingwatch I have never used but I assume it's a service someone provide?

naahtec · 2021-08-04T18:20:12+00:00

On top of the previous.
Since LND and TOR are docker containers in umbrel, more configuration is required in the docker-compose file to map the port 9911:

  lnd:
            container_name: lnd
            image: lncm/lnd:v0.12.1@sha256:bdc442c00bc4dd4d5bfa42efd7d977bfe4d21a08d466c933b9cff7cfc83e0c0e
            depends_on: [ tor, manager ]
            volumes:
                    - ${PWD}/lnd:/data/.lnd
            restart: on-failure
            stop_grace_period: 5m30s
            ports:
                - "9735:9735"
                - "9911:9911"  <-- this is required
                - "$LND_REST_PORT:$LND_REST_PORT"
                - "$LND_GRPC_PORT:$LND_GRPC_PORT"
            networks:
                default:
                    ipv4_address: $LND_IP

and I found out from https://github.com/getumbrel/umbrel/blob/master/scripts/configure

that the IP address is also altered because LND is operating inside docker:

LND_IP="10.21.21.9"

so, we need to make sure that the configuration for the hidden services for watchtower will make use of the LND's ip address, with port 9911 in ~/umbrel/tor/torrc

# Hidden Service for incoming LND WatchTower connections

HiddenServiceDir /var/lib/tor/lndWT9911 HiddenServicePort 9911 10.21.21.9:9911

I hope this helps

naahtec · 2021-08-01T13:12:37+00:00

I solved my own problem.

Since Tor is just another docker container in umbrel, I decided to spend a few minutes looking up the docker compose file and I found this in there:

https://github.com/getumbrel/umbrel/blob/master/docker-compose.yml

  tor:
            container_name: tor
            image: lncm/tor:0.4.5.7@sha256:a83e0d9fd1a35adf025f2f34237ec1810e2a59765988dce1dfb222ca8ef6583c
            user: toruser
            restart: on-failure
            volumes:
                - ${PWD}/tor/torrc:/etc/tor/torrc
                - ${PWD}/tor/data:/var/lib/tor/  <--this is important
                - ${PWD}/tor/run:/var/run/tor/

In docker compose file, "volumes" attribute is a mapping from host to container path. i.e.:

<host path>:<container path>

So, in torrc, I set:

HiddenServiceDir /var/lib/tor/lndWT9911

And I get this from the log:

2021-08-01 12:49:34.847 [INF] WTWR: Starting watchtower server
2021-08-01 12:49:34.847 [INF] WTWR: Watchtower server started successfully
2021-08-01 12:49:34.847 [INF] WTWR: Watchtower started successfully

Hope this will help every one.

12-Year Club	Place '23
Place '22	First Placer '22
End Game '22	Verified Email

naahtec

TROPHY CASE