Avatar
⚡️ᗪㄖ匚⚡️
3129509e23d3a6125e1451a5912dbe01099e151726c4766b44e1ecb8c846f506
@NostReport | Physician | Bitcoiner | #plebchain | #docchain Think about it, do it.

Yea you’re right. Way too early for a play like this. Maybe he should have waited till we get over 10k daily active users first 😂

Even if profit is the primary motivation, it’ll be pretty damn bullish for Nostr if someone is willing to put $5m up for the domain.

Wen Tindstr™️?

#datechain

GM Nostr! Was in a funk this morning until I heard this. 🔥 nostr:note1yu2a7yztuuc7wpfsa92nr0cj7ghp7me36eegtjpyspl84rm09nksaem8vx

Damn just tried this… went to advanced and then restore seed. It wanted to protect with a pin and then connect to Green 🤔

Are there any other ways to easily make a QR code from my current seedphrase so that I can use the Jade as an airgapped signing device?

Holy crap. Amazing tutorial man. Just went through this and set up with a super easy air-gapped solution. Question… can I make a QR using the Jade with a seed phrase that I already have?

We are switching over to Epic right now. I’ve used epic before. It sucks, but at least you have access to everyone’s records. It’s built with billing as the focus, not clinical practice. We need an open source solution.

Replying to Avatar bitcoinaz

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

Ok cool… but why do we NEED drivechains again?

Getting my covered #Bridgestr in this weekend at the cabin

Nice, I had to turn off NWC bc it was causing issues switching back and forth from the Nostreport account

I use both. I actually like nostr:npub1wxl6njlcgygduct7jkgzrvyvd9fylj4pqvll6p32h59wyetm5fxqjchcan better, it’s faster than opening up my Zeus wallet.

Apologies, it wasn’t my intent to misrepresent your thesis. My understanding from your article “The Place of Drivechain in Bitcoin’s Future” was that:

Bitcoin needs mass adoption otherwise it will die. And “without Drivechain, Bitcoin will be a fragile success in the best case and dead in the worst case scenario.”

Anyway, even though I don’t have the technical chops to know the right way to scale, I appreciate the different points of view and ways to attack the problem. Build on brother 🤛