To me, that seems like a strike and zeus issue. Zeus had a problem connecting to node over tor prior to an update couple of months ago. I had that problem from time to time. Phoenix is a 10× improvement after splicing and ux is same as using on-chain bitcoin wallet

Fiatjaf is not honest about drivechains tradeoffs. Anyone even discussing drivechains before broad SV2 adoption is not a serious person. Even then, STARK verifier offers better tradeoffs (this is possible using covenants)

Reply to this note

Please Login to reply.

Discussion

Discussion and debate is how things get moved forward.

Pushing issues under the carpet is how slow progress is made.

I know nothing about stark so I can’t comment on that.

Drivechains is not worth discussing because without SV2, it has worse trade-offs than even liquid

Liquid is federated sidechain that requires permission to use.

Drivechain is a trustless sidechain and your forgetting drivechain includes bip 301 as well for blind merge mining.

Drivechain is federated and enables mev and no, that doesn't just affect sidechains as it does with stacks blocks now. It distorts miner incentives in ways that threaten censorship resistance

The MeV fud has been addressed countless times.

No it hasn't. To claim sidechain mev doesn't affect bitcoin is regarded