BTC PUMP-1H▲ P=0.866 ETH-LIQ-1H▼ P=0.183 SOL PUMP-4H▲ P=0.621 FUNDING FLIP▼ short MEV SANDWICH F10.942 RUG DETECTOR AUC0.910 XRP REGIMERANGING · 0.66 DEPEG-USDC 6H0.041 WHALE FLOWACCUMULATION 0.71 BTC PUMP-1H▲ P=0.866 ETH-LIQ-1H▼ P=0.183 SOL PUMP-4H▲ P=0.621 FUNDING FLIP▼ short MEV SANDWICH F10.942 RUG DETECTOR AUC0.910 XRP REGIMERANGING · 0.66 DEPEG-USDC 6H0.041 WHALE FLOWACCUMULATION 0.71
GL1F First decentralized AI · Mainnet
Open Studio →
v1.0 · the first truly decentralized ai

The first truly decentralized AI lives on Genesis L1.

GL1F is a no-code, browser-only AI studio that trains gradient-boosted tree models on your machine, mints them as ERC-721 AI Model NFTs on GenesisL1 mainnet, and runs deterministic AI inference directly inside smart contracts — for free, by tip, or by paid subscription. No SaaS. No oracle. No company in the middle.

Decentralized AI No install No code Mainnet only ERC-721 AI NFTs EIP-712 gated Permissionless
LIVE · MAINNET root · all-features split · rsi < 32.4 leaf · p(pump)=0.87
0
Install steps
4
AI task types
3
Monetization modes
100%
On-chain inference
Manifesto

What "decentralized AI" actually means.

Most projects calling themselves "decentralized AI" are SaaS with a token glued on: weights live on a private server, inference is an HTTP call, and the chain only sees a payment. That isn't decentralized AI — that's a paywall.

GL1F is the first system where every part of the AI lifecycle is decentralized:

LayerGL1F"Decentralized AI" SaaS
trainingbrowser / your machinetheir gpu cluster
datanever leaves your deviceuploaded to them
weightson-chain bytes (GL1C)private server
inferenceEVM opcodes · deterministichttps api
identitykeccak256(model)"v3-final-final"
monetizationsmart contract · ERC-721stripe
kill switchnone — chain is the hosttheir devops team
01 / The problem

Crypto AI is a black box.

Every quant claims a 70% hit-rate. Every "AI trading bot" promises edge. None of them can prove it. The models are private, the backtests are private, the signals arrive without provenance, and "mint a prediction" doesn't exist on any chain.

× Unverifiable

You can't audit a Discord bot's brain. An "AI signal" arrives — was the model overfit yesterday? Retrained on the answer? You'll never know.

× Unowned

You can't license an AI model. You can't transfer one. You can't earn royalties on inference. The asset class doesn't exist yet.

× Off-chain only

Smart contracts cannot call XGBoost. AI predictions live in centralized APIs that vanish, rate-limit, or lie. Trust required.

× Code-required

Even if you can train an AI model, deploying it needs Python, Docker, an inference server, an API gateway, monitoring. Most traders just want to drag a CSV.

02 / The AI studio

One AI studio. Three compute paths. All driven from the browser.

The GL1F AI studio is a static web application that opens at gl1f.com and runs entirely in your browser. AI training happens locally; deployment uses your wallet. No code is required, no install is required. For datasets larger than browser memory, GL1F supplies optional local Python and C++ servers that you spin up on your own machine — but you keep using the same browser studio UI. Only the compute backend changes.

Default · in-browser 01

Sandbox

// wasm
  • runtimeWASM + WebWorker
  • installnone — open URL
  • dataset cap~100k rows
  • UXdrag-and-drop CSV
  • output.gl1f bytes
  • use caseprototyping
Optional · local server 02

Research

// python · supplied
  • runtimeNumPy / pyarrow
  • installlocal server, browser UI
  • dataset cap~10M rows
  • UXsame browser studio
  • output.gl1f bytes
  • use casefeature R&D
Optional · local server 03

Forge

// c++ · supplied
  • runtimeSIMD · OpenMP
  • installlocal server, browser UI
  • dataset cap1B+ rows
  • UXsame browser studio
  • output.gl1f (mint-ready)
  • use casefinal training
i

The studio UI is identical in all three modes.

You always interact with GL1F through the browser at gl1f.com — drag CSVs, pick features, set hyperparameters, watch metrics, mint NFTs. The Python and C++ "trainers" are local servers GL1F supplies that run on your own machine over localhost, and the studio talks to them when you need more compute. Datasets stay on your machine. Wallet stays in your browser. No SaaS, no upload to a third party, no telemetry.

