pull down to refresh
0 sats \ 0 replies \ @lnvisualizer 22 Apr 2023 \ on: Bitcoin Miami ticket - 1 million sats bitcoin
I would love to go! I have never gone and have always wanted to. Reach out to me at lnvisualizer@gmail.com
I'd say amount only because that's the name of the type in the source code
https://github.com/bitcoin/bitcoin/blob/master/src/consensus/amount.h
// Copyright (c) 2009-2010 Satoshi Nakamoto // Copyright (c) 2009-2021 The Bitcoin Core developers // Distributed under the MIT software license, see the accompanying // file COPYING or http://www.opensource.org/licenses/mit-license.php. #ifndef BITCOIN_CONSENSUS_AMOUNT_H #define BITCOIN_CONSENSUS_AMOUNT_H #include <cstdint> /** Amount in satoshis (Can be negative) */ typedef int64_t CAmount; /** The amount of satoshis in one BTC. */ static constexpr CAmount COIN = 100000000; /** No amount larger than this (in satoshi) is valid. * * Note that this constant is *not* the total money supply, which in Bitcoin * currently happens to be less than 21,000,000 BTC for various reasons, but * rather a sanity check. As this sanity check is used by consensus-critical * validation code, the exact value of the MAX_MONEY constant is consensus * critical; in unusual circumstances like a(nother) overflow bug that allowed * for the creation of coins out of thin air modification could lead to a fork. * */ static constexpr CAmount MAX_MONEY = 21000000 * COIN; inline bool MoneyRange(const CAmount& nValue) { return (nValue >= 0 && nValue <= MAX_MONEY); } #endif // BITCOIN_CONSENSUS_AMOUNT_H
1000 sats \ 1 reply \ @lnvisualizer 11 Oct 2022 \ parent \ on: lnd cant sync to chain due to taproot bug bitcoin
Wow thank you so much! Really appreciate it. Happy your node is fixed.
Update: the PR has been merged. These steps should not be needed. You should be able to update from the umbrel app store.
If you don't see it try
sudo ./umbrel/scripts/repo updateAs or upgrading to 0.5.X, you should be able to go to the settings menu and click the update button if you are on 0.4.18.
https://github.com/getumbrel/umbrel/issues/1422
If not, then I'm not then in all honesty not sure what the procedure is. It might let you update to 0.4.18 and then after 0.5.X.
If not, you may need to manually apply the fix or reinstall 0.5.X.
5100 sats \ 7 replies \ @lnvisualizer 10 Oct 2022 \ parent \ on: lnd cant sync to chain due to taproot bug bitcoin
Yeah this won't work for that. You'll have to update to 0.5.X or manually fix it.
For umbrel 0.4.x you'll have to edit the
./umbrel/docker-compose.yml file manually.In that file you'll see a list of services.
If you scroll down to the lnd section
... networks: default: ipv4_address: $BITCOIN_IP lnd: container_name: lnd image: lightninglabs/lnd:v0.14.1-beta
you should be able to manually edit the container (on line 7 here) to
lightninglabs/lnd:v0.15.2-beta
and then restart the node, or run
sudo ./umbrel/script/startto just apply the update
for anyone using umbel you can fix it by doing the following
ssh into your machine
sudo ./umbrel/scripts/repo set https://github.com/MaxKotlan/umbrel-appssudo ./umbrel/scripts/repo updatethen go to the umbrel app store and update lnd
this fix hasn't been merged in yet, but once an official umbrel update is created you can
sudo ./umbrel/scripts/repo default-repoto set it back to the official repo.
Submitted this change as a pull request to umbrel
https://github.com/getumbrel/umbrel-apps/pull/190
To my knowledge their website currently does not have a list of apps.
I agree, I think it would be nice if they added the list to their website.
This is the current repository for all the apps they have on their AppStore
https://github.com/getumbrel/umbrel-apps
LND specific answer
Basically the server has this identityKeyLoc property:
https://github.com/lightningnetwork/lnd/blob/9c97d26cfb505081732cb457b513a356879ad57e/server.go#L160
that is used whenever your node announces itself to the network:
https://github.com/lightningnetwork/lnd/blob/9c97d26cfb505081732cb457b513a356879ad57e/server.go#L2766
According to this comment here about key locators
https://github.com/lightningnetwork/lnd/blob/7106ea59db9ade78d65bb46605f94637900c0e3f/keychain/derivation.go#L140
It seems to generate ECDSA public keys using a BIP43 like keychain system commonly used for wallets.
So ultimately it is derived from a BIP43 like key derivation mechanism based on the comments. Like what you would see in a wallet.
I don't think there would be anything stopping you from modifying this and just hardcoding a custom vanity key.
Or somehow generating a path/keyindex that derives your vanity key.
However, most node public keys are commonly displayed in base16 so you don't have a ton of options other than making a vanity like DEADBEEF1234567890...
Given the limitation, I'm not sure if that would be worth doing.
Probably better to just define yourself through an alias.
@DiscoPay Update on #4). The weighted mode for channel capacity has been added!
You need to change the line primitive dropdown from gl-line to line-mesh then you can change the width of the channels.
The other dropdown that shows up when selecting line-mesh will allow you to either have uniform linewidth (all of them are the same), or you can select channel capacity and the width will scale with the capacity.
Attenuation (similar to node attenuation). Lines get smaller the farther they are from the camera.
Were you still downloading the graph data? (It will show a loading bar at the bottom of the screen beneath the graph)
I noticed while you are downloading, every time it gets a new chunk of graph data it resets the sliders.
Should probably find a better way to do that.
Update on this. Noticed the server also crashed yesterday. I upgraded the server to have more resources. Hopefully that is good enough for now. In the future, I am hoping to have horizontal scaling.