Triall
Triall — 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).
Triall — an AI/Other project on the Ethereum network, token (symbol: TRL).
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/ecosystem around software and services for clinical trials (clinical trials) and working with medical data.
- Who it’s for: clinical researchers, organizations/teams working with clinical trials.
- Why onchain/token: the confirmed onchain artifact is the TRL ERC‑20 token on Ethereum; the Tier‑1 whitepaper describes the blockchain components of the product and the token model (including a staking program and the secondary token T‑CRED), but whether the token is mandatory for access to/operation of the product requires clarification per Tier‑1.
How it works (very briefly)
- The user does: uses Triall eClinical solutions/services (per the description on the website).
- The system does: helps conduct clinical trials and work with data/processes.
- The user gets: tools for planning/execution/analytics (details — per the documentation/whitepaper).
- Where the blockchain is: the onchain component is confirmed by the existence of an ERC‑20 token on Ethereum.
- Token role (if any): TRL (ERC‑20); the whitepaper describes changes to the token system (including a staking program and the secondary token T‑CRED).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Triall |
| Also known as (aliases) | TRL |
| Logo (logo) | ../assets/735_triall_logo.webp |
| Token symbol (ticker) | TRL |
| Category | AI/Other |
| 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 | 0x58f9102bf53cf186682bd9a281d3cd3c616eec41 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | The whitepaper describes changes to the token system (including the secondary token T‑CRED, Triall Community Fund and staking program). |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI + privacy-enhancing analytics |
| Use‑case (use_case) | eClinical software + services for clinical trials |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 1 / onchain_score 2 / token_score 1 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.triall.io |
| Docs | https://uploads-ssl.webflow.com/63319a2d0a41c733a9d60da7/63e3cd5943813b4d24a35cb7_Triall-Whitepaper-v2.1.3-August2021.pdf |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://uploads-ssl.webflow.com/63319a2d0a41c733a9d60da7/63e3cd5943813b4d24a35cb7_Triall-Whitepaper-v2.1.3-August2021.pdf |
| Roadmap | https://medium.com/triall/presenting-the-new-triall-roadmap-1d2db597e8fb |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x58f9102bf53cf186682bd9a281d3cd3c616eec41 |
| X | https://twitter.com/triallofficial |
| Discord | — |
| Telegram | https://t.me/triallcommunity |
| Medium | https://medium.com/triall-foundation |
| Audit report(s) | https://www.triall.io/services/auditing |
| Bug bounty | — |
| CoinGecko (profile, reference) | — |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/triall/ |
General project overview
On the Tier‑1 website, Triall describes itself as a provider of software and services for clinical trials. The technology description on the website mentions “Artificial intelligence”, as well as a separate analytics module/area (Clinical Insights Exchange). Within this card, we record verifiable elements: the Tier‑1 website/whitepaper and the existence of the TRL ERC‑20 token on Ethereum.
Features/modules
- eClinical solutions and research services (per the description on the website).
- Mention of AI as part of “advanced technologies” (without metrics/architecture per Tier‑1).
Typical scenarios
- Scenario 1: an organization uses Triall software/services to conduct a trial → receives tools/processes.
- Scenario 2: a user interacts with the TRL token → transactions are observable in the Ethereum explorer.
Getting started (wallet/network)
- What you need: access to the project’s website/materials; a wallet for EVM networks (for operations with the token).
- Network/chain: Ethereum (for the token).
- Fees: Ethereum network fees for token transactions.
Architecture/tech (non‑AI)
- Components: an ERC‑20 token on Ethereum; Triall offchain software/services (details are not established per Tier‑1).
- Participant roles: users/client organizations and token holders.
- Where logic runs: the token — onchain; the product — offchain (in the sense of SaaS), details are not established.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: the whitepaper describes changes to the token system and a staking program; however, Tier‑1 confirmation of the mandatory role of the token as a “gate”/payment for the product is not recorded in this card.
- Who pays fees: for token transactions, the sender pays fees (Ethereum gas).
- Issuance/burn: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: typical token risks and offchain software risks (details not established).
Project status and timeline
- Current status: mainnet (the token on Ethereum).
- Key releases/milestones: —.
- Roadmap: see links_* (Medium post with a roadmap).
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? the Tier‑1 website mentions AI as part of the set of technologies/solutions.
- What is truly onchain? the confirmed onchain artifact is the TRL ERC‑20 token on Ethereum.
- Why is a token needed? The whitepaper describes the token system and a staking program; whether the token is mandatory for access to/operation of the product requires separate Tier‑1 confirmation.
- Red flags (based on the information found): mention of AI without metrics/architecture; mixing the SaaS description and “onchain” without explicit necessity.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | medium | 2 |
| Token necessity | low | 1 |
| Evidence | Tier‑1 present | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): The Tier‑1 website mentions Artificial intelligence in the list of technologies.
- Evidence: Tier‑1 — https://www.triall.io/
- Why sufficient / why not (one line): This is a mention/intent; it does not prove metrics/architecture of the AI part.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): What exactly the AI part of the product does is not established per Tier‑1.
- Evidence: Tier‑1 — https://www.triall.io/
- Why sufficient / why not (one line): There is a general mention of AI, but without a description of a specific function/module.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): A public reproducible demo of the AI part is not recorded per Tier‑1.
- Evidence: Tier‑1 — https://www.triall.io/
- Why sufficient / why not (one line): A verifiable “what you can touch” scenario is needed.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://www.triall.io/
- Why sufficient / why not (one line): No quantitative quality metrics for the AI part were found in the available Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): The tech description/architecture of the AI part is not established per Tier‑1.
- Evidence: Tier‑1 — https://www.triall.io/
- Why sufficient / why not (one line): There is no sufficient tech description to set 1.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: token contract 0x58f9102bf53cf186682bd9a281d3cd3c616eec41
- Evidence: Tier‑1 — https://etherscan.io/token/0x58f9102bf53cf186682bd9a281d3cd3c616eec41
- Why sufficient / why not (one line): The existence of the token and an observable contract in the explorer confirms an onchain artifact.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: The whitepaper describes blockchain‑enabled eTMF (Verial eTMF) and “blockchain‑secured verifiable proofs of clinical data” as part of the solution.
- Evidence: Tier‑1 — https://uploads-ssl.webflow.com/63319a2d0a41c733a9d60da7/63e3cd5943813b4d24a35cb7_Triall-Whitepaper-v2.1.3-August2021.pdf
- Why sufficient / why not (one line): The Tier‑1 whitepaper describes the use of the blockchain as a mechanism in the product, not just token issuance.
- 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 onchain.
- Evidence: Tier‑1 — https://www.triall.io/
- Why sufficient / why not (one line): OC_3=1 requires an explicit justification of “replacing the blockchain”; it is not recorded in this card.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, TRL (ERC‑20).
- Evidence: Tier‑1 — https://etherscan.io/token/0x58f9102bf53cf186682bd9a281d3cd3c616eec41
- Why sufficient / why not (one line): The token and its contract are observable in the Tier‑1 explorer.
- 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): The use of the token as a mandatory payment for the service is not established per Tier‑1.
- Evidence: Tier‑1 — https://www.triall.io/
- Why sufficient / why not (one line): 1 requires an explicit Tier‑1 mechanism for payment/access via the token.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): The whitepaper indicates changes to the token system, including a staking program and a secondary token (T‑CRED).
- Evidence: Tier‑1 — https://uploads-ssl.webflow.com/63319a2d0a41c733a9d60da7/63e3cd5943813b4d24a35cb7_Triall-Whitepaper-v2.1.3-August2021.pdf
- Why sufficient / why not (one line): A staking program is a direct sign of incentives/rewards/collateral in the token model (Tier‑1).
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): No Tier‑1 confirmation of the governance role of the token was found.
- Evidence: Tier‑1 — https://www.triall.io/
- Why sufficient / why not (one line): 1 requires an explicit governance process/documentation.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token without loss of meaning is not established per Tier‑1.
- Evidence: Tier‑1 — https://www.triall.io/
- Why sufficient / why not (one line): There is insufficient data on the role of the token in the product.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.triall.io/ | Product description (clinical trials software/services) and mention of AI in the set of technologies. |
| Tier‑1 | https://uploads-ssl.webflow.com/63319a2d0a41c733a9d60da7/63e3cd5943813b4d24a35cb7_Triall-Whitepaper-v2.1.3-August2021.pdf | Project whitepaper (context and claims). |
| Tier‑1 | https://uploads-ssl.webflow.com/63319a2d0a41c733a9d60da7/63e3cd5943813b4d24a35cb7_Triall-Whitepaper-v2.1.3-August2021.pdf | Whitepaper: blockchain‑enabled Verial eTMF and “blockchain‑secured verifiable proofs of clinical data”. |
| Tier‑1 | https://uploads-ssl.webflow.com/63319a2d0a41c733a9d60da7/63e3cd5943813b4d24a35cb7_Triall-Whitepaper-v2.1.3-August2021.pdf | Whitepaper: changes to the token system (T‑CRED, staking program). |
| Tier‑1 | https://etherscan.io/token/0x58f9102bf53cf186682bd9a281d3cd3c616eec41 | The existence of the TRL ERC‑20 token on Ethereum (contract/network). |
| Tier‑3 | https://coinmarketcap.com/currencies/triall/ | Token profile on an aggregator (context; not proof). |
No comments to display
No comments to display