Smart Contract Security Field Guide
1–10 of 156 posts
Re: Smart Contract Security Field Guide
#2Re: Smart Contract Security Field Guide
#3Re: Smart Contract Security Field Guide
#4[flagged]
Re: Smart Contract Security Field Guide
#5[flagged]
They were found guilty of unregistered offerings to institutional. There's no way that the jury/judge won't take that prior decision into account with the non-institutional tranche. Somehow this was spun as a good thing?
Re: Smart Contract Security Field Guide
#6I expect the low-hanging fruit has gone now. And setting up spearfishing attacks to scam teenagers out of their NFTs doesn't seem as noble (or as profitable).
Re: Smart Contract Security Field Guide
#7Re: Smart Contract Security Field Guide
#8[flagged]
Now you’re saying this year is the year? n+1
Re: Smart Contract Security Field Guide
#9Every time I hear about another massive hack on Ethereum, I feel a little bit sad that I didn't specialize in software security. For many years there was huge amounts of free cash just sitting on a table waiting to be taken, a victimless crime (VCs and cryptobros are not victims, everyone is playing the same game). I expect the low-hanging fruit has gone now. And setting up spearfishing attacks to scam teenagers out…
Meanwhile there are still hundreds of millions of dollars of bounties available for white-hats who responsibly disclose.
The dark-hat hackers who aren't held responsible are likely in either Russia or North Korea
Re: Smart Contract Security Field Guide
#10[flagged]
From every lawyer I spoke to about this, this was not a win for Ripple but the SEC. They were found guilty of unregistered offerings to institutional. There's no way that the jury/judge won't take that prior decision into account with the non-institutional tranche. Somehow this was spun as a good thing?