Web Platform
Api3 Market: Oracles that pay you
A data feed marketplace designed to reduce risks associated with oracle manipulation while saving dApps money
Visit ↗The Problem
dApps that rely on data feeds need decentralized sources to avoid losses caused by manipulated oracles
Oracles are systems that deliver real-world data to blockchain applications.
The Solution
A self-service, transparent data marketplace that allows dApps to earn rewards
Background
Reducing risk for dApps
"An estimated $403.2 million was exploited across DeFi through oracle manipulation in 2022"
Chainalysis, 2024Imagine you created a defi lending protocol that allows a user to deposit TokenX and borrow TokenY. Your app gets the prices of the tokens from an exchange. TokenX is normally worth $10. An attacker buys a lot of TokenX on a small exchange, temporarily pushing the price to $20. Your app then receives that TokenX is now $20. The attacker deposits 1,000 TokenX into your app. Your app believes the attacker has $20,000 in collateral (when it's really worth $10,000) and allows them to borrow more TokenY than they should. After borrowing, the attacker stops buying TokenX and the price quickly falls back to $10. Now the attacker has the borrowed TokenY, but the collateral is worth half of what the app thought.
If your app used the Api3 Market, the price of TokenX would have never been reported as $20 because of the decentralized and transparent protocol behind Api3's data feeds.
In addition to preventing market manipulation, Api3's technology also closes other loopholes that cause dApps to lose money (the integrated OEV rewards).
From start to finish, the Api3 Market is designed to help dApps stay competitive by allowing their resources to be used more efficiently with less risk.
The Research
All about data feeds
Our audience
We conducted user interviews with dApp leads and blockchain developers to understand what makes them pick one data feed over another and explored their opportunities and pain points. We found that dApps can be split into four different types, with only two of them aligning with our interests: methodical and spontaneous.
Insights
Unique, less popular data feeds are extremely costly and time-consuming for larger platforms to make available to dApps
dApps use social media to evaluate a protocol through other dApps' experiences instead of researching the protocol themselves
Some dApps will be looking towards developer communities not only for support from other developers, but to also evaluate a project’s presence in the space and potential for longevity
dApps expect to look for a customer support email or phone first. It's important to give the customer options and also show that Discord is available for support
Once dApps are happy with their data feed provider, they will stay loyal unless the cost becomes too high or the provider no longer suits their needs
Developers feel they have a strong influence within their own dApp companies when it comes to picking the data feed provider for the dApp
User Journeys
I created user journey maps for our target audience and current clients that connected through our business team as well as the first iteration of our market platform.
Define
Meet Mr. Spontaneous and Mr. Methodical
Based on the user interviews, I created the user personas of Javier Spontaneous and Kristian Methodical to represent the two distinct dApp archetypes and their unique data feed requirements.
HOW MIGHT WE…
best serve unique data feeds to dApps while building trust through transparency and showing them that our protocols reduce risk?
Ideation & Design
Creating the marketplace
Information Architecture
To use a specific data feed, dApps would already know what chain they wanted to use. The market was designed around this intuitive search.
Lo-fi Designs
I wireframed the core flows to get a basic idea of the visuals and interactions while prioritizing transparency and ensuring that all key information dApps need to make informed decisions is easily accessible. I typically take a mobile-first approach, but prioritized desktop experiences for the Api3 Market since its primary use cases revolve around implementing code snippets.
UI & Accessibility Testing
I worked with our UI team to ensure the final version is within our brand guidelines and fits well within our design system. I also conducted accessibility testing to ensure the design meets WCAG 2.1 standards.
Testing & Iteration
Closing the Gaps Automated Tools Missed
Executing Tasks Within a Prototype
I conducted usability tests on 7 people that fit our user personas by creating a prototype and using services like Maze and Useberry to track their clicks, time, and other metrics. They were asked to complete a number of core tasks.
Prioritizing Issues
Each issue that was discovered was assigned an ID number, level of task criticality (how important is the task affected by the issue), level of impact (how high is the interference of the issue in the experience), and frequency (how many participants experience this issue divided by total participants). These values were multiplied together to give us issue severity (task criticality * impact * frequency). This allowed me to prioritize which issues need to be handled and discussed first.
Retesting
The updated prototype was retested with 5 new participants, confirming that the previous issues were resolved.
Results
416,069USD paid to dApps with OEV rewards
Rewards paid to dApps is a direct reflection of the design success- dApps need to effectively use the data feeds to earn the rewards.
Final Thoughts
What the Api3 Market Taught Me
WHAT I LEARNED
Building trust is more than just educating consumers about the product; it's about fostering a supportive community that they can rely on.
NEXT STEPS
I'd like to continue working to find a balance between educating the users on complex topics without overwhelming them.
MOST PROUD OF
I'm proud to be part of a team that created a product that is genuinely looking to support the user's best interests above all else.
Like what you see?






