Hey folks! I'm going to retire this account for now (too many spam notifications to be useful!). If you want to get a hold of me or follow what I'm doing, @iamnafets is my main. Would love to stay in touch with the awesome people I connected with here.
Annoying thing about web3 security today is that the best solution is your social circle alerting you to potential hacks+vulns. These are often wrong but there's also not a better alternative for most users.
@Plumferno Also worth a discussion in the community about how best to protect users: https://t.co/syPzzO2ChS
Traditional security team models and postures just don't work here. Everyone trying their best but the ecosystem/community needs better solutions.
Annoying thing about web3 security today is that the best solution is your social circle alerting you to potential hacks+vulns. These are often wrong but there's also not a better alternative for most users.
@Plumferno Thanks Plum. Really take security seriously, [email protected] if there's something to look into.
We would never sell to a party which would abuse the userbase/data/trust of Inspect. Full stop.
@ZsMann@Plumferno@OfficialTravlad@FadiRaees We have not sold Inspect, we will notify via @nftinspect if that happens. Inspect does not request nor have tweet write permissions. If there are security concerns please DM me directly or email [email protected] - we will look into them promptly.
@iamrobotbear@OfficialTravlad@nftinspect We haven't sold Inspect and there have been no substantive changes. We also don't have tweet permissions in the Twitter API. Can you point me to any of these technical POCs? I want to take this seriously but it seems likely FUD atm.