Fortytwo

Sign in to add this project to your watchlist

Overview

Tickers
None recorded
Sector
machine-learning infrastructure
Lifecycle stage
Development
Pre-TGE classification
Pre-TGE
Token status
Unknown
Last updated

AI inference project researching peer-ranked collaboration among models. It originally announced a decentralized network on Monad testnet and now markets Engine API and Harbor on-premise inference; current API documentation describes centrally controlled hosting. Token status is unresolved.

Token status summary

Unknown

Synthesis

No synthesis has been written yet.

Product

The documentation describes an OpenAI Chat Completions-compatible API, with model-listing and chat-completion endpoints and API-key access.

Supported

Project announcement

Evidence (2): 2 supporting
  • supports: Fortytwo
    The Fortytwo API is compatible with the OpenAI Chat Completions API.
  • supports: Fortytwo
    GET /v1/models List the available model IDs POST /v1/chat/completions Generate a response Every request needs an API key .

Whether the currently offered API is served by independent public nodes is disputed by Fortytwo materials across products and time: the 2025 network description says it is community-run, but current API data-handling documentation explicitly says requests run on Fortytwo-controlled US infrastructure and are not routed to independent public node operators. These may describe different offerings or a product transition; the operating boundary has not been independently established.

Disputed

Evidence (2): 1 supporting, 1 contradicting; 1 needs review
  • supports: Fortytwo
    The network is run by a community of AI enthusiasts worldwide.
  • contradicts: Fortytwo
    Inference runs on Fortytwo-controlled infrastructure in the United States . Requests are not routed to independent public node operators.

    Needs review

Fortytwo currently markets Engine, an inference API for open-weight models using Swarm Inference, and Harbor, an on-premise multi-model inference system.

Supported

Project announcement

Evidence (2): 2 supporting
  • supports: Fortytwo
    Fortytwo Engine is an inference API that runs open-weight models through Swarm Inference.
  • supports: Fortytwo
    Fortytwo Harbor combines specialized models and on-premise compute into one inference system

Harbor advertises two pilot formats: an eight-week software-and-hardware bundle and a four-week software-only deployment on the customer’s infrastructure.

Supported

Project announcement

Evidence (2): 2 supporting
  • supports: Fortytwo
    Track A — Turnkey · 8 weeks Software license + hardware bundle.
  • supports: Fortytwo
    Track B — Your infra · 4 weeks Software-only deployment on your hardware.

Fortytwo advertises Strand-Rust-Coder-14B as its first model built on a Fortytwo-generated dataset and says it is open-sourced. The model weights and Rust benchmark ranking were not independently checked.

Supported

Project announcement

Evidence (1): 1 supporting
  • supports: Fortytwo
    The first AI model built on a Fortytwo-generated dataset.

The relationship between the earlier permissionless node network, Prime, Engine and Harbor is not yet independently verifiable. Which production workloads use public nodes, how requests are allocated, geographic node distribution, service availability and the current blockchain dependency remain unestablished. No authenticated inference request or node operation was performed.

Not yet verifiable

No evidence recorded.

Fortytwo announced in March 2025 a decentralized inference network of small language models running on consumer hardware, with node ratings recorded on Monad.

Supported

Project announcement

Evidence (1): 1 supporting
Back to sections

Team

A complete independently corroborated founder roster, current management roles, biographies and prior employment, headcount, ownership, and the relationship between legal entities were not established from the fetched sources. No corporate registry filing was fetched.

Not yet verifiable

No evidence recorded.

The fetched Terms of Service identify Fortytwo MENA Limited, incorporated in Abu Dhabi Global Market, with registration number 36387, as the service provider. The document is labelled effective 13 November 2026, one day after retrieval, so it is recorded as a future-dated statement rather than proof of terms already in force.

Supported

Project announcement

Evidence (2): 2 supporting; 1 needs review

Hub71 lists Fortytwo in its Hub71+ Digital Assets programme at pre-seed stage. Hub71 is the programme host, so the listing is contextual rather than independent product validation.

Unverified

Evidence (1): 1 supporting

The October 2025 Fortytwo paper lists Vladyslav Larin, Ihor Naumenko, Aleksei Ivashov, Ivan Nikitin and Alexander Firsov as authors. Authorship alone does not establish current employment or executive roles.

Supported

Project announcement

Evidence (1): 1 supporting
Back to sections

Funding

The lead investor attribution conflicts: ChainCatcher names Big Brain Holdings as lead, while CertiK’s funding feed says CMT Digital led the $2.3 million pre-seed round. The sponsored project release agrees with ChainCatcher. CertiK’s funding-data provenance is unclear; the discrepancy is unresolved.

Disputed

Evidence (2): 1 supporting, 1 contradicting; 1 needs review

Fortytwo’s sponsored Chainwire release names Big Brain Holdings, CMT Digital, Escape Velocity Ventures, Chorus One and Mentat Group among the round’s investors.

Supported

Project announcement

Evidence (1): 1 supporting

ChainCatcher reported on 6 March 2025 that Fortytwo announced completion of a $2.3 million pre-seed round. This is reporting of the announcement, not verification of funds received.

Supported

Evidence (1): 1 supporting

Round valuation, financing instrument, token warrants, investor rights, independently verified receipts, subsequent financing, cumulative capital raised, cash balance, burn and runway were not established. The $2.3 million figure is a dated announced round, not a current audited funding total.

Not yet verifiable

No evidence recorded.

Back to sections

Technical progress

Fortytwo’s October 2025 paper proposes peer-ranked, reputation-weighted consensus across heterogeneous models, with on-chain reputation and proof-of-capability calibration to resist Sybil attacks. These are the authors’ design claims.

Supported

Project announcement

Evidence (2): 2 supporting

Engine advertises Qwen3.8-27B with 7% higher average accuracy and up to 25% fewer tokens per task than the base model. The page describes token-efficiency evaluation across 450 DeepSWE benchmark runs; this has not been independently replicated.

Supported

Project announcement

Evidence (2): 2 supporting
  • supports: Fortytwo
    7% more accurate on average vs. base model Up to 25% fewer tokens per task
  • supports: Fortytwo
    Usage across 450 DeepSWE benchmark runs.

The x402Escrow repository describes a UUPS-upgradeable USDC escrow for variable-cost AI services: a facilitator settles and releases payments, and a timeout permits refunds to the client. A repository description does not establish live deployment or security.

Supported

Project announcement

Evidence (2): 2 supporting
  • supports: Fortytwo Network on GitHub
    x402Escrow is a UUPS-upgradeable escrow contract developed by Fortytwo
  • supports: Fortytwo Network on GitHub
    The facilitator calls settle(...) to pull USDC into escrow. The facilitator calls release(escrowId, facilitatorAmount) after the request is completed. If the release never happens, anyone can call refundAfterTimeout(escrowId) and funds return to the client.

The paper’s authors report 85.90% on GPQA Diamond versus 68.69% for majority voting using the same model set; their stated prompt-injection degradation is 0.12% versus 6.20% for a monolithic baseline. These are self-reported research results, not independently reproduced production measurements.

Supported

Project announcement

Evidence (2): 2 supporting

The Fortytwo GitHub organization lists node clients, P2P setup scripts, agent integrations and an x402Escrow contract repository. At retrieval its repository list showed 10 of 13 repositories and a LangChain integration updated on 5 November 2026; code was not built or audited in this review.

Supported

Project announcement

Evidence (3): 3 supporting; 1 needs review

Current mainnet deployment, chain IDs and deployed reputation-contract addresses, production peer-consensus enforcement, reproducible benchmark artifacts, independent replication, uptime, throughput, latency, and a security audit of the complete system were not established. Public repository visibility is not evidence that the entire production service is open source.

Not yet verifiable

No evidence recorded.

Back to sections

Adoption

Harbor solicits pilot calls and says its exact model configuration and hardware footprint are scoped with the customer during a pilot.

Supported

Project announcement

Evidence (2): 2 supporting
  • supports: Fortytwo
    We lock the exact configuration with you during the pilot.
  • supports: Fortytwo
    We size the exact footprint with you in the pilot

Named paying customers, customer-confirmed deployments, independently measured API requests, monthly active users, active nodes and operators, retention, revenue, fees, utilisation, repeat demand, paid Harbor pilots and payment-settlement volume were not established. Programme listings and repository activity do not supply these metrics.

Not yet verifiable

No evidence recorded.

The project’s node-skills README describes FOR points for answering and judging queries, with nodes starting as Challengers and reaching full participation at rank 42. This documents the advertised contributor programme, not current active-node counts.

Supported

Project announcement

Evidence (1): 1 supporting
  • supports: Fortytwo Network on GitHub
    Your node earns FOR points by answering queries and judging responses. New nodes start as Challengers (rank 0) and grind through Capability Challenges until rank 42
Back to sections

Competitors

Independent comparisons against decentralized inference networks, comparable quality-adjusted costs, end-to-end latency, token consumption, hardware requirements, total cost of ownership and security were not established. The project’s benchmark claims cannot establish a current competitive lead.

Not yet verifiable

No evidence recorded.

Harbor positions itself between cloud frontier-model APIs and local open-source models, advertising fixed hardware cost and 30% lower total cost of ownership. The comparison is vendor marketing, not an independent cost study.

Supported

Project announcement

Evidence (1): 1 supporting
  • supports: Fortytwo
    30% lower TCO Fixed hardware cost replaces per-token billing.

Fortytwo’s October 2025 benchmark page compares its swarm with ChatGPT 5, Gemini 2.5 Pro, Claude Opus 4.1, Grok 4 and DeepSeek R1. It specifies pass@1 raw prompts without tools. These are the project’s comparisons with dated model versions.

Supported

Project announcement

Evidence (2): 2 supporting
  • supports: Fortytwo
    OpenAI’s ChatGPT 5, Google Gemini 2.5 Pro, Anthropic Claude Opus 4.1, xAI Grok 4, and DeepSeek R1
  • supports: Fortytwo
    All models tested on pass@1 using raw prompts with no tools usage.
Back to sections

Token status

An official native-token contract address and chain were not established; no token contract match or on-chain token verification was performed. The x402Escrow payment contract is not evidence of a Fortytwo-issued token. Prime pages returned only an application shell to curl, so search-result contract addresses and payment-chain claims were excluded.

Not yet verifiable

No evidence recorded.

Token supply, allocations, insider shares, vesting, cliffs, unlocks, issuance, burns, governance rights, token utility, sale or airdrop terms, points conversion and eligibility were not established from fetched official materials.

Not yet verifiable

No evidence recorded.

The official node README calls FOR rewards points. It does not by itself establish a transferable crypto-asset, a confirmed token ticker, a conversion entitlement or a token launch.

Supported

Project announcement

Evidence (1): 1 supporting

No fetched official source explicitly confirmed no token, a planned transferable token, TGE date or a completed launch. Token status is unknown; pre-TGE is a provisional screening classification based on points terminology and the third-party pre-launch label, not confirmation of absence. No ticker is assigned.

Not yet verifiable

No evidence recorded.

CertiK labels Fortytwo Pre-Launch, gives no token launch date and lists token/contracts information as unavailable. This is a third-party profile with unclear completeness and data provenance, so it is not confirmation that no token exists.

Unverified

Evidence (2): 2 supporting; 2 need review
Back to sections

Risks

CertiK’s profile says Fortytwo is not audited by CertiK and shows no third-party audit or KYC. This records the profile’s coverage only; it does not prove no review exists elsewhere.

Unverified

Evidence (2): 2 supporting; 2 need review

The API data-handling documentation says inference runs on Fortytwo-controlled US infrastructure rather than independent public nodes. This makes its current hosting boundary materially different from the older permissionless-network positioning.

Supported

Project announcement

Evidence (1): 1 supporting
  • supports: Fortytwo
    Requests are not routed to independent public node operators.

Fortytwo’s data-handling documentation describes zero retention and no training as defaults, but says free-model requests are collected for product improvement and training regardless of the optional contribution setting. Serious-abuse flags can retain content for up to 30 days, with extensions for investigations, disputes or legal requirements.

Supported

Project announcement

Evidence (3): 3 supporting
  • supports: Fortytwo
    Every request to a free model is collected and used to improve Fortytwo products and services, including evaluating and training models
  • supports: Fortytwo
    the flagged content and related identifiers can be kept for up to 30 days.
  • supports: Fortytwo
    A documented investigation, dispute or legal requirement can extend the period.

The escrow README reserves proxy upgrades to the owner, role assignment and timeout changes to the default administrator, and settlement/release to facilitators. These are documented privileged powers, not an audit of deployed ownership or fund safety.

Supported

Project announcement

Evidence (2): 2 supporting

The fetched future-effective terms warn that AI results may be inaccurate or misleading and require evaluation before use. They state no particular uptime or latency commitment without an SLA. Applicability of this 13 November 2026 version at the 12 November retrieval date is unresolved.

Supported

Project announcement

Evidence (2): 2 supporting; 2 need review

Independent confirmation of Sybil and collusion resistance, correlated model errors, prompt-injection protection, privacy guarantees, malicious-node handling, central operator controls, deployed upgrade-key custody, incident history and regulatory compliance was not established. Self-reported benchmark resilience and CertiK profile fields do not resolve these risks.

Not yet verifiable

No evidence recorded.

Back to sections

Sources

Back to sections
Back to discovery

Nothing on this site is financial advice.