Product notes · reviewed source

Four roles. Different levels of proof.

The repository explores yield selection, arbitrage, risk thresholds, and portfolio rebalancing. The page below uses only schematic examples: it does not fetch a market, read a wallet, or submit a transaction.

ScopeSource snapshotNot a live financial service

Illustrative decision path

  1. Inputs
  2. Candidate model
  3. Risk markers
  4. Contract boundary
  5. Observed state

One explanatory path across several independent prototypes. It does not imply end-to-end deployment.

01 / Candidate selection

Yield optimizer

Prototype

Strategy selection appears in the Node service and a Solidity contract prototype. The original code explores protocol, asset, reported yield, and risk fields; this website does not invent a current APY or rank real offers.

Illustrative comparisonNo live offer data

Candidate fields, without a rate

Candidate A selected. This is a conceptual candidate, not a current protocol offer or yield figure.

What the source contains

A yield-optimizer service, a contract interface, and strategy-shaped data.

LokiAi/backend/services/agents/yield-optimizer-agent.jsloki-contracts/contracts/YieldOptimizer.sol

What it does not prove

That a protocol is reachable, that a quote is current, that an APY is realized, or that a transaction succeeded.

02 / Route comparison

Arbitrage bot

Simulated

The browser-side model describes two route legs and an execution boundary. Its simulated result is not a live price, executable quote, or evidence of net profitability after fees and slippage.

Schematic pathIllustrative only

Compare the route shape

Two schematic routes. The drawing contains no live prices or execution proof.

What the source contains

An arbitrage model and a Solidity contract file with mock-oriented execution paths.

LokiAi/src/services/ml-models/arbitrage-bot-model.tsloki-contracts/contracts/ArbitrageBot.sol

What remains unverified

External liquidity, block inclusion, fees, slippage, front-running resistance, and a settled transaction.

03 / Threshold review

Risk manager

Prototype

The current contract source defines score markers at 700 and 900. The control is a local teaching aid that lets you inspect those constants; it does not evaluate an account or enforce a safety boundary.

Illustrative sample onlyRiskManager.sol source constants

Move a sample across the markers

0700 · warning marker900 · upper marker1000

Illustrative value 640 / 1000: below the source warning marker. No wallet data is read and no action occurs.

What the source contains

A Solidity module with threshold-oriented score and state logic.

loki-contracts/contracts/RiskManager.sol

What a threshold cannot establish

Model validity, oracle quality, coverage of every risk, or a guarantee that loss can be prevented. It is not an audit.

04 / Allocation shape

Portfolio rebalancer

Simulated

The Python workflow compares current and target allocation maps, then uses a simulated execution path. This graphic is a pattern comparison only: no wallet, balances, token amounts, or orders are involved.

Allocation patternNo account data

A proposal is not a transfer

Schematic observed pattern shown. It is not connected to a wallet or live portfolio.

What the source contains

A Python engine for allocation deviation and candidate rebalance recommendations, plus a contract prototype.

portfolio_rebalancer/rebalance_engine.pyloki-contracts/contracts/PortfolioRebalancer.sol

What is not represented here

A signed order, bridge transfer, live balance, tax outcome, or suitability recommendation.

Wallet and network context

The four roles sit among other unfinished boundaries.

These neighboring modules matter to the system story, but their presence does not imply a complete, connected financial product.

Trust boundary

A prototype label is part of the product.

Do not treat this website or repository as an offer, recommendation, performance record, audited security system, or production-ready financial service.