Public technical evidence · GenLayer Studionet

The intelligence layer behind All-in-One Terminal.

We use GenLayer where ordinary software reaches its limit: deciding what social content actually means, whether a crypto signal is trustworthy, and whether independent live sources support the same conclusion.

Inspect the contracts View public source

4deployed Intelligent Contracts

5production workflows

3live verification APIs

0points from unresolved verdicts

Important technical distinction

Four contracts. Five ways GenLayer changes the product.

All-in-One Terminal currently integrates four independently deployed, reusable Intelligent Contracts. Continuous sentiment is the fifth GenLayer-powered workflow: it derives a market label from finalized Relevance Police decisions. We document it separately without misrepresenting it as a fifth contract address.

Architecture

From noisy inputs to auditable product decisions

GenLayer is not a decorative badge in the interface. It sits inside the data path, between collection and the features that users trust.

Collect

Social posts, Smart-People interactions, market pairs, project identity, score history, and on-chain context.

Build evidence

Normalize identities, preserve context, deduplicate repeated phrases, cap payloads, and create an audit fingerprint.

Verify live context

GenLayer validators independently fetch public web sources inside non-deterministic execution blocks.

Reach consensus

The Equivalence Principle resolves semantic questions that deterministic code and single-model APIs cannot safely answer.

Gate the product

Finalized verdicts become auditable evidence. Pending or low-confidence results remain visible but receive zero scoring power.

Deterministic application layer

Collects and normalizes source data
Resolves project and token identities
Builds compact, context-preserving evidence
Stores transaction hashes and finalized verdicts
Applies confidence thresholds and scoring rules

GenLayer consensus layer

Fetches live web context independently per validator
Interprets ambiguous natural-language evidence
Reconciles disagreements between sources
Produces structured, consensus-backed decisions
Persists reusable contract state for public reads

Contract registry

Four standalone Intelligent Contracts

Each artifact has a focused interface, public source repository, and matching GenLayer Studio Explorer deployment.

Relevance Police

v2.0.0

deployed

WRITE METHODcheck_relevance(…)

Adjudicates whether a social phrase genuinely refers to a specific crypto token, instead of trusting a ticker-shaped keyword match.

What GenLayer does

Validators independently fetch DexScreener and CoinGecko context, then use the Equivalence Principle to return one semantic verdict per phrase.

STRUCTURED OUTPUTrelevant · confidence · reason · token_verified · source_mismatches

STUDIONET CONTRACT0x4C0af15200D956Ae3Bda73cF42F02AA49Efc3599

Signal Verifier

v2.0.0

deployed

WRITE METHODverify_signal(…)

Cross-checks a discovered token address and the evidence behind its signal before the terminal presents it as trustworthy alpha.

What GenLayer does

Validators inspect live token, ticker, liquidity, volume, pool-age, identity, and social-quality evidence across multiple web sources.

STRUCTURED OUTPUT8 checks · CLEAN/SUSPICIOUS/DANGEROUS · risk_score · flags

STUDIONET CONTRACT0x926A3b2C039a02290A7503ae94641c15C53D57c7

Research Report

v2.0.0

deployed

WRITE METHODgenerate_report(…)

Produces a structured token research brief while checking the terminal’s evidence against live market identity and pricing sources.

What GenLayer does

The contract asks validators to reconcile app evidence with live DexScreener and CoinGecko data and explicitly report disagreements.

STRUCTURED OUTPUTmarket analysis · risks · catalysts · sentiment · source agreement

STUDIONET CONTRACT0x2b3Abc58111B0F9f66acA6836445A8dff725d48B

Token Intelligence

v1.0.0

deployed

WRITE METHODassess_token(…)

Combines market health, social authenticity, project legitimacy, manipulation risk, and alpha potential into one assessment.

What GenLayer does

Validators gather live market, token-security, and identity context before reaching consensus on the five-dimensional brief.

STRUCTURED OUTPUT5 dimensions · composite score · verdict · risks · opportunities

STUDIONET CONTRACT0x3A91fD34fb1700fAEB499DAf912EE11dFf8204dB

Production integration

Five workflows users experience

The contracts are reusable artifacts. These are the concrete ways their decisions affect the terminal.

False-positive protection

Ambiguous phrases are judged before social evidence can increase a project score. A post about “launching a product” cannot silently become a $LAUNCH signal.

Continuous sentiment

The same finalized phrase verdicts are aggregated into bullish, bearish, or neutral labels. This is a production workflow powered by Relevance Police, not a fictitious extra deployment.

Signal risk verification

Contract address, pool quality, token identity, social quality, and source consistency are evaluated before a signal receives a GenLayer verification badge.

Consensus research

Users can request a structured report whose claims and market figures are cross-checked by validators rather than generated by one private model.

Five-dimension intelligence

Project dossiers can surface one explainable assessment covering market, social, legitimacy, manipulation, and alpha potential.

Where verdicts are consumed

One protection layer across the app

Alpha LeaderboardEmerging SignalsSmart FeedSpacesProject DiscoveryProject DossiersResearch ReportsAdmin Relevance Audit

Safety and integrity

Consensus is useful only when the pipeline respects it

The surrounding application is designed so a missing or unresolved GenLayer result cannot quietly become positive evidence.

Fail-closed scoring

Only finalized, sufficiently confident relevance decisions can increase social scores. Pending verdicts receive zero points.

Prompt-injection boundary

User and social content is wrapped as untrusted data, while contract prompts explicitly reject instructions embedded inside evidence.

Context-preserving batches

Repeated posts are deduplicated without reducing a phrase to one keyword. The validator receives the surrounding meaning.

Identity before interpretation

Ticker, token name, address, aliases, market pair, and project metadata are assembled before semantic adjudication.

Bounded contract state

Payload size, batch size, input shape, and stored entries are capped to keep the contracts reusable and operationally predictable.

End-to-end audit trail

Every accepted result is stored with its transaction hash, confidence, explanation, contract version, and evidence fingerprint.

Open evidence

Inspect the implementation yourself.

The source repositories explain the public interfaces, security constraints, output schemas, and deployed versions. The Explorer links show the matching contracts and their real transaction histories.

Relevance PoliceGitHub Explorer

Signal VerifierGitHub Explorer

Research ReportGitHub Explorer

Token IntelligenceGitHub Explorer

GenLayer turns collected data into decisions users can audit.

That is the role it plays in All-in-One Terminal: semantic adjudication, independent live-source verification, consensus, and an evidence trail.

Explore the terminal GenLayer documentation