Magician & Developer | 🪄✨ Wuzard | Crafting spells with code and magic | Making the impossible possible, one line at a time | I don’t like to spell wizard.
We’re looking for a PR KOL BD
Build KOL relationships, support events, and gain real PR experience in the crypto space. Fresh grads with strong communication skills this is your sign 👋
🔥 Apply now! https://t.co/aK31mfpl7Y
Every builder has that one thing that gets them into build mode 👷
With #BNBHack Abu Dhabi coming up on Dec 5 & 6, tell us yours and you could win a share of 1 $BNB! It could be a playlist, your go-to beverage or a small habit.
To enter,
1️⃣ Follow @BNBCHAIN
2️⃣ Like & repost this
3️⃣ Comment something that gets you into build mode and #BNBHack
Five random builders will win from a 1 $BNB prize pool.
Terms & Conditions
🔸 Competition Period: Nov 25 - Dec 4, 2025.
🔸 Winners announced: Five winners will be picked and announced on Dec 5 (Picked via Simpliers).
🔸 All 3 steps required to be eligible to win.
I usually try not to criticize other industry players, but I still do it once in a while. 😂
This update from Safe is not that great. It uses vague language to brush over the issues. I have more questions than answers after reading it.
1. What does "compromising a Safe {Wallet} developer machine" mean? How did they hack this particular machine? Was it social engineering, a virus, etc?
2. how did a developer machine have access to "an account operated by Bybit"? Some code got deployed from this developer machine straight to prod?
3. How did they fool the Ledger verification step at multiple signers? Was it blind signing? or did the signers not verify properly?
4. So, was $1.4 billion the largest address managed using Safe? How come they didn't target others?
5. What lessons can other "self-custody, multi-sig" wallet providers and users learn from this?
🤷♂️