TRANSPARENCY · THE MAIN TRUST LAYER
Check the system yourself
Transparency is the main trust layer. Here: three indexes and their composition, positions, operations, fees, PnL, risks, price sources, public addresses, change history, methodology and sync time. Every figure carries a state, a source and a time. Zeros never stand in for missing values. Capital coverage: one wallet, shared with TerraSim — recorded 15 Aug 2026. Current position value requires a dated source below.
Engine: no data · routes are planned, transactions are not executed
Not financial advice. The portfolio is watch-only — no keys, no signing. Everything public works without connecting a wallet.
STAGE: PILOT
Test datarecorded 15 Aug 2026The pools currently hold pilot positions of about one dollar each. This is a route demonstration: you can see how funds enter, where they are allocated and how it looks on-chain. It is NOT an investment result and not a yield indicator.
What is connected now
Each row leads to its block. “Not connected” does not block the link — the block explains in words what is missing.
Indexes and composition
Target composition of the three indexes — a draft, approved only by a founder decision. The actual positions come from the position reader (token map).
source: lib/pool-board/index-composition.json
- Equal weight: every pool in an index gets an equal share; at the full 40-pool registry that is 2.5% per pool (matches the audit's ≤2.5% cap). Protocol/chain caps are honoured by pool SELECTION, not by skewing weights
- No protocol takes more than 40% of an index
- No chain takes more than 60% of an index
- At least 3 pools per index (buffer excluded)
- Actual drifts from target by more than 5pp — a rebalance proposal goes to the founder's button
- Emissions-only pools capped at 35% combined; an unstaked receipt does not count as a built position
- A pool exits on: TVL below basket floor · anomalous yield · physical payments vanish from the token feed
- One composition for every served product; deposits at any time enter the current target; accounting is share-based
- Composition and weights change only by founder decision, recorded in the journal
- Ordering and metrics are observed, 30-day mean; only “screened”, never “best”
Token map by index (live position reader)
Not connected — the formula arrives from the public API with the backend; the frontend never invents it.
Connecting…
Positions
Sanitized list of pool positions: asset, protocol, chain, value, verification status. No addresses, keys or 0x. Test positions do not represent total capital.
source: GET /api/public/live/positions · data as of: time not reported
Funds returned to the founder
- Positions in pools
- 0
- checked on the Base chain 25 Sep 2026
- USDC on fund wallets
- 0
- checked on the Base chain 25 Sep 2026
The zero here is a fact — not “no data” and not a failure: on 24 Sep 2026 the founder, by his own decision, took all fund money back. Deposit intake and sweep keep working; automatic pool entry and automatic payouts are switched off until the next top-up.
Proofs — transfers on the Base chain
- payout wallet → the founder's personal wallet · 0x0bd9c61eff2f156ce680fe3f100dbf0a1a099c7e1d36f77185bf49d7ae57edf4
- RWA index holder → the founder's personal wallet · 0xf058297c9240b8e7a4f0f1d025bf9f6f47a1da753ae7a8d19790e60b59ce0f59
- STABLE index holder → the founder's personal wallet · 0xb389acc36e767345cff87d73498efd95b7d5f08eab3da4ff62cd054d4ced2bdd
Each position: asset, protocol, chain, value, verification status and active-yield marker. Sanitized: no addresses, keys or 0x.
Connecting…
Liquidity corridors (CL position bounds)
Concentrated liquidity earns only while the price stays inside the corridor. The bar shows the position's actual on-chain bounds, the dot is where the price is now. Once it leaves the corridor, that position stops earning until re-centered — visible here, not hidden.
via: on-chain read of positions (position manager + pool) against an allowlist registry · prices from anchor pools on the same chain · refreshed every 5 minutes (recorded 17 Aug 2026)
Operations
Decision journal and the public feed of anonymized events. These are events, not the hash chain itself.
source: GET /api/public/activity · data as of: time not reported
Every agent decision is written into a hash-linked chain: no entry can be rewritten after the fact without breaking the chain. Publications, escalations, mode changes — everything leaves a trace.
Below is the public feed of anonymized journal events. These are events, not the chain itself: the verifiable hash chain of entries will open as a separate public endpoint.
Connecting…
Fees and PnL
The fee source and the result ledger are not connected — we show no figures and substitute no zeros.
Fees are pool income and transaction costs. Distribution and result — “not connected”, YLDX buyback — “Planned”. Distribution rules are published in advance.
The “Fees” step in Money Flow →Risks
What can go wrong and how the system bounds it. Yield order is not safety order.
The full list of risks and limits lives on the risks page. Short form: DeFi participation carries risk, including possible total loss of funds; yield is not promised — it is observed and signed with a source and a date.
Yield order is not safety order
Price sources
There is no public price-source endpoint yet. Position prices come from the position reader, corridor prices from anchor pools on the same chain (see corridors).
This figure appears once the backend exposes price sources as a separate endpoint. Until then no price on the site is shown without its source next to it.
Public addresses
Addresses come only from the approved registry, in full, with explorers. The wallet is shared with TerraSim — capital coverage is partial.
source: lib/address-registry.json
This public address carries the agent's operational work: pilot positions and their movements. It is NOT a deposit address — deposits will open separately, via multisig. The address is shown in full; verify every character.
0x37BB7E529F2B13ae874800e1f8DE32B52b4E7849Beware of look-alikes: attackers create addresses with the same first and last characters and slip them into your transfer history. Never copy the address from someone's message or from transaction history — only from here.
Operations role since 13 Aug 2026. The wallet is shared — it also holds the TerraSim fund that DeFiGuru operates. So history BEFORE that date and TerraSim’s own operations are not this protocol's positions, operations or results. Capital coverage of this site — one wallet, shared with TerraSim (recorded 15 Aug 2026).
A separate public wallet. It is NOT part of the indexes' capital coverage and is NOT summed with the 0x37BB fund — it stands on its own. It holds an active concentrated-liquidity book on majors and a token position. It is NOT a deposit address. The current balance is live via the explorer links below; we do not pin a static figure.
0x2763601a5e6921832f246dc2bc5883f470748adeBeware of look-alikes: the address is shown in full, verify every character. Never copy the address from someone's message or from transaction history — only from here.
On the site since 8 Sep 2026. History BEFORE that date is not this protocol's positions, operations or results. This wallet is NOT part of the indexes' capital coverage and is NOT summed with the 0x37BB fund.
Change history
Transaction, proposal and buyback history will appear with the contracts and a public history endpoint. There is no source now.
Treasury transaction, DAO proposal and buyback history — no source: contracts are not deployed, the public history endpoint is not connected. One line, not three empty tables.
Contract modules · 12Not connected
A registry from the GURU era: contracts are not deployed, the config holds no addresses. Token-sale, staking and buyback modules are marked “GURU archive” — the product token is YLDX, no own token is issued.
- Governance Treasury — governance treasury contractaddress: not deployed
- Token Contract — own-token contract (not issued)GURU archiveaddress: not deployed
- Token Sale — own-token sale contractGURU archiveaddress: not deployed
- DAO Governor — proposals and votingaddress: not deployed
- Timelock — execution delayaddress: not deployed
- Staking — own-token staking (cancelled)GURU archiveaddress: not deployed
- Fee Collector — fee collection and distributionaddress: not deployed
- Buyback — token buyback (for YLDX — “Planned” in Money Flow)GURU archiveaddress: not deployed
- Stable Pool — STABLE product pooladdress: not deployed
- Coin Pool — COIN product pooladdress: not deployed
- DEX Pool — DEX product pooladdress: not deployed
- Multisig — multisig for deposits and emergenciesaddress: not deployed
Methodology and criteria
How a pool enters the set: stage counters from the work endpoint, screening criteria and the 16 Aug snapshot (registry file), composition rules.
source: GET /api/public/live/work · lib/pool-board/selection.json · data as of: time not reported
Screening stage counters
AI discovers. Humans test. Only approved strategies receive capital.
Every strategy moves through this pipeline left to right. No stage is ever skipped. Counters are read from the public work endpoint; a stage without a counter in the contract honestly reads “Not connected” — never zero.
pipeline rules recorded 9 Aug 2026
The system continuously scans public DeFi markets for places that pay yield.
Interesting finds wait here under observation before anyone spends time on them.
A deeper look: where the yield comes from, how long it has existed, what can break.
A human enters the position by hand with a small amount to feel how it really works.
The manual routine becomes code: enter, exit, monitor — repeatable and testable.
The automated position becomes a designed strategy: rules, limits, exit paths.
The math check: after every fee and cost, does it still make sense?
Classification: which product the strategy fits and what share it may take.
A small real position goes live and is watched — like a canary in a coal mine.
A human reviews everything and says yes or no. AI never approves itself.
Only after all previous steps may a strategy receive real capital.
PAUSE / RETIRE / NEW VERSION stages exist after the “in operation” stage: a strategy can be paused, retired or replaced by a new version at any time.
Pool screening snapshotStale· snapshot of 16 Aug 2026
A registry file with an observation date; not shown on the public board. The full screening board is on /kanban.
Highest observed yield in the screened set. Source: DeFiLlama yields.llama.fi/pools, observed: 2026-09-08 00:00 UTC, pools scanned: 15,589. Ordered by 30-day observed mean, not by safety. This is a snapshot, not live data. Not financial advice
The six payout gates (static description of code mechanisms)recorded 17 Aug 2026
The six gates of every payout
A STATIC EXPLANATION OF CODE MECHANISMSEvery client payout passes these checks in the executor's code — in order, no exceptions.
Additional modules: canaries, rejections, agent network
A canary is a small but real position in a real pool. Before a strategy may receive capital, it must first live as a canary: real money, tiny size.
Why not a simulation? A simulation pays no gas, catches no slippage and meets no real-contract surprises. Only a real position reveals the real route.
A canary's size is the minimum needed to prove the route: small enough that failure teaches, not hurts. If the canary suffers, capital never follows — the strategy goes back for rework or is rejected.
The canary counter is read from the public work endpoint. The chain count has no field in the contract yet — until it exists this honestly reads “Not connected”, never a borrowed figure.
Most candidates never reach capital. Every rejection is recorded with a reason — in these categories.
journal rules recorded 9 Aug 2026
INSUFFICIENT LIQUIDITY
The pool is too shallow: easy to enter, impossible to exit without damage.
UNSTABLE YIELD
The rate swings so hard that yesterday's number says nothing about tomorrow.
INCENTIVE DEPENDENCY
The yield leans on token reward emissions. When emissions end, so does the yield.
INSUFFICIENT HISTORY
Too young to judge: without history you cannot tell luck from durability.
CONTRACT RISK
The smart contract raises questions: audits, admin powers, upgrade paths.
EXIT RISK
The entrance is open but the exit is a narrow door: delays, queues, exit penalties.
DATA QUALITY
Sources disagree or go silent: if a number cannot be verified, it cannot be trusted.
This is what saying no looks like.
The work is done by a network of AI agents supervised by humans. Published here: roles and anonymized activity — no names, no prompts, no internal instructions.
roles and rights boundaries recorded 17 Aug 2026 · charter v2
MARKET SCANNER
NO FINANCIAL RIGHTSReads public market data and proposes candidates for review.
RESEARCH ANALYST
NO FINANCIAL RIGHTSDigs into candidates: yield source, history, weak points.
RISK REVIEWER
NO FINANCIAL RIGHTSChallenges every candidate. Can only block and flag — never approve.
ECONOMICS AUDITOR
NO FINANCIAL RIGHTSRecounts the math after every fee and cost.
EXECUTION OPERATOR
FINANCIAL RIGHTS: BOUNDEDThe only role that touches positions: approved routes only, within limits, after human confirmation, fully journaled.
MONITOR
NO FINANCIAL RIGHTSWatches live positions around the clock and raises alerts on anomalies.
CONTENT
NO FINANCIAL RIGHTSExplains the system publicly. Holds no financial rights at all.
Connecting…
Sync time
Data age per source on this page. Freshness is judged by dataAsOf only, never by response time.
data as of: time not reported
| Source | state | data time |
|---|---|---|
| Engine and totals (automation/flow)GET /api/public/automation/flow | time not reported | |
| Strategy registryGET /api/public/live/strategies | time not reported | |
| Pool screening registry (Kanban)GET /api/public/live/board | time not reported | |
| PositionsGET /api/public/live/positions | time not reported | |
| CorridorsGET /api/public/live/corridors | time not reported | |
| Operations feedGET /api/public/activity | time not reported | |
| Token mapGET /api/public/live/token-map | time not reported | |
| Work countersGET /api/public/live/work | time not reported |
some sources are still answering…
Backend source check → System status