Not an oracle for settlement
This is an experimental feed. Event state is published as is, with no warranty of accuracy, completeness, uptime, or fitness for any purpose.
How It Works
Events on Algorand (EOA) bridges real-world event data onto the Algorand blockchain as shared, subscribable event state contracts.
1 What EOA Does
Shared on-chain event state contracts
Each tracked event gets one Algorand smart contract that any dApp can read. State is updated automatically as outcomes change — no per-app integration required.
Any real-world event source
Sports results, financial data, elections, weather — if an authoritative data source exists, it can be wired up as a data feed. Prediction market outcomes are the current proof-of-concept source.
2 Reading the contract
EOA writes the outcome onto a shared contract. Your application reads that state when it needs it. This deployment does not call any other contract.
Pull
Read the shared contract
Subscribe to an event state contract and read the outcome from its on-chain globals whenever your dApp needs it. You pull the data — EOA does not call your app.
- ✓ Cheaper for most use cases
- ✓ One-time deploy + subscribe fees up front
- ✓ No per-update charge to your account
3 Funding Your Account
EOA uses a prepaid ALGO credit balance on your account — separate from any wallet you use to send the deposit. When your dashboard shows Available Balance: 0 ALGO, you have not deposited yet (or your credit is fully reserved). That is normal for new accounts.
Open your dashboard
After signing in, the dashboard shows your deposit address and a unique memo (looks like eoa:abc123…). Every user shares the same treasury address but has a different memo.
Send ALGO from any wallet
Send ALGO on Algorand (testnet or mainnet, matching the environment you are using) to the deposit address. Put your memo in the transaction note / memo field exactly — without it we cannot credit your account.
Wait for credit
A background watcher matches on-chain deposits to your memo and adds the amount to your Available Balance, usually within ~30 seconds. Refresh the dashboard to confirm. Fees for subscribe and deploy are then deducted from this balance automatically.
What available balance is not
It is not your Algorand wallet balance and not ALGO sitting in an event contract. It is platform credit used to pay EOA service fees. Withdrawals are not supported in the current release — only deposit what you plan to use on the platform.
4 Fees
Pull — deploy & subscribe (one-time)
The first subscriber to an event pays a one-time deploy fee plus on-chain transaction fees to create the shared contract. Every subscriber pays a smaller subscribe fee to reveal the App ID. After that, state updates are funded from the shared contract pot — not billed per read to your account.
Prepaid credit model
All fees are deducted from a prepaid ALGO credit balance you deposit to your EOA account (see Funding your account above). You can top up at any time. Withdrawals at this time are not supported. Please only deposit ALGO to your EOA account that you intend to use for the platform.
5 Requesting New Event Sources
Prediction markets are a proof of concept
The current prediction market integrations demonstrate that EOA can ingest off-chain state and deploy event state contracts in real time. It is not the only source this platform can support — it was chosen as a first integration to validate the architecture.
Any authoritative data feed can be added
Sports APIs, financial data providers, weather services, election results, on-chain data from other networks — if a reliable feed exists, an ingestor can be written for it.
Submit a request
Have a data source in mind? Reach out and describe the event type, data provider, and your use case. Community-requested sources will be prioritised for upcoming integrations.