Avatar
Manánguri
4180da638a2579c5187be5d2129cd2fd2ba6244a8f9f4dd99092b4487b3c147e
Murri. Jagera.

"As of May 2024, GPT-4 has knowledge of events that occurred up to December 2023 and GPT-4o's knowledge cut-off is October 2023."

That's why ChatGPT doesn't know anything about the Trump attempted assassination.

Couldn't you do even a tiny bit of research before posting crazy conspiracy theories?

I have never used TikTok and this idiot sure isn't going to get me to start.

Anyone who believes anything the see on TikTok is a bloody idiot.

You'll need to add your nsec to each client you use. Or, use a browser plugin signer like #nos2x where you enter your nsec into the signer and it authorizes clients to post.

I guess you've never heard of the Roman empire. Those pesky Italians that stated a world war, and won.

Replying to Avatar Rusty Russell

First up, I want to recognize that this is an uncomfortable topic! Bitcoin is inevitably changing towards user-pays, and that's not all positive. But facts we don't like are still facts: can't engineer a solution if we can't think about the problems.

There are three kinds of bitcoiners.

A. Those who can afford any fee.

B. Those who can afford a UTXO, but not often.

C. Those who can't afford a UTXO.

Nobody worries about the A group (and in the early days, that was everyone). Obviously Lightning (my area!) caters to the B group, and we want it to be as large as possible. To do this we can (1) make lightning as resiliant as we can so onchain spends are rare, (2) make bitcoin as efficient as possible so we can cram as much as we can into what we have.

(1) Making lightning more resilient and reliable is engineering. Lots of people working on this, even before we get soft-forks which could help further.

(2) More efficiency has two benefits: obviously if your own onchain spends are 20% smaller, that's 20% cheaper. But if *everyone's* onchain spends are 20% smaller, that means fees are lower *for everyone* too (and it's non-linear). So we really care about all Bitcoin usage! Some things are obvious wins: Taproot so you can avoid even putting the script onchain in many cases, FROST so you can cram your 2 of 3 or other scheme into a single key and signature. We know we want to get more aggressive with sharing one signature across multiple inputs (Cross Input Signature Aggregation), but that needs a lot more research, and a soft-fork.

But even with all these, the math is clear: some people, even if you somehow gave them their wealth in a UTXO, it couldn't afford its own fees to spend. The C group is real. Spoiler alert: we don't have an answer for this! But let's look at some approaches people have tried.

Firstly, there are attempts to move these people into the B group: give them long enough that maybe fees will reach a point they can afford. This seems unlikely to me:

1. As fees increase everyone will start doing the work to take advantage of low fee times, and that itself means that low-fee times won't be so low.

2. These schemes tend to increase onchain footprints, so they need fees to drop a lot to overcome that (typical is 2x the transaction size, so you need fees to halve to gain anything).

3. If you really can't afford the fee, you probably also can't afford to wait.

4. You still haven't actually dealt with those who really, really can't afford the fees. Ever.

Another suggestion is that someone (e.g. a lightning service provider) will lock up funds which would cover fees, in case something goes wrong. This doesn't work economically, because nobody is paying $100 for a $5 user (not at scale), but it doesn't even work mathematically: the reason some people will have small UTXOs is because there are not enough sats for 10 billion people with any realistic distribution.

There are two basic approaches left:

1. Group people, so they fall into the B category (i.e. onchain tx is possible, but expensive).

2. Trust someone, but rely on incentives.

1. Grouping people is possible, but they need to work together if somenthing goes wrong. So grouping inside a community is probably better than grouping with randos.

For example, there are various tree-of-transaction schemes where you go onchain only if the coordinator fails/goes rogue, and how much it costs you depends on whether anyone near you in the tree pays to get themselves out. These are basically free if nothing goes wrong (one UTXO required for thousands of users!). But this is subject to ghettoization, where the coordinator makes sure all the C people are grouped together, knowing none of them can afford the transactions they need to get their funds back. It's particularly bad because the coordinator can insert its own fake "whales" to make it look like it's not ghettoized.

You can play with incentives here, too: more research needed. The details matter!

2. Relying on incentives.

As a simple example, lightning-connected e-cash mints. They can't rug individuals very easily, they have to rug everyone together (or go fractional and rug the last ones to exit). Maybe with enough anonymity and reputation, these would be Good Enough.

More ambitious would be a single UTXO held for multiple people by a coordinator. Can we make it so that if a coordinator is dishonest, you can force them to burn your funds? Maybe burn more than your funds (ie. a bond)? Won't get your money, but it aligns incentives so they're not motivated to rug you. The details here really matter!

There's a cute scheme which has been proposed where the coordinator pays a temporary bond, and asserts that they actually have everyone's signature to transfer the funds. If nobody challenges within a week, they get the bond back and the funds move. If someone challenges, all the signatures are put onchain, and if they're not all valid, the bond gets half-burned and half-given to the (successful) challenger. This is hard to make work, though. Someone needs to get the money to challenge (hard if you don't have the money in the first place, plus it's hard to prove to someone you *didn't* sign something!), and then make sure nobody gets the challenge bond before them (in particular, a dishonest coordinator, seeing the game is up, completes the successful challenge *themselves* and gets half their bond back), and make sure someone can't grief and delay the settlement indefinitely or bankrupt the coordinator.