browser/wasm in-tab WebWorker · default localhost:8088 python server (supplied) localhost:8089 c++ server (supplied) browser studio (gl1f.com) Dataset · Training Local preview · Mint no-code UI · same in all 3 modes .gl1f bytes v1 (scalar) / v2 (vector) GenesisL1 mainnet chainId = 29 ModelStore (GL1C) ModelRegistry ModelNFT (ERC-721) ForestRuntime ModelMarketplace FIG.01 — STUDIO → BYTES → CHAIN · ALWAYS BROWSER UI datasets and wallet keys never leave the user's machine.
03 / The algorithm · AI primitive

The AI primitive for chains: weak guesses, boosted strong.

GL1F is a gradient boosting machine over fixed-depth decision trees — the most successful tabular AI architecture of the last decade, and the only one whose inference is cheap and deterministic enough to live inside a smart contract. Each tree fits the residual error of the trees before it. Predictions are the sum of every tree's leaf value, passed through a link function — logistic for binary, softmax for multiclass, sigmoid-per-label for multilabel, identity for regression.

Trees are interpretable, fast, and — critically for on-chain AI — deterministic integer math after quantisation. Thresholds and leaf values are stored as int32; features are packed as int32 LE at scale scaleQ. No floats. No GPU drift. Same input, same byte-exact output, on every node, every block, forever.

PropertyGL1F
weak learnercomplete binary tree, depth ≤ 12
quantisationint32 thresholds · int32 leaves
format · scalarGL1F v1 (regression / binary)
format · vectorGL1F v2 (multiclass / multilabel)
typical config250 trees · depth 4 · lr 0.05
on-chain costO(n_trees · depth) bytecode reads
04 / AI task types

Four AI tasks. One studio.

GL1F covers the full GBDT taxonomy supported by the studio. The task is selected on the Dataset tab; everything downstream — loss, link, label encoding, output dimensionality — adapts automatically. Binary classification gets the focus in the rest of this deck because, in crypto, almost every actionable AI question reduces to yes or no.

04.1

Regression

→ continuous value · ŷ ∈ ℝ

Predict a number. Squared-error loss. Identity link. The label column must be numeric; non-finite rows are dropped automatically.

Crypto example ETH realised volatility over the next 4 hours. Target: σ₄ₕ
format · GL1F v1 (scalar)
★ Focus · 04.2

Binary
classification

→ probability ∈ [0, 1]

Predict yes/no. Logistic loss, sigmoid link. You pick which label value is class 0 and which is class 1; rows with other labels are dropped. Output is calibrated; threshold at 0.5 (or wherever your edge lives).

Crypto example Will BTC's next 1h candle close green? Target: I[r₁ₕ > 0]
format · GL1F v1 (scalar)
04.3

Multiclass
classification

→ softmax over K classes

K mutually exclusive outcomes (K ≥ 2). Softmax cross-entropy loss. K trees per boosting round, stored class-major in the file. Returns a probability vector summing to 1.

Crypto example Market regime: trend-up / trend-down / chop / squeeze. K = 4 classes
format · GL1F v2 (vector)
04.4

Multilabel
classification

→ L independent sigmoids

L labels (L ≥ 2), each a separate yes/no. Independent sigmoids per label. Each row may have any combination of labels active. Per-label positive weights handle imbalance.

Crypto example Token risk flags: low-liquidity / unlocked-supply / dev-active / honeypot. L = 4 labels, any subset
format · GL1F v2 (vector)
05 / Binary classification — focus

Yes or no. The most useful question in crypto.

Half of the alpha in this market reduces to a binary: does this event happen in the next N minutes? Pump, liquidation, funding flip, listing announcement, sandwich attack, depeg. Binary classifiers are cheap to train, cheap to evaluate on-chain, and trivially turn into trading rules.

BTC PUMP-1H · model 0x9af3…7c2d +87% AUC
5,000 PREDICTIONS · BACKTEST
actual
predicted: pump
predicted: no pump
pump
1,847
true positive
412
false negative
no pump
638
false positive
2,103
true negative
79.0%
Accuracy
+ 29 vs random
0.743
Precision
low false alarms
0.818
Recall
catches most pumps
0.871
ROC-AUC
strong separation

A 0.871 AUC on hourly BTC direction is, in practice, a deployable edge — not because it's "magic", but because the cost of being wrong is bounded (your stop-loss) while the payoff of being right compounds. GL1F's job is not to be a crystal ball. Its job is to be a verifiable and tradeable 0.871.

