
Snob de #Bitcoin 🤓 Pseudo Trader 😜 memes 😎 #GameBoyMarket ⚡👾 ⚡ [email protected] Nostr 🟣 gameboybtc
CrackAss-Memezuela🏴
Joined December 2020
- Tweets4K
- Following2.3K
- Followers524
- Likes13.8K
GameBoyBTC ⚡👾 retweeted
Sparrow v2.5.6 has been released, removing the eMudhra root certificates and upgrading the bundled Tor to meet the client protocols now required by the Tor network.
It also brings extensive screen reader and keyboard accessibility improvements.
Changelog: github.com/sparrowwallet/spa…
Download: sparrowwallet.com/download
Sparrow v2.5.0 released with:
Silent Payments (SP) wallets
SP-capable Frigate public server @2140_dev
bitview.space fee rates source
sparrowwallet.com/download
Estos últimos días
Alguien empezando en #Bitcoin 🤓 pero con consejos algo avanzados para quitar los animos xD
GameBoyBTC ⚡👾 retweeted
Hoy se cumplen 3 meses del doble terremoto en Venezuela. 🇻🇪
Tenía pendiente este resumen:
2.793.607 sats recaudados entre @geyserfund y Nostr, convertidos en ayuda real en el terreno para los afectados en la Guaira.
Muchas GRACIAS a todos 🫶
El detalle completo 👇
🤖 Made with AI
GameBoyBTC ⚡👾 retweeted
I was able to decompile and analyse 494 wallets on the AppStore.
I found 45 apps that raised red flags for me during my research.
I looked specifically for 2 things: private keys exfiltration and weak entropy.
GameBoyBTC ⚡👾 retweeted
A veces se habla del capitalismo como si fuera una abstracción fría. Pero detrás de cada negocio que funciona hay alguien que madrugó, planificó, tomó un riesgo y trató de hacer algo útil. No es perfecto. Pero prefiero ese mundo al de esperar que otro decida quién merece avanzar.
GameBoyBTC ⚡👾 retweeted
A year ago, we soft-launched Tor VPN Beta as a way to extend Tor's privacy protections beyond the browser to an entire Android device. Since then, we've been able to learn from how people are actually using it in real-world scenarios. Learn more about what makes our per-app circuit isolation different from commercial VPNs, the surprising UX lesson when trying to bypass blocks, and the mobile foundation we're building for what's next. blog.torproject.org/tor-vpn-…
Our third-party e-mail provider has been breached. Please be aware that the email named ‘Critical Security Alert: STM32 Entropy Vulnerability’ is not coming from us, and it’s a phishing attempt. Do not click on any link.
We have taken down the domain, and we are investigating the situation, including how the hackers got access to our legit domain.
GameBoyBTC ⚡👾 retweeted
📌 AI made finding bugs cheap, but it didn’t make responsible disclosure optional.
Finding and exploiting vulnerabilities has never been easier. A few hours of prompting now does what used to take a skilled researcher weeks. Unfortunately, defenders no longer enjoy the asymmetry they relied on. Security is still a cat-and-mouse game, but with many more cats, the user suffers.
Which is exactly why the process around disclosure matters more than ever.
How it works, and it is not complicated:
➤ A researcher finds a bug and contacts the vendor privately.
➤ The vendor reproduces, acknowledges, and both sides agree on a timeline. 90 days is the common default, more or less depending on severity, capacity to fix...
➤ During that window both sides keep it secret while the vendor fixes and ships.
➤ Once users are protected, both sides publish. The ecosystem learns. The researcher usually gets paid.
The issue now is the barrier is so low that anyone can surface a finding with no security background, and some skip straight to the audience:
❗Presenting a reproduction of an already-fixed bug as a live compromise.
❗Full disclosure of a bug that is not fixed yet.
❗"Critical vulnerability found" teasers, dripping details for engagement.
Call it what it is: attention farming with someone else's risk. When the bug sits between a user and their funds, this is reckless. Especially in crypto, where there is no chargeback. But the damage doesn't require live funds to be at stake. Manufactured panic causes harm of its own, because it drives people away from self-custody, and that damages the whole ecosystem.
So I have three asks:
1️⃣ For users: software and hardware have bugs, always. The single most effective thing you can do is stay updated and follow basic security hygiene. That has never mattered more than today. The time between releases and malicious actors exploiting the vulnerabilities have shrunk dramatically due to LLMs and that one can't afford to be passive and postpone security updates any more
2️⃣ For new researchers with a fresh model and a real, validated finding: welcome, we need you. Use the vendor's disclosure process. That is not bureaucracy. It is the difference between making the ecosystem safer and putting users in the crosshairs for a few likes. Remember that security communication must be accurate and proportionate. State the severity, affected versions, and fix status in the first sentence, not the tenth.
3️⃣ And to everyone building in this industry, vendors and researchers alike: let's make coordinated disclosure the norm we defend out loud, not the fine print. Reward the researchers who do it right. Refuse to amplify the ones who trade user safety for reach. This is how we win, together.
Some of the actors already support the initiative. @Ledger @Trezor @FoundationHQ @AnchorWatch @_SEAL_Org and others
Spread the message.
"Chat Hacks the Liquid Network. Don't Make Any Mistakes"
I seriously doubt it's a coincidence that the Liquid bridge got drained just a couple days after Astra dropped.
Looks like the Liquid functionary codebase hasn't been touched in 2 years, which isn't a good sign.
teapaw.org/lopp/status/2085341618…
GameBoyBTC ⚡👾 retweeted
We launched mostro.world 🧌
A public observatory for the Mostro network.
Orders, volume, currencies, disputes, dev fees and active markets computed from the public Nostr events emitted by Mostro instances.
bestiario publishes the reports as signed Nostr events, and mostro.world verifies them in your browser.
But you do not have to trust us.
Run the open-source software yourself and reproduce the same results.
mostro.world
Don’t trust. Verify.
#Mostro #Bitcoin #Nostr #Lightning #P2P
GameBoyBTC ⚡👾 retweeted
This is laughable. AI compute doesn't solve the double coincidence of wants problem and intelligence is a singular commodity that, while valuable, isn't always what individuals are demanding.
Bitcoin doesn't turn energy into value, it turns it into money, which has value. Money is a specific tool with a specific purpose, to solve the double coincidence of wants problem and bitcoin does this in a way that makes the tool resistant to centralized control.
Bitcoin and AI will be synergistic over the long-run. AI provides intelligence and bitcoin provides the money that coordinates the economic activity throughout the economy, in the digital economy and in meat space.
GameBoyBTC ⚡👾 retweeted
🚀 Mostro mobile v1.3.1 is out!
Olá, Bitcoiners! 🇧🇷🇵🇹 Mostro now speaks Portuguese ⚡
This release also comes with a bunch of fixes to make trading smoother:
💬 More reliable encrypted chat attachments
🔔 Push notifications fixed for trades created from range orders
⚡ Adding a Lightning invoice is now much easier when the keyboard is open
🌎 Better language selector handling
🖥️ Desktop builds are back too
Same Mostro: peer-to-peer Bitcoin trading, no KYC, built on Lightning + Nostr. 💚
Get v1.3.1 👇
zapstore: zapstore.dev/apps/network.mo…
github: github.com/MostroP2P/mobile/…
GameBoyBTC ⚡👾 retweeted
Mostro has official user documentation 🧌
If you want to understand how the protocol works
before trading, the guide covers:
📖 How to make your first trade
🔑 How identity and keys work
⚡ What a hold invoice is and how it operates
🛡️ How to open a dispute if something goes wrong
🔒 The advanced privacy mode
All in one place, with clear examples
and no unnecessary technical jargon.
Read the full guide 👇
mostro.network/docs-english/
#Bitcoin #Lightning #Nostr #P2P #Mostro
GameBoyBTC ⚡👾 retweeted
Comunicado
Lamentamos comunicarles que el día que no queríamos que llegara ha llegado: @lnp2pBot llega a su fin.
Como comunicamos hace pocos días, @lnp2pBot ha sido atacado desde el primer día, las pérdidas que hemos sufrido las hemos asumido por el simple hecho de seguir dándole el servicio que se merecen nuestros fieles usuarios. Sin embargo los hechos se han precipitado y aunque llevamos meses trabajando para mejorar la seguridad del bot no contamos con los recursos para enfrentar un ejercito de script kiddies armados con modelos de IA.
Por todo esto hemos tomado la dura y penosa decisión de detener indefinidamente todo tipo de actividad de @lnp2pBot, con efecto inmediato.
Una vez más las pérdidas son nuestras. Nos comunicaremos con los pocos usuarios que tienen pagos pendientes para resolver esos casos particulares. No habrá ni un solo usuario afectado económicamente.
El bot nació como nuestra legítima defensa ante gobiernos autoritarios que pretenden obligar a los usuarios en entregar todo tipo de información personal con la excusa de que es por su propio bien. Muchas veces pensamos que eran ellos quienes iban a lograr cerrar al bot. Irónicamente no fue ningún gobierno autoritario quien lo logró sino probablemente algunos de nuestros propios usuarios.
A todos nuestros usuarios.
¡Gracias totales!
Huele a que estamos en el piso (área) del Bearmarket 🔥
Tiempo sin entrar a @LNMarkets
GameBoyBTC ⚡👾 retweeted
We made a short visual explainer to help people understand the Coldcard bug, and what it means for the security of affected wallets.
Bitcoin's entire security model depends on a user's ability to select astronomically large numbers from a truly random set.
If you imagine every possible Bitcoin private key as individual atoms, when a private key is generated properly, the pool of possibilities is so large that it's like an attacker is hunting for one specific atom hidden somewhere across 2 billion galaxies. No classical computer could ever search that many possibilities.
Unfortunately, affected Coldcard firmware drew its seeds from a much smaller, more predictable pool. If every possible Coldcard private key was an atom, the possible set of keys would only be about the size of a large virus. In comparison, a standard computer could work through that space in just a few hours.
Our video helps visualize what this difference looks like, we hope this is helpful for everyone to establish the importance of true entropy in key generation.
We are deeply sorry for anyone who lost funds to this bug. We know several people that were personally affected, including members of the BPI team. Losing funds after working hard protect your wealth is extremely difficult.
We are developing a set of policy reflections based on this vulnerability that we hope to publish as soon as possible.


























