🤖 You won't believe these 100 ways GPT-4 can make your life easier! Say hello to your new AI best friend! 👋 A thread: #GPT4 #AILifeHack

ctxm is open source: github.com/jiga/ctxm Auto research harness included. Swap in your eval. 30 experiments. $0.15. 12 min. What system are you pointing this at?

Some independent app builders in the Stacks ecosystem were recently targeted via Github in an effort to insert malicious code in their app repositories. We have found no evidence of an attack or compromise of the sBTC or Stacks Core repositories, but because some of these open-source devs also contributed separately to other ecosystem projects (including sBTC), we are taking the opportunity to review security practices around sBTC and Stacks Core and provide more guidance to contributors about their personal and company setups. Core development (including sBTC) already has extensive security practices in place including least-privilege permissions, branch protections, multi-man rules, MFA, code audits, and more. But as the Stacks ecosystem and sBTC usage grows, attempts on our software development process will become more common. We’re prepared for this increased scrutiny on our Github repositories and continue to strengthen our security practices. Stacks core devs are working with internal and external security experts to further tighten our software development process. We’ll publish a more detailed analysis of the attempted attack and security measures that helped catch it, along with information on upgraded security processes to help prevent future attacks. There are no user-facing changes at this time and no steps that users need to take - sBTC and the Stacks network continue to function as normal. Please note that as part of the sBTC development plan, it has filled its 3,000 BTC cap, and withdrawals are not enabled, so it is not currently possible to peg in or peg out of sBTC. You can always report anything suspicious or find more information on security at stacks.org/security.

StacksPay is a SIP proposal so your feedback is invaluable. Help us shape the future of payments on Stacks by reviewing and commenting on the proposal here: github.com/stacksgov/sips/pu… Documentation is in progress on the StacksPay web site: stackspay.org

⌛️Have you voted SIP-029: Preserving Economic Incentives During Stacks Network Upgrades? Shape @Stacks future - your voice matters🧡 📅Vote ends: ~Sunday, Dec 1st (Bitcoin block 872,750) 👉Cast vote: stx.eco 🔗More details: stacks.org/sip-029-vote-over… 👇Tables

RT @muthusleuths: How to install a @Stacks full node on your @Umbrel. You can find links referenced in the video in the replies. Restrict…

867,867

🔥 Nakamoto 3.0 is live on Nakamoto Testnet Nakamoto Mainnet: Bitcoin Block #864864 Exciting

Stackers, Core Developers have selected the Nakamoto hard fork block! Let's meet our block, but note some important details first: 🧵

No - for Nakamoto upgrade Yes - for sbtc v1 upgrade

I think I need to try a different way. Does the initial rollout of the @Stacks Nakamoto upgrade only allow a permissioned set of block producers ?