Why comment if you don't understand the bips ?
I wasn't actually saying fuck you
I am very curious to hear the feedback on this
https://github.com/vitorpamplona/nips/blob/relationship-status/81.md
Wide spread not wise spread ***
Nope, not all transactions. Just those for whonever want to participate in a sidechain.
Its like we all use tomato sauce from the same farm (bitcoin) but some want chunky some want spicy. We get to keep the same tomatoes but have a choice in what kind of sauce.
This is a soft fork, which means nodes and users who don't want thos new feature won't be affected.
The great thing is, for this one last change, we get a layer 2, for most future changes.
And pocket nukes
Just when i was going to take a break. 4chan starts talking about bip300 & drivechains
A priesthood of devs and corporations should not determine bitcoins rules. Marketing campaigns that mimic political campaigns should not determine bitcoins code.
Bip300 allows us to choose, without centralization, the way a free market works.
Explaining complex topics to simple and stubborn minds has diminishing returns.
....Unless you have a podcast i just realized.
nostr:npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399s on nostr:npub1jfujw6llhq7wuvu5detycdsq5v5yqf56sgrdq8wlgrryx2a2p09svwm0gx about Drivechain:
"Here is the "drivechain canon," a series of 4 essays by fiatjaf, myself, Paul Storcz, and John Light:"
Drivechain
by nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
https://fiatjaf.com/drivechain.html
Answering Objections to Drivechain
by nostr:npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399s
https://stacker.news/items/127974
Blind Merged Mining
by Paul Sztorc
https://www.truthcoin.info/blog/blind-merged-mining/
Another response to the âminers can stealâ critique of Drivechain
by John Light
https://lightco.in/2022/06/15/miners-can-steal-2/
I'll also just start you off with several of my attempts to boil down the essence of drivechain into as few words as possible:
What makes a drivechain different from a federated sidechain like liquid is this: with a federated sidechain, all deposits are held in an address where 15 people can vote on what to do with it. These 15 people are trusted to let the "right" person withdraw the money. On a drivechain, all deposits are held in an address where a set of bitcoin miners -- namely, 50% + 1 of them -- can vote on what to do with it. Miners (in general) are trusted to let the "right" person withdraw the money.
And:
Bip300 works by creating a new type of timelock. A bip300 timelock is similar to OP_CHECKSEQUENCEVERIFY, which is the timelock where you can only spend your coins after waiting X blocks. Bip300's new timelock is different because it lets any miner increase the value of X by adding a message to their bitcoin block. A person enters a drivechain by depositing coins into a âdrivechain deposit addressâ that uses this timelock. If, later, two different people try to spend those coins, the timelock gives miners time to decide who should "win."
A miner who sides with the second person can increase the value of X for the first person, delaying their withdrawal attempt, but leave the second personâs attempt unhindered. Each miner can delay either withdrawal attempt, or both. Whichever attempt is delayed by fewer miners will succeed and the other one will fail, unless both attempts are delayed long enough to allow yet another attempt to succeed before them. By this method, 51% of miners get to choose who can withdraw the coins first.
And:
The essence of a drivechain's "deposit address" is one where a withdrawal attempt from that address can be delayed indefinitely if miners keep incrementing an integer, but miners can only increment it once per bitcoin block, and incrementing it is optional.
And:
Anyone can try to withdraw from a drivechain, but each withdrawal has a timed delay, during which miners can check if the withdrawal is authorized by the drivechainâs rules. If itâs not, any miner can extend the delay to let an authorized withdrawal happen first.
source:
https://stacker.news/items/228754
in response to
The Drivechain bluff
https://gist.github.com/fernandonm/41eaaf4b1875c3f10b040afad995d24d
Also, withdrawls are not intended for average or most users. They are intended to limit rugpulling and to be done by specialist brokers.
That's a feature, not a bug.
Paying for a niche product is called a market.
Offering a service (spam filtering ) is a business.
Paying for things through ads is what gave us modern privacy violations.
If we had just payed for email (each email sent, like regular mail) in the beginning it would have been different.
Its not meant for everyday user use. Its intended for techinaly skilled brokers.
It's opt-in. If you don't want to use it, you never have to.
Please gigi. Don't just jump on the bandwagon. Please compile from source
He does not have good reasons for his positions though.
In the second part of a recent podcast in conversation with Paul Sztorc he admitted he hasn't even read the drivechain bip but offers opinion and commentary against it as though he knows the topic.
He is worst than a bad faith actor.
He has listened to hours of discussion about drivechain, is paid by his company to do research, but can't or won't read the bip.
Again. It doesn't create bitcoin, Only miners can mine bitcoin. Drivechain creates a locked "fake" token representing the real bitcoin ON LAYER 2.
This token can be redeemed on L1 for the same amount that went it. It does not create more bitcoin on layer one.
Sorry micah, i wrote this while i should have been asleep. I misunderstood what you were saying. Late night posting is dangerous.