BitScript
@bitscriptapp
Followers
885
Following
1K
Media
135
Statuses
312
Browser-based ₿itcoin script integrated development environment | Getting Bitcoiners off the sidelines & into the stack - why not you?
Joined July 2023
Both sides seem p entrenched, would you support a BIP aiming for the middle?
Would you support a BIP that: 1. Decreases OP_RETURN to 256 bytes 2. Removes the SegWit discount 3. Activates OP_CTV, OP_CSFS, & OP_CAT? Curious, if not, why not? Gib some visibility if you can plz 🙏, tryna see something:
0
1
3
Chad “we should build Bitcoin how we want” Gloria vs. Virgin “capitalism is evil” Luke. (I’m sorry but if the former bothers you more than the latter you’re a deeply unserious Bitcoiner & should immediately sell)
0
1
11
We’ll communicate here more frequently on what’s coming down the pipeline. For now we want to give a ~warm~ embrace to many of the folks along the way that gave us feedback, introduced us to the community, & generally had our back - a deep thank you 🙏 to the following:
2
0
9
Exhilarated that we can ~finally~ talk about this 🙌 Deep, deep sense of gratitude for the community we’ve built & the supporters along the way. While this failed as a business, we’ve proudly made BitScript FOSS to continue the mission: onboard the next 1000 Bitcoin developers!
👩🏫 The Global South is underrepresented in Bitcoin development BitScript (@bitscriptapp) trains devs across Latin America & Africa to build #Bitcoin tools via a browser-based ₿itcoin Script IDE. With HRF’s support, it’s diversifying Bitcoin development to reflect global needs
1
6
20
If you’re a SWE interested in working on Bitcoin (or crypto), one of the biggest mental shifts is to switch from: "How can I fetch / pass in X" To "How can I verify / proof X” Critical intangible. Start with digital signatures & Merkle proofs.
1
2
12
One of my favorite tricks when looking at bytes in Bitcoin is to look at the *length* of the buffer. Surprisingly, that alone usually reveals useful info: 20-bytes -> most recent hash was RIPEMD160 32-bytes -> most recent hash was SHA256
1
3
11
Take a break from Core vs Knots & brush up on digital signatures. By *far* where the majority of Bitcoin innovation actually takes place, here’s a quick list to get you started👇 ECDSA Multisig Schnorr MuSig2 Frost Roast Adaptor Blind Lamport Quantam-resistant
4
11
55
❎ vibe coding script ✅ using BitScript
0
0
2
11/ Which P2P feature matters most for Bitcoin’s security? Peer discovery | Block relay | Tx relay | Misbehavior handling | other Reply with your pick 👇
1
0
2
10/ From peer discovery to banning bad actors, Bitcoin’s P2P network is a carefully engineered, attack-aware gossip mesh. No servers. No leaders. Just code + cryptography + incentives. 📡 See it in action: https://t.co/A0WE2JsAPm
https://t.co/HawhsGURAg
github.com
Bitcoin Core integration/staging tree. Contribute to bitcoin/bitcoin development by creating an account on GitHub.
1
0
1
9/ Misbehaving Nodes 🚫 Nodes track a banscore for peers that waste bandwidth or send invalid data. If the score exceeds the -banscore threshold, the peer is banned for -bantime seconds (86,400 by default, or 24 hours). This protects the network from bad actors without any
1
0
1
8/ 🗄 Full nodes keep a mempool in RAM for valid, unconfirmed transactions that could be mined in the next block. 💾 RAM-only, cleared on shutdown (except wallet txs), so unconfirmed txs disappear over time as nodes restart or free memory. 🔄 Stale block txs are re-added, then
1
0
1
7/ Transactions follow the same announce → request → deliver pattern as blocks. 📤 Node sends inv with tx ID 📥 Peer responds with getdata 📦 Full transaction sent in a tx message Valid txs are forwarded under the same rules. BIP339 (wtxidrelay) uses the wtxid
1
0
1
6/ Sometimes a block arrives before the previous block in the chain. Bitcoin Core stores it as an “orphan” until its parent block is received. Once the parent arrives, the block can be linked & validated. Different from a stale block ❌, which lost a race to be in the main
1
0
1
5/ When a miner finds a valid block, it must share it with peers quickly. 📢 Bitcoin uses a 3-step pull model: Announce → Request → Deliver. For blocks, this can happen via: 1️⃣ INV (classic): send block hash, then the peer requests the full block 2️⃣ Direct headers (BIP130):
1
0
2
4/ After connecting to peers, a new or out-of-date node must download & verify the entire blockchain. Bitcoin Core uses headers-first sync: 📜 Ask for 2,000 headers at a time 🔍 Verify PoW & total chainwork ⚡ Fetch block bodies in parallel from many peers Result:
1
0
2
3/ When a node connects to another: 1️⃣ Sends a version message (protocol version, services, best block, timestamp) 2️⃣ Receives the peer’s version 3️⃣ Exchange verack to confirm After that, nodes may exchange getaddr / addr messages to share addresses of other
1
0
3
2/ How does a node find friends? 🌱 DNS seeds (hardcoded) give a starting list of peers 📡 Address gossip (addr, addrv2) spreads new IPs 🤝 Feeler connections test random peers for liveness 🗂 All saved in addrman (on-disk DB) for future restarts Goal: a random,
1
0
2