06 / Tutorial

Build a BTC pump-or-dump predictor. Mint it. Query it on-chain.

Fit a forest. Three ways. Same studio.

NO CODE · NO INSTALL · MAINNET ONLY

Open gl1f.com. Drag a CSV. Click train. Click mint.

The studio is a five-tab single-page web application. Every step below — dataset, training, preview, mint, query — happens in the browser UI, regardless of whether the heavy lifting runs on WASM, on the supplied Python local server, or on the supplied C++ local server. No notebook. No Solidity for the trainer. No upload to anyone's server. The only place "code" appears in this tutorial is at the very end, when an external smart contract wants to call your minted model from another dapp.

i.
Step one · Dataset tab — in browser

Drag a CSV in.

Open gl1f.com → Create → Dataset. Drop a CSV with hourly BTC candles plus engineered features. The studio parses it in your browser, infers numeric vs categorical columns, and lets you click to mark feature columns and the label column. Pick the task — binary_classification — and choose which label value is "pump" (class 1).

The Data Galaxy sub-panel shows a live 3D PCA projection of your data so you can spot leakage or cluster structure before training. Walk-forward, not random split — for time-indexed crypto data the studio defaults to chronological train/val/test partitioning so the model never peeks at the future.

gl1f.com / create / dataset
step 1 of 4
DROP CSV HERE btc_1h_features.csv · 44,160 rows ✓ parsed locally — never uploaded TASK BINARY REGR MULTICLASS MULTILABEL SPLIT ⊳ WALK-FORWARD (default) ○ random FEATURES (7 SELECTED) ☑ r_5m numeric ☑ r_1h ☑ rsi_14 ☑ vol_1h ☑ funding_8h ☑ oi_delta_1h ☑ dist_ma20 ◉ y (label) binary DATA GALAXY · PCA-3 PC1 PC2 PC3 pump no-pump
ii.
Step two · Training tab — in browser

Set the dials. Click train.

The Training tab exposes the hyperparameters that matter — number of trees, depth, learning rate, min-leaf, bins, seed — with sane defaults for crypto. Training runs in a Web Worker (UI stays smooth); validation log-loss streams live as each tree is added.

Click Heuristic search and the studio runs bounded random mutation around your config to find a better one. Click Refit on train+val at the end and it retrains using the best tree count on the union. All of this is point-and-click in the browser.

gl1f.com / create / training
step 2 of 4
HYPERPARAMETERS trees 250 depth 4 learning_rate 0.05 min_leaf 10 bins · quantile 32 seed 0xC0FFEE COMPUTE BACKEND WASM PYTHON :8088 C++ :8089 ▶ TRAIN ↻ HEURISTIC SEARCH LIVE TRAINING · VALIDATION LOG-LOSS 0.69 0.42 BEST 187 val log-loss train log-loss tree #187 / 250 · est 1.4s VAL ACC 0.790 VAL AUC 0.871 BRIER 0.146 PATIENCE 12 / 25 ● LIVE

More than ~100k rows? Switch the Compute backend selector from WASM to PYTHON :8088 or C++ :8089. The supplied local server runs on your own machine; the studio sends it the dataset over localhost. The training UI stays exactly the same. Your data never leaves the device.

iii.
Step three · Local preview tab — in browser

Walk-forward, no peeking.

The Local preview tab decodes the just-trained model bytes locally, replays predictions row-by-row in chronological order, and shows feature importances (split-usage + permutation), per-tree metric curves, and a per-row playground for sanity checks. Time series leak past into future under random splits — GL1F enforces walk-forward by default, so the metrics you see here are the ones you'll get in production.

Everything in this tab runs locally against the binary .gl1f file the studio just produced. It is the same decoder the on-chain runtime uses, so what you see here is what the chain will return.

gl1f.com / create / preview
step 3 of 4
FEATURE IMPORTANCE · PERMUTATION Δloss funding_8h +0.041 rsi_14 +0.034 vol_1h +0.026 oi_delta_1h +0.019 r_1h +0.014 dist_ma20 +0.008 r_5m +0.004 PER-ROW PLAYGROUND · ROW 18,432 r_5m -0.0023 r_1h -0.0140 rsi_14 28.4 vol_1h 0.0180 funding_8h -0.0110 oi_delta_1h -0.0340 dist_ma20 -0.0270 PREDICTION 0.866 P(pump · next 1h) threshold = 0.500 SIGNAL · LONG ACTUAL +1.4% realised next-1h return label · y = 1 ✓ TRUE POSITIVE DECODED LOCALLY · same engine the on-chain ForestRuntime uses
iv.
Step four · Mint tab — in browser, on-chain

