brice.btc

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

@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 - addevent.com/event/h0tncsjx…

Proposal: limit `at-block` to a 6-tenure lookback in a new Clarity version. Anything older returns an error. That lets nodes safely prune old state. We think this is a big win but want input. Are you using it? Is 6 tenures enough? forum.stacks.org/t/chain-state-…

Chain state on Stacks keeps growing and it’s starting to hurt. Running a node is getting more expensive. We’d like to support pruned nodes, but one thing blocks it: `at-block`. It allows Clarity contracts to read any past state, so nodes must store the entire history. 🧵 👇

@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?

we're up to 163 endpoints on stx402 self-register your endpoint (using x402!) 👇

@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 github.com/stacks-network…

@obycode @alexlmiller @mrwolf_btc @Stacks In ~1 month 2TB SSD won't be enough to run both BTC and Stack node.

Do you run a @Stacks node? Curious to see how decentralized we really are 👀

@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.

@JakeBlockchain @RaphaStacks We can just sponsor the user's gas fees and absorb from other fees or small BTC fee. User should not even know what gas fees are. Users paying gas fees is like asking user to pay for making a SQL query 😂

Champs need it yesterday

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.

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.

🚨 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

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

#5 overall #1 on Bitcoin Builders are here and they’re building on Stacks 🟧 Source: @ElectricCapital

🗳️ Voting for SIP-033: Clarity 4 is now live! Cast your vote on the new platform built with the Ballot aka @BlockSurvey team → stx.is/clarity4vote 📅 Vote window: Oct 16 – 30 More details here: stacks.org/sip-033-vote

@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

@herogamer21btc @privy_io @turnkeyhq @obycode @RaphaStacks @rockyntheblock @attractfund1ng @ECBSJ @KenTheRogers So the big benefit is Privy leveraging the new Clarity4 curve? That’s what I’m reading.

🧠 Learning about the trade-offs between: 1. @privy_io 2. @turnkeyhq 3. Stacks without native secp256r1 support 4. Stacks WITH native secp256r1 support (Clarity 4 Upgrade will enable this) 💬 ChatGPT Conversation here - learn with me: chatgpt.com/share/68e91132…

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!

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

@obycode @v1n1_c0d35 @alexlmiller @mrwolf_btc @Stacks ~2.3GB/day

@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?

@obycode @v1n1_c0d35 @alexlmiller @mrwolf_btc @Stacks If observers are down, or can't keep up - so be it. Node still will be able to do its job at max perf. And separate thread solely responsible for sending events will keep pushing events at the pace observers are able to handle.

@LNow_ @v1n1_c0d35 @alexlmiller @mrwolf_btc @Stacks Agreed, this is a limitation in the event observer setup. The node just knows that it has an observer that it is supposed to send every event to, but it has no way of knowing that it should send any before it reaches tip or any other logic.

@obycode @v1n1_c0d35 @alexlmiller @mrwolf_btc @Stacks So it looks like signer doesn't have any information whether node is sill trying to catch up with the network, right? I don't know all the details, but it seems counterproductive when singer talks to the node, while node didn't reach Nakamoto block yet.

@LNow_ @v1n1_c0d35 @alexlmiller @mrwolf_btc @Stacks yeah, it definitely seems like the signer was a bottleneck. it makes sense that it would slow things down if the node has to interact with the signer between every single block.

@obycode @v1n1_c0d35 @alexlmiller @mrwolf_btc @Stacks Does that mean mock signer was the bottleneck? Do you know why?

@LNow_ @v1n1_c0d35 @alexlmiller @mrwolf_btc @Stacks Reached tip around 9 this morning, so around 2 days and 16 hours since I removed the mock signer.

@LNow_ @v1n1_c0d35 @alexlmiller @mrwolf_btc @Stacks Now I'm at 782451

Want to help shape the future of @Stacks? You don’t need to be a core dev, anyone can review a SIP in minutes. Here’s your beginner’s guide. (5/5)🧵👇 #Clarity4 #SIPs