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 โฌ
We've been cooking ๐งโ๐ณ
On Friday we sat down for a community call to show you what's been on the stove.
Nino shares where Privana stands ahead of its rollout, and Ahmed walks through how we drew the Challenge Hub winners in a way anyone can check ๐ฅ
Watch the full call:
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.
new week, clean slate, inbox already at 97 ๐
we're starting ours the right way: coffee first, and Discord trivia on Wednesday to look forward to
have a good one ๐ซก
Food for thought: in any negotiation, the first person whose limit becomes visible is usually the one who pays it.
Most of what we call bargaining power is just keeping a number to yourself.
What a week in Slovenia. Our hero Primoลพ Rogliฤ is the European time trial champion ๐
Itโs his first European title on home roads, a day after he sat for a caricature at our stand in ล enฤur.
Thank you to everyone who came by during the championships ๐
Proud sponsor of the Slovenian Cycling Federation, the chain of champions ๐
1/ Decoded: the envelope.
Run an auction on a public blockchain and every bid is visible the moment it is sent.
The winning strategy becomes waiting until the last second and bidding one unit more than the last person, which works well for snipers and badly for everyone else.
2/ The usual workaround is commit and reveal: send a hash of your bid first, then reveal it once bidding closes.
That takes two transactions, and anyone who changes their mind can simply not reveal.
On a confidential chain the contract can hold the bids in encrypted state instead, compare them when the auction closes and publish only the result.