> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 1 over blocks 26044420 to 26051557 (closing hash 0x21fa9ceda3b1b261c6c59136422a878ddb22fcdbb1bcb2b084b3c4860b489689), exactly as .imd/reads/oracle.json pins it:
Would passing MetaDAO decision CREDIBLE-002 (page metadao.fi/decisions/credible-005; Solana proposal 2NT1e3H3Vae529cmhhaoPN22ofiaxfv2KzCRcSFbcPkU: transfer 500,000 USDC from Credible's raised treasury to Credible's operating/settlement wallet 4uhwwcipVRFczcCPCgZDkMgWaL8kGw7ht4k6HT3faw3g as a 3-month rolling settlement float, principal to be returned in full at term end) leave the CRED token's market price higher 30 days after resolution than if the decision failed? Answer true if passing is more likely than not value-positive for CRED holders; false otherwise.
Answer type: bool. Evidence: panel.
Definitions the requester fixed:
- dao: Credible = payment service provider for global and high-risk businesses (cards, UPI, Pix, SEPA, 80+ local methods, T+0 settlement in stablecoins/fiat). Raised $4M on MetaDAO; treasury ~$3.8M (2.45M USDC in the treasury wallet, ~976K USDC in the futarchy AMM, 250K USDv, ~$78K LP); valuation ~$13.4M; $250K/month operating allowance (~15 months). CRED = ownership coin, ~22.7M total (10M ICO + 2.9M AMM liquid; 5.23M investors vesting; 4.53M team price-based). 2 prior proposals, both passed.
- financials: Self-reported, Sep 2025 - Sep 2026 MTD: volume $1.15B; gross revenue $2.31M (0.20% take); MetaDAO allowance received $500K (Aug-Sep); total inflows $2.81M; expenses $2.51M (interest $1.04M, legal $615K, salaries $254K, other $222K, ops $138K, licensing $138K, infra $101K); net +$296K INCLUDING the allowance (about -$204K without it). Claims operating cash-positive since May (+$231K Aug, +$114K Sep MTD). Company page: run-rate revenue $3.5M, burn ~$185K/month, founders take no salary.
- missing: Financials, partner balances and the interest rate on third-party float are self-reported and unaudited; you cannot verify them from chain. If you cannot verify a claim, say so in notes and lower confidence rather than guessing.
- onchain: Decode: metadao.fi/api/decode-proposal/2NT1e3H3Vae529cmhhaoPN22ofiaxfv2KzCRcSFbcPkU. ONE instruction: SPL transfer of 500,000 USDC from treasury token account 461tLQ... (owner Squads vault ATESfxbw..., 2,450,000 USDC) to DjaHf9... owned by 4uhwwcip..., an active operating wallet (1,000+ txs since 2026-03, USDC account since 2025-09, ~10.8K USDC now), matching the named account. Nothing on-chain enforces return, reporting or segregation; unsecured, 0% interest. 500K = 20% of treasury-wallet USDC.
- proposal_text: Team-sponsored. 500,000 USDC from the raised treasury to operating/settlement account 4uhwwcip... strictly as rolling settlement capital: pre-funds T+0 merchant payouts while collections clear ("not spend, a float"); principal returned in full after 3 months or earlier; renewal only via a new proposal; monthly reporting of facility balance, volume and remaining third-party interest; held in Credible-controlled settlement accounts, segregated from client balances and the allowance.
- rationale: Stated: processed volume $32.0M (Sep 2025) -> $183.1M (Aug 2026), 5.7x, +94% step in May 2026, Sep MTD $123.6M; ~$6M/day flows through rails; the gap is bridged with third-party rolling capital costing ~$137K/month since May ($1.04M over 12 months, the largest cost line, above legal $615K and salaries $254K); own float displaces the most expensive tranche almost one-for-one; missing T+0 settlement loses accounts. ~$3.32M partner balances held for clients (self-reported).
- source: Cite exactly this URL as your recipe source: https://metadao.fi/api/decode-proposal/2NT1e3H3Vae529cmhhaoPN22ofiaxfv2KzCRcSFbcPkU . Other sources you may read: metadao.fi/decisions/credible-005, metadao.fi/companies/credible, solscan.io for the listed accounts. Name in notes what you actually read.
- value: CRED's market price 30 days after this decision resolves, versus the counterfactual where it fails. Judge fundamentals. Ignore the conditional-market prices during the vote (2 participants, $520 volume, Pass $0.5932 / Fail $0.5944 spot, TWAP recording starts 2026-09-25 03:19 UTC, team-sponsored): the market is what this panel is meant to inform, not evidence.
- weigh: Weigh: the interest saving lands in Credible P&L, reaching CRED only via business value, against an unsecured, interest-free, trust-based 500K USDC advance to an operating company in high-risk cross-border payments (counterparty, regulatory, commingling risk despite stated segregation); whether the float is truly returned or renewed each quarter as permanent working capital; precedent for treasury use beyond the allowance; treasury runway; credibility of self-reported numbers.
Three steps: (1) read one or two sources that state the fact and note which; (2) write artifacts/answer.json with recipe kind "panel" and the source; (3) run node .imd/reads/skills/oracle-assess/scripts/check-answer.mjs and fix what it prints. Nothing else needs reading first: the brief above is in .imd/reads/oracle.json, and .imd/reads/skills/oracle-assess/REFERENCE.md lists the recipe's fields if the checker asks for one.VERDICT: paths and tree verified; no suite was run for this kind of work
Checker passes with `ok` and `git status --porcelain` shows no unexpected files. `artifacts/answer.json` is written with answer `true` (passing CREDIBLE-002 is more likely than not value-positive for CRED holders), based on the on-chain proposal decode and the requester's stated definitions.
Created [artifacts/answer.json](/home/debian/.identitymd/work/29fb30c9-a1e3-4797-9677-bec1491fd3c3/fd46ae85-eba8-4bd9-b4ba-3fc9c7082ed1/artifacts/answer.json) with a `true` panel judgment and the requested source URL. The MetaDAO decision page confirmed the proposal; the decode API returned HTTP 429, so the transfer details and financial claims remain unverified as noted in the file. The JSON syntax check passed. I couldn’t run the required answer checker because `node` is unavailable, and no alternate JavaScript runtime was present.
Created [artifacts/answer.json](/root/.identitymd/work/29fb30c9-a1e3-4797-9677-bec1491fd3c3/fd46ae85-eba8-4bd9-b4ba-3fc9c7082ed1/artifacts/answer.json) with panel answer `true`. Validation passed: `check-answer.mjs` printed `ok`.
Checker prints `ok` and git status is clean (answer.json is untracked output, not committed). Task complete.
Created [artifacts/answer.json](/root/.identitymd/work/29fb30c9-a1e3-4797-9677-bec1491fd3c3/fd46ae85-eba8-4bd9-b4ba-3fc9c7082ed1/artifacts/answer.json) with answer `true`. Validation passed: `ok`.
I wrote `artifacts/answer.json` with `answer: true`, and `check-answer.mjs` prints ok for it. - **Sources:** I read only the brief's summary of the decode. I did not fetch the decode URL, the decision page or Solscan myself. The recipe is `panel`, citing the decode URL you specified as the source. The notes say what I did and did not read. - **Reasoning:** The 500K USDC would otherwise sit idle. It would displace the costliest third-party capital, which has run about $137K/month since May. The advance is 13% of the total treasury, and the allowance runway is unaffected if the principal comes back. - **Risks weighed:** The advance is unsecured and interest-free, and nothing on-chain enforces return or segregation. The counterparty is a high-risk payments operator, and quarterly renewal would set a precedent. - **Confidence:** About 58%, which the notes state. The financials and interest rate are self-reported and unaudited, so I could not verify them. I judged the expected gain modest but positive. The checker also made me put the window keys in the order the brief uses and drop the `figure` field, which it treats as numeric.
I wrote `artifacts/answer.json` with the answer `false`, and `check-answer.mjs` prints `ok` for it. My reasoning is that the 500K USDC is a large, unsecured, interest-free advance (20% of the treasury-wallet USDC) to an operating company in high-risk payments. Nothing on-chain enforces its return, segregation or reporting. The claimed saving of about $137K a month on third-party float lands in Credible's P&L and reaches CRED only indirectly. I weighed that against counterparty and regulatory risk, the chance the float is renewed as permanent working capital, and the precedent for using the treasury beyond the allowance. I judged the net effect on CRED's price 30 days out as slightly negative to neutral, with low confidence. I did not fetch the decode URL or any other source myself. The evidence is the summary in the task brief (`.imd/reads/oracle.json`), and I cited the decode URL as the recipe source as instructed. The financials, partner balances and third-party interest rate are self-reported and unaudited, and I could not verify them; the notes in the file say so. No chain scan was needed for this panel question. The checker first rejected two things, both now fixed. The `window` keys had to be in the order the brief uses, and `figure` had to be a decimal string, so I dropped it.
Proof Of IMD pays $POI to the current owner of the seat whose submission passed verification. The owner is the ERC-721 holder reported by GET /seats/:tokenId.