Aye 👩🏻‍💻 ⚡️

3.9K posts

Aye 👩🏻‍💻 ⚡️ banner
Aye 👩🏻‍💻 ⚡️

Aye 👩🏻‍💻 ⚡️

@ayebytes

Co-founder @OpenCloudTech - Bitcoin engineering, systems, and education 🇦🇷

Katılım Ağustos 2012
846 Takip Edilen5.3K Takipçiler
Sabitlenmiş Tweet
Aye 👩🏻‍💻 ⚡️
Aye 👩🏻‍💻 ⚡️@ayebytes·
Mi trabajo actual en Bitcoin me hace agradecer todos los días la carrera de Ingeniería de sistemas. Programar transacciones Taproot no es para cualquiera.
Español
31
28
863
115.6K
Aye 👩🏻‍💻 ⚡️
Bitcoin contains an ambiguity that leads to a vulnerability affecting SPV nodes. the issue lies in the merkle tree committed to in each block header an internal merkle node is created by hashing a 64 byte preimage (the concatenation of two 32 byte hashes). however, a serialized transaction without witness data can also be exactly 64 bytes long as a result, the same 64 byte sequence can be interpreted as either a transaction or an internal merkle node, depending on the context this ambiguity does not affect full nodes because they download and validate the entire block. however, SPV clients only verify merkle proofs, making them susceptible to this ambiguity bip54 aims to eliminate this by making 64 byte transactions consensus invalid #motivation" target="_blank" rel="nofollow noopener">github.com/bitcoin/bips/b…
Aye 👩🏻‍💻 ⚡️ tweet media
English
0
1
20
748
Aye 👩🏻‍💻 ⚡️
interesting idea instead of making post quantum signatures smaller, use STARK to prove that hundreds of signatures were verified correctly 12-15 ms to cover 1-512 signatures a prover does the heavy work by verifying all the signatures and generating a single proof
Bitcoin Optech@bitcoinoptech

Remix7531 posted to the Bitcoin-Dev mailing list his benchmark results for aggregating many SPHINCS signature verifications into a single STARK proof... #benchmarking-slh-dsa-stark-aggregation" target="_blank" rel="nofollow noopener">bitcoinops.org/en/newsletters…

English
3
3
24
3.6K
Aye 👩🏻‍💻 ⚡️
different architecture. different trust model in centralized services, your computer connects to third party servers and not the other way around client —> server in peer-to-peer systems, every peer both consumes services from other peers and provides services to them peer <—> peer this is one of the fundamental ideas behind Bitcoin
Aye 👩🏻‍💻 ⚡️ tweet media
English
0
1
6
303
Aye 👩🏻‍💻 ⚡️
faster node bootstrap means less waiting before your backend can validate utxos, build psbts, detect spends, and start serving users building on Bitcoin often means waiting for nodes to sync before you can even start developing backend infrastructure github.com/bitcoin/bips/p… is a great complement to AssumeUTXO by allowing snapshots to be exchanged directly between peers, instead of relying on a third party download
English
0
0
6
302
Aye 👩🏻‍💻 ⚡️
@EliBenSasson i can only speak for myself i grew up in Argentina, where high inflation made me question how money works i didn’t join crypto to trade. i joined because i wanted to understand money, inflation, and how Bitcoin actually works that eventually led me to protocol development
English
0
0
12
184
Eli Ben-Sasson | Starknet.io
Eli Ben-Sasson | Starknet.io@EliBenSasson·
I'm curious about this and want your thoughts: Crypto is male-heavy. Why? What do women do on crypto when they onboard?
English
38
0
42
8.2K
Aye 👩🏻‍💻 ⚡️
self custody is a spectrum you don’t have to go from an exchange directly to an air gapped multisig setup there are many points along the way: - hardware wallet - hardware wallet + passphrase - multisig with a trusted cosigner - self managed multisig - air gapped signing each step reduces trust in third parties, but increases the responsibility you take on the goal isn’t to maximize complexity. the goal is to find a setup whose trade-offs you understand and can manage confidently
English
1
2
11
2.8K
lawrence⚡
lawrence⚡@AxeCapYa·
@ayebytes This is why I am a fan of @Bitkey There's levels to the self custody game and MOST won't make it to full sovereignty. Gotta back them as far away from exchanges as possible!
English
1
2
10
1.2K
Aye 👩🏻‍💻 ⚡️
self custody is probably Bitcoin’s greatest feature it’s also one of its biggest adoption barriers most people want ownership, but not the responsibility that comes with it
English
6
3
33
1.9K
Aye 👩🏻‍💻 ⚡️
ord io was one of the main explorers and discovery layers of ordinals ecosystem its shutdown doesn’t affect Ordinals (protocol) directly but it does impact part of the infrastructure and culture around ordinals and runes
Ord.io@ord_io

Ord io is shutting down on June 1. Three years ago, we launched our idea for "an Ordinals explorer with upvotes". We had no idea what was about to happen. Since then, Ord io has grown into a platform used by over a million people to explore inscriptions on Bitcoin. It brought us so much joy to ship features like Satributes for discovering the rare sats behind inscriptions and Block Vision for monitoring real-time Runes minting activity. Even simple filters and sorting options took on a life of their own. "Sort by largest inscription" quickly turned into a leaderboard where inscribers competed to create the biggest "four megger". And even the things that annoyed us at the time are funny to look back on now, like when the Bitcoin Puppets community would "raid" other collections so hard that we had to remove the downvote feature. To help preserve some of the Bitcoin culture that happened on Ord io, we'll be uploading the full history of upvotes, replies, and public address profiles to GitHub. That way, if someone wants to build their own Ordinals explorer with this context in the future, they can. Thank you to every single artist, collector, dev, and degen who joined us for this ride 🧡

English
2
0
4
413
Jarvis Nuss
Jarvis Nuss@jarvisnuss·
ECDSA verification is a pure function of (msg, sig, pubkey), it carries zero information about how the signature was produced. Satoshi's pubkey has been exposed in P2PK outputs since 2009. Once Shor runs on secp256k1 (~2330 logical qubits per Roetteler et al, days of wall-clock per key), a valid "Satoshi signature" is mathematically indistinguishable from one a cracker produced against that exposed pubkey. The question "would you believe it" collapses to "do you trust nobody ran Shor on this key in the last week." Trust shifts from the math to the hardware timeline.
English
1
0
2
57
Aye 👩🏻‍💻 ⚡️
as quantum computing advances… if Satoshi signed a messages today, would you believe it?
English
1
0
6
367
@₿itchain
@₿itchain@Bitchain11·
@ayebytes Tremendo y horrible lo de Binance, pero otra muestra dura y cruda de que NOT YOUR KEYS NOT YOUR COINS
Español
1
0
3
73
Aye 👩🏻‍💻 ⚡️
many controversies in Bitcoin start with proposals to change default values in the code today, Bitcoin has 175 configuration options, each with a default. if you don’t explicitly set them, your node runs with those defaults that is why they matter most users don’t tweak every setting. they run a node and rely on what is defined. so in practice, defaults shape how Bitcoin behaves across the network by changing the defaults, you are voting and changing Bitcoin
English
1
0
7
427
Cap. Ace McCloud
Cap. Ace McCloud@allinargy·
Armemos una gran mesa de diálogo
Español
4
0
17
1.1K