Closed diegokolling closed 3 weeks ago
Com qual frequência um node repassa blocos ou transações inválidas? Li que são necessárias “algumas transações inválidas” para que um node exclua outro e coloque ele na "lista negra"? Essa "lista negra" é apenas daquele node ou é passada pra frente? Se eu atualizar meu node para 22 milhões de BTC, ele desconecta da rede na hora?
Evolução dos Miners de loteria Bitaxe Gamma: https://x.com/altair_tech/status/1836419203080790024?t=ot7P3VJlhN9FQnpbRq5pEQ&s=19 BMM 101: https://shop.braiins.com/products/braiins-mini-miner-bmm-101-pre-order-12-2024
O Bitcoin é uma armazenagem descentralizada? https://x.com/stevesimple/status/1837544142575927766?s=46&t=zAjxz5gV-hM4odRtK474uA
243 milhões de dólares pelo ralo… https://x.com/lopp/status/1836757720713547975?s=46&t=zAjxz5gV-hM4odRtK474uA
Como é o anti-spam do Bitcoin e quais ataques do tipo já ocorreram? https://x.com/lopp/status/1835517907612090489?s=46&t=zAjxz5gV-hM4odRtK474uA
NOIST: a non-interactive, single-round t-of-n threshold signature scheme.
https://x.com/brqgoo/status/1835278458718462254?s=46&t=zAjxz5gV-hM4odRtK474uA
Brick Wallet: a web frontend for NWC (Nostr Wallet Connect)
https://x.com/super_testnet/status/1834016108321669439?s=46&t=zAjxz5gV-hM4odRtK474uA
Introducing Selfie-Records, by @_miguelmedeiros at Synonym.
Selfie-Records builds on BIP353, which initially focused on payments through DNS TXT records, but we've expanded its utility to support a variety of use cases, including:
🔑 Identities: Verifying and associating public keys (e.g., Nostr, Bitcoin, PGP) with email addresses, domains or subdomain names.
💸 Payments: Continuing to support Bitcoin payments using DNS-based resolutions.
🗃️ Other Data Types: Storing anything from authentication keys to metadata, making it a flexible and decentralized data solution
https://x.com/synonym_to/status/1833907090567602589?s=46&t=zAjxz5gV-hM4odRtK474uA
PPLNS-JD - a breakthrough in how to calculate the payouts based both on selected transactions and hash power provided.
@plebhash
https://x.com/demand_pool/status/1833509389539676538?s=46&t=zAjxz5gV-hM4odRtK474uA
https://delvingbitcoin.org/t/pplns-with-job-declaration/1099
Como calcular o tamanho mínimo das UTXOs
https://x.com/lopp/status/1833047373167067379?s=46&t=zAjxz5gV-hM4odRtK474uA
GAP limit pode te matar do coração:
https://x.com/lopp/status/1832981200048103787?s=46&t=zAjxz5gV-hM4odRtK474uA
O que acontece se a Coinbase for hackeada e perder absolutamente tudo?
https://x.com/francispouliot_/status/1832003127676977495?s=46&t=zAjxz5gV-hM4odRtK474uA
I'm proposing to stop the processing of unrequested transactions in Bitcoin Core 22.0+ at TX message reception. An unrequested transaction is one defined by which a "getdata" message for its specific identifier (either txid or wtxid) has not been previously issued by the node [0].
This change is motivated by reducing the CPU DoS surface of Bitcoin Core around mempool acceptance. Currently, an attacker can open multiple inbound connections to a node and send expensive to validate, junk transactions. Once the canonical INV/GETDATA sequence is enforced on the network, a further protection would be to deprioritize bandwidth and validation resources allocation, or even to wither connections with such DoSy peers. A permissioned peer (PF_RELAY) will still be able to bypass such restrictions.
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-February/018391.html
Silent payments in the wild:
https://x.com/bitboxswiss/status/1831981915827757560?s=46&t=zAjxz5gV-hM4odRtK474uA
Bip 300 e 301 atualizada
https://x.com/truthcoin/status/1838538369464435055?s=46&t=zAjxz5gV-hM4odRtK474uA
[bitcoindev] Signing a Bitcoin Transaction with Lamport Signatures (no changes needed)
Veja o link para os outros Bitdevs, onde você pode pegar inspiração para os seus próprios tópicos sugeridos.
https://github.com/plebemineira/bhbitdevs.org/issues/8