Samsara
Samsara — 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).
Samsara — an AI/Agents project on Base, token (symbol: SAMS).
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: not established (no available Tier‑1 description of the product/AI component).
- Who it’s for: not established (no available Tier‑1).
- Why onchain/token: the SAMS ERC‑20 token on the Base network is confirmed; token utility is not established (no available Tier‑1).
How it works (very briefly)
- The user does: creates an AI agent via a no‑code interface (configuration/goal/personality/data).
- The system does: connects a model/LLM and integrations (for example, Telegram / X — claimed).
- The user gets: an AI assistant for tasks (including automation/support/content — claimed).
- Where the blockchain is: onchain is confirmed at the level of the SAMS token (contract on Base).
- Token role (if any): not established (no available Tier‑1).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Samsara |
| Also known as (aliases) | SAMS, $SAMS |
| Logo (logo) | — |
| Token symbol (ticker) | SAMS |
| Category | AI/Other | Infra |
| Primary chain (chain) | Base |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Base; Ethereum L2) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0x4c95CD5b24Cba798C56F9C3045975d7b24437415 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | — |
| DecAI Fit — AI thesis fit | 2/6 — low alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 0 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.samsara.build/ |
| Docs | — |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://basescan.org/token/0x4c95CD5b24Cba798C56F9C3045975d7b24437415 |
| X | https://twitter.com/Samsara_build |
| Discord | — |
| Telegram | https://t.me/samsarabuild |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/samsara-build/ |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/samsara-build/ |
General project overview
For Samsara Build (SAMS), a Tier‑1 description of the product/AI component could not be confirmed: the domains samsara.build and docs.samsara.build lead to a domain sale page at the time of the check. The SAMS token contract on the Base network (BaseScan) remains a verifiable Tier‑1 artifact.
Features/modules
- Not established (no available Tier‑1 description of the product).
Typical scenarios
- Not established (no available Tier‑1 description of the product).
Getting started (wallet/network)
- What you need: not established (no available Tier‑1 “getting started”/product); operations with the token require an EVM wallet (Base).
- Network/chain: Base (the SAMS token).
- Fees: network fees for operations with the token (Base).
Architecture/tech (non‑AI)
- Components: only the token contract on the Base network is confirmed in verifiable Tier‑1 sources.
- Participant roles: token holders/Base users.
- Where logic runs: not established (no Tier‑1 description of the product).
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not established (no available Tier‑1 description of utility/necessity).
- Protocol necessity drivers: the token on the Base network is confirmed; separate onchain logic (other than the token) is not established.
- Issuance/burn: not established (no available Tier‑1).
- Distribution: not established (no available Tier‑1).
Governance
- Who makes decisions: not established (no available Tier‑1).
- How protocol parameters change: not established.
Security and incidents
- Audits: not established.
- Bug bounty: not established.
- Incidents: not established.
- Threat model: typical risks of AI services (quality/hallucinations/data access) + token risks (contract/keys) — without Tier‑1 details.
Project status and timeline
- Current status: active (based on the fact of the token’s onchain artifact); token network — Base mainnet.
- Roadmap: not established (no available Tier‑1).
Ecosystem/integrations
- Integrations: not established (no available Tier‑1); for public social media links, see links_*.
- Partners: —.
- Where it’s actually used: not established (no available Tier‑1).
AI component of the project
- What is real AI here? not established (no available Tier‑1 description of the AI component).
- What is truly onchain? the onchain component of the SAMS token on the Base network is confirmed; other onchain logic is not established.
- Why is a token needed? not established (no available Tier‑1 description of utility).
- Red flags (based on the information found): absence of a public demo/guide on “what you can touch”; absence of Tier‑1 proof of onchain logic other than the token; absence of an audit/bug bounty in Tier‑1.
DecAI Fit component summary
- DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 2 |
| Onchain necessity | low | 1 |
| Token necessity | low | 1 |
| Evidence | Tier‑1 present | 0 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): A Tier‑1 source with AI intent/roadmap is not established (no available official documentation/website).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no available Tier‑1 artifact with AI intent/roadmap.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): What exactly the AI does is not established (no available Tier‑1 description of the product).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a Tier‑1 description of AI features, we set 0.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): A public link to an application/demo for “trying the product” is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): The documentation describes the product but does not provide a direct public link to an available demo interface.
- 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): No reproducible set of quality metrics for AI agents/models was found in Tier‑1.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): The technical description/architecture is not established (no available Tier‑1).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no available Tier‑1 tech description/documentation.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Base
- Addresses/identifiers: token contract 0x4c95CD5b24Cba798C56F9C3045975d7b24437415
- Evidence: Tier‑1 — https://basescan.org/token/0x4c95CD5b24Cba798C56F9C3045975d7b24437415
- Why sufficient / why not (one line): There is an onchain artifact (the token contract) and a network 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 (other than the token).
- Evidence: Tier‑1 — https://docs.samsara.build/
- Why sufficient / why not (one line): Even if Web3 integration was claimed, confirmation of onchain logic other than the token is not established per Tier‑1.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: it is not established that a key property of the product breaks down without the blockchain.
- Evidence: Tier‑1 — https://docs.samsara.build/
- Why sufficient / why not (one line): There is no Tier‑1 justification of “why the product loses its meaning without onchain”.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a claimed token, SAMS.
- Evidence: Tier‑1 — https://basescan.org/token/0x4c95CD5b24Cba798C56F9C3045975d7b24437415
- Why sufficient / why not (one line): The documentation directly points to “Native token ($SAMS)”.
- Conflict note (if any): —
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 1
- Claim (one line): The SAMS token is claimed to be a “native token powering the ecosystem” (the ecosystem’s payment token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): The Tier‑1 wording indicates the token’s payment/utility purpose within the platform.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Mechanics of token‑based incentives/collateral/penalties are not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): 1 requires an explicit description of incentives/staking/slashing.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): The use of the token for governance is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): 1 requires explicit mechanics for governance/voting with 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 (for example, with payment in a stablecoin) is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): 1 requires an explicit “can be replaced without loss of meaning” or a technical/economic justification.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://basescan.org/token/0x4c95CD5b24Cba798C56F9C3045975d7b24437415 | Onchain artifact: the SAMS token contract on the Base network. |
| Tier‑1 | — | A Tier‑1 source for claim “what is real AI here” is not established (no available official documentation/website). |
| Tier‑1 | — | A Tier‑1 source for claim “there is onchain logic other than the token” is not established. |
| Tier‑1 | — | A Tier‑1 source for claim “there is a public demo/application that can be tried” is not established. |
No comments to display
No comments to display