Privacy you can verify. For any chain, any application, any builder.
Joined July 2019
- Tweets9.5K
- Following667
- Followers28K
- Likes6.9K
Pinned Tweet
The Challenge Hub season is over, and the winners have been drawn 🥳🥳🥳
One lucky winner takes home the Canyon Endurance CF 5, but there are more surprises across the prize list. Thank you to everyone who spent the season picking podiums with us and the Slovenian Cycling Federation 💙
Here is the draw, start to finish ⏬
Trivia is on tonight in the Oasis Discord at 21:00 CET 🕘
Anyone can join and you don't need to prepare anything, though last week's winners would very much like someone to give them a challenge 😒
discord.gg/62zG63WJ6v
2/ Before the draw, the full list of entries was committed onchain, which fixed who was in.
A single random number was then generated inside a secure enclave on Oasis, an isolated part of the processor that the machine's operator cannot read or change.
3/ There was no way to draw a second time, and the result is recorded onchain.
More than 20,000 tickets went into the draw, and anyone can check the outcome at raffle.cycling.oasis.net
Privacy in Everyday Life: in Denmark, attackers spent about ten days in September looking up names, addresses and personal ID numbers for roughly 8.8 million people in the national register, living and dead.
They didn't break into the register, they used the lookup access of a small private company that was allowed to search it.
Your data is only as safe as the least watched account with permission to read it.
Our first Challenge Hub season with the Slovenian Cycling Federation, in numbers:
112,800 visitors
15,310 new sign ups
5,801 players
20,000+ raffle tickets
10 winners
Plus a prize draw you can check for yourself. Check out the full season review:
oasis.net/blog/oasis-x-slove…
Oasis 🌹 retweeted
Internal auditing started... 💪💪
Cooking something genuinely novel @PrivanaFinance
1. Programmable policies for your assets
2. Multi-chain key derivation inside TEEs
3. Liquidity pools across chains *with privacy*
4. All app services fully verifiable via ROFL
None of this exists anywhere else in DeFi.
1/ Data rarely leaks from the system everyone is worried about, it rather leaks at the seams between systems.
The database is encrypted and access controlled, then the same records get copied into logs, analytics tools, support tickets and vendor dashboards, each with its own rules.
2/ Every integration is another copy. Debug logs keep request bodies. An analytics SDK sends events to someone else's servers.
A vendor gets lookup access to do one job and keeps it for years.
Each of these is reasonable on its own, and together they make the real attack surface.
- 5 races
- 6,000 players
- 35,000+ predictions
One season with @KZS_cycling, built by everyone who showed up. Thank you 💙
Trivia tonight in the Oasis Discord, 21:00 CET 🎉
come for the questions, stay for the arguments about whether the answer key is wrong
discord.gg/62zG63WJ6v
1/ Decoded: connecting rooms.
Most privacy in crypto lives inside one app such as a private token, a private pool or a private vote.
The moment you want to use that with anything else, you step back out into public, which is a bit like a hotel with soundproof rooms and glass corridors.
2/ Composable privacy means private applications can work together without stepping outside.
For example, on Sapphire, contract state is confidential, and when one confidential contract calls another, the values passed between them stay inside the confidential runtime.
A lending app can read a private balance from a vault without that balance ever appearing on chain.