better safu than sorry
Lots of Security incidents today, here's some practical tips for those who just wanna protect yourself:
1) UPDATE EVERYTHING - main targets are:
a) Browsers - Chrome, Safari, Firefox
b) OS: : Settings -> General -> software update; Linux: sudo apt update && sudo apt upgrade; Windows: I think there's a button. Do this for any remote home servers & Openclaw/hermes boxes
c) Phones: Update it all
d) Desktop apps (Slack, Cursor, Discord, etc)
2) Limit web browsing this week: Stay within walled gardens (twitter, youtube, etc); don't click random links this week. Just wait until the patches go through. Do step 1 again after a week.
3) Avoid untrusted Wifi networks until your devices are updated
4) Stay vigilant about phishing emails offering "certificate fixes" or fraud updates
5) Have an iPhone 11-16? TURN BLUETOOTH OFF for the time being until apple patches come through.
6) Code/Dev: UPDATE ALL YOUR REPOS - @charliermarsh has already updated uv 0.13.4 which reacts to the eMudra incident for uv (Python), Typesript according to Claude has equivelant. Tell your agents to go and update all your active repos to update package manager across uv, npm, bun, cargo, etc etc
What advice did I miss?
3
0
11
1,503
the year is 2036
php mess was uncovered 10 years ago
ai has connected your real name to your old dating profile, hair loss order, std test and the forum where you asked if being attracted to your wife’s sister is normal
your teenage posts. your private messages. the photos you thought you deleted
all from websites you forgot existed
some old government site or crypto exchange circa 2016 exposes your passport and your home address
oh hi anon, how u doing?
php mess was uncovered 10 years ago
ai has connected your real name to your old dating profile, hair loss order, std test and the forum where you asked if being attracted to your wife’s sister is normal
your teenage posts. your private messages. the photos you thought you deleted
all from websites you forgot existed
some old government site or crypto exchange circa 2016 exposes your passport and your home address
oh hi anon, how u doing?
4
0
16
879
I’ve been reluctant to speak publicly about this, but using @ryskfinance without dark mode has started to affect my personal life.
At first, it was small adjustments. Lowering my brightness. Sitting further from the screen. Only checking positions during daylight hours. You tell yourself these are reasonable compromises for sustainable yield paid upfront.
Over time, your world gets smaller.
My wife and I now have an agreement that I won’t open Rysk in the bedroom. I respect that boundary. But it means that when I need to manage a position at night, I have to leave our bed and sit alone in the kitchen, illuminated by bone.
The team has been very clear that the colour is bone. I’ve passed this information on to my family.
My sleep has deteriorated. I’m less present at dinner. Sometimes my wife is talking and I’m still looking at the bone-coloured page. I’ve started taking walks without my phone, but certain shades of pavement remind me of Rysk. I just can’t stop thinking about it…
There are financial consequences too. I’ve begun selecting longer expiries simply to reduce how often I need to look at the website. But I keep coming back every Friday to see if my friends got exercised.
I still believe in the product. I love the product. That’s what makes this so difficult.
The team has indicated that dark mode could take approximately three years. I appreciate having a timeline. It gives us something to plan around. And it gives us hope.
My wife asked me last night whether I thought things would get better.
I told her 2029, subject to engineering capacity.
At first, it was small adjustments. Lowering my brightness. Sitting further from the screen. Only checking positions during daylight hours. You tell yourself these are reasonable compromises for sustainable yield paid upfront.
Over time, your world gets smaller.
My wife and I now have an agreement that I won’t open Rysk in the bedroom. I respect that boundary. But it means that when I need to manage a position at night, I have to leave our bed and sit alone in the kitchen, illuminated by bone.
The team has been very clear that the colour is bone. I’ve passed this information on to my family.
My sleep has deteriorated. I’m less present at dinner. Sometimes my wife is talking and I’m still looking at the bone-coloured page. I’ve started taking walks without my phone, but certain shades of pavement remind me of Rysk. I just can’t stop thinking about it…
There are financial consequences too. I’ve begun selecting longer expiries simply to reduce how often I need to look at the website. But I keep coming back every Friday to see if my friends got exercised.
I still believe in the product. I love the product. That’s what makes this so difficult.
The team has indicated that dark mode could take approximately three years. I appreciate having a timeline. It gives us something to plan around. And it gives us hope.
My wife asked me last night whether I thought things would get better.
I told her 2029, subject to engineering capacity.
13
1
71
3,955
fwiw full alignment with bybit was probably always mantle’s only real shot at winning
think mantle desperately needs a rebrand
MNT —> BIT (as it was originally called)
mantle —> bitchain
until then the alignment will never be understood by the wider market
think mantle desperately needs a rebrand
MNT —> BIT (as it was originally called)
mantle —> bitchain
until then the alignment will never be understood by the wider market
@wayofhustle it died right after bybit takeover for me, but in @0xVEER era? amazing chain
6
0
26
1,367
VEER retweeted
Bybit, as the biggest holder and supporter of Mantle, will vote YES for this proposal. When we got hacked the industry got together and helped us. It is the only right thing that we do the same to unit together and walk out from difficult times.
Following this week's rsETH incident involving @KelpDAO and @LayerZero_Core, a proposal has been put forward for Mantle to contribute a loan facility to @aave's coordinated relief effort.
The loan would form part of a wider coordinated framework, structured to minimize disruption across the broader ecosystem and contribute to a measured path forward for users affected.
DeFi United, as one.
Full details below: forum.mantle.xyz/t/discussion-m…
155
124
1,491
167,650
VEER retweeted
The fallout from the Kelp rsETH exploit is going to be messy and could potentially be quite a bit more severe than some people are making out right now.
It seems rsETH on mainnet is technically still backed, but, there's no liquidity to sell rsETH, and with rsETH contracts paused, there’s currently no usable redemption path either.
In the unlikely case they socialised the loss across all rsETH holders, it would be worth something like 81.25% (1 - $300m/$1.6b) of its original value.
I don't think they will do that though. It would likely push a number of large positions on Aave towards undercollateralisation and risk creating bad debt. That alone would be enough to trigger a long and painful lawsuit.
So realistically rsETH holders on L2s are likely going to swallow the loss. Who are they? Why did they have rsETH on L2s in the first place? Could be other DAOs or funds etc who've taken a huge hit. That alone could have consequences we won't know about for some time.
Impacted individuals on L2s will likely consider their own legal action to force socialisation, potentially prolonging the delay before redemptions are opened.
Either way, once redemptions are eventually opened, it's unlikely any lending protocols would re-allow collateralisation, so there will be need to be a massive unwind of huge volume of rsETH/ETH looping trades.
All those looping trades are currently massively negative ROE. Aave ETH utilisation is currently at 100% with ETH borrow rate at 8.71%. Since staked ETH yield is around 2.5%, the ROE for any LST or LRT borrow or looped borrow is anywhere between -6.21% and around -90%, depending how degen people are. So we could see an unwind of lots of LST loops aside from just rsETH/ETH ones.
The normal path to unwind a loop is to swap collateral and repay, but this is unlikely to be possible for such a large amount of unwinds at once, and certainly won't be feasible for rsETH unless someone puts up significant liquidity for it.
When the swap and repay path fails, you normally have to withdraw as much collateral as you can, manually redeem, repay some debt, withdraw more collateral, and so on.
Here's the kicker. If rsETH is no longer collateral and no longer has borrowing power, this makes it much more difficult for people to manually unwind as well.
If people get stuck for longer periods paying huge negative ROE for too long, and there’s no liquidity to liquidate them, their equity gets eroded. Once debt exceeds recoverable collateral value, bad debt appears, and can keep worsening as interest accrues and the position remains unresolved.
It seems rsETH on mainnet is technically still backed, but, there's no liquidity to sell rsETH, and with rsETH contracts paused, there’s currently no usable redemption path either.
In the unlikely case they socialised the loss across all rsETH holders, it would be worth something like 81.25% (1 - $300m/$1.6b) of its original value.
I don't think they will do that though. It would likely push a number of large positions on Aave towards undercollateralisation and risk creating bad debt. That alone would be enough to trigger a long and painful lawsuit.
So realistically rsETH holders on L2s are likely going to swallow the loss. Who are they? Why did they have rsETH on L2s in the first place? Could be other DAOs or funds etc who've taken a huge hit. That alone could have consequences we won't know about for some time.
Impacted individuals on L2s will likely consider their own legal action to force socialisation, potentially prolonging the delay before redemptions are opened.
Either way, once redemptions are eventually opened, it's unlikely any lending protocols would re-allow collateralisation, so there will be need to be a massive unwind of huge volume of rsETH/ETH looping trades.
All those looping trades are currently massively negative ROE. Aave ETH utilisation is currently at 100% with ETH borrow rate at 8.71%. Since staked ETH yield is around 2.5%, the ROE for any LST or LRT borrow or looped borrow is anywhere between -6.21% and around -90%, depending how degen people are. So we could see an unwind of lots of LST loops aside from just rsETH/ETH ones.
The normal path to unwind a loop is to swap collateral and repay, but this is unlikely to be possible for such a large amount of unwinds at once, and certainly won't be feasible for rsETH unless someone puts up significant liquidity for it.
When the swap and repay path fails, you normally have to withdraw as much collateral as you can, manually redeem, repay some debt, withdraw more collateral, and so on.
Here's the kicker. If rsETH is no longer collateral and no longer has borrowing power, this makes it much more difficult for people to manually unwind as well.
If people get stuck for longer periods paying huge negative ROE for too long, and there’s no liquidity to liquidate them, their equity gets eroded. Once debt exceeds recoverable collateral value, bad debt appears, and can keep worsening as interest accrues and the position remains unresolved.
42
93
711
237,609
VEER retweeted
Hi. Professional C/C++ programmer here. The open-source code I can find written by Adam Back and Satoshi Nakamoto don't look remotely similar.
Back's code looks typical of academic Unix programmers who also hack their code to run on Windows.
Satoshi code was written by a professional Windows programmer who also wrote for Unix.
Stylistically, they look nothing alike. There's not enough time between 2005 when I can find the newest Adam Back and January 2009 when Satoshi published Bitcoin/0.1 to account for the change. Both are perfectly competent programmers, but stylistically, they are completely different.
The NYTimes tried to compare their English language in posts/emails. I'm compare their C/C++ language in their open-source code. The NYTimes merely points out they both use C++ as if that's another corroborating detail, when the actual code seems to disqualify Adam Back.
Back's code looks typical of academic Unix programmers who also hack their code to run on Windows.
Satoshi code was written by a professional Windows programmer who also wrote for Unix.
Stylistically, they look nothing alike. There's not enough time between 2005 when I can find the newest Adam Back and January 2009 when Satoshi published Bitcoin/0.1 to account for the change. Both are perfectly competent programmers, but stylistically, they are completely different.
The NYTimes tried to compare their English language in posts/emails. I'm compare their C/C++ language in their open-source code. The NYTimes merely points out they both use C++ as if that's another corroborating detail, when the actual code seems to disqualify Adam Back.
Bitcoin’s founder, Satoshi Nakamoto, has remained hidden for 17 years. A trail of clues — and a year of digging by our reporter, John Carreyrou — led us to a 55-year-old computer scientist in El Salvador named Adam Back. nyti.ms/4bXWC3V
254
878
10,481
1,408,426
VEER retweeted
first off, Ethereum is ALIVE
just shipped an @ethereum events globe
🔹160 mapped over 52 countries
🔹browsable event calendar
🔹find your city & event!
Made possible with @ethereumfndn 's curation with the ethereum community page
Link 🔽
thank you @gabrielchua, I feel the AGI
just shipped an @ethereum events globe
🔹160 mapped over 52 countries
🔹browsable event calendar
🔹find your city & event!
Made possible with @ethereumfndn 's curation with the ethereum community page
Link 🔽
thank you @gabrielchua, I feel the AGI
20
27
202
22,716
money per se is not dangerous
money per se is not useful
pg
money per se is not useful
pg
Don't fear competitors who've raised a lot, unless you can say precisely how all that extra money is going to make them beat you. E.g. if ads are the only way to acquire users, and they can buy all the ads, you're in trouble. But money per se is not dangerous.
32
1
42
1,973