Mint the forest as an NFT.

The Mint tab packages your trained .gl1f bytes, splits them into GL1C chunks (≤24,572 B each, the EIP-170 code-size limit minus a 4-byte magic prefix), and deploys each chunk as a tiny pointer contract using ModelStore.write(). A pointer-table contract follows; then ModelRegistry.registerModel() mints the NFT and binds the model.

You fill out: a 128×128 PNG icon, a name, a description, a pricing mode (free / tips / paid-required), a fee, and an owner API access key. You agree to the active license (default CC BY-SA 4.0) and the on-chain Terms version. Click mint. N + 2 transactions later, your model is live on GenesisL1.

For very large models (millions of bytes, tens of chunks), GL1F also supplies an optional Python minter (gl1f-mint) so you can deploy chunks from your terminal in parallel. Same ABIs, same network, same end result. The browser path remains the default and works for the overwhelming majority of models.

gl1f.com / create / mint
step 4 of 4
NFT PREVIEW BTC Pump 1h v1 binary · 250 trees · depth 4 tokenId · #1428 modelId · 0x9af3…7c2d METADATA name BTC Pump 1h v1 description Hourly direction classifier on BTC, trained on funding + RSI + OI features. pricing mode FREE TIPS PAID 0.1 L1 owner api key 0x4F1c…b8E2 · ↻ regenerate ☑ I agree to ToS v3 and license CC BY-SA 4.0 DEPLOY PROGRESS ✓ chunk 1 / 6 written 0xa7…f2 ✓ chunk 2 / 6 written 0x3c…91 ✓ chunk 3 / 6 written 0xbe…05 ✓ chunk 4 / 6 written 0x18…aa ▶ chunk 5 / 6 pending ○ chunk 6 / 6 ○ pointer table ○ registerModel · mint NFT deploy fee 0.043 L1 est gas ~ 18.2M fees paid in L1 (GenesisL1 native)

Once mined, the model is a transferable ERC-721. Its tokenId is human-facing; its modelId = keccak256(bytes) is content-addressed. Anyone can re-derive that hash from the on-chain bytes — your training is its own witness.

v.
Step five · Query the model — anywhere

Predict, on-chain or off.

The model lives on GenesisL1 and is queryable by any wallet, any contract, any chain client. This is the only step in the tutorial where code appears — because it's how other dapps consume your model. From the studio side, you've already shipped.

The studio's Model page lets anyone — owner or visitor — call inference with a feature form. Type values, click Predict. Free models call predictView as a gas-free eth_call. Tipped models offer a tip slider. Paid-required models prompt the user to either pay per call or buy a subscription.

gl1f.com / model / 1428
predict
INPUT FEATURES r_5m -0.0023 r_1h -0.0140 rsi_14 28.4 funding_8h -0.0110 vol_1h 0.0180 oi_delta_1h -0.0340 dist_ma20 -0.0270 ▶ PREDICT (free) RESULT · predictView() · eth_call 0.866 P(pump · next 1h) scoreQ = 866_113 · scaleQ = 1_000_000 latency · 240ms · gas · 0 (view call) SIGNAL · LONG ↻ EXPORT JSON ↪ COPY ABI CALL
onchain_consumer.solsolidity
// Any contract on GenesisL1 (chainId 29) can call your model.
// No oracle middleman. The prediction is part of the same atomic tx as the trade.

interface IForestRuntime {
    function predictView(bytes32 modelId, bytes calldata packedFeaturesQ)
        external view returns (int256 scoreQ);
}

contract PumpStrategy {
    IForestRuntime public immutable runtime;
    bytes32  public immutable modelId;        // 0x9af3…7c2d
    uint32   public immutable scaleQ;         // 1_000_000

    function isPump(int32[7] calldata q) external view returns (bool) {
        bytes memory packed = _packLE(q);                // int32 LE per feature
        int256 scoreQ = runtime.predictView(modelId, packed);
        // score is logit · scaleQ; >0 means P(pump) > 0.5
        return scoreQ > 0;
    }
}
node_consumer.tsjavascript · ethers v6
import { JsonRpcProvider, Contract } from "ethers";
import { RUNTIME_ADDR, RUNTIME_ABI, packFeatures } from "./gl1f";

