6B002C6EA3F91B1B0DF0C9BC8F617F1200A6D25C
- Tweets 1,762
- Following 166
- Followers 17,244
- Likes 6,128
erm, did not expect this but now that i have ur attention, freeross.org/ could use some mobbing too
51
86
1,883
how is bitcoin different from venmo tho?
they’re both peer to peer right, is it just implementation details?
90
83
761
men, why aren't u holding ur women? 🥺
Men are 4x more likely to hold #Bitcoin than women - Fortune
Ladies, what’s stopping you? 🤷🏻♂️
120
24
698
hot take: you can’t live in your bitcoin, you can’t eat your bitcoin, your bitcoin isn’t growing old with you. I don’t understand regrets about selling at a lower price to make those purchases. What is money for, other than to spend it on building your life?
147
31
609
96,017
Book of Nakamoto, Chapter 3, Verses 4–11
And Satoshi spake, not in whispers but in hex, saying:
“Thou shalt not embed thine data in every field, for the blockchain is not thy diary.”
“Yet I bestow upon thee OP_RETURN, a sanctuary for up to 40 bytes — no more, lest ye walk the path of vanity.”
“For 40 is the number of discipline: 40 bytes for thy message, no more than is righteous, no less than is truthful.”
“And behold, I give thee one more blessing: the coinbase message. A field untouched by consensus, wherein miners may write freely.”
“Use it to bear witness, to mark genesis, to declare revolt — as I once wrote about the Chancellor”
“But thou shalt not waste it with shills and tokens of greed, or the wrath of prune shall be upon thee.”
And so the nodes upheld this covenant, and the mempool was serene.
So go forth, brothers and sisters. Let us inscribe only that which is worthy.
And let thy payloads be small, lest one abuse the sacred ledger for thine idle bytes.
In the name of the Nonce, the Witness, and the Unspent,
Amen.
67
102
587
87,475
Feeling like the luckiest person in the world... I get to work on #Bitcoin full-time after I graduate???
Eternally grateful to @adamcjonas, @amizi and @jfnewbery for the orange pill
and to @bitcoinbrink, @HRF, and @sqcrypto for making dreams come true <3
Bitcoin development nonprofit Brink (@bitcoinbrink) has awarded its first fellowship to Gloria Zhao (@glozow), who will work on package relay for Bitcoin mempools.
Our Aaron van Wirdum (@AaronvanW) breaks the news:
bitcoinmagazine.com/articles…
36
23
513
THE MOST PRIVATE OPTION YOU CAN OFFER TO THE USER SHOULD BE THE DEFAULT SETTING, THEY SHOULDN'T NEED TO MANUALLY SET IT
7
30
362
Seeing #bitcoin in Argentina humbled and inspired me.
Stories about gov rug pulls and black market cash trades seemed quite abstract to me as an American, so I've always wanted to visit. All expectations were met within 1h of landing in Buenos Aires.
0/n
17
40
362
585 github comments, 3 mailing list posts, and 4 Delving threads later:
Merged PR from Gloria Zhao: v3 transaction policy for antipinning github.com/bitcoin/bitcoin/p…
30
102
301
27,159
Please send this to whoever doesn’t think moderation in an online community is necessary.
The Bitcoin Core github org has suffered from a lack of moderation for years - killing projects and burning out contributors - and we should thank software engineers who give up their time to be moderators.
First, just imagine an online forum where technical people come to discuss Bitcoin. The community is thriving if the quality of technical discussions is high, and many people visit the site when they are curious about a technical subject. Disagreements are fine and, in fact, it’s a sign of success if people feel comfortable debating topics there.
Anyone who’s participated in any online forum knows that spam is always abundant. Clear-cut stuff is easy to hide and ban: “you’re an ugly <noun> so I will <verb> you,” “Bitcoin was sent by aliens to enslave us,” “Bitcoin was sent by God,” “you should buy my token” etc. But mods struggle when it goes beyond that.
It only takes 1-2 usernames and an LLM to fill up a thread with technical slop, drown out all the actual content, and kill intelligent discussion entirely. Nobody is obligated to stay there and continue arguing the reasonable side; they can and will leave at any time. The smart people can start their a private group chat where they don’t have to deal with OurLordSatoshisProphet9999 and SelfSovereignGovHater21, who doesn’t even know what a signed integer is.
In the Bitcoin Core repo, these threads are PRs where people review code that adds user-facing features, fixes vulnerabilities, and contributes to complex projects. These PRs are necessary as the security model, performance requirements, and testing infrastructure scales with the amount of real people’s money dependent on this software.
And the Bitcoin Core repo suffers from the exact same problem as all online forums. Year after year, projects grind to a halt because they are brigaded by a storm of people from twitter, one guy with an LLM (or is just really verbose, I can’t tell), or someone who is a technical contributor but harasses people by nacking their PRs with walls of text. In annual surveys of Bitcoin Core devs, people often name the same 3-4 trolls as the worst part of working in the repository.
It’s already difficult to get people to care about your PR. If reviewing your PR requires reading thousands of angry words and getting dragged to the whipping post on twitter, maybe I’ll just go look at one of the other 300+ PRs open to the repo. The discussion dies, the author can’t get reviewers to come back, and they have to close the PR. Maybe things cool off, 2 years later people think it’s a good time to revive it, it’s reopened, and the brigading returns. Regardless of how you feel about OP_RETURN, if it’s so easy to stop code progress, it’s a sign the community is poorly managed.
So yes, it is appropriate and important to keep discussions on topic by hiding off-topic comments, penalizing users who refuse to follow basic guidelines for discourse, and asking people to take conversations elsewhere. Additionally, we should thank the people who volunteer their time to moderate when they could be writing code. Everybody hates to do it - especially Bitcoiners - but it has to be done. And it is not fun.
Sometimes, mods can’t keep up, especially when the number of brand new commenters on a thread is higher than the number of regular contributors to the entire repository, so it needs to be locked. That’s unfortunate, but it’s the only action left when brigading gets to that volume, short of requiring permissions across the entire repo - we have discussed that idea and always feel uncomfortable with it.
I don’t think the process is perfect, but there are many false claims about what moderation actions have been taken.
I disagree that moderation of the repo is “censorship” or “attacking” Bitcoin to enforce rules of engagement within a community. The Bitcoin Core repo (again, a code collaboration platform) is far from the only place where people can discuss Bitcoin. In fact, it is *not* the appropriate place for discussions that should involve the wider ecosystem, as Bitcoin Core devs are not representative of Bitcoin. That is why PRs touching network/protocol often start with a mailing list thread. We *don’t* want the conceptual discussion to happen in a place that we moderate.
The decentralized open source repository that is Bitcoin Core means software development on hard mode. Developers put up with a lot, but they continue to work in public precisely because they believe in censorship resistance, open forums, and transparency. Let’s not punish them for their ideology by forcing them to deal with threats, harassment, and brigading while they are at work.
59
50
314
40,925
Always struggling to accept that much of Bitcoin twitter consists of people I'm embarrassed to be grouped with. But we're here to write code they, among others, are free to use, because that's the whole point of Bitcoin...
43
14
277
22,841
Bitcoin Core has not merged any of the PRs changing OP_RETURN limits. Observe that the PRs are still open.
github.com/bitcoin/bitcoin/p…
github.com/bitcoin/bitcoin/p…
PRs that change userspace or change policy defaults require release notes. It was apparent OP_RETURN limit changes would require a longer-form explanation.
@theinstagibbs volunteered to create a writeup. This writeup was shared publicly for review, just like everything else that is proposed for merge to Bitcoin Core.
gist.github.com/instagibbs/c…
People are tweeting a screenshot of the writeup to show that Bitcoin Core has gone ahead and merged it. This is wrong. In general, ask for sources when you see screenshots.
I completely reject the idea that draft release notes should be kept private before merge. Stop punishing people who choose to work in public.
32
47
283
30,901
It’s incredibly disrespectful to Satoshi to try to dox / speculate about identity after they made it abundantly clear that they want to protect personal privacy
24
28
273
11,144
Obviously crushing when some Core users don’t seem to value its reproducible + verifiable builds, agonizingly long review process, security policy, decentralized dev team, commitment to working in public.
But if you don’t know why you were running Core in the first place, you were trusting, not verifying.
63
18
274
58,403
Today is my 4-year brinkieversary! @bitcoinbrink was my first job out of college, and I was its first dev 🫂 we grew up together.
I’m feeling sentimental today - this was my desk in the first London office, a 10ft x 10ft wework fishbowl. I was taping txout types and CTransaction fields to the wall to remember them.
Today Brink celebrates Gloria Zhao’s (@glozow) 4 year anniversary at Brink! 🎉
In her first Brink epoch she went from Brink fellow to Bitcoin Core maintainer while championing several big projects in Bitcoin development…
brink.dev/blog/2025/01/04/gl…
19
17
247
17,194
There have been a number demands that Bitcoin Core use transaction relay policy to prevent certain kinds of transactions from being mined based on use case. This idea has been controversial for various reasons, including:
- Bitcoin Core is a completely voluntary piece of software that may or may not be run by miners. It cannot force anybody to do anything at all.
- When transactions are reliably mined in blocks, disallowing them in default relay policy only serves to harm mempool utility and block propagation.
Many contributors have communicated these arguments individually, but don't want to speak on behalf of others by saying "this isn't the project's direction."
Other projects state explicitly that filtering is one of their development priorities. That is their prerogative, but it seemed clear that Bitcoin Core's contributors don't share this priority.
This statement was an attempt to verify this - soliciting opinions from as many active contributors as possible - and communicate it to the public.
This isn't an official top-down post from a corporation's marketing department, but a rare case of public alignment amongst a group of people who staunchly avoid centralized direction.
I hope you can appreciate how widely supported something must be if a wide majority of contributors are willing to put their name on it.
A statement on Bitcoin Core development and transaction relay policy - bitcoincore.org/en/2025/06/0…
79
33
231
68,084
Just used Bitcoin Core v28.0rc1 to broadcast and (package) relay a ZERO FEE tx cpfp'd by a high fee child on testnet4, using TRUC transactions. Look at that 1-1 straight flow arrow!
Who is the Unknown miner of block 41657? Thanks for mining my package :)
mempool.space/testnet4/tx/8e…
20
37
229
52,498
A horror story about custody
1/ Let’s say u keep ur coins in an exchange that’s all about c o m p l i a n c e, gives u pretty UI and is insured and everything. U don’t self-custody bc ur scared ur gonna screw it up and lose hr coins. Ur too shy to ask matt for help
12
34
203
Some people seem to have missed the summary accompanying the OP_RETURN defaults increase, so I'll post it here again. It has absolutely nothing to do with *wanting* arbitrary data stuffed in the chain.
199
25
219
79,473
i feel like daylight savings is one of those things that should be application layer not protocol layer 🤨
7
15
207
Bitcoin Core v29.1 is available. See release notes for more details. bitcoincore.org/en/2025/09/0…
A new release candidate of Bitcoin Core, v29.1rc2, is available for testing. This is a new minor release, and follows v29.0.
Release notes: github.com/bitcoin/bitcoin/b…
Binaries are available here: bitcoincore.org/bin/bitcoin-…
133
22
202
50,285
A core mission of Bitcoin is to enable anyone, anywhere in the world, to send a payment. This means designing a transaction broadcast system that is permissionless, censorship-resistant and private by default.
As you might imagine, designing a p2p tx relay system is hard. 1/🧵
2
41
193
People are asking about "Luke being hacked/removed from the Transifex" so here is the full IRC log from that day.
erisian.com.au/bitcoin-core-…
Here is a summary (please do your own reading + let me know if you think this is misrepresentative and I'm happy to edit it):
1. Translators were confused that Bitcoin Knots strings were suddenly added to the site. @hhebasto, who maintains the Transifex site, brought this up in the weekly IRC meeting.
2. Luke asserted that the Bitcoin Core translations page should be used for Bitcoin Knots because "Bitcoin Knots is part of the Bitcoin Core project."
3. Contributors found this absurd and advocated for removal of the Knots strings.
4. Luke rejected this decision and edited the page to say "Bitcoin Core & Knots". He also removed all other admins from the project.
5. @hhebasto was able to recover access and restore the page.
6. Luke's Transifex privileges were revoked due to this clear misuse of them.
Bitcoin Core's supported features, including translations, come from the community. Please contribute translations and review - we frequently see scams, ads, and garbage stuffed into translation strings. Unfortunately, that often means removing translation updates wholesale. Devs can cover a pretty wide range of languages between us, but not all of them.
17
23
194
33,257
light clients act as servers to other clients and are also serviced by nodes but they’re also nodes. or are they? idk...😐wrote this simplified #Bitcoin network map link.medium.com/TDtdK0P957
9
59
189
Today, I've been at @bitcoinbrink for 3 years!
I'm grateful to be supported by an org that focuses on technical contributions, supports edu initiatives, allows us work independently, and is funded through community donations. And doesn't use twitter to make grant decisions💀
18
9
177
19,315
voice assistants listen to + process everything you say and respond when you say the trigger word
they dont only start listening when you say alexa goddammit
why do u think companies hand them out like candy, they get a free 24/7 mic in ur house and u get weather reports
11
28
157
wordle except you guess the SHA256 hash of a block of transactions, but instead of a new puzzle every day you get it every time someone else guesses the last one. the best part is u get free no-KYC BTC when u win. also theres computers optimized for it.
9
28
161
Can't believe someone bribed @mempool into adding a submitpackage endpoint.
It all happened after they opened a github issue - extremely suspicious.
Packages ARENT EVEN A THING ON CHAIN. Next thing you know, they'll start displaying FEERATES too.
mempool.space/tx/push
21
16
157
15,767
A release candidate for the next major version of Bitcoin Core is available 🚀
We need you to test it. This helps find + fix bugs *before* release.
Don’t know how to test? Some wonderful people made an awesome testing guide and will walk us through it at review club next week:
In next week's review club, we'll test a release candidate for Bitcoin Core v27.0.
cbergqvist, tdb3, davidgumberg, marcofleon put together an extensive Testing Guide.
Do the "Preparation" steps first, and we'll walk through the guide together next Wed!
bitcoincore.reviews/v27-rc-t…
9
48
140
38,156
Fwiw, as somebody who is outspoken about digital privacy, I dislike seeing people prying into our personal lives just because we contribute to software that they use.
That is distinct from transparency in the development process, which I think Core takes to the extreme and makes the development culture truly special.
The combination is illustrated well with in-person meetings: pseudonymity and no-photos policy are sacred, but discussions are transcribed (Chatham house) and posted publicly so that they can be referenced and viewed.
Hey Dennis, as the co-organizer of most of the Bitcoin Core developer meetings in the last years, I can say there is no industry lobbying at these events. They are for the Bitcoin Core project contributors, not for industry.
You can see all of the events, each events' sponsors, as well as transcripts for the sessions (which began in the last years) here: coredev.tech/pastevents.html
Sponsors of these events simply have an acknowledgment of their sponsorship of the event on the website, which also serves as transparency as to who is sponsoring these events.
You are welcome to query or corroborate that these events are in no way related to industry lobbying with other co-organizers like @adamcjonas @moneyball @_jonasschnelli_ as well.
I wont tag the attendees of these historical events out of privacy, practicality, and out of consideration for not annoying them with this on social media, but they are welcome to attest to their experiences at these events as focused on Bitcoin technicals and the Bitcoin Core project and not in any way a venue for industry/companies to come lobby them.
--
Also, as the executive director of Brink, who I believe you are referring to as the recipient of Marathon's $500,000 donation, I can speak to that as well.
As a 501(c)(3) nonprofit, Brink must operate exclusively for the public good, not to benefit any individual, company, or donor. Donors cannot, and do not, direct our operations, programs, or decision-making.
Our donation agreements specifically also outline this clause: 'NO QUID PRO QUO: The Donation is made voluntarily and without expectation of goods, services, business advantages, or promotional benefits in return.'
Additionally our board of directors, including independent members, approve all donations of this size before we accept them. They have the sole and final authority over how all funds are used, and we are very protective of that independence. This ensures that every gift furthers Brink’s charitable mission and preserves our nonprofit status. There have been 8 board members of Brink over these 5 years of operation, 6 of which are independent from Brink (myself and John as co-founders being the other two). All of these board members have been publicly named and their reputations speak for themselves. Here are their twitter handles if you are curious: @jfnewbery @jerrybrito @actuallyCarlaKC @hrdng @Snyke @jonathanbier @Leishman @bitschmidty (this tagging will also alert them to this post so they can call out any falsehoods in my explanations)
We, voluntarily, also pay an third party independent auditing company, Rogers & Company, who can and does review these agreements and the associated donations, and flows of money in and out of Brink to ensure compliance.
This voluntary audit, that we choose to do and pay to do each year, is separate and in addition to our other obligations we have for compliance like annual 990 filings.
Additionally, we have a separate grant committee, that also includes independent members, who help decide which engineers to fund and which to continue funding. The quality and reputation of these members over the years also I believe speaks volumes.
The engineering applicants for Brink and the engineers that we end up funding, choose their own focuses for projects, sub projects, and research areas. We simply provide them the funding to execute on their vision.
Additionally, we specifically have crafted the agreements we have with the engineers that we fund to be favorable for their independence. For example, for the engineers that we employ, we have a zero notice out clause for engineers, so that in the event Brink acted in a way they object to, they can immediately terminate the agreement (whereas Brink must give 3 months notice). We also simply state in the agreement that the expectation we have of the engineers is to execute the work described in their own proposal.
The board, the grant commitee, myself, Emily (who oversees much of the administration, operations, and compliance), and the donors do not direct the day-to-day work of the engineers.
Any of our current or past engineers can also happily attest or object to anything that I have said here: @macrohead7 @fanquake @hhebasto @theStack @dergoegge @stphnvlstk @fjahr Crypt-iQ (no twitter), @jesseposner, @lightlike1, @brrrunog, @0xB10C, @tdryja, @afilini, @larryruane, @palazzovincenzo, @glozow
I hope that both the structure of Brink, our processes, as well as the number and independence of people involved at all levels that Ive outlined here can show how seriously we take the independence of Brink as an organization from our donors as well as our engineers' freedom from Brink as an organization.
33
14
154
20,066
DEVS NUKED THE WALLET, BASICALLY DELETING MONEY, WHY IS NO ONE TALKING ABOUT THIS
(In all seriousness, huge props to @achow101 for dealing with 6+ years - SIX YEARS - of rebase hell in order to support legacy wallet migration as smoothly as possible)
Merged PR from achow101: Remove the legacy wallet and BDB dependency github.com/bitcoin/bitcoin/p…
30
13
177
30,170
A very pleasant surprise from @0xb10c this morning on compact block reconstruction stats improving to 80% with the min feerate changes!
24
29
144
21,422
For people who are unfamiliar: "Locked" means nobody can comment other than people with write access on github (which is almost nobody).
That *also excludes members of the org*. The purpose is a cooldown, that's why none of the people with write access comment either.
There is no need for the "I've contributed so much why can't I comment" chest-thumping.
31
13
133
20,628
hey y'all if we hit $20k sometime, my parents might forgive me for not going back to google and I can ask them if I can move to London 🥺 everybody please stack some sats today ok? 🙏
Hi folks my parents would be super proud if we hit a new all time high on launch day so if y'all could just stack a few more sats that'd be tremendous thx
3
2
129
It's so surprising that computers require energy! Just found out that the Lord of the Rings films required a 3200-processor server farm, running for 9 months, to produce the visual effects.
wired.com/2003/12/the-wall-o…
1
21
121
hoho, some of u convert ur fiat to bitcoin just so u can convert it back to more fiat later and it shows
10
7
123
gov: u can't multiply numbers anymore because it hurts national security. also we request u don't use big words in ur diary, and english only, please!
1
12
122
relaaax, all other coins are basically testnets. they are funding research and playing out good/bad ideas for us
11
6
124
8,094
Generally, it is resource intensive and unreasonable to demand a full refutation each time Luke makes an accusation against Core, and I'm not going to make this a regular thing. Instead, I request that everybody ask *him* to provide evidence when he makes claims.
9
8
123
5,325
there is so much development work in bitcoin privacy, please do not negate all of it by delivering your IP address + txid on a web request silver platter to block explorers 🤦 at least use a VPN
bruh, if you don't run your personal block explorer with @mempool on your umbrel and instead use a public explorer to lookup your transactions/balances, you're ngmi
2
19
119
gm. soft forks are overrated, the interesting stuff is in the p2p network.
@murchandamus and I just finished our 10w series for @bitcoinoptech about mempool, saving on fees, tx relay policy, DoS and censorship, and improvement proposals.
Give it a read: bitcoinops.org/en/blog/waiti…
8
28
115
12,712
In case it wasn't already clear, this suggestion is the only PR that is open at the moment. #32406 changes the default -datacarriersize and leaves the config option intact.
A good compromise between both camps could be to change the OP_RETURN defaults as originally intended and leave users the option to adjust their node's parameters.
That way, users who don't agree can opt out and still use Core.
And we all march stronger into the future.
38
11
123
37,025
WAKE UP BABE
4
9
109
7,479
I've written a summary of the arguments surrounding the datacarriersize PR #28408: github.com/glozow/bitcoin-no…
One of my fav things about bitcoin core is how much of dev history/discussion is public. Here is the timeline of datacarrier code/doc changes. It is for op_returns.
21
21
94
22,888
Woooooo auto-cpfp when spending unconfirmed utxos is here @murchandamus
github.com/bitcoin/bitcoin/p…
6
25
110
16,734
WOOOOOO 💃🏻📦
Merged PR from Gloria Zhao: rpcvalidation enable packages through testmempoolaccept github.com/bitcoin/bitcoin/p…
2
1
103
coming soon: Child Pays For Parent And For Replacing Parents’ Conflicts Even Though Parent Doesn't Meet Minimum Mempool Fee (CPFPAFRPCETPDMMMF)
14
5
102
😱 in 26.0, you'll be able to use the submitpackage RPC to CPFP below-mempoolminfee transactions on a node (note this does NOT mean the transactions will propagate to peers/miners).
Merged PR from Gloria Zhao: rpc allow submitpackage to be called outside of regtest github.com/bitcoin/bitcoin/p…
6
26
82
13,021
9/10 when I tell someone (including swes) what I do for a living, they don't believe me because "nobody works on Bitcoin" or "the protocol is fixed bc of PoW." or they believe me but "why work on a ponzi scheme that harms the environment."
that's the problem, not just funding 🥲
3
4
93
@murchandamus and I are writing a weekly series with @bitcoinoptech about mempool, fees, standardness/policy: bitcoinops.org/en/blog/waiti…
The goal is to start conversations about how we can build a better tx relay interface for users, L2 protocols, and applications as a community.
3
45
91
16,841
NUMBER GO UP
0 -> 1 FELLOWS
The grant we gave Brink (@bitcoinbrink) is going to support Gloria Zhao (@glozow), the first recipient of a Brink fellowship. This fellowship is partially funded by us and partially funded by @HRF’s Bitcoin Development Fund.
4
3
86
does anyone in London need a roommate 🤓
We're thrilled to announce @glozow as our first fellow. Welcome Gloria!
brink.dev/blog/2020/12/01/gl…
8
2
87
If you're in London for @advbitcoin, join us at bitdevs this Wednesday evening in Shoreditch!
It's a socratic seminar hosted by @Stphnvlstk @ConorOkus and myself. We'll chat about what's been going on in bitcoin dev/research.
Drinks on @bitcoinbrink ;)
meetup.com/bitdevsldn/events…
7
29
79
18,692
im so nervous for this i put on makeup for an irc meeting 😅 in ~3 hours!
Next Wednesday's Bitcoin Core PR Review Club is on PR 19339 "Re-delegate absurd fee checking from mempool to clients" (rpc/rest/zmq, tests, validation, wallet). Notes and questions are up -- thanks @gzhao408 for hosting! bitcoincore.reviews/19339
6
3
86
hey shadowy coders, we're gonna look at some secret code together today. just kidding it's open source. i also wrote some notes to help you understand it. come through it'll be fun
afterward, we're gonna hack into the main frame and crash the d-base. bring ur illegal drugs!
Notes and questions for next week's meeting are now posted. We'll be reviewing PR #22155: "Wallet test: Add test for subtract fee from recipient behavior" by ryanofsky. Thanks to @glozow for hosting!
bitcoincore.reviews/22155
2
9
84
HIRING: open source software engineer
Responsibilities include: flamewar moderation, customer service for eol versions, press & media agent, whipping boy for anything that can possibly go wrong on the network, and central person responsible for things being decentralized.
Bitcoin is decentralized.
Bitcoin Core is not a central authority.
The Bitcoin Core devs are not a governance committee.
The Bitcoin Core maintainers are not officers.
I am not a dictator.
15
8
88
11,019
WOOO package mempool accept works with lightning!!! 😍
I've been testing @glozow's package relay implementation (github.com/glozow/bitcoin/tr…) with eclair and it's smooooth!
We can say goodbye to `update_fee` and still safely get our transactions confirmed 🚀
Please review her PRs to get this into bitcoin!
5
12
77
it’s like venmo but for criminals. thats why we need to make it illegal since criminals cant use illegal stuff. also it uses more energy than iceland and isn't scalable because china has to burn, like, a bunch of coal for each tx. also it's not turing complete - very important.
11
6
88
hosting a party this saturday... not stressing over the playlist. I'm just going to have AI read the Bitcoin Core v28.0 release notes draft on repeat, it's going to be lit
14
9
86
6,545
ok idk if this is an unpopular opinion but i feel like if the gov really cared about us, they'd require all messaging clients to be e2ee and everything touching personal info to be open source?
but instead
3
13
82
tbh i don’t know anyone who understood bitcoin the first time they heard about it
cheers 🥂 to the ones who explained it to us the 1st, 2nd... nth time until we got it. for me that's @MaxFangX. immensely thankful 🙏 🦃
for funsies, a thread of embarrassing beliefs as a noob 👇
6
4
77
This month, we're doing a series of @BitcoinCorePRs review clubs on soft fork PRs to bitcoin-inquisition (h/t @ajtowns). We'll *review the code* which is for *signet* and will not argue about activation.
I think it'll be a calm, neutral space to learn and discuss code - join us!
This week's review club is bitcoin-inquisition PR #39, "Re enable OP_CAT". Join us on IRC to learn about the script interpreter code, discuss the implementation approach, and review the tests together!
bitcoincore.reviews/bitcoin-…
9
25
80
12,860
I agree with that. That’s why we push people to discuss on the mailing list and delving, ie forums *not* moderated by Bitcoin Core. User opinions matter, but arguments are weighed based on their technical merits - turning this into a social media information war and encouraging hundreds of people to swamp the PR doesn’t make you more right. It just makes the discussion unproductive.
And I don’t like how rude some people have been on social media, but I don’t see any examples by people who actually work on Core. Free speech proponents would argue that social media personality doesn’t disqualify somebody from having a technical opinion - I assume that is why you tolerate Samson’s behavior.
24
79
49,324
If you're confused about P2PKH, P2SH, P2WPKH, P2WSH, P2SH-P2WPKH, and P2SH-P2WSH, this review club is the one for you! :) and you'll have a nice lil cheatsheet at the end! 🤓
Notes and questions for next week's meeting are now up. @glozow will host on PR 22363 "Use `script_util` helpers for creating P2{PKH,SH,WPKH,WSH} scripts". Come and learn about Bitcoin script and the functional tests.
bitcoincore.reviews/22363
3
11
74
Happy new year / 新年快乐！
Did you know: 恭喜发财 literally translates to “bitcoin is going to the moon this year”
9
6
72
5,823
hell yeah SCRIPT_VERIFY_TAPROOT flag will start being returned from GetBlockScriptFlags in v0.21.1 and above, make sure u eat a carrot today
if u havent upgraded ur node, no carrots for u
2
8
73
Here is a thread of the resources for beginners reviewing Bitcoin Core PRs mentioned in the livestream yesterday (thanks @ConorOkus for having me and @StephenDeLorme for backstage magic)
⚠️Starting in 15 Minutes!⚠️
@glozow is about to teach us some steps we can take to review a #Bitcoin core PR.
⬇️ Join Us Here ⬇️
twitch.tv/bitcoindevelopers
3
21
73
A comment on whether this process was “rushed”.
As someone who has both authored and merged mempool policy changes for the last 4 years, I’d say this is par for the course.
- The original PR was discussed around 2 years ago (of course, echoing arguments that were made 10 years ago).
- Interest in the idea waned, then was renewed around 2 months ago with more real-world information.
- After some google group discussion, the PR was reopened. Discussion continued on delvingbitcoin.org, twitter, reddit, etc.
- Alternate PRs were opened to address some concerns, and we eventually converged on one.
- Code review took around a month. It had broad interest from regular conributors.
- It was merged in June, and the change will ship in v30 in ~October.
- If people upgrade to v30 and keep the default, it usually takes 6-12 months for reliable relay.
10
73
5,837
5/ So then we’re back to square one using fiat again. all because u “trust coinbase more than i trust myself 🥺😅”
10
2
69
It's very important that Bitcoin Core can't push auto-updates directly, but that means the onus is on you to ensure your node is up-to-date.
Cmon guys. If you can be your own bank, take on the gov, be a sovereign individual etc, surely you can remember to update some software.
Two new advisories have been added to bitcoincore.org/en/security-….
9
17
66
9,699
I know protocol development is necessary for the network to function, but won't make hyperbitcoinization happen by itself. It's the humans who understand real world problems to teach family, friends, and strangers how to use Bitcoin as a tool to solve them.
3/n
1
4
69
When Niklas discovers a deviation in your consensus engine, he discloses it responsibly instead of causing a net split and putting people's money in danger. Don't be an asshole. Be like Niklas!
Bitcoiners, please give this post the engagement it deserves 👏
8
13
68
11,239
