pull down to refresh
1 sat \ 9 replies \ @nerd2ninja 17 Jan 2023 \ parent \ on: Drivechain (BIP300-301) Bitcoin advanced sidechain discussion bitcoin
Who would ensure only that type of side chain is approved in the 256 possible side chains? Not node runners. Only miners would decide these sorts of things.
I also don't like a narrative wherein a scam or shitcoin or anything of a negative perception is associated as necessary for Bitcoins security or that it is part of Bitcoin itself.
scams and shitcoins can already be built on bitcoin, it cannot be avoided. so don't let the mere possibility of such turn you away from a new protocol that can add functionality that is valuable for bitcoin holders. otherwise to be consistent you have to condemn bitcoin itself for already enabling these possibilities.
reply
regardless of your opinion on altcoins, bitcoin by its very nature of being an open source project will always enable these possibilities, as the code can be forked an repurposed in any way anyone sees fit. the difference is this would have been carried out in a way which strengthened bitcoin adoption rather than weakening it.
reply
My instinct says it would not strengthen adoption at all. Shitcoins are a result of a failure to understand the "why" behind Bitcoin
reply
My comment should not be interpreted to be an endorsement of shitcoins in any way. The functionality about Drivechain that I find most valuable are things that give BTC more utility and value, like new self-custody contracts, better privacy, p2p finance, etc. I am only saying that it is already possible to create shitcoins on bitcoin with the many colored coins protocols like Omni, Counterparty, OpenAssets, Taro, etc, so it's unfair and inconsistent to support bitcoin but oppose a new protocol like Drivechain just because it is also possible to create shitcoins using it.
edit: sorry, just noticed you were replying to someone else
reply
I did make a reply to your comment though. It just isn't this one
reply
I'm against LND because taro was built on it. "Get your shitcoins off my lightning node"
And its not the mere possibility, it seems to be the main feature of BIP 300. To fund Bitcoin mining with shitcoins.
I think part of this misunderstanding is "really useful features" that do not exist in shitcoins but claim to exist. "Web 3" was the latest example that got shot down with the development of nostr. Here, less text
Web 3 => nostr
Smart contracts => if a block chain needs an oracle why does an oracle need a block chain?
Privacy => teleports
DAOs => multi-sig with irc (you can even call each multisig participat an Oracle if you must)
Bitcoiners just build things differently. Stick around and you'll see how.
reply
I've been around for over a decade and have been following bitcoin developments closely throughout this time. Many improvements are possible with drivechains that aren't possible on bitcoin today. For example teleport and other coinjoin/coinswap based protocols are far less private and more expensive on a relative basis than Zerocash-style protocols, smart wallets provide much more flexibility in programming the spending conditions for a wallet which makes self-custody easier and more secure, I could go on and on.
That said, it doesn't really matter what you or I think about the value of these other use cases. What matters is that out there in the market there are things people want to be able to do with their coins that currently they can't do on bitcoin or existing L2 protocols, so they turn to altcoins instead. You and I might dismiss or dislike those use cases but that is irrelevant. Choosing to turn away customers, simply because we are obstinate in our opinion of their desires, when we could instead work to solve their problems is a losing strategy and artificially limits bitcoin's potential. Drivechains can bring that business back to bitcoin and help bitcoin get closer to achieving its greatest potential as p2p electronic cash.
This is not to mention future use-cases that we can't even imagine right now, that bitcoin does not support, and we will wish it did once the need arises. Drivechains can "future-proof" to some degree and give bitcoin developers the flexibility to address these future problems without needing to make any other changes to bitcoin L1.
reply
What is this about customers and business? Bitcoin is not a business. After all this time you've been thinking of Bitcoin as a product that you're selling people on? p2p cash is not just cash for cash's sake. It is money and money is a social construct. Bitcoin is also a social construct, not a business or a product that is being sold to customers.
I don't know if you know this, but you can very much run drivechains right now. Its considered a brittle fork (that's my name for it) whereas a merge would be a softfork. The difference is that if your brittle fork client loses consensus at any point, it is no longer considered Bitcoin, but if a brittle fork client becomes a soft fork through shear adoption, it becomes Bitcoin
So if this is really such an in-demand feature that people would like to make into the social construct we call Bitcoin, then LET THEM RUN FULL NODES
That being said, it sounds like you don't understand why Bitcoin doesn't use zerocash. We want blockchain auditability. We had a buffer overflow once upon a time and seeing that transaction create Bitcoin out of thin air was important to the participants who all decided to pick up mining an older state of the chain which was not above the 21 million limit, with a new client that had the patch as well as a hard coded cap rather than the implied cap of the miner subsidy.
Now, smart wallets is a thing I've never heard of before. That is its own topic though.
reply
This special feature, that users, not miners control the network, can be used to take away users ability to control the network by implementing this BIP. Users can give all their power to these miners, but keeping my power over the network with my node and keeping miners as paid security rather than owners of the network is also part of why this BIP is being rejected.
reply