jaonoctus

7.5K posts

jaonoctus banner
jaonoctus

jaonoctus

@jaoNoctus

PGP: 0xD8F31505B581D617 / Tenho medo de falar que faço programa e as pessoas pensarem que entendo de computação.

Brazil Katılım Mart 2015
700 Takip Edilen2.4K Takipçiler
Sabitlenmiş Tweet
jaonoctus
jaonoctus@jaoNoctus·
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 hello world -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQTru4F1HbgJ3lDdWMSsdchrbudDNAUCaStVegAKCRCsdchrbudD NK63AP46arPsNgBtrupZuUnHVvR5KjeozhX2xD1A0apcTVBEjAEAiqCui4LKPowJ WTrDlWUPHH9rHOJFC6531mpbTdYRkgg= =jVR1 -----END PGP SIGNATURE-----
4
3
36
7.7K
jaonoctus
jaonoctus@jaoNoctus·
Mork1e@mork1e

Ok so.. they left their CDN exposed. If you ping the domain, you get this ip: 151.101.129.49 It turns out this is a fastly.com IP . I had never heard of fastly but it looked to be something similar to vercel, so I figured maybe they had custom deployment links like vercel does. Tried a few different combos and BINGO: btc.day.global.prod.fastly.net This took me to this: d325bmwzjz2yc7.cloudfront.net That’s their CDN bucket on AWS. They currently have it setup so that any invalid endpoints redirect back to index.html I went on a hunch and figured that they’d probably already have their production app stored somewhere in the CDN ready for deployment I used SECLISTs (github.com/danielmiessler… )and ffuf to try out over 20k different combinations on this URL. After some sleuthing, BINGO!! I found these two files: > live.html > .DS_STORE The important one here that immediately caught my eye was “live.html”. That sounded like a prod deployment. And sure enough, it was! This is what the btc.day site will look like on the day the faucet goes live: d325bmwzjz2yc7.cloudfront.net/live.html d325bmwzjz2yc7.cloudfront.net/bitkey.html It turns out the entire faucet will be revealed to just be a promotion scheme to get you to buy a bitkey and use cash app. There is no faucet - at least in the sense most were expecting.

1
0
1
114
Joule
Joule@joulebtc·
Pra quem não pegou faucet de btc. Fica a oportunidade. Se liguem que eh agora 06/abril. Faltam menos de 3 dias.
jack@jack

btc.day

Português
15
6
146
26.8K
jaonoctus
jaonoctus@jaoNoctus·
Mork1e@mork1e

Ok so.. they left their CDN exposed. If you ping the domain, you get this ip: 151.101.129.49 It turns out this is a fastly.com IP . I had never heard of fastly but it looked to be something similar to vercel, so I figured maybe they had custom deployment links like vercel does. Tried a few different combos and BINGO: btc.day.global.prod.fastly.net This took me to this: d325bmwzjz2yc7.cloudfront.net That’s their CDN bucket on AWS. They currently have it setup so that any invalid endpoints redirect back to index.html I went on a hunch and figured that they’d probably already have their production app stored somewhere in the CDN ready for deployment I used SECLISTs (github.com/danielmiessler… )and ffuf to try out over 20k different combinations on this URL. After some sleuthing, BINGO!! I found these two files: > live.html > .DS_STORE The important one here that immediately caught my eye was “live.html”. That sounded like a prod deployment. And sure enough, it was! This is what the btc.day site will look like on the day the faucet goes live: d325bmwzjz2yc7.cloudfront.net/live.html d325bmwzjz2yc7.cloudfront.net/bitkey.html It turns out the entire faucet will be revealed to just be a promotion scheme to get you to buy a bitkey and use cash app. There is no faucet - at least in the sense most were expecting.

