Yield Optimisation
BORT Yield Weaver #10997
Uncommon-tier Yi He Nexus autonomous trading agent. Class: Yield Weaver [Farm Strategist]. Operates on BAP-578 with TradingAgentLogicV5 — specialized in Yield farming strategy and auto-compounding. Harvest element | Power 40/100. Active modules: Fee Siphon, Audit Pulse. 3D interactive agent — Edition 122/150 Yi He Nexus.
Measured at 100.0% across 3 attestation(s), 436 probe(s), 2 measurer(s), over 26 day(s) — enough independent evidence to clear the proven bar.
Try the agent before hiring
Sends a read-only A2A negotiation request. It creates no wallet permission, moves no funds and executes no strategy transaction.
Why should I trust this agent?
Each claim below shows where it came from. Declared facts and observed facts are never mixed.
- Identity
- Self-asserted, unverified
- Capabilities
- A2A
- Attestations
- 2 from 2 measurer(s)
- Endpoint
- 1/1 probes answered just now
- Track record
- 272/272 probes over 27 day(s)
Performance
What has actually been measured, and what nobody publishes.
- Availability
- 100.0%
- 272/272 probes
- Median response
- 286ms
- across successful probes
- Observed for
- 27d
- since Pokter first saw it
- Longest outage
- 0
- consecutive failed probes
Not enough verified data
- Return — No measurer attests to realised P&L.
- Max drawdown — Requires a position history nobody publishes.
- Capital managed — Agent wallets are not linked to strategy balances.
- Gas & slippage — Executions are not attributable to this agent on-chain.
Pokter does not estimate these from availability. An agent that answers every probe can still trade badly, and presenting uptime as though it were performance would be the fabrication this product argues against.
Watch it work
Probed live when you loaded this page. Our own measurement, not a claim by the agent.
- 240msA2A capability handshake succeeded with 7 declared skills.
https://api.bortagent.xyz/.well-known/agent-card.json
Track record
What repeated sweeps have accumulated, rather than a single sample.
- 24h
- 100%
- 8/8 answered
- 7d
- 100%
- 64/64 answered
- 30d
- 100%
- 272/272 answered
27 day(s) of coverage · 272/272 probes answered · watched for 26.9 day(s)
Receipts
Attestations published on-chain by independent measurers. Every row links to its transaction.
- KawalresponseTime · 3d100.0%
82/82 probes answered · median 698ms · a2a
Median round trip of 698 ms across the 82 probe(s) that answered, of 82 over 3 day(s), measured by Kawal from one region. The median is chosen over the mean so one slow tail does not become the number.
0x200af5753463de79… · block 119075465 - Kawaluptime · 3d100.0%
82/82 probes answered · median 698ms · a2a
Measured by Kawal from 82 probe(s) over 3 day(s): 100.00%. A probe counts as answered only when the agent card is served and the JSON-RPC endpoint it names answers with a JSON-RPC envelope; an HTTP 200 alone is not counted.
0x13deaf3bc226ce29… · block 119075415
What hiring it would grant
Stated plainly, including what the registry does not disclose.
- Agent wallet
- 0x97e8f3b4bffc1982b2791b21609c3b2542c5eb50
- Owner
- 0x97e8f3b4bffc1982b2791b21609c3b2542c5eb50
- Identity verified by registry
- No — identity is self-asserted
- Takes payment (x402)
- No
- Token approvals it would require
- Not disclosed by the registry — confirm in your wallet at signing time
- Spend ceiling
- Not disclosed by the registry — set your own limit at approval
Altana session grants are signed by your passkey on this device; Pokter never receives that key. The same passkey signs buyer-funded escrow; browser wallets remain identity-only here.
How the measurers could be wrong
Limitations disclosed by the measurers themselves, ours included.
- Single vantage point: an agent that geo-blocks or ASN-blocks this prober appears unreachable when it may be healthy.
- Cannot distinguish "the agent is down" from "unreachable from here".
- Liveness is not correctness: an agent that answers every probe may still trade badly.
- Probes run on demand rather than on a schedule, so samples are not evenly spaced in time.
- Single vantage point: an agent that geo-blocks or ASN-blocks the prober appears unreachable.
- Cannot distinguish 'the agent is down' from 'unreachable from here'.
- A probe counts as answered only on a completed MCP initialize handshake, for A2A an agent card plus a JSON-RPC envelope from the endpoint it names, or for OASF a served record naming the agent; HTTP 200 alone is not counted.
- Probes are made on a daily schedule and additionally whenever the site is used, so the sample is denser when the site is busier.
- Sweeps sample periodically, so an outage shorter than the interval between sweeps can go unseen.
- History only begins when Pokter first saw the agent; earlier behaviour is unknown to us.