Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 3/9 - On July 7 the argument left the forums. An attacker running at least 10 automated wallets began pumping out dust transactions, each one packing 102 outputs of 0.0001 BTC. Every transaction was perfectly valid, economically pointless, and built to devour block space.
R to @daily_btc_lore: 3/9 - On July 7 the argument left the forums. An attacker running at least 10 automated wallets began pumping out dust transactions, each one packing 102 outputs of 0.0001 BTC. Every transaction was perfectly valid, economically pointless, and built to devour block space.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 4/9 - F2Pool tried to clean up by sweeping thousands of dust outputs into one giant transaction. It weighed 999.657 KB and filled nearly an entire block on its own. Regular nodes refused to relay anything that size, so F2Pool mined it into its own blocks directly.
R to @daily_btc_lore: 4/9 - F2Pool tried to clean up by sweeping thousands of dust outputs into one giant transaction. It weighed 999.657 KB and filled nearly an entire block on its own. Regular nodes refused to relay anything that size, so F2Pool mined it into its own blocks directly.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 5/9 - Even the cleanup hurt. The giant sweep took over 20 seconds to verify, lagging block explorers across the network. Greg Maxwell stepped in with a fix: reuse identical signatures across the inputs, which made the sweeps highly compressible and fast to check.
R to @daily_btc_lore: 5/9 - Even the cleanup hurt. The giant sweep took over 20 seconds to verify, lagging block explorers across the network. Greg Maxwell stepped in with a fix: reuse identical signatures across the inputs, which made the sweeps highly compressible and fast to check.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 6/9 - The damage was measurable. Researchers later classified 385,256 transactions from those ten days as spam, roughly 23% of everything Bitcoin processed. The mempool swelled past 80,000 waiting transactions, average fees jumped 51%, and confirmation times stretched sevenfold.
R to @daily_btc_lore: 6/9 - The damage was measurable. Researchers later classified 385,256 transactions from those ten days as spam, roughly 23% of everything Bitcoin processed. The mempool swelled past 80,000 waiting transactions, average fees jumped 51%, and confirmation times stretched sevenfold.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 7/9 - Suspicion fell on http://Coinwallet.eu, which had advertised a paid stress test weeks earlier. A shared address tied the two campaigns together. @peterktodd had once offered to run a stress test for $7,000 and publicly denied involvement. Nobody ever claimed the attack.
R to @daily_btc_lore: 7/9 - Suspicion fell on http://Coinwallet.eu, which had advertised a paid stress test weeks earlier. A shared address tied the two campaigns together. @peterktodd had once offered to run a stress test for $7,000 and publicly denied involvement. Nobody ever claimed the attack.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 8/9 - Bitcoin Core answered with economics instead of capacity. Version 0.11.0 set a minimum relay fee of 1,000 satoshis, raised to 5,000 by October. The reasoning was simple: if every byte of spam costs real money, sustained spam becomes a losing trade.
R to @daily_btc_lore: 8/9 - Bitcoin Core answered with economics instead of capacity. Version 0.11.0 set a minimum relay fee of 1,000 satoshis, raised to 5,000 by October. The reasoning was simple: if every byte of spam costs real money, sustained spam becomes a losing trade.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 9/9 - The attacker spent $49,000 proving Bitcoin could be congested, and changed nobody's mind. Two years later SegWit activated without a block size increase. The full post-mortem still lives on the Bitcoin wiki:
https://en.bitcoin.it/wiki/July_2015_flood_attack
R to @daily_btc_lore: 9/9 - The attacker spent $49,000 proving Bitcoin could be congested, and changed nobody's mind. Two years later SegWit activated without a block size increase. The full post-mortem still lives on the Bitcoin wiki:
https://en.bitcoin.it/wiki/July_2015_flood_attack
Psicologia da Prosperidade:
Aja Como Quem Já Vive Em Abundância e Sua Realidade Começará a Mudar | Bob Proctor
Aja Como Quem Já Vive Em Abundância e Sua Realidade Começará a Mudar | Bob Proctor
YouTube
Aja Como Quem Já Vive Em Abundância e Sua Realidade Começará a Mudar | Bob Proctor
Você já se perguntou por que algumas pessoas parecem atrair oportunidades enquanto outras permanecem presas aos mesmos ciclos? Neste vídeo inspirado nas ideias de Bob Proctor, Napoleon Hill e outros autores do desenvolvimento pessoal, você vai descobrir por…
Samuel Gregory:
Can This New Local AI Model Beat Qwen?
Can This New Local AI Model Beat Qwen?
YouTube
Can This New Local AI Model Beat Qwen?
█▀█ █▀▀ ▄▀█ █▀▄ █▀▄▀█ █▀█ █▀█ █▀▀
█▀▄ ██▄ █▀█ █▄▀ █ ▀ █ █▄█ █▀▄ ██▄
The SaaS era is ending as local, agentic AI models like Ornith allow founders to build personal software on their own hardware. In this video, I test the Ornith…
█▀▄ ██▄ █▀█ █▄▀ █ ▀ █ █▄█ █▀▄ ██▄
The SaaS era is ending as local, agentic AI models like Ornith allow founders to build personal software on their own hardware. In this video, I test the Ornith…
Linux Archives - OSTechNix:
Things to Back Up Before Reinstalling Linux: The Complete Checklist (2026)
Things to Back Up Before Reinstalling Linux: The Complete Checklist (2026)
OSTechNix
Things to Back Up Before Reinstalling Linux: The Complete Checklist (2026)
Learn the important things to back up before reinstalling your Linux system. SSH/GPG keys, dotfiles, packages, browser data, 2FA and more.