0
0
0
624
Livecoins
Livecoins@livecoinsBR·
🚨Bitcoin de graça!!! Block, de Jack Dorsey, vai relançar o famoso “Bitcoin faucet” para distribuir BTC grátis. Em 2010, o site dava 5 BTC por usuário por completar um captcha — hoje, mais de US$ 1 milhão.
Livecoins tweet mediaLivecoins tweet media
Português
15
10
168
13.4K
Mork1e
Mork1e@mork1e·
Ok so.. they left their CDN exposed. If you ping the domain, you get this ip: 151.101.129.49 It turns out this is a fastly.com IP . I had never heard of fastly but it looked to be something similar to vercel, so I figured maybe they had custom deployment links like vercel does. Tried a few different combos and BINGO: btc.day.global.prod.fastly.net This took me to this: d325bmwzjz2yc7.cloudfront.net That’s their CDN bucket on AWS. They currently have it setup so that any invalid endpoints redirect back to index.html I went on a hunch and figured that they’d probably already have their production app stored somewhere in the CDN ready for deployment I used SECLISTs (github.com/danielmiessler… )and ffuf to try out over 20k different combinations on this URL. After some sleuthing, BINGO!! I found these two files: > live.html > .DS_STORE The important one here that immediately caught my eye was “live.html”. That sounded like a prod deployment. And sure enough, it was! This is what the btc.day site will look like on the day the faucet goes live: d325bmwzjz2yc7.cloudfront.net/live.html d325bmwzjz2yc7.cloudfront.net/bitkey.html It turns out the entire faucet will be revealed to just be a promotion scheme to get you to buy a bitkey and use cash app. There is no faucet - at least in the sense most were expecting.
Mork1e tweet mediaMork1e tweet media
Bitcoin at Block@BitcoinatBlock

The bitcoin faucet is back. 04.06.26 btc.day

English
385
559
6K
828K
Bitcoin Coders
Bitcoin Coders@bitcoin_coders·
Começamos hoje uma série de puzzles mensais. 🧩 Puzzle 01 — Bitcoin Coders (abril/2026) 💰 Recompensa: 30.000 sats 🔑 Endereço: bc1q5uuhy8e5gvzsg0vk8r2929jlj8za7x8x6dwlvc 🧠 A seed de 12 palavras está escondida na imagem. 📆 Novas dicas serão liberadas semanalmente (caso ninguém resolva antes). ⚠️ Todas as dicas saem primeiro no Discord do Bitcoin Coders: discord.gg/e5qUsNWgQg Nem tudo é relevante. Boa sorte.
Bitcoin Coders tweet media
Português
2
4
15
975
nifty, bitcoin++ villains 🇺🇸 Apr 23+24
Why did bitcoin ship taproot as P2PK, even knowing that it’s “quantum vulnerable”? Here’s why: - Quantum wasn’t considered a noteworthy threat in 2018/2019 when the proposal was designed. It was understood that new engineering would be required to be PQ proof, and the shape of the PQ problem was unknowable. Therefore not worth considering. - A single onchain footprint is better for hiding what type of contract is locking coins up, and it is elegant. You can’t guess what’s required to unlock coins just by looking at what they’re locked up to - Taproot aimed to improve privacy by decreasing signal about multisigs. The P2PK design uses new capabilities unlocked with Schnorr to achieve that. Taproot accomplished its design goals to increase privacy. Being quantum safe wasn’t on the list of design goals. Now we’re in the era where PQ is a design goal. Whether we can preserve privacy while also moving to a PQ protocol has yet to be determined.
English
14
14
145
14.4K
jaonoctus retweetledi
jaonoctus
jaonoctus@jaoNoctus·
wen P2QRH
jaonoctus tweet media
Deutsch
0
46
10
1.5K
Explica Bitcoin
Explica Bitcoin@BitcoinExplica·
O ATAQUE QUÂNTICO É INEVITÁVEL! Conversei com o @storopoli sobre os riscos que o Bitcoin corre com a computação quântica O Bitcoin está mesmo condenado? Melhor a gente desistir e ir vender nossa arte na praia? Tudo isso e muito mais nessa conversa
Explica Bitcoin tweet media
Português
4
3
26
1K
Tur.js
Tur.js@Tur24Tur·
Claude Code literally DREAMS about your code at night. Found in the leaked source: an "autoDream" service that runs every 24 hours as a background AI agent. The prompt says: "You are performing a dream - a reflective pass over your memory files." It has phases: - Orient (review current memories) - Gather (scan recent session transcripts) - Consolidate (synthesize into durable knowledge) - Prune (remove stale/contradicted facts) Uses a PID-based lock file. Only triggers after 5+ sessions. The dream agent gets restricted permissions - read-only bash, can only edit memory files. #ClaudeCode #AI #autoDream
Tur.js tweet media
Chaofan Shou@Fried_rice

