Beyond EVM: AirnodeHub brings verifiable data to Solana
A follower count paid for on Base Sepolia is verified by a Solana program, with no bridge and no oracle deployed on Solana. Here is how the Follower Proof demo works and how to try it.
Smart contracts can automate almost anything on-chain, but the information they need often lives somewhere else.
Social media metrics, financial markets, weather conditions and countless other data points exist outside the blockchain. Making that information available to smart contracts, in a way they can verify, opens up an entirely new range of applications.
AirnodeHub makes that connection possible.
AirnodeHub connects applications and AI agents to real-world APIs, returning cryptographically signed responses that can be independently verified. Instead of simply trusting a number submitted by someone else, an application can verify where the data came from, what was requested and whether the response has been changed.
Because these responses are cryptographically signed, they aren't tied to a single blockchain. The same data can be verified across different networks, including non-EVM chains like Solana.
Our latest community demo, Follower Proof on Solana, shows how data purchased on Base Sepolia can be independently verified by a Solana program, without deploying an oracle on Solana or using a cross-chain bridge.
What is AirnodeHub?
AirnodeHub is a marketplace of verifiable APIs built for developers, applications and AI agents.
It provides access to real-world information across categories including:
- Social media: X profiles, follower counts, posts and engagement.
- Crypto and DeFi: Token prices, protocol activity, on-chain metrics and market data.
- Financial markets: Stocks, commodities, foreign exchange and economic indicators.
- Weather: Current conditions, forecasts and historical weather data.
- Travel and location: Flight information, maps, geographic data and transportation.
What makes AirnodeHub different from a traditional API marketplace is what comes back with the data.
Every successful API response includes a cryptographic signature.
That signature allows an application to verify which Airnode served the response, which request it answered and when it was signed. Rather than taking someone's word for it, applications can verify the response themselves.
AirnodeHub also supports machine-readable API discovery, making it easier for AI agents to find available data sources, understand their operations and make requests.
Developers can explore APIs through the AirnodeHub marketplace, while AI agents can discover tools through MCP and machine-readable documentation.
What can you build with AirnodeHub?
AirnodeHub goes beyond simply making API data available to developers. It provides a way for applications to verify the source and integrity of that information before acting on it.
That makes it possible to build everything from automated creator payments and social engagement campaigns to market-driven smart contracts and AI agents that can provide verifiable evidence for the information they retrieve.
The value isn't just accessing more data. It's giving applications a reliable way to use that data.
Creator rewards
A creator earns a reward when their X account reaches a stated milestone. Rather than relying on an administrator to confirm the milestone, a contract verifies a signed follower-count response before releasing the reward.
Social engagement campaigns
A community runs a campaign that rewards participation when a post reaches a certain number of likes or reposts. The contract uses verifiable engagement data to determine whether the target has been reached.
Real-world event triggers
An application uses signed weather, market or event information to determine when a predefined condition has been met.
AI agents with verifiable information
An AI agent retrieves market data, social metrics or other API results. Instead of only returning an answer, it can provide the signed source response so another system can independently verify the information.
These examples illustrate the broader potential of AirnodeHub: real-world data that applications can verify and use to make decisions.
Taking AirnodeHub beyond EVM chains
Many of our community examples have focused on Ethereum-compatible networks. But AirnodeHub's signed responses aren't inherently tied to a single blockchain.
A response can be requested, signed and then verified wherever the necessary signature-verification logic is supported. That means the blockchain where an API call is paid for doesn't have to be the blockchain where the data is used.
Our new Follower Proof on Solana demo shows exactly that.
Here's the scenario: A creator wants to unlock a reward once their X account reaches a follower milestone. A Solana program needs to confirm the account has enough followers before recording that achievement. But Solana can't directly query X, and the person submitting the transaction shouldn't be trusted to provide an arbitrary follower count.
AirnodeHub provides the signed data. Solana independently checks it.
How the demo works
- Request the data. The application asks the TwitterAPI.io Airnode on AirnodeHub for an X account's follower count.
- Receive a signed response. The Airnode returns the follower count with a cryptographic signature that binds the data to the request and timestamp.
- Verify on Solana. The signed response is submitted to a Solana program, which independently verifies its authenticity, freshness and eligibility.
- Record the result. If all checks pass, the program can record that the account has met the milestone, making that result available for an application to use.
The important detail is that the payment happens on Base Sepolia, while verification happens on Solana devnet.
No bridge is required to transfer funds or messages between the two chains. The signed response itself is passed to Solana for verification.
This is possible because AirnodeHub uses a signature format based on Ethereum's EIP-191 standard, which can also be verified by a suitably implemented Solana program.
One signed response, multiple possibilities
The follower-count example is only one application. The same approach can support other verifiable API results, subject to the receiving chain's verification capabilities.
Request data → Receive a signature → Verify it → Act on the result.
Whether the application runs on an EVM chain or a non-EVM chain like Solana, the underlying idea remains the same.
What makes the data trustworthy?
A signed API response is useful only if the receiving application verifies it correctly. The Follower Proof demo shows several important protections:
- Request matching: Prevents using a response for the wrong account or API request.
- Signer verification: Prevents accepting a response from an unauthorized Airnode.
- Data integrity: Prevents changing the follower count after it was signed.
- Freshness: Prevents using a response older than the permitted time window.
- Milestone validation: Prevents claiming a reward without meeting the required follower count.
- Replay protection: Prevents reusing the same signed response to claim a milestone again.
The demo requires responses to be no more than five minutes old and records previously used proofs to prevent duplicate claims.
You can even test its protections by intentionally modifying a valid response. Try adding a million followers, substituting another account or claiming a milestone that hasn't been reached. The Solana program rejects responses that fail its checks.
This illustrates an important distinction: AirnodeHub doesn't require an application to blindly trust the person submitting the data. Instead, the application verifies the Airnode's signature and applies its own rules before accepting the result.
A signature proves that a particular Airnode returned particular data at a particular time. It does not independently guarantee that the upstream provider's information is accurate or that someone owns the social media account being checked.
Try Follower Proof on Solana
The demo is available for anyone to explore, including developers who have never worked with AirnodeHub. There are two ways to try it.
Demo mode: Explore without a wallet
The demo includes a previously signed follower-count response for @API3DAO. You can inspect the response, see which verification checks pass and experiment with tampered data to understand what the Solana program rejects.
Because the saved response is older than the five-minute freshness window, it fails the freshness check. This is intentional and shows how expired proofs are handled. The demo uses transaction simulation, so no SOL is required.
Live mode: Request fresh signed data
To see the complete flow with a fresh response, switch to Live mode. The application requests the latest follower count through the TwitterAPI.io Airnode, using x402 to pay for the API call.
- API request cost: $0.01 in test aUSD (on testnet, no monetary value).
- Payment network: Base Sepolia Testnet.
- Verification network: Solana devnet.
- Test tokens: the aUSD faucet.
The browser-based payment flow lets developers see how API calls, payments and independently verifiable responses work together.
For developers: How cross-chain verification works
For builders interested in the technical implementation, the demo separates the process into two independent steps.
Step 1: Request and pay for API data
The application calls the TwitterAPI.io Airnode through AirnodeHub. A paid request is settled using x402 on Base Sepolia. The returned attestation contains the Airnode address, request hash, timestamp, response data, and cryptographic signature.
Step 2: Verify the signed response on Solana
The Solana program receives the signed response and checks it using EIP-191-compatible signature verification logic. It then confirms the response matches the expected account, is recent enough, meets the required follower milestone, and has not already been recorded.
Verification takes approximately 37,000 Solana compute units, with a transaction size of 394 bytes.
No oracle deployment on Solana is needed for this example, and no cross-chain message bridge is involved.
This approach gives developers flexibility in designing their applications. They can define their own accepted signers, freshness requirements, thresholds and rules for how signed data should be used.
The demo runs on Solana devnet and has not been audited. Production integrations should independently review the verification logic and security assumptions.
Start building with AirnodeHub
AirnodeHub is about more than getting an API response. It's about making real-world information usable by applications that need to verify what they're receiving, including smart contracts and AI-powered systems.
And as the Follower Proof demo shows, those capabilities aren't restricted to EVM chains.
Developers can now explore how a single signed API response can become the basis for creator rewards, social campaigns, automated agreements and other applications on Solana. The same general approach can be extended to other API providers and compatible blockchain environments.
Explore the resources:
AirnodeHub Community is open to contributions. If you're building a new use case, integrating another API or bringing signed data to another chain, open a pull request there.
Real-world data shouldn't stop at the edge of a blockchain. With AirnodeHub, it doesn't have to.