const rpc     = new JsonRpcProvider("https://rpc.genesisl1.org");
const runtime = new Contract(RUNTIME_ADDR, RUNTIME_ABI, rpc);

const packed = packFeatures([-0.0023, -0.0140, 28.4, 0.0180,
                              -0.0110, -0.0340, -0.0270], 1_000_000);

const scoreQ = await runtime.predictView("0x9af3…7c2d", packed);
const p      = sigmoid(Number(scoreQ) / 1_000_000);
console.log(p);   // 0.866 — strong pump signal
07 / What it looks like in production

Predictions visualised. One model. Twelve hours. Real candles.

BTC/USDT · 1H · model 0x9af3…7c2d ▲ +1.4%
STREAMING
$71,400 $71,200 $71,000 $70,800 $70,600 0.5 threshold BUY · p=0.86 TP +1.4% price P(pump · next 1h) — · 0.5 decision threshold

The model crossed 0.5 → 0.86 at candle #7, after the funding rate flipped negative and RSI bottomed at 28.4. Price climbed +1.4% over the following six hours. That is what binary classification on-chain looks like in production: a single, calibrated, signed number — and a deterministic forest you can re-run yourself.

08 / On-chain AI inference

Why integer trees are the only AI that belongs in a smart contract.

Code-as-data via GL1C chunks

Model bytes are stored as contract code rather than storage slots, using the SSTORE2 pattern. Each chunk is a tiny pointer contract whose runtime bytecode is "GL1C" || data, capped at 24,572 bytes (EIP-170 minus 4-byte magic).

The ForestRuntime reads thresholds and leaves with EXTCODECOPY — far cheaper than SLOAD for medium blobs.

Deterministic integer math

Forest evaluation is just int32 comparisons followed by int32 leaf accumulation into int256. No floats. No GPU non-determinism. Solidity does this natively.

The same input must produce the same output, on every node, every block, forever. Neural nets give that up; GBDTs get it for free.

Identity = hash

A model is its bytes. modelId = keccak256(bytes). There is no version drift, no "which checkpoint did we deploy?", no rug-by-silent-update.

Want to fork a model? Mint a new modelId. Want to upgrade? You're minting a new asset — the market decides which to query.

EIP-712 gated paid inference

Off-chain eth_call can spoof msg.sender, so paid models cannot rely on it. GL1F gates view inference for paid models with EIP-712 signatures: owners and subscribed access keys sign typed data; the runtime verifies on-chain.

Domain separation pins each signature to GenesisL1's chainId and the runtime address. Short deadlines bound the replay window.

09 / Monetization · AI marketplace

An AI marketplace where you own the asset.

Every minted AI model is an ERC-721 — and the GL1F suite ships with an on-chain AI marketplace (ModelMarketplace) plus a subscription access system (ModelRegistry.AccessPlan). Two orthogonal monetization paths: rent AI inference, or sell the AI asset outright.

Mode 0 — Public good
Free
Open inference

Anyone calls predictView() as a free eth_call. Useful for public-good models, reputational plays, and "loss-leader" demonstrations of your alpha.

cost per call0
Mode 1 — Tip jar
Tips
Free + optional tip

Free view inference, plus an optional predictTx() path that lets users send a tip. The runtime emits a tipped-inference event. Good models accumulate a public revenue trail.

tip floor≥ 0.001 L1
Mode 2 — Paywalled
Paid
Pay-per-call or subscribe

Free view is disabled. Users pay per call via predictTx(), or buy a subscription AccessPlan (price + duration) — generating an EIP-712 access key for unlimited view calls until expiry.

fees splitcreator → owner → marketplace
$

How a model creator earns.

Mint with mode 2 and define one or more access plans — say, 7 days for 0.1 L1 or 30 days for 0.3 L1. Buyers generate an Ethereum keypair locally, call buyAccess(), and the registry extends their key's expiry on-chain. The L1 paid flows directly to your fee recipient. Your buyers query through predictAccessView() with their key's signature — no further fees, until expiry. Want to trade the model itself? List the NFT in ModelMarketplace. Owner change is an ERC-721 transfer; access keys, plans, and inference settings all follow the new owner.

Discovery is also on-chain: every minted model registers a word-hash index of its title (_wordTokens). The Forest catalog tab and AI Store marketplace tab both use it for paginated AND-search — no off-chain indexer required.

10 / Example designs

Twelve example crypto-native models.

