pull down to refresh
2756 sats \ 9 replies \ @lnproxy 28 Jan 2023 \ parent \ on: Answering Objections to Drivechain bitcoin
There are many unknown risks of not activating BIP300.
-
Will the lack of privacy on Bitcoin enable state co-option?BIP300 might help with that.
-
Will the declining revenue for miners mean bitcoin transactions take weeks to settle, forcing users onto other chains?BIP300 might help with that too.
-
Will the scarcity of bockspace on Bitcoin force most users to rely on a custodian?BIP300 might even help with this.
I think it's much more risky not to activate BIP300.
Does this guy have a family?
If anyone knows, I'll pledge a million sats for them and I'm sure there's many other anons that could do the same and more.
I think we're too small to win these battles still but, we can do something to take care of our own.
Won't work today because there's only my tiny test relay running but, this is one of the cases where lnproxy can help.
10 sats \ 0 replies \ @lnproxy 17 Dec 2022 \ parent \ on: Lightning @-address but for on-chain? bitcoin
Oh, I think I didn't understand you. Yeah, it would be nice to just be able to make a GET request to something like https://lnproxy.org/.well-known/bcurlp/support and get a fresh onchain donation address. I guess it could be part of the lnurl spec, it's kind of like auth, not really dependent on lightning but nice to have in the same spec so you can use one key.
parsing a bolt11 invoice is not hard, there's no reason an onchain wallet should not be able to do it.
haha, yeah but it's a pretty easy hoop if it already has to implement the logic to send the lnurl request. Plus, every onchain wallet should be able to do this.
Drivechains
Not exactly a company, but Paul and CryptAxe are building the future of bitcoin scaling.
Galoy
Open source bitcoin bank stack that scales to millions (more?). (Banks will be necessary to scale until we get drivechains activated).
- compromise: attempt to provide most of the same convenience with much less balance data (I think rene proposed 2 bits)
5021 sats \ 7 replies \ @lnproxy 27 Oct 2022 \ parent \ on: Amboss Launches New Stats Portal bitcoin
Do you think any of these ideas could help counter this trend:
- white listing: only open channels with counter parties you can trust not to share balances
- black listing: compile a list of known balance sharing nodes and develop open source tools to automatically blacklist them in routing, peering, and channel creation
- Taint balance history databases with intentionally bad data
- Modify routing algorithms to split payments more aggressively and route through more nodes
- Augment the protocol with some kind of payment batching / net settlement protocol
What do you think about integrating into a bridge server so that
me@me.com would first access the lnproxy api to hide the @me.com public key? Then the owner of me.com could trust the bridge server code they're running to make sure that the payment hashes always match and the "max fees" don't change.