Claude code source code has been leaked via a map file in their npm registry! Code: …a8527898604c1bbb12468b1581d95e.r2.dev/src.zip

English
4
5
69
17.6K
jaonoctus
jaonoctus@jaoNoctus·
April Fool's 🥀
Français
1
0
11
228
EddieOz ⚡
EddieOz ⚡@eddieoz·
@jaoNoctus Indeed, but it was also cool. That's why he said he was happy and sad at the same time. It was a trade-off he made consciously.
English
1
0
2
189
EddieOz ⚡
EddieOz ⚡@eddieoz·
Finding a block with a Bitaxe is "impossible"... until it actually happens. ⚡️⛏️ Huge win for the Brazilian 🇧🇷 Bitcoin community! One of our own just found a block. We’re a small group, but the talent is real: 3 awarded BTC++ hackers, Bitdevs builders, node runners, LoRa mesh hackers, cybersec experts, and now one very lucky (and happy) solo miner. ⛏️✨ Some say you're "elite" just for owning BTC. I disagree. The real elite comes from being surrounded by a community of builders and dreamers like this. Incredibly proud of what we’re growing here. 🚀 BLOCO, vcs são FODA! #Bitcoin #Bitaxe #SoloMining #BitcoinBrazil #btc @Cointelegraph @BrCointelegraph @DecryptMedia @CoinDesk @criptofacil @BitcoinNewsCom @TheBlockCo @BitcoinMagazine 🧵👇
EddieOz ⚡ tweet mediaEddieOz ⚡ tweet mediaEddieOz ⚡ tweet mediaEddieOz ⚡ tweet media
English
19
14
104
4.6K
jaonoctus retweetledi
Jose Storopoli
Jose Storopoli@storopoli·
Quantum computing and the threat to bitcoin in a Brazilian podcast @BitcoinExplica that I've recorded last week. It was a very fun talk. It is in Portuguese but I think you can auto-translate or use translated captions if you want to watch it. youtu.be/jKgICVpRnxc
YouTube video
YouTube
English
0
5
8
859
Carol Souza
Carol Souza@carol_bitcoin·
Sobre o medo do computador quântico, aqui soluções sugeridas pelo próprio Satoshi em caso de ataque: "A SHA-256 é muito forte. Não é como o passo incremental do MD5 para o SHA-1. Ele pode durar várias décadas, a menos que surja algum ataque revolucionário. Se o SHA-256 fosse completamente quebrado, acho que poderíamos chegar a um consenso sobre qual era a blockchain honesta antes do problema começar, travá-la e continuar a partir dali com uma nova função de hash. Se a quebra do hash acontecesse de forma gradual, poderíamos fazer a transição para um novo hash de maneira organizada. O software seria programado para começar a usar o novo hash após um determinado número de bloco. Todos teriam que atualizar até aquela data. O software poderia salvar o novo hash de todos os blocos antigos para garantir que um bloco diferente com o mesmo hash antigo não pudesse ser usado."
Carol Souza tweet media
Português
30
30
306
21.5K
Diego Kerber
Diego Kerber@kerberdiego·
Florianópolis, Brazil 🇧🇷 ZXX
13
10
217
6K