ANCHORWATCH CEO ROB HAMILTON IS SPENDING THOUSANDS OF DOLLARS OF HIS OWN MONEY TO AUDIT EVERY SINGLE #BITCOIN CODEBASE
HE'S FOUND OVER 4,900 BUGS AND OVER 85 CRITICAL ISSUES
WHILE OTHERS ARE PANICKING, HE IS MARSHALING A CODER ARMY TO COMBAT ADVANCED AI THREATS
THIS STARTUP EXECUTIVE IS DOING EVERYTHING HE CAN TO SECURE MILLIONS WORTH OF BTC
WHAT AN ABSOLUTE LEGEND 🔥
🚨JAPANESE YEN STABLECOIN IS HERE!
🇯🇵Startup JPYC will launch the world’s first yen-pegged stablecoin, fully backed by Japanese savings and government bonds.
it's programming 101 that any programming language can have data hidden in any number of ways.
and internet power user 101 that any internet protocol can have data stuffed into protocol headers, formats etc.
even completely non-IT savvy people can see that the english language written in a book can be used to hide data, codes, in various levels of efficiency.
filters to limit spam, don't work and can't really work for VERY easy to understand reasons. if you consider yourself a critical thinking man, don't trust, verify the filter arguments, THINK about it for yourself: the p2p network is hard to censor by design, it's a flood fill network, literally designed to be a space where tolerant minority rules win - for very good reason - to protect the unpopular minority from being censored.
now filter proponents will rightly say filtering wouldn't have to be 100%, but reality is it's very very nearly 0% (of what there's any non-trivial motive to send after competing with financial usage fees), and there are side-effects that make that nearly 0% not worth it. but let's ignore the side-effects for the sake of argument, or assume developers or power users can work around them, and look to the next move, if spam-filters worked. then miners would have incentive just bypass the p2p network, something they have done before, and still have robust tools to do. and the incentive is not small $1mil/day.
this is why there is wide-spread technical consensus to not go down the filter rabbit-hole. it ends in building the architecture for censorship. @lukedashjr's committee for deciding which transactions data to delete, modify etc. really a very bad idea. due to the legal principle apple used in the apple vs FBI case. if you build the mechanism to selectively decrypt, delete, modify you can and will be compelled to do that. so don't build it, it's quite dangerous for bitcoin.
that's not to say nothing can be done about spam, but we need to be smarter, think about game-theory, understand motives, understand legal risks, steer incentives so that economically rational miners and yes even the hated spam industry will actually use something less bad for nodes, and less bad for bitcoin decentralization.
this is something bitcoin developers and protocol researchers have been working on... soft-fork consensus enforceable ways to steer spam in economically rational ways into data-availability space, that is scarce, pays miner fees, but opt-in to download, relay or store, so that fullnodes can fully verify consensus rules without needing to download it.
let the people who want the data-availability, and bitcoiners who are not afraid of convoluted artificial what-if risks, run the data-availability. the people who are pragmatic, common sense, and have a bit of mettle.
BLACKROCK is launching a Bitcoin Income Fund!
I assume they'll be generating max front month yield on IBIT, and I predict it will be a MONSTER product.
I assume somewhere around a 3% a month yield, back by the full power of BlackRock.
Well done team!
In leaked messages to The Rage, Knots maintainer Luke Dashjr is proposing a Bitcoin hardfork to implement a trusted committee that enables the retroactive altering of data on the blockchain.
All relevant messages we received are contained in the article for you to read for yourself.
This phrase has been greatly inflated over the years, but what Luke is proposing here is an attack on Bitcoin.
I‘ve stayed out of the Knots v Core debate until now bc I can sympathize with not turning BTC into ETH -If you want to do JPEG stuff, there‘s other chains for that, and the only reason to use Bitcoin for it is to astroturf off of its value.
On the other hand, its also been clear that filters alone do not work. This is what Luke essentially concedes in the leaked messages. Keeping JPEGs off of Bitcoin can only be done if the entire network adopts his changes - and there‘s hardly another way to do this than by decree.
No matter what side you stand on in this debate, I hope that we can agree that proposing the implementation of sich a decree in the form of a hardfork that would implement a *trusted committee* with the power to *retroactively alter the blockchain* goes too far.
Not only does it effectively erase Bitcoin‘s censorship resistance - it would turn Bitcoin into a permissioned network, and potentially make node runners face criminal liability for not complying with the committee‘s proposed removals.
As Luke stated himself, lawyers are already working on public letters to advocate for the sanctioning of illicit content on Bitcoin - Letters which Luke is involved in behind the scenes, but feels are better to stay out of publicly on advice of counsel.
Let me be very clear: if Luke‘s hardfork is implemented, it opens the door for law enforcement to request the removal of other data on the Blockchain, making the implementation of KYC/AML technically feasible.
I hope that publishing this article will do two things. First, I hope that it makes clear to the people running Knots what the future of Bitcoin is they are supporting.
Second, I hope that Core developers will begin to consider the opinions of the people who chose to run Knots. If anything, a majorly harmful hardfork activation should be grounds enough to take their concerns seriously. Burning Bitcoin to the ground over JPEGs is not worth it.
Some people seem to want to argue that there is already CSAM in Bitcoin's blockchain. This is false. Bitcoin today does not support images at all - only arbitrary data up to 80 bytes (or 95 in the coinbase).
Exploits like "Inscriptions" work by _misinterpreting_ script code, and _bypassing_ existing policy rules. They are not actually storing images, but merely putting gibberish code on the chain, which they later themselves (not Bitcoin) _misinterpret_ as images.
This distinction is very real and relevant. If you don't differentiate between "data that can be misinterpreted to produce CSAM" and "data that correctly interpreted displays CSAM", then literally _all data_ is CSAM, with _no exceptions at all_. This tweet would be CSAM. Google's logo would be CSAM. Your phone's operating system would be CSAM. Literally anything _can_ be misinterpreted as CSAM.