Content
@
https://cbr.stanford.edu/sbc23/
0 reply
0 recast
0 reaction
gakonst
@gakonst
consensus workshop livecast
1 reply
3 recasts
20 reactions
gakonst
@gakonst
kicking uss off, Elaine Shi talking about ORAM -- "Oblivious RAM" TLDR even if you have confidential compute, querying the DB can leak sensitive information via your access patterns
1 reply
0 recast
0 reaction
gakonst
@gakonst
example
1 reply
0 recast
0 reaction
gakonst
@gakonst
https://eprint.iacr.org/2013/280.pdf
1 reply
0 recast
0 reaction
gakonst
@gakonst
an easy way to think about ORAM is that it "encrypts" the access patterns, for every query, it generates multiple accesses, and you're unable to distinguish which one is the right one - almost like a noising process
1 reply
0 recast
0 reaction
gakonst
@gakonst
so you run the oram algo inside of your enclave, and you get both encrypted compute and unable to correlate which gives you both confidential compute and db queries but this has been hard to make practical due to large constants
1 reply
0 recast
0 reaction