brice.btc

building web3 with Stacks on #bitcoin

[stacks.btc @Stacks]

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 @obycode]

👀

[stacks.btc @Stacks]

Tomorrow.

[Stacks Developers @StacksDevs]

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.

[brice.btc @obycode]

@herogamer21btc Me!

[brice.btc @obycode]

@RaphaStacks @enjoywithouthey @JakeBlockchain @tripnm0nkey @PepeCoinSTX @cryptodude_btc @whoabuddydev 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

[Stacks Developers @StacksDevs]

"in my professional opinion, I would discourage anyone from using allow mode unless you're just testing locally." - @obycode

Here's exactly why:

[brice.btc @obycode]

@StacksDevs Or maybe we could even just get rid of at-block altogether? It would really simplify a bunch of complicated code in the node, in addition to allowing for pruned chainstate. Come chat about it in 50 minutes - https://t.co/7EaZqPj7Be

[brice.btc @obycode]

@aibtcdev Love this work! I’m looking for the docs on what exactly goes in the X-PAYMENT header. Where can I find that info?

[brice.btc @obycode]

@LNow_ @alexlmiller @mrwolf_btc @Stacks Significant improvements on this coming soon! I’m doing a genesis sync right now, currently at block 759308 and only using 25GB! Check out https://t.co/xAov6UjemK

[brice.btc @obycode]

@jakob_btc @JakeBlockchain @RaphaStacks I'd like to think about the fee more like a credit card fee. Users don't expect to pay it (not directly at least). The seller handles that fee and the buyer doesn't need to think about it.

[stacks.btc @Stacks]

gm @circle 🟠

Circle’s first move into Bitcoin DeFi is happening on Stacks, the only Bitcoin Layer 2 in their pilot launch of Circle xReserve.

Circle xReserve is enabling Stacks to bring a USDC-backed stablecoin to Bitcoin DeFi.

[WalletConnect @WalletConnect]

The next wave of Bitcoin adoption won’t come from price.

It will come from builders creating apps, markets, and new financial layers on top of it.

Leading Bitcoin layer @Stacks makes that possible.

[BitcoinYield @bitcoin_yield]

🚨 New BitcoinYield pod is LIVE!

We're joined by @andrerserrano, Product Lead at @stackslabs, to break down the new "Dual Stacking" release.

We cover:
🔸 Previous work at @Zcash
🔸 Earn native base yield for holding $sBTC
🔸 Get a 10x multiplier if in DeFi
++ more

LISTEN NOW

[brice.btc @obycode]

Don’t forget to vote for SIP-033. We’re at nearly 100% yes, but we also need to hit the 80M STX threshold.

[HeroGamer⚡ @herogamer21btc]

Thank you @dawgcoin_stx ❤️

Yes SIP-033: Clarity 4 Upgrade public voting is underway for anyone who holds $STX or Stacking STX in a pool.

🗳️ Cast vote: https://t.co/ZYhf0uzBn1

[Stacks Developers @StacksDevs]

#5 overall
#1 on Bitcoin

Builders are here and they’re building on Stacks 🟧

Source: @ElectricCapital

[Stacks Foundation 🟧 @StacksOrg]

🗳️ Voting for SIP-033: Clarity 4 is now live!

Cast your vote on the new platform built with the Ballot aka @BlockSurvey team → https://t.co/MODeVRotUf

📅 Vote window: Oct 16 – 30
More details here: https://t.co/1JokhdPpTe

[brice.btc @obycode]

@JakeBlockchain @herogamer21btc @privy_io @turnkeyhq @RaphaStacks @rockyntheblock @attractfund1ng @ECBSJ @KenTheRogers I think instead, with these new curves, the use case is one where the wallet is a smart contract and any actions on that wallet require secp256r1 signatures

[HeroGamer⚡ @herogamer21btc]

Tune in - SIP call at 10.30am ET with SIP-033 author @obycode & @RaphaStacks to talk about “secp256” - which will allow huge onboarding experience improvement.

Clarity 4 Upgrade is upon us!

[brice.btc @obycode]

@LNow_ @v1n1_c0d35 @alexlmiller @mrwolf_btc @Stacks 💯 work in progress

[brice.btc @obycode]

@LNow_ @v1n1_c0d35 @alexlmiller @mrwolf_btc @Stacks Yeah that’s a good idea to make use of that existing db for this. Want to open an issue for this?