0 sats \ 1 reply \ @openoms 6 May 2023 \ on: A Warning to Users: Tippin.me Potentially an Exit Scam bitcoin
The node is connectable and the channels seem to be online: https://amboss.space/node/03c2abfa93eacec04721c019644584424aab2ba4dff3ac9bdab4e9c97007491dda
still don't deposit and try to withdraw when possible.
Their support has been ghosted a long time ago. Noone should use it any more.
I reviewed and merged your pull request. Thank you for contributing!
back at you, thank you for building this and iterating fast!
Check if you have something like ublock origin running. For me, it did that til I turned off ublock origin.
I definitely have adblockers running. Will try again once bootstrapped a testnet node. On that note testnet channels would be welcome to:
0340a5fc39195696d42e4f43cc01f8c6726a0ef2c4b25e836352437e32d121b97c@rcl5jtbxbqqo5ttygooi53dyk7h33r4j5somy7xulkgosoytgjwa7kad.onion:9735Proposing to use the mempool.space
hourFee aka Low Priority instead of the minimumFee which results in funds in swaps being stuck for days: https://github.com/supertestnet/swap-service/pull/1Great concept, I am sure it will see a lot of use!
What I find most tricky is managing the onchain fee.
Using the minimal fee is good for the Maker, but not suitable for the Taker.
As required by the submarine swap model there are two transactions:
- first the Maker deposits to the swap address - this can be a minimal fee transaction, but needs to be CPFP-d by the next.
- then the Taker sweeps - using the minimal fee here as well results in transactions stuck for days in the mempool in the current environment. Even if there would be choice (which should be!) the sweep transaction needs to account for the deposit as well so even trying the next block fee might not be enough. For example a deposit could be a large, consolidating transaction which would have a much larger weight than the 1in-1out sweep txn. Prediction is difficult since all the fees need to be agreed beforehand.
For now there should be a warning to only swap to an own address and not use the platform to pay directly to a third party as the sweep transaction might need CPFP itself.
(also a bug report for the testnet page - querying the testnet mempool api returns a CORS error)
These are some mitigations and the blacklisting especially does hurt the network.
What we need is to change the approach:
Don't make data sharing the norm because probing is already possible.
Rather make probing more difficult, expensive and inconclusive.
Improve payment reliability by implementing Pickhardt-payments and share known good hops in Blinded Paths.
1132 sats \ 0 replies \ @openoms 27 Oct 2022 \ parent \ on: Amboss Launches New Stats Portal bitcoin
First was enthusiastic about the possibilities described in the article: https://ambosstech.medium.com/lightning-balance-sharing-and-network-statistics-32e687a4db25, but thinking just a little this is clearly the living hell of surveillance capitalism.
A short thread:
https://twitter.com/openoms/status/1585526779648917511
We need a simple app for the cursed LND nodes to share random data quickly.
Found that BtcPayServer >/=v1.6.0 with the LNURL NFC Support plugin activated can also support paying with the Bolt Card.
For an example try to open https://tips.diynodes.com in Chromium or Chrome on mobile (Fennec/Firefox does not seem to have access to the NFC).
Notes to enable I2P on a RaspiBlitz, RaspiBolt or similar: https://github.com/rootzoll/raspiblitz/issues/2413#issuecomment-1013855483
GENESIS