Avatar
j
2590201e2919a8aa6568c88900192aa54ef00e6c0974a5b0432f52614a841ec8
keep nostr weird
Replying to Avatar hodlbod

Guys, I fixed global

https://v.nostr.build/ZlKP.mov

Of course, I also made it impossible for new people to find followers for people who use this feature. What should the default be for new users? I'm thinking 1 — enough to keep people safe, but a low enough bar to allow for discoverability.

Awesome feature

"safe" is the wrong word tho, that's the language censors use. maybe "spam-free" would be better. Or "1 - enough to ensure posts have *some* low level of quality, but low enough to allow for discoverability"

Awesome! I'll have to investigate.

lol, how would you "pump someone's bags" with drivechains? The whole point is to use Bitcoin.

This is just more of the "shitcoins on Bitcoin" nonsense.

As far as Cosmos is concerned, no, I don't know anything about it, I will look into it, thanks. But your point about cross chain swaps not working is silly. Already works today, and there's many account-less exchanges that offer them. The main problem is you'd have to trade your Bitcoin for some shitcoin (except for submarine swaps which are great) so I wouldn't use most of them.

lmao, yeah totally dawg

who cares about hashrate amirite?

Replying to Avatar Guy Swann

This isn’t even half of the issue though. Thinking that these are the only considerations is foolish:

• federations can be spread out across jurisdictions. Attacks are permissioned

• attacks on a hash lock are permissionless. Anyone can do it and they don’t have to have any stake in the sidechain whatever

• NONE of this does anything to solve the validation problem, because the only way to assume it’s secure, is if miners are validating everything, and if the only reason it is beneficial is because they don’t have to, then it’s not remotely secure.

• it seems that any attacker can issue a fraudulent transaction from the DC hash lock. And miners are expected to vote against it. Except that this again, presupposes they *are* validating every single drivechain.

— in other words we’ve dumped the validation problem of the *entire* DC ecosystem into their lap, said “don’t worry your don’t have to validate,” but then turn right around and demand they be the judge regarding what is and isn’t valid… demanding that they validate.

• a permissionless attacker in DC can attack literally *every* single DC that exists at the exact same time, with no cost to expanding the attack except the rejection of their block *if* other miners are validating the DCs. Except that if they aren’t, they may very well get continuous “yes” votes from major pools that are just default not caring and want to get fees, which immediately creates an enormous consensus battle that takes place entirely our raise of the chain - which is the whole situation we are trying to avoid.

• lastly, if we take the simple incentive that miners will maximize profits - the claim made for why they will force DCs on the network without consensus - then there is no reason for them to not steal from the sidechains. As participation is again permissionless, and it would absolutely maximize output. We are requiring *social* constraints to keep them honest, not validation rules - because theft is valid in the DC system.

This isn’t remotely as simple as proponents are claiming, and the complete refusal to admit significant trade offs is what has made me so annoyed. And like I said before, it’s not worse than a permissioned federation but it’s also mot clear that it’s any better at scale, and there is no solution to the validation problem here, it’s just *all* being dumped on miners and then hand waved away.

There may be some good points here but it's obvious you didn't read my much shorter reply (I anticipated the common cope of federation members being in different jutisdictions and why it doesn't actually help much) so I wont engage further.

For Guy's audience: the criticism above (that miners have to validate all sidechains to downvote obvious attacks) is equally baseless.

For example, a miner could just run a light client for the drivechain or even just check a drivechain block explorer to see that a "permissionless" attack is just noise. Of course, this could be easily automated. There is no risk of ddos because these "attacks" would have to pay transaction fees.

Even if there is a light client or block explorer issue, and a miner votes incorrectly, the most likely outcome would be that the issue would be fixed by the people running the sidechain and the rest of the vptes wpyld be correct.

I hope you all can see how easy it was to refute Guy's supposedly well-thought out fud and you consider this exchange next time this influencer tells you you can't have a zcash sidechain because reasons.

Federated multisig -> known set of custodians (can't be anon because it would make it vulnerable to a sybill attack) easy for the government to coerce. yes, even in multiple jurisdictions since governments today act in lockstep

Drivechain -> Sybill resistant, annonymous, dynamic, and incentive aligned custodians. Very hard for the governmenr to identify.

Obviously drivechains are superior, how do you not see this?