building web3 with Stacks on #bitcoin
Baltimore, MD
Joined February 2012
- Tweets971
- Following2.4K
- Followers803
- Likes3K
brice.btc retweeted
wait so i can keep native BTC on bitcoin and borrow USDC on ethereum against it
without wrapping or bridging anything
did my digital pet rock finally learn a trick
Just vibe coded this fun little page to answer the questions I always have when driving around... "wouldn't this intersection be better as a traffic circle?" or "why don't they put a light here?" obycode.github.io/traffic/
brice.btc retweeted
STX is now live on @Bullish.
One of the largest venues in the world for BTC spot volume just listed the asset powering Bitcoin-native capital markets.
Institutions across 50+ jurisdictions can now access STX where they already trade Bitcoin.
brice.btc retweeted
The best of Bitcoin and Ethereum.
There is an idea I’ve been obsessed with for over a decade. It’s a very simple idea. It’s a trillion-dollar idea if it works.
The idea is simply to take the best qualities of Bitcoin and Ethereum and combine them.
Bitcoin is the superior asset. Ethereum has better rails. BTC is winning as digital capital. Ethereum pioneered on-chain capital markets (Solana is challenging that position). Why can’t we have best of both?
ETH tried being internet money and that didn’t work. BTC clearly won as digital capital. Ethereum rails, however, have created thriving on-chain capital markets. Not just directly on Ethereum, but on derivative chains like Arbitrum (used by Robinhood), Tempo (by Stripe), Tron (largest Tether usage), etc.
Bitcoin and Ethereum have been #1 and #2 digital assets for close to a decade now. There is obviously competition between them. ETH has nowhere else to go but try to be #1. This is what the entire “flippening” movement was about (it failed, for now).
If we take the best parts of Ethereum (like faster transactions, programmability) and vertically integrate them on top of Bitcoin, like HTTP on top of TCP/IP, then we have a scenario where the best asset, BTC, can be integrated with modern rails. Simple.
The internet didn’t become *the* internet until HTTP took off atop TCP/IP. Fragmented networks don’t become global standards. We’re still fragmented in crypto, but the consolidation phase has started.
If a vertically integrated modern rails like Stacks truly takes off for BTC, then Bitcoin solidifies its #1 spot even further. BTC gets native BTC yield, and gets deployed in bitcoin capital markets. Bitcoin can then keep evolving (like adding privacy features) without ever changing the base.
The best of Bitcoin and Ethereum. In one vertically integrated system. That’s the dream. We’ve built it at Stacks.
And as Adriano said, the case is even less likely to happen when all signers are behaving properly as we see now!
The specific problems we’re fixing in those PRs are not new issues and so the specific scenarios they’re trying to handle are rare and I don’t expect them to show up again any time soon. That particular stall was worsened by a very long Bitcoin block.
i’m the author of both of those referenced PRs. feel free to @ me with any specific technical questions.
brice.btc retweeted
With some emotion, I can say this:
Cycle 140 rewards have been distributed.
For the last time, Fast Pool admin touched your rewards.
From here on, your rewards are yours and only yours.
Stacks pools are now fully trustless. You choose the signer you trust and the reward distribution rules encoded in their signer-manager contract.
A huge milestone for @Stacks.
And yes, I’m biased, but I still don’t think there’s an alternative to Fast Pool Max500
brice.btc retweeted
We made a short visual explainer to help people understand the Coldcard bug, and what it means for the security of affected wallets.
Bitcoin's entire security model depends on a user's ability to select astronomically large numbers from a truly random set.
If you imagine every possible Bitcoin private key as individual atoms, when a private key is generated properly, the pool of possibilities is so large that it's like an attacker is hunting for one specific atom hidden somewhere across 2 billion galaxies. No classical computer could ever search that many possibilities.
Unfortunately, affected Coldcard firmware drew its seeds from a much smaller, more predictable pool. If every possible Coldcard private key was an atom, the possible set of keys would only be about the size of a large virus. In comparison, a standard computer could work through that space in just a few hours.
Our video helps visualize what this difference looks like, we hope this is helpful for everyone to establish the importance of true entropy in key generation.
We are deeply sorry for anyone who lost funds to this bug. We know several people that were personally affected, including members of the BPI team. Losing funds after working hard protect your wealth is extremely difficult.
We are developing a set of policy reflections based on this vulnerability that we hope to publish as soon as possible.
Make sure to upgrade your nodes before the hard fork ~July 29. github.com/stacks-network/st…
brice.btc retweeted
Hold BTC. Earn BTC. That's what Bitcoiners want.
Today we're publishing the Bitcoin Staking whitepaper.
Self-custodial. BTC-denominated yield.
Here's what it is and why it matters 🧵
brice.btc retweeted
REQUIRED UPGRADE BY APRIL 2 🚨
Stacks Core 3.4.0.0.0 is live.
If you're a signer, custodian, exchange partner, validator, or running a node you MUST upgrade.
I’m not sure I get the use case. The contract hash is most useful when calling traits passed in from users. If you just want to check a contract before calling it, you can do that off-chain
brice.btc retweeted
"in my professional opinion, I would discourage anyone from using allow mode unless you're just testing locally." - @obycode
Here's exactly why: