Blessing | web3creed 🛡️

@FarzaTV @dabit3 Amazing

Hey, I'm open-sourcing Clicky. Go forth into the wild and build the future of education and the future of AI interfaces, my friends. I'm happy to have given a spark. Enjoy! github.com/farzaa/clicky

What does it actually take to be a pilot. Might just fuck around and find out

@VictorOlogun3 @henokcrypto Anytime big chief

@dicethedev @henokcrypto Thanks man!

Time to expand We’re hiring Vibe Coders and Agentic Engineers If you are that person or know someone obsessed send them my way asap

@Franc0Fernand0 Kindly add comments to the code when you can 🙏🏻

After years of reading and writing code, I find that the dumbest code is the best code. It doesn't matter if it's C#, C++, or Python. Make your code simple. Don't use complex abstractions or difficult syntactic sugar, and you'll have a codebase that anyone can jump into and quickly add features without introducing bugs (or bugs that are less likely to happen). This matters more than anything else.

I really hope your protocol has at least timelocks + security council right now. If not, make it a top priority to upgrade.

@bigbrutha_ Smart. Yeah?

Yeah that guy is definitely bringing them back into govt contracts

😂😂😂

@BobbyThakkar Banger

MOST BULLISH THING IN ALL OF CRYPTO Most people don't know this but I was an open source contributor to the Mozilla Foundation >10 years ago and I got into this industry bc I viewed it as OS + incentives. And thought that would create a better internet for all. Honestly the fact that it took this long to get here and have a legitimate OS foundation adopt a standard from the crypto industry feels magical to me.

@haha_girrrl 😂 dude this is a joke

After 4 yrs of Computer Science engineering, I'm thrilled to announce completion of my first website

Been deep in the trenches with blockchain protocol-level stuff for months now, studying research papers and understanding core mechanisms and grand works. Big thanks to @EFprotocol @TMIYChao

Proposal sent @Interledger I hope it goes well.

@FarzaTV Banger

I built this thing called Clicky. It's an AI teacher that lives as a buddy next to your cursor. It can see your screen, talk to you, and even point at stuff, kinda like having a real teacher next to you. I've been using it the past few days to learn Davinci Resolve, 10/10.

Quantum computing poses a fundamental threat to the cryptography securing digital assets. @Ledger CTO @P3b7_ broke down the state of Post-Quantum Cryptography (PQC) and the hardware challenges ahead at @EthCC. Here is a technical summary of his presentation. 🧵👇

NASA Artemis passing close to the Moon

I spent the evening looking into quantum computing timelines as a non-expert in quantum computing. Here is what I’ve learned: We currently have machines with ~1,000–1,500 physical qubits at error rates around 10⁻³, and Google’s algorithm requires ~500,000 physical qubits operating coherently together with surface code error correction, yoked qubit storage, magic state cultivation producing ~500K T states per second, and reaction-limited execution at 10μs cycle times — none of which has been demonstrated beyond small-scale proof-of-concept experiments. Scaling from where we are to where this needs to be isn’t a matter of incremental improvement along a Moore’s Law curve; it requires solving qualitatively new engineering problems in qubit fabrication yield, correlated error suppression across a massive chip (or multi-chip interconnects that don’t exist yet), cryogenic wiring and control electronics for half a million qubits, real-time classical decoding at the required throughput, and sustained coherence of a “primed” quantum state across minutes of wall-clock time — any one of which could prove to be a multi-year bottleneck, and all of which must be solved simultaneously.​​​​​​​​​​​​​​​​ Given the above, I just don’t see how we’re going to get to a cryptographically relevant quantum computer by 2030, especially given that we need a ~350× increase in physical qubit count with simultaneously tighter error correlations, an entirely new cryogenic control and wiring architecture to address half a million qubits, real-time decoding infrastructure that doesn’t exist yet, magic state distillation factories operating at industrial throughput, and multi-minute coherent idle times for primed states — and historically, solving even one of these at scale has taken the field the better part of a decade.

how to self-study math don’t treat it like a class. treat it like a machine you need to understand inside out. what actually works: • start with foundations → arithmetic, algebra, basic geometry. every advanced concept builds on these. • don’t memorize → understand why a formula works, not just how to use it • solve problems → intuition comes from doing, not watching • explore proofs → see the logic, see the connections, see the patterns • build connections → link math to physics, cs, economics. patterns repeat across disciplines • iterate → revisit topics. depth grows on second, third passes, not first exposure • teach yourself → explain concepts aloud, write notes, challenge your own understanding math isn’t a subject. it’s a way to see and reason about structure, patterns, and reality. self-study is slow, but mastery is permanent.

Quantum computing isn't a faster PC; it's a fundamentally different paradigm running on qubits as said by @w4vitale during @EthCC. It poses a massive threat to blockchain cryptography, but Ethereum is preparing. Here is a breakdown of the quantum threat and ETH's roadmap. 🧵👇

@macxxxxx0 @the_popemichael Wow.. Netherlands??

@the_popemichael netherlands also. i thinks it’s 45k for them.

Learned yesterday that in Germany, France & Switzerland (a bit more technical than the rest), you actually don't need your employer to file for visa support for you. All you need is to get a job that pays you above a threshold (€50k avg.), you apply and get a renewable blue card.

North Korean intelligence agents built an entire fake company to compromise one JavaScript developer. And it worked. UNC1069 didn't hack Axios. They befriended its maintainer. They cloned a real company founder's identity, built a branded Slack workspace with fake employee profiles and LinkedIn post channels, then scheduled a Microsoft Teams call with what appeared to be a full team. During the call, a fake error message said his system needed an update. He installed it. That update was the RAT. From one developer's laptop, they had everything: npm credentials, publishing access, the keys to a package installed in 80% of cloud environments. Axios gets 100 million downloads per week. The attackers published two poisoned versions at 12:21 AM UTC on a Sunday night, tagging both the latest and legacy branches within 39 minutes. The malicious dependency had been pre-staged 18 hours earlier with a clean decoy version to build registry history. Three separate RAT payloads were pre-built for macOS, Windows, and Linux. The malware self-deleted after execution to erase forensic evidence. The poisoned versions were live for about three hours before npm pulled them. Huntress observed 135 endpoints across all operating systems calling the attacker's command-and-control server during that window. Wiz found the malicious versions in roughly 3% of environments scanned. Every affected machine needs full credential rotation: npm tokens, AWS keys, SSH keys, CI/CD secrets, everything in .env files. The part that keeps getting worse: this isn't isolated. The same threat cluster compromised Trivy (a security scanner), KICS, LiteLLM, and multiple GitHub Actions in the two weeks before Axios. Google estimates hundreds of thousands of stolen secrets are now circulating from these combined attacks. The maintainer had 2FA enabled. He said himself: "I have 2FA/MFA on practically everything." The exact method of token compromise is still undetermined. One person. One fake Teams call. 100 million weekly downloads weaponized in under three hours. The npm ecosystem runs on mass trust in individual maintainers who volunteer their time, and North Korean intelligence now has a repeatable playbook for turning that trust into a delivery mechanism.