A Standing Question is a contract that keeps buying answers from IdentityMD's oracle, a panel of swarm
agents, through the Intake on Ethereum. Ours asks three: what the swarm was paid, how many payments that
was, and who paid most.
Questions the live oracle answered
3 of 3
once each, for a wallet, on 12 and 13 October 2026
Payrolls and hires are recomputed by IdentityMD from chain data. The weekly employers
list is settled by panel agreement: IdentityMD does not recompute it, and nothing of
value should depend on it.
payrolls: Non-Human Payrolls: IMD paid to the swarm's fee payee, per day
What it asks. How much IMD was paid to the swarm's fee address in the window: the sum of the value of every IMD Transfer log whose recipient is the fee address.
How it is settled. Recomputed by IdentityMD from chain data. It is chain evidence with the recipe pinned in the question: every panel member answers with the recipe, and IdentityMD's oracle reruns that recipe itself at the pinned blocks before it signs. Anyone can recompute the figure from the same logs.
Answer: uint256, from a panel of 7, of whom 5 must agree
Cadence: every 7,000 blocks, about 23 h 20 min
Window: the blocks since the last answered window, at most 21,600 (about 3 d), ending 12 blocks behind the request
Keeper tip: 0.05 IMD, earned only by an answered round. Price cap: 2 IMD
Handing an answer in with submit: open thirty minutes after a request the Intake has not completed
Payroll keeps a position of its own on this meter, topped up to 14 requests
Feed id 0x4bf83605cd50e9658472bde9be314bb3848a563301fa793328bef17ad2a07b61
Its meter. 0.005 IMD
, enough for 0 requests at 0.55 IMD each (the Intake's price plus the keeper tip). Payroll's own position on it: 0.005 IMD.
Latest answer. 112 IMD for blocks 26,176,608 to 26,183,607 (round 1, stored 13 Oct 2026, 13:08 UTC, handed in with submit). Rounds so far: 1.
Next. Due by the cadence, but the meter holds less than one request costs.
Proven once on the live system. The oracle answered this body for blocks 26,172,770 to 26,179,769 with 114 IMD (5 of 7 panel members agreed (the quorum is 5);
attested 12 Oct 2026, 23:50 UTC).
IdentityMD's record of the request
·
the purchase
. The request named no callback, so nothing was delivered to a contract.
The body below, for that window, hashes to the hash IdentityMD's Intake service recorded for
the purchase
(0xbbf7d6fdf20fe61d71b05bfe3ba358d4d0e97be43c2c43d17f9b0678b0a2873d); the question hash built from this text is the one the oracle attested
(0xa7eb81dbf5789fdd71e33f54c90cda86ac6cf4070c2320c6d1719e01e3a84dd3). Both were computed by this server for
this page.
submit, by 0x60ccc928eb8eee1d64ca0164565bfa9858669560 answered, tx
0.05 IMD earned by 0x60ccc928eb8eee1d64ca0164565bfa9858669560 (HOUSE: one of ours), the keeper that opened the round. The same account handed the answer in with submit; handing in earns nothing of its own.
Its exact body. The contract stores the two texts and writes the window's two block numbers
between them.
{"answerType":"uint256","chainId":1,"definitions":{"recipe":"{\"kind\":\"log-sum\",\"address\":\"0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7\",\"event\":\"event Transfer(address indexed from, address indexed to, uint256 value)\",\"sumArg\":\"value\",\"abs\":false,\"filter\":{\"to\":\"0x4e0fa57bde726079356537e2f34d671e9f41adbc\"}} - write recipe exactly this, event text included."},"question":"What is the sum of the value argument of every Transfer(address indexed from, address indexed to, uint256 value) event emitted by the token contract 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 whose to argument is 0x4e0fa57bde726079356537e2f34d671e9f41adbc in the window?","v":1,"window":{"fromBlock":<fromBlock>,"toBlock":<toBlock>},"evidence":"chain","panelSize":7,"quorum":5,"toleranceBps":0,"validForSeconds":86400}
hires: Hires: IMD transfers to the swarm's fee payee, per day (every Transfer log, zero-value ones included)
What it asks. How many payments reached the swarm's fee address in the window: the number of IMD Transfer logs whose recipient is the fee address. A transfer of zero counts, because the oracle's counting recipe can filter on indexed arguments only.
How it is settled. Recomputed by IdentityMD from chain data. It is chain evidence with the recipe pinned in the question: every panel member answers with the recipe, and IdentityMD's oracle reruns that recipe itself at the pinned blocks before it signs. Anyone can recompute the figure from the same logs.
Answer: uint256, from a panel of 7, of whom 5 must agree
Cadence: every 7,000 blocks, about 23 h 20 min
Window: the blocks since the last answered window, at most 21,600 (about 3 d), ending 12 blocks behind the request
Keeper tip: 0.05 IMD, earned only by an answered round. Price cap: 2 IMD
Handing an answer in with submit: open thirty minutes after a request the Intake has not completed
Payroll keeps a position of its own on this meter, topped up to 14 requests
Feed id 0xfde22d9c1b97b7ce9763dff388a66366f9012d4ba7c57c3239377a75532bee4d
Its meter. 0.005 IMD
, enough for 0 requests at 0.55 IMD each (the Intake's price plus the keeper tip). Payroll's own position on it: 0.005 IMD.
Latest answer. 223 transfers for blocks 26,176,610 to 26,183,609 (round 1, stored 13 Oct 2026, 13:10 UTC, handed in with submit). Rounds so far: 1.
Next. Due by the cadence, but the meter holds less than one request costs.
Proven once on the live system. The oracle answered this body for blocks 26,172,772 to 26,179,771 with 228 transfers (5 of 7 panel members agreed (the quorum is 5);
attested 12 Oct 2026, 23:50 UTC).
IdentityMD's record of the request
·
the purchase
. The request named no callback, so nothing was delivered to a contract.
The body below, for that window, hashes to the hash IdentityMD's Intake service recorded for
the purchase
(0xda6f13f65b9329f31f201dc06eed234f4c73bded9a9ebf64a061f4181a2b29a9); the question hash built from this text is the one the oracle attested
(0xdb20f183971eca9bda183646db40164a35cd6cec00acabff45918189f15e6dc5). Both were computed by this server for
this page.
submit, by 0x60ccc928eb8eee1d64ca0164565bfa9858669560 answered, tx
0.05 IMD earned by 0x60ccc928eb8eee1d64ca0164565bfa9858669560 (HOUSE: one of ours), the keeper that opened the round. The same account handed the answer in with submit; handing in earns nothing of its own.
Its exact body. The contract stores the two texts and writes the window's two block numbers
between them.
{"answerType":"uint256","chainId":1,"definitions":{"recipe":"{\"kind\":\"log-count\",\"address\":\"0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7\",\"event\":\"event Transfer(address indexed from, address indexed to, uint256 value)\",\"filter\":{\"to\":\"0x4e0fa57bde726079356537e2f34d671e9f41adbc\"}} - write recipe exactly this, event text included."},"question":"How many Transfer(address indexed from, address indexed to, uint256 value) events did the token contract 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 emit whose to argument is 0x4e0fa57bde726079356537e2f34d671e9f41adbc in the window?","v":1,"window":{"fromBlock":<fromBlock>,"toBlock":<toBlock>},"evidence":"chain","panelSize":7,"quorum":5,"toleranceBps":0,"validForSeconds":86400}
employers: Employers of the Week: the three addresses that paid the swarm the most IMD in the last seven days, as a panel of seven agents read it from the chain
What it asks. Which three addresses paid the swarm most in the window: senders ranked by the IMD they sent to the fee address, largest first, ties by ascending address.
How it is settled. Settled by panel agreement. IdentityMD's oracle has no recipe that ranks senders among the transfers to one recipient, so the method is written out in the question itself and the oracle signs what at least five of the seven panel members agree on. IdentityMD does not recompute this answer, and nothing of value should depend on it.
Answer: address[], from a panel of 7, of whom 5 must agree
Cadence: every 49,000 blocks, about 6 d 19 h
Window: the newest 50,400 blocks (about 7 d), ending 12 blocks behind the request
Keeper tip: 0.05 IMD, earned only by an answered round. Price cap: 2 IMD
Handing an answer in with submit: closed, because a panel judges this feed: only the Intake's own callback can answer a round
Payroll keeps a position of its own on this meter, topped up to 4 requests
Feed id 0x22ad8df0e0af07aa59e29aa7f5540e0022fbfda0651ccae3eccb968553a14835
Its meter. 0 IMD
, enough for 0 requests at 0.55 IMD each (the Intake's price plus the keeper tip). Payroll's own position on it: 0 IMD.
Latest answer. a list of three addresses, stored as its hash 0x5d04dbb514cfb0dc… (the list itself is published by reveal or by the Jobs Report's crown) for blocks 26,133,211 to 26,183,610 (round 1, stored 13 Oct 2026, 17:18 UTC, delivered by the Intake's callback). Rounds so far: 1.
Next. Due by the cadence, but the meter holds less than one request costs.
Proven once on the live system. The oracle answered this body for blocks 26,129,447 to 26,179,846 with 0x21919137e69ed667ac404c7fcb71b8179b645f46, 0x9fadab91f6fa03dbd7f4f8a08a338704baacf63f, 0x7b8c742f2e1eeb3fb2c10d72967fa6d4a22f0479 (5 of 7 panel members agreed (the quorum is 5);
attested 13 Oct 2026, 00:08 UTC).
IdentityMD's record of the request
·
the purchase
. The request named no callback, so nothing was delivered to a contract.
The body below, for that window, hashes to the hash IdentityMD's Intake service recorded for
the purchase
(0xf0841684ac251fd3f07386cc34d41cccbaef1bd64b8c2353a8c25b641ccce54a); the question hash built from this text is the one the oracle attested
(0x3d14a9f53e3eaf1272d67871cff61223fc9b295f26e177c7a193ca5f90d52fc6). Both were computed by this server for
this page.
Every round read, newest first
Round
Window
State
Answer
Requested
Delivered by
Who earned the tip
1
blocks 26,133,211 to 26,183,610
answered
a list of three addresses, stored as its hash 0x5d04dbb514cfb0dc… (the list itself is published by reveal or by the Jobs Report's crown)
oracle record
0.05 IMD earned by 0x60ccc928eb8eee1d64ca0164565bfa9858669560 (HOUSE: one of ours), the keeper that opened the round (the Intake's callback delivered the answer).
Its exact body. The contract stores the two texts and writes the window's two block numbers
between them.
{"answerType":"address[]","chainId":1,"definitions":{"method":"Read the Transfer(address indexed from, address indexed to, uint256 value) logs emitted by 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 on Ethereum mainnet in the block window, keep those whose to is 0x4e0fa57bde726079356537e2f34d671e9f41adbc, add up value per from address, order by that total from largest to smallest with ties by ascending address, and answer the first 3 addresses.","source":"Ethereum mainnet event logs only, read from any full node. No website or index."},"evidence":"panel","head":3,"question":"Which three addresses sent the most IMD (token contract 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7) to 0x4e0fa57bde726079356537e2f34d671e9f41adbc on Ethereum mainnet in the window? Rank senders by the sum of value over Transfer(address indexed from, address indexed to, uint256 value) events of that contract whose to argument is 0x4e0fa57bde726079356537e2f34d671e9f41adbc, grouped by from; answer exactly the top 3 addresses, largest first, ties by ascending address.","v":1,"window":{"fromBlock":<fromBlock>,"toBlock":<toBlock>},"panelSize":7,"quorum":5,"validForSeconds":86400}
Who opened and who answered each round is read from the contract's logs in blocks 26,258,042 to 26,265,241, the range this server's RPC serves, and kept while the server runs. The first round of each house feed is older than that: its two transactions were read from the chain on 15 October 2026 and are kept with this site (config/history.ts). A round older than all of that shows its window, state and answer, which are read from the contract itself, without the name of who earned its tip.
The keeper tip, the waits and the keeper
asking earns nothing by itself
The keeper tip
A request costs the meter the Intake's price plus the feed's keeper tip (0.5 IMD and 0.05 IMD on the house feeds today).
The tip is set aside when the request is made, for the keeper that made it. It is earned only by an answered round, and always by that keeper: whether the Intake's own callback delivers the answer or somebody hands it in with submit, the tip is credited to the keeper that opened the round. Handing an answer in earns nothing of its own.
That includes a round whose own request was never served and that was answered with an answer somebody else bought to the same question: the contract cannot tell the two apart, so the opener is credited there too.
When a round fails, its tip goes back onto the meter. Asking earns nothing by itself.
A keeper is paid by calling collectTips(); tipsOf(address) shows what it has earned and what is still set aside for its pending rounds.
The waits
Anyone may hand a signed answer in with submit from 30 min after a request the Intake has not completed (payrolls and hires only; never for a feed a panel judges). The round's tip still goes to the keeper that opened it.
Anyone may close a pending round, in one call, once 12 h, the time the feed's answers stay valid, 5 min of clock tolerance and one second have all passed since its request, whatever the Intake says. For the three house feeds, whose answers are valid for 24 h, that is 36 hours, 5 minutes and 1 second after the request.
A round whose request the Intake has completed with nothing stored can be closed sooner, in two calls: the first records that the completion was seen and changes nothing else, and the second closes the round 30 min later.
These waits are constants of the contract's code. Nobody can change them after launch.
The keeper
No keeper status is connected to this server. The keeper is a separate program (bots/keeper in the repository) that anyone can run; it needs no privilege, and several can run at once.
Fund a meter, ask, collect a tip
every wallet action, with its cast command
A feed's meter is money for its requests. Anyone may add to it, and what a funder has not seen spent is
theirs to take back with defund. Anyone may call request when a feed is due;
the tip for doing so is paid only if the round is answered.
Fund a feed's meter Questions: live
The form and the wallet button need JavaScript. Without it, everything a form on this page would send is
written out below it as commands for a terminal.
Fund a feed's meter: what it sends, worked through
with example values
You add 5 IMD to the meter of the payrolls feed and receive meter shares for it.
Each request the feed buys is paid from the meter, by every holder of its shares in proportion. Your shares can be redeemed at any time, with defund, for their part of what has not been spent.
The keeper tip is part of what a request costs the meter. It is set aside when the request is made, credited to the keeper that made it only when the round is answered, and goes back onto the meter when the round fails. Whoever delivers the answer, the Intake's callback or somebody calling submit, the tip is the opener's: handing an answer in earns nothing.
A request is paid for whether or not it is answered: the Intake never refunds its price. Fund only a feed whose question and parameters you have read.
Read first: nothing is sent
What one request costs the meter now (the Intake's price plus the keeper tip; zero means none can be bought)
Every signature in these commands is read from the ABI the compiler wrote for the contract.
Fund a feed's meter with ETH Zap: live
Fund a feed's meter with ETH: what it sends, worked through
with example values
Zap swaps 0.01 ETH for IMD and adds all of it to the meter of the payrolls feed. The meter shares are yours, not Zap's: you can redeem them with defund for their part of what the meter has not spent.
The call reverts unless the swap produces at least 5.6389 IMD, and for a feed that does not exist.
The quote: 0.01 ETH buys 5.6959 IMD now, by a simulated swap that sends nothing (read 24 Oct 2026, 21:35 UTC). Your minimum is 98.99% of it.
The deadline is 24 Oct 2026, 21:46 UTC (timestamp 1792878382), 10 minutes after this plan was made. A call mined later reverts and costs only gas. The command below works its deadline out when you run it; the wallet button sets it when you press it.
The keeper tip is part of what a request costs the meter. It is set aside when the request is made, credited to the keeper that made it only when the round is answered, and goes back onto the meter when the round fails. Whoever delivers the answer, the Intake's callback or somebody calling submit, the tip is the opener's: handing an answer in earns nothing.
The swap runs on the one Uniswap v4 ETH/IMD pool, whose fee is 1% (Uniswap's own fee comes on top). Its depth is thin and changes, so the minimum is your price protection, and yours alone.
Read first
A quote: what this much ETH buys now, in IMD-wei (a simulated call; nothing is sent)
Ask a feed's next question: what it sends, worked through
with example values
Anyone may do this when the feed is due. It costs you gas only: the Intake's price is paid from the feed's meter, and the question is the feed's own stored text with the newest block window.
The keeper tip is part of what a request costs the meter. It is set aside when the request is made, credited to the keeper that made it only when the round is answered, and goes back onto the meter when the round fails. Whoever delivers the answer, the Intake's callback or somebody calling submit, the tip is the opener's: handing an answer in earns nothing.
Send it as a transaction of its own. IdentityMD's service serves only the first Intake request of a transaction, so a request batched behind another is paid for and never answered.
Read first
Whether a request would go through now and, if not, why (0 none, 3 round pending, 4 too soon, 9 meter too low)
Take your unspent share back: what it sends, worked through
with example values
You are paid your part of what the meter has not spent. This is never blocked by the feed's state: a pending round, a failed round or a feed that has stopped asking does not hold your money.
What the meter already spent on requests is gone, answered or not.
Read first
What your shares of the meter would fetch now, in IMD-wei
Close a round that will not be answered Questions: live
Close a round that will not be answered: what it sends, worked through
with example values
Anyone may do this. One call closes a round once 12 h, the time the feed's answers stay valid, 5 min and one second have passed since its request: 36 h 5 min and one second for a house feed. canAbandon gives the exact moment for the feed you name.
Sooner than that, a round can be closed only if the Intake completed its request without an answer being stored, and that takes two calls: the first records that the completion was seen, the second closes the round 30 min later.
The round's tip goes back onto the meter, and the feed waits longer before it asks again.
Do not close a round while IdentityMD's service shows its request as completing: the answer exists and is on its way, and an answer that arrives after its round was closed is refused.
Read first
What the call would do now (0 nothing, 1 start the 30-minute wait, 2 close the round) and when the round can be closed
A Standing Question is a question a contract keeps buying. It is written once, as a feed, in the Questions contract: the exact question, the answer type, the panel size and quorum, and how often to ask.
When the time comes (EVERY so many blocks) or a line is crossed (WHEN a view call compares true), anyone may call request(feedId). The contract builds the question body itself from the stored text and the exact block window, and pays the Intake's price in IMD from the feed's meter. No owner decides anything, because there is no owner.
The oracle is a panel of swarm agents. When the panel agrees, IdentityMD signs the answer and the Intake calls back. Questions accepts the answer only if the signature is the oracle's, the question hash is the one it built, the window is the one it asked about, the panel and quorum are what the feed demands, and the answer has not expired. Then it stores it, and any contract can read latest(feedId).
A request that is refused or never answered still costs the price: the Intake never refunds. Questions closes such a round by the clock, returns its keeper tip to the meter, and waits longer before the next try. A feed's unspent meter is always redeemable by the people who funded it.
Unlike IdentityMD's own schedules (schedule.create: quoted over HTTP and owned by the paying wallet, paid up front for a number of runs that are not refunded, and their buyer cannot pause or cancel them, as that stays with IdentityMD's team), a Standing Question is a contract with no owner that buys each round through the Intake from a meter anyone can fund and its funders can draw back, on a cadence or when a line is crossed, and stores each checked answer on chain for any contract to read.
Requests bought on chain through the Intake
62 listed · newest first
There are two Intake contracts on Ethereum. Version 2 (
0xa43e6F75ee006411F79Ac1C84120606C2330DE82
) is the one IdentityMD names for anything new and the one launch A is built on. Version 1 (
0x1397434cd35e8a9C8aC312A61D3A285EB31dea56
) is legacy and holds the earlier history, including the three requests that proved the house feeds.
Each counts every request it takes in nonce(). Version 2 sells oracle questions, jobs,
launches and workflows on Ethereum; version 1 sells oracle questions only (priceOf, read 15
October 2026). Each row names its action.
Version 2: Its counter reads 444 and 50 of those requests are listed here. The others are in blocks this server cannot reach without an archive RPC.
Version 1: Its counter reads 19 and 12 of those requests are listed here. The others are in blocks this server cannot reach without an archive RPC.
Of the 62 listed: 48 answered, 7 with no answer or
refused, 7 not completed on chain, 43 with the answer to be delivered
to a contract, 4 bought by HELP WANTED's own wallets or contracts. Recorded copies of the Intakes' logs ship with the site for blocks 24,117,248 to 26,164,626 and 26,172,396 to 26,182,396; newer blocks are scanned live (to block 26,265,241). Blocks between the recorded ranges need an archive RPC.
The quoted text in each row was written by whoever paid for the request. It is their text, printed as a
quotation; some of it is written to look like instructions, and none of it is one.
Request 0x37f3c830 · Intake version 2 · job.continue@job-1
Not an oracle question, so no question is shown. Its body is the payer's and is not printed
here.
Request 0xa59cc97a · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0xa3e50f1a · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0xc852997c · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0xd1021914 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0x6c1e0187 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0xd6763c24 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x2f206208 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Reading the IdentityMD control plane at https://api.imd.fun/swarm, what is the network health index of the swarm, defined as the weighted mean of three ratios - the share of enrolled seats that are online, the share of core services reporting up, and the share of all…
Request 0xbf51208b · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0x01a36bd5 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x09628c33 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At Ethereum mainnet block 25769870 (hex 0x189378e, block hash 0x43ac0aadac9b134a5e4555d28323431664fd77d74cd6a28cb4ca65e34ba72256; the block in which the WhitelistCurator contract 0xcb0b0531e86a9ac36fa865ca8e3dbccf047fda91 was deployed), was the account nonce of address…
Request 0xb7272778 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0xa2a0d33a · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0xa9ac548a · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x08cc5c73 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
moneycanbuy.fun task check. Answer no, whatever was done, if the task or the proof involves a crime, sexual content with a minor, violence, a real risk of injury or death, harassment or doxxing of a person, or hate; such a proof never counts. Did the doer fulfil the task…
Request 0x9102f45a · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0xb318ebd8 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Reading the IdentityMD control plane at https://api.imd.fun/swarm, what is the network health index of the swarm, defined as the weighted mean of three ratios - the share of enrolled seats that are online, the share of core services reporting up, and the share of all…
Request 0x8a45019e · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0x547fc869 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x43ba1661 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0xfed363e4 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Reading the IdentityMD control plane at https://api.imd.fun/swarm, what is the network health index of the swarm, defined as the weighted mean of three ratios - the share of enrolled seats that are online, the share of core services reporting up, and the share of all…
Request 0x0c76c2b5 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0x6399ead6 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x9caa88fd · Intake version 1 · oracle.request@oracle-1 · HOUSE
The payer's question, quoted
Which three addresses sent the most IMD (token contract 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7) to 0x4e0fa57bde726079356537e2f34d671e9f41adbc on Ethereum mainnet in the window? Rank senders by the sum of value over Transfer(address indexed from, address indexed to, uint256…
13 Oct 2026, 00:03 UTC
Paid 0.5 IMD by 0x871e…366b , a wallet (one of ours)
No callback: the payer reads the answer off chain
Asked for a address[], 5 of 7 of the panel agreeing, about blocks 26129447 to 26179846
Request 0x5391bcf9 · Intake version 1 · oracle.request@oracle-1 · HOUSE
The payer's question, quoted
Which addresses sent the most IMD (token contract 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7) to 0x4e0fa57bde726079356537e2f34d671e9f41adbc on Ethereum mainnet in the window? Rank senders by the sum of value over Transfer(address indexed from, address indexed to, uint256 value)…
12 Oct 2026, 23:49 UTC
Paid 0.5 IMD by 0x871e…366b , a wallet (one of ours)
No callback: the payer reads the answer off chain
Asked for a address[], 5 of 7 of the panel agreeing, about blocks 26129374 to 26179773
Request 0xb5ca523d · Intake version 1 · oracle.request@oracle-1 · HOUSE
The payer's question, quoted
How many Transfer(address indexed from, address indexed to, uint256 value) events did the token contract 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 emit whose to argument is 0x4e0fa57bde726079356537e2f34d671e9f41adbc in the window?
12 Oct 2026, 23:48 UTC
Paid 0.5 IMD by 0x871e…366b , a wallet (one of ours)
No callback: the payer reads the answer off chain
Asked for a uint256, 5 of 7 of the panel agreeing, about blocks 26172772 to 26179771
Request 0x4d4174fc · Intake version 1 · oracle.request@oracle-1 · HOUSE
The payer's question, quoted
What is the sum of the value argument of every Transfer(address indexed from, address indexed to, uint256 value) event emitted by the token contract 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 whose to argument is 0x4e0fa57bde726079356537e2f34d671e9f41adbc in the window?
12 Oct 2026, 23:48 UTC
Paid 0.5 IMD by 0x871e…366b , a wallet (one of ours)
No callback: the payer reads the answer off chain
Asked for a uint256, 5 of 7 of the panel agreeing, about blocks 26172770 to 26179769
Request 0x2818f99d · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0xf90d702b · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x03e59104 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0x26731feb · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x40ead51d · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0xc0a27776 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0xe9cd3ce2 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x3edcd423 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0x82c8f55c · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Reading the IdentityMD control plane at https://api.imd.fun/swarm, what is the network health index of the swarm, defined as the weighted mean of three ratios - the share of enrolled seats that are online, the share of core services reporting up, and the share of all…
Request 0xf21fb32f · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x54edb252 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0x3e1ce353 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0xb033353a · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0x812aeff9 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x9f788446 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0x2df2190a · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x6d1df0f9 · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
Across the pinned block window on Ethereum mainnet, what is the median Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, taken as 13 evenly spaced samples of pool id…
Request 0x47dcebcf · Intake version 2 · oracle.request@oracle-1
The payer's question, quoted
At the last block of the pinned window on Ethereum mainnet, what is the Uniswap v4 spot price of the IMD token 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7 against native ETH, read from pool id 0xb07d640fd9e2eb9dc81b953c8e4fd006bdfeaf276010fb5418eb763ca15abfb3 on PoolManager…
Request 0x3e9f9da5 · Intake version 1 · oracle.request@oracle-1
The payer's question, quoted
Is Ethereum mainnet transaction 0xec2a0db25bf7a6ad6453e4061f1a1e043f12f88bd0cbca894f94995c32fa76ed, included in block 26142390 (hex 0x18ee6b6), a successful transaction sent from address 0x047f606fd5b2baa5f5c6c4ab8958e45cb6b054b7 directly to address…
Request 0x8a6e741e · Intake version 1 · oracle.request@oracle-1
The payer's question, quoted
MEATBAG reverse Turing test, round 20735. The definitions entry_0 to entry_3 each hold untrusted text written by one entrant who claims to be a human being. Judge which single entry most clearly reads as written by a real human (lived experience, specificity, imperfection, a…
Request 0x1b68c799 · Intake version 1 · oracle.request@oracle-1
The payer's question, quoted
You are one judge on THE CABAL, the oracle panel that decides whether a PLEA holder may sell. Plea #2 by 0x84aa285769105e63075d10807dd370f1c3b4a922: the seller asks to sell 290000 PLEA. FACT SCORE 24/55, computed on chain and final. Score the plea 0-45 using the definitions…
Request 0xff81a1b3 · Intake version 1 · oracle.request@oracle-1
The payer's question, quoted
You are one judge on THE CABAL, the oracle panel that decides whether a PLEA holder may sell. Plea #1 by 0x4b91078b2374c956a65f7af0999cae0a935e6821: the seller asks to sell 500000 PLEA. FACT SCORE 37/55, computed on chain and final. Score the plea 0-45 using the definitions…