pull down to refresh
10 sats \ 1 reply \ @82e78180a1 12 Sep 2023 \ on: We're trying to turn Bitcoin into a real global payment network. Lightspark CEO bitcoin
"We're trying to turn Bitcoin into a real global payment network"
- Bitcoin already has a payment network, it's called lightning
- It wasn't built by anyone at Lightspark
- They're merely basking in the glory of true builders of the space without putting much work and instead offering an overpriced & proprietary API
The reality is, those in favor of a drivechains soft fork aren't going away. If anything, they will grow louder.
Exactly, this echoes the endless debate we had with big-blockers and allowed us to focus on more productive endeavours.
I still use monero to pay for VPN services. Not that I go out of my way to do that, but the shitheads at mullvad don't accept lightning and making an on-chain payment kinda defeats the purpose of using a VPN for privacy.
I actually don't mind "using" any shitcoin for this purpose. It's the store of value purpose that I care the most and that's what I use bitcoin of course.
This is a very interesting resource, thanks for it.
However even though I recognize that Gavin did an important job in maintaining the project back in the day, it seems like things got to his head pretty quickly and that ended up tarnishing his reputation a lot. I remember him saying something about throwing his weight around when talking about a block size increase.
Then you had the whole CSW episode, something for which to this day he has failed to clarify things. By doing so he tacitly supports that crazy megalomaniac in his crusade agains Bitcoin devs.
No.. I don't think Gavin's contributions are enough to outweigh the bad stuff he later did and/or supported.
1469 sats \ 0 replies \ @82e78180a1 2 Sep 2023 \ parent \ on: What's the TLDR for Drive Chains? bitcoin
Besides there's zero demand for any of these. The only people that are pro-drivechains are devs with some strange kind of fetiche for these obscure mechanisms that no one wants to use.
It probably means 80 decimal digits. But even then it's a bit off. As a 256 bits number would require at most 78 decimal digits.
A bitcoin private key is 256 bits long, that's 32 bytes, which when represented in hexadecimal would yield 64 characters.
However I'm puzzled by the extra 2 or even the other question marks. Are they spread all over the sequence of characters? or are they kept at one side?
Oh and both Armory and Multibit were started in 2011, so this is almost certainly from bitcoin core.
Well I guess that was the problem, the expiration time on that invoice is 24 hours. And for what I see from your other reply the invoice your server is generating is good for 100 blocks, or ~16.6 hours. Good thing your server is catching that!
But I think 24 hours must be the LND default invoice expiration time. Since LND is widely used and most apps don't let you set a pre-image for the invoice, you're likely to encounter this problem frequently unless you make it clearer in the user interface that a shorter expiration is required.
Sure, here it is:
lnbc33460n1pjw4tnhpp5aujpg5lwf5pg57thzf3u2xd3s23qhgevnj9adxv8el7su5c06yuqdqqcqzzsxqyz5vqsp5a5l58jawk3dwx3dcarvk4z90ann4gq26a97xskw6w04z0zwck39s9qyyssqlfe42yrluuwrsq8r3gmj7qzhh3jt3d2n0qzj0ga43ss0l0pcfwt4z59r86c887299yssae675ktv86k4p533pk4pmsdjdsl6098xzmgp2qve98
Ok I tried paying with lnbits as suggested and indeed it apparently worked. But when trying to claim with an invoice generated by LND I get:
status: nice try, asking me to pay you when the invoice that pays me is about to expire
This is funny, but wrong I think, because the payment only expires in ~800 minutes.
You can try manually adding an entry to the
/etc/hosts file. I know, this will break in the long term because it's akin to just using the IP directly, but it will at least allow us to test it for now :)Also I managed to fetch the lnurl data and now I get a different error:
invalid amount. The range is apparently 4187 to 9007199254740 sats. And I'm trying with 5K, 10K and 15K sats, all with the same results.No problem man, I know how it is.
10K requests indeed seems like a lot, but still I've never ran into an OS issue like that. What OS are you using?
Super cool man!! But is your server having some issues? I keep getting this response with status 500 and
{"detail":""} as body when entering the LNURL in lnbits. Also failed to pay my LN address with breez.This is the LNURL if you want to debug:
LNURL1DP68GURN8GHJ77NPWPKX7CMTV4EZUCM0D5HJUAM9D3KZ66MWDAMKUTMVDE6HYMRS9A3XJMR5DPHKUUREUMA
GENESIS