Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

lucky pfp
lucky
@lsankar.eth
increasingly bullish on TEEs
2 replies
4 recasts
49 reactions

androidsixteen pfp
androidsixteen
@androidsixteen.eth
Can you say more? I am still concerned about relying on custom hardware that has a history of vulnerabilities
1 reply
0 recast
0 reaction

lucky pfp
lucky
@lsankar.eth
I see 'trust chip/cloud provider' as an intermediate trust assumption b/w 'trust anon dev' and 'trust no one' certainly risk there (and I want FHE to be performant, it's just not yet for what i want to do), but feels 10x better than 'trust anon dev' also TEEs seem to be picking up in dev/ecosystem energy
2 replies
0 recast
1 reaction

androidsixteen pfp
androidsixteen
@androidsixteen.eth
The former point makes a lot of sense. It’s practical and real-world oriented The latter is what I worry about It feels like we’re psyching ourselves out about weak technology (https://cdixon.org/2019/01/08/strong-and-weak-technologies) and hope it doesn’t block investment / attention into software based solutions to the same problems (eg. FHE)
2 replies
0 recast
2 reactions

lucky pfp
lucky
@lsankar.eth
good point
0 reply
0 recast
1 reaction

tex pfp
tex
@tex
TEEs can be particularly powerful for private information. I see the concerns about using them to secure funds, but think they’re nearly perfect for applications like sealed bids. Made me realize how much we take private information for granted in Web2 compared to blockchain contexts
0 reply
0 recast
1 reaction