More research needed, here, too.

Summary

A longer post than I had expected to write. And it's buried in the middle of a thread nobody will read. (I do this sometimes. I suck at marketing I guess!)

Sub-fee bitcoin amounts will have tradeoffs, involving trusting someone who has more money than you (at least, in someone's competence, even if their *financial* incentives can be made to match yours). This is difficult to build well, and not a very exciting thing to build today, so it hasn't really happened (custodial things are much, much easier!).

This is also a key reason I believe we need to make Bitcoin more expressive: if we can do *more* with our own UTXOs, we can build better solutions. And by "we" I mean "someone smarter than me" of course!

Feedback welcome!

The ability to transfer channels without an on-chain transaction is on the way.

When you can rent instant liquidity when needed, and return it when it's no longer needed, all without any on-chain transactions, a lot of the current problems with onboarding new users with non-custodial wallets will be solved.

Lightning is cool, but still very much beta software and not ready for mass consumption by people that use 0000 as their PIN.

For some people, right now, a custodial wallet where someone in support can help them when they forget their password is not a bad compromise.

I have 1000 sats. I can't send the whole amount, because there's routing fees to pay to get the payment to the destination. The fees estimate was 30 sats.

So, I send 970 sats. But it still fails. Fee estimate this time was 37 sats.

So, I send 963 sats, and this time it goes through, but I end up with 9 sats left over because the fee ended up being only 28 sats.

Fee estimates aren't accurate. The fees to make a payment are calculated each time, not pre set.

The only way to get all the Bitcoin out of a channel, is to close it. It's not your channel so that's not an option for you in this case.

You can't spend all of the Bitcoin out of a channel. There'll always be some unspendable amount. It's called dust.

You're inevitably going to be leaving some dust in the mutiny wallet. Mutiny doesn't get to keep that dust. Miners will get it when the channel closes.

Property rights? Like in the USA where rich people can use Eminent Domain laws to seize the property of poor people.

Because the only real property rights you have, are those you can defend yourself.

Rich people can afford to defend their property rights and, they take your property away from you whenever they want.

Poor people with a mortgage, family, bills to pay, have zero property rights in the USA and there's any number of government departments, banks, and billionaires like Donald Trump that can and will take your property from you if they want it. Eminent Domain laws extinguish any property rights you think you have.

Are they the sort of property rights you speak of? Your government, left or right, doesn't give a shit about your property rights because you don't have any.

Like local government taking the homes of working-class people to make room for big-box stores, corporate headquarters, or luxury condos.

“Eminent domain is an absolute necessity for a country,” Without it, you wouldn't have roads, you wouldn't have hospitals, you wouldn't have anything.” -- Donald Trump

Donald Trump used Eminent Domain laws to seize an old lady's home so he could build a carpark for limousines.

A Welsh Christian murdered 3 children so the Russian FSB got their agent Tommy Robinson to spread the lie that the murderer was a Muslim immigrant and then incited race riots built upon that lie

Knuckle dragging racists have now gone on a destructive rampage destroying the shops and property of innocent bystanders.

Many are now being arrested and remanded in custody where real tough guys servering life sentences for murder will appreciate the new meat and rape those morons mercilessly.

They'll then be released from prison, and sheepishly slink away having leaned how stupid it was to listen to a Russian FSB agent and traitor like Tommy Robinson. The rapes, well that they'll never talk about.

Make sure you read all of the API documents on Kraken. You have to treat your API like your seed words. Keep it very secure. If someone gets access to it, they can drain your account.

Should work anywhere. It uses the same API interface with Kraken that you would use it you were using a trading bot.

You can control how much access btcpayserver gets by setting permissions when creating the API.