+1 I don't know the chef stuff well.
For the record: ADMIN_TOKEN is set this means accounts can only be created using this admin token (through akkounts for example)
We do not have the fee reserve enabled, which means the user can withdraw 100% of their funds and we pay the outgoing lightning network fees.
The user's balance will then be negative, so once the user sends money in again it will be accounted.
+1 I don't know the chef stuff well.
For the record:
`ADMIN_TOKEN` is set this means accounts can only be created using this admin token (through akkounts for example)
We do not have the fee reserve enabled, which means the user can withdraw 100% of their funds and we pay the outgoing lightning network fees.
The user's balance will then be negative, so once the user sends money in again it will be accounted.
The respective bucket needs to be configured with a domain alias. When a
new alias is added to the `s3_web_domains` config, a new nginx site can
then be deployed to the `nginx_proxy` hosts.
Allows to swap sats in and out of Lightning channels without a 3rd party
(and their fees). Instead, swaps can be initiated directly with the
channel peer.
https://www.peerswap.dev/
greg
We have migrated all balances from legacy lndhub to the new lndhub.go instance, and deployed akkounts from the respective branch for now.
closes #454
+1 I don't know the chef stuff well.
For the record:
ADMIN_TOKENis set this means accounts can only be created using this admin token (through akkounts for example)We do not have the fee reserve enabled, which means the user can withdraw 100% of their funds and we pay the outgoing lightning network fees.
The user's balance will then be negative, so once the user sends money in again it will be accounted.
695d0925a4，至a7e04f4e63比较WIP: Set up lndhub.go为 Set up lndhub.goJust FYI, I cherry-picked a commit from #458 into this one, so that I could converge
nginx_proxywith that config still working.