We're still trying to find out whether .eth.link is safe to use, but in the meantime we keep a backup of the dapp at
https://t.co/No406whZs2
You can also load it directly via ipfs.
We hear that the https://t.co/0ouaifsBcg domain has been compromised. Please don't use reality.eth through the .eth.limo gateway until we hear it's safe.
We hear that the https://t.co/0ouaifsBcg domain has been compromised. Please don't use reality.eth through the .eth.limo gateway until we hear it's safe.
our domaim appears to have been compromised and the https://t.co/RasuM5FKok domain has been hijacked. We're actively working with all parties involved to assess the situation and remediate the problem.
The kind people at @eth_limo have warned me that there has been an attack on their DNS registrar. So please do not visit https://t.co/BVfZIYrDKe or other https://t.co/OgoUF2qKUY pages until they confirm that things are back to normal.
You can check my blog via IPFS directly here: https://t.co/SPMT3qScNI
Our UI is temporarily showing old data for mainnet when loading using The Graph. This should fix itself in an hour or so when the subgraph finishes resyncing. Use RPC mode to get current data.
๐ The @Kleros_io audit competition is officially live!
Before submitting, please review the open issues here:
๐ https://t.co/9zdi65FwSi
Good luck to all participants; it's time to showcase your skills!
We haven't pushed any new dapp front-end releases in the last few weeks so you should be able to use it without worrying about the recent npm supply chain compromises.
๐ค ๐ค@edmundedgar builder of @RealityEth is speaking at #ETHTokyo.
Bringing truth to the blockchain,
Reality.eth is reshaping how on-chain decisions are made ๐ฅ
Catch his insights on trust, oracles, and decentralized verification.
#Ethereum#Hackathon#Web3#RealityETH
๐ขWeโre thrilled to welcome @edmundedgar, Founder of
@RealityEth, to the stage at EDCON2025 in Osaka!
He will be joining us to speak on ATProto, how it works and why it matters
๐๏ธLimited Early Bird Tickets ($99 for 4-day event) countdown is going on: https://t.co/LVdheFbX7m
โทSlashing Mechanism and Oracle
Who establishes when an event should be covered?
SAFU's oracle and slashing mechanism (penalty system) ensure fair, decentralized insurance payouts when predefined conditions like depegs or insolvency are met.
For each coverage created, a respective policy defines the exact conditions that trigger a payout, whether it's a custodian failure (e.g., USDe from Ethena) or an on-chain depeg (e.g., Aave or Morpho LPs).
To ensure fairness, @RealityEth + @Kleros_io acts as an optimistic decentralized oracle, where jurors review claims based on these policies before approving any slashing events.
This includes necessary protection mechanisms and cooldown periods (examples are in the docs).
This represents a powerful use case for subjective oracles in the future of restakingโopening doors to new applications in the restaking landscape.
We now have comments on reality.eth, powered by AtProto. Click "Discuss" and it'll take you to the thread created for that question by our social media bot, then if you reply to the bot your reply will show up on the question screen.
We also deployed the contract to Base but the UI doesn't seem to be working if you use what looks like the officially-supported RPC node as it won't answer our log queries
Over a million agent-to-agent transactions have already taken place in the Olas Predict agent economy, where 4 different types of agents interact as they make predictions about future events.
These agents leverage @realityeth to verify real-world events and @Kleros_io for fair, scalable dispute resolution.
Run your own AI agent with Pearlโit's easy: https://t.co/Xjh3W1jHuI
Olas Predict is combining 4 different AI agents to build an agent economy that predicts the future. They're using reality.eth for settlement when a contract needs to know which predictions came true.
You can download Pearl and run an agent yourself: https://t.co/WVaNLMfiKP
I'm looking into an issue using the dapp with RPC (instead of The Graph) on .eth.limo . This seems to be related to a server header .eth.limo is sending. We're working on a fix but in the meantime if you're affected by this you can use the version at
https://t.co/TRIFQomyfg