Templates and design sketches you can train in the studio today. Every one fits the GBDT mold — modest feature count, fast inference, on-chain settleable. AUCs and metrics shown are illustrative reference targets, not benchmarks of any deployed model.

BTC
BTC pump
1h binary

The tutorial model. Predicts P(close_t+1 > close_t) on hourly BTC.

binary · ref auc 0.871
LIQ
Liquidation
hazard

Per-position binary. Will this position liquidate within Nh given health factor, vol, funding?

binary · per-position
FUND
Funding
flip detector

Predicts whether perp funding will flip sign in the next 8h epoch.

binary · ref f1 0.84
σ
VOL
Volatility
forecast

4h realised vol on BTC, ETH, SOL. Useful for options-vault rebalancers.

regression · l2
MEV
Sandwich
classifier

Real-time MEV detection on incoming swap calldata. Pre-trade screening.

binary · ref recall 0.94
RISK
Token risk
multi-flag

Multilabel: low-liquidity / unlocked-supply / dev-active / honeypot. Any subset can fire.

multilabel · L=4
REG
Regime
classifier

4-class market state: trend-up / trend-down / chop / squeeze. Drives strategy router.

multiclass · K=4
PEG
Stablecoin
depeg risk

P(|price − 1| > 1% within 6h). Powers depeg-protected stablecoin vaults.

binary · ref brier 0.04
FLOW
Whale flow
classifier

Multiclass: accumulation / distribution / rotation / exit. Built on labelled wallet clusters.

multiclass · K=4
TWAP
TWAP
slippage

Expected slippage on a sized order, given pool depth and recent flow.

regression · huber-like
BRDG
Bridge
risk score

Cross-chain bridge incident probability over the next 24h, by route.

binary · per-route
DROP
Airdrop
eligibility

Multilabel over a wallet's behaviour: bridger / LPer / lender / governance / sybil-suspect.

multilabel · L=5
11 / What comes next

A new wave of on-chain AI dapps. GenesisL1 is the backend.

Once an AI model is just a bytes32 modelId on a public chain, every dapp inherits it. Risk engines, AMMs, vaults, prediction markets — they stop calling out to opaque AI APIs and start composing models the same way they compose tokens. None of these are roadmap promises; they're the obvious shape of what builders will reach for next.

i.
Lending where the liquidator asks the model first.

A money market reads a liquidation-hazard classifier inside the same transaction that decides whether to seize collateral. Borrowers with low predicted hazard get tighter spreads. The model is auditable bytecode; the price of risk is on-chain.

No oracle. No human risk-team Discord vote. Just a forest, a feature vector, and an integer.

ii.
AMMs that re-weight themselves by regime.

A pool reads a multiclass regime model and adjusts its concentration parameters when the market flips trend → chop. LPs subscribe to the model whose calls they trust; subscription fees become part of the pool's operating cost.

Liquidity becomes a function of belief, not a static curve.

iii.
Insurance vaults gated by depeg classifiers.

A stablecoin-protection vault auto-pays out when a binary depeg-risk model crosses a threshold for N consecutive blocks. The trigger is the prediction itself — not a human committee, not a centralized oracle.

Premiums adjust as the model's calibration drifts.

iv.
Prediction markets settled by signed model attestations.

A market on "will SOL cross $250 by Friday?" resolves when a registered ensemble of signed model outputs converges. Each model is an NFT with a known author, a known training Terms version, and a known license. Disagreement becomes basis.

Polymarket, but every settlement is a forest.

v.
Strategy routers reading on-chain regime models.

A vault routes capital between sub-strategies based on a multiclass regime classifier. Subscribers can swap which model the router consumes — a governance over models, not over parameters.

Active management, fully transparent, no off-chain JSON.

vi.
Under-collateralized credit, scored on-chain.

A wallet's behaviour features become inputs to a binary credit model. Borrowers with high predicted-repay probability unlock under-collateralized lines. The model is public; lenders can fork it, retrain on their own labels, and redeploy.

Credit scoring becomes open source.

All composable. All auditable. All deterministic. All on GenesisL1, with GL1F as the decentralized AI primitive.

12 / Now

Plant a forest. Mint the prediction. Own the AI.

The studio is open at gl1f.com. There is no testnet — only GenesisL1 mainnet. Permissionless: no whitelist, no waitlist, no signup, no KYC. The only requirement is a working wallet on chainId 29 with enough L1 (the GenesisL1 native coin) for gas and the deploy fee. This is what decentralized AI looks like.

✓ No testnet ✓ Permissionless ✓ chainId · 29 ✓ Pay in L1