MOROS NET

MOROS NET — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

MOROS NET — an AI/Other project on Ethereum, token (symbol: MOROS).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

What it is: a project/movement that claims the goal of funding open‑source development (including AI, privacy and cybersecurity) through grants (Tier‑1 website).
Who it’s for: teams/developers who apply for grants, and token holders (claimed).
Why onchain/token: the MOROS token on the Ethereum network is confirmed onchain; the website claims mechanics for distributing funds/allocations and trading fees to support grants/projects (details require validation against contracts).

How it works (very briefly)

The user does: applies for a grant or participates in the project’s community (claimed).
The system does: distributes funding/support and publishes a list of funded projects (claimed).
The user gets: grant support (for teams) or participation in token mechanics (for holders; details are not established per Tier‑1 at the contract level).
Where the blockchain is: onchain — the MOROS token on Ethereum.
Token role: the website describes the token as an ecosystem tool for grants and distributions (claim), but the contract implementation requires separate validation.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	MOROS NET
Also known as (aliases)	MOROS
Logo (logo)	../assets/778_moros-net_logo.webp
Token symbol (ticker)	MOROS
Category	AI/Other \| Infra
Primary chain (chain)	Ethereum
Type	EVM
Network status	mainnet
Consensus (consensus)	PoS (Ethereum)
Launch date (launch_date)	—
Project status (status)	active
Token (standard)	ERC-20
Token contract	0xAb85fc558d722A2b7c040FfB77dB676Bd9e7D322
Token model (token_type)	—
Max supply	1 000 000 000 MOROS
Issuance	—
Tokenomics (tokenomics, brief)	The website describes grants and distributions for holders (claim); the contract implementation is not confirmed by Tier‑1.
Governance	—
Admins/keys	—
Audit	—
Bug bounty	—
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	open-source AI funding
Use‑case (use_case)	grants + development funding
DecAI Fit — AI thesis fit	3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary	ai_score 1 / onchain_score 1 / token_score 1 / evidence_score 2
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://morosnet.com
Docs	—
GitHub	https://github.com/moroscult
Releases / Changelog	—
Whitepaper	—
Roadmap	https://morosnet.com/roadmap
Security advisories	—
Explorer	https://etherscan.io/token/0xAb85fc558d722A2b7c040FfB77dB676Bd9e7D322
X	https://twitter.com/morosnet
Discord	—
Telegram	https://t.me/morosnet
Medium	—
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/moros-net
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/moros-net/

General project overview

MOROS NET is positioned as an initiative/funding effort aimed at supporting open‑source development in AI, privacy and cybersecurity through grants. Per the Tier‑1 website, the project publishes examples of funded projects and describes the terms/application process. Onchain, the MOROS token on the Ethereum network is confirmed per Tier‑1; however, details of which processes are implemented in smart contracts are not established per Tier‑1.

Features/modules

Grant program: applications and a list of funded projects (Tier‑1).
Distribution mechanics (claimed): described on the website as part of the token model (require validation).

Typical scenarios

Scenario 1: a team applies → receives grant support if approved (claimed).
Scenario 2: a user interacts with the MOROS token → operations are visible onchain.

Getting started (wallet/network)

What you need: an Ethereum wallet for onchain operations with the token; for grants — an application on the website.
Network/chain: Ethereum mainnet.
Fees: Ethereum network fees for transactions.

Architecture/tech (non‑AI)

Components: website/grant processes (offchain), the MOROS ERC‑20 token (onchain).
Participant roles: grant applicants, token holders, the team/process operators.
Where logic runs: most processes are offchain; the token is confirmed onchain.
Dependencies: Ethereum infrastructure.

Token/economics (expanded, no forecasts)

Token utility: the website describes the token as a tool for funding/distributions and participation in the ecosystem (claim); details of mechanics and contracts are not established.
Supply parameters: max total supply 1 000 000 000 MOROS (onchain).
Who pays fees: users (gas in ETH) for transactions.
Where fees go: to Ethereum network validators/stakers (within the network mechanics).
Issuance/burn: —.

Governance

Who makes decisions: not established per Tier‑1.
How protocol parameters change: —.
Where decisions are discussed/made: —.
Keys/multisig: —.

Security and incidents

Audits: not found per Tier‑1.
Bug bounty: not found per Tier‑1.
Incidents: —.
Threat model: typical risks of an ERC‑20 token and offchain grant processes.

Project status and timeline

Current status: token on Ethereum mainnet; the grant program is described on the website.
Key releases/milestones: —.
Roadmap: there is a brief description of the roadmap page (see links_*).

Ecosystem/integrations

Integrations: —.
Partners: partners/collaborations are listed on the website (as claims; details are not verified).
Where it’s actually used: the list of funded projects on the website (Tier‑1).

AI component of the project

What is real AI here? In the Tier‑1 source, AI is specified as a focus/funding area (intent), but a working AI component of the product is not identified.
What is truly onchain? The MOROS ERC‑20 token on the Ethereum network.
Why is a token needed? The website links the token to the grant/distribution model; detailed verification of onchain mechanics requires separate artifacts (contracts/addresses/rules).
Red flags (based on the information found): absence of a Tier‑1 tech description of a specific AI product; onchain logic (other than the token) is not confirmed by Tier‑1 sources.

DecAI Fit component summary

DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis

Component	Level	Score
AI reality	low	1
Onchain necessity	low	1
Token necessity	low	1
Evidence	Tier‑1 present	2

Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

AI_0 (decision): 1
Claim (one line): The website claims a focus on funding open‑source AI (as intent).
Evidence: Tier‑1 — https://morosnet.com
Why sufficient / why not (one line): This records intent/intention, but does not prove a working AI component of the product.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 0
Claim (one line): No Tier‑1 description of a specific AI component/features of the product was found.
Evidence: Tier‑1 — https://morosnet.com
Why sufficient / why not (one line): The project is described as a grant/movement initiative, not a specific AI protocol.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): No demo of an AI product is identified in Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no object for a demo other than the initiative’s website.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: —
Context (version/date/how measured): —
Evidence: Tier‑1 — —
Why sufficient / why not (one line): Metrics/benchmarks are not applicable without an identified AI product.
Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

AI_4 (decision): 0
Claim (one line): A Tier‑1 tech description of an AI component is absent (so far there is only intent).
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no object for architecture/versions.
Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

OC_1 (decision): 1
Chain: Ethereum
Addresses/identifiers: MOROS ERC‑20 token contract: 0xAb85fc558d722A2b7c040FfB77dB676Bd9e7D322
Evidence: Tier‑1 — https://etherscan.io/token/0xAb85fc558d722A2b7c040FfB77dB676Bd9e7D322
Why sufficient / why not (one line): The token contract is verifiable via the explorer.
Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

OC_2 (decision): 0
What useful logic is onchain: not established per Tier‑1 (other than the token).
Evidence: Tier‑1 — —
Why sufficient / why not (one line): No Tier‑1 description of specific onchain logic for grants/distributions was found.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 0
“Replace the blockchain” test: not established.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): The project has a MOROS ERC‑20 token on the Ethereum network.
Evidence: Tier‑1 — https://etherscan.io/token/0xAb85fc558d722A2b7c040FfB77dB676Bd9e7D322
Why sufficient / why not (one line): The existence of the token is verifiable onchain.
Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

TK_1 (decision): 0
Claim (one line): Mandatory payment for the service with the token is not established per Tier‑1.
Evidence: Tier‑1 — https://morosnet.com
Why sufficient / why not (one line): The website describes the token as a tool of the initiative, but an explicit payment function is not singled out.
Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

TK_2 (decision): 1
Claim (one line): The website describes a grant model and distributions linked to the token’s trading fee (claim).
Evidence: Tier‑1 — https://morosnet.com
Why sufficient / why not (one line): This reflects token‑related incentives/distributions, but implementation details require checking against contracts.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): No Tier‑1 confirmation of governance use of the MOROS token was found.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): Mentioning a DAO is not the same as describing the mechanics of governance via the token.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): The replaceability of the token is not established.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no sufficient description of the mechanics and their necessity.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://morosnet.com	AI intent and description of the grant/funding initiative; description of the token model (claims).
Tier‑1	https://etherscan.io/token/0xAb85fc558d722A2b7c040FfB77dB676Bd9e7D322	Onchain facts: the MOROS token, Ethereum network, contract, max supply.
Tier‑1	https://morosnet.com/funded-projects/	Examples of funded projects (as a Tier‑1 showcase of results).
Tier‑1	https://morosnet.com/roadmap	Roadmap page (high‑level).
Tier‑2	https://coinmarketcap.com/currencies/moros-net/	Aggregator profile (for reference).