https://discord.com/channels/1273861754660851763/1420141981774123029/1561696785863286864

Project Research Dossier: Dataline

Research date: 17 October 2026
Preliminary assessment: Watchlist — product thesis plausible; evidence incomplete.

Eligibility note

The quest requires a project with no public raise and no active ICO/TGE. I did not locate an official announcement of an active token sale/TGE in the primary sources reviewed. However, older official Tearline material discusses paid nodes/node upgrades and reward mechanisms. Since “public raise” is not defined here, eligibility is not confirmed. Please confirm with the verifier whether historical node sales count before submission.

1. Project goal

Dataline presents a unified data layer for AI agents operating across Web3: information from multiple venues and on-chain environments is normalized into a common schema, with confidence/freshness context intended to help agents evaluate responses. This could reduce the engineering burden of integrating fragmented data sources. A confidence score is not a guarantee of truth, freshness, or safe execution.

Earlier official materials under the Tearline name describe FlowAgent for task planning/execution and GhostDriver for browser automation. The sources reviewed do not establish that every earlier component is currently maintained or commercially integrated into the current data product.

Primary sources:

• Official technical overview: https://medium.com/tearline/dive-into-our-full-chain-ai-stack-architecting-the-execution-layer-for-intelligent-e1b77b80662f
• FlowAgent repository: https://github.com/dataline-xyz/FlowAgent-preview
• GhostDriver repository: https://github.com/dataline-xyz/GhostDriver

2. Tokenomics and dilution

In the official sources reviewed, I did not locate an authoritative token ticker/contract, total or max supply, initial circulating supply, allocation table, token price, FDV, vesting cliffs, linear unlocks, emissions schedule, or token-governance controls. FDV and circulating-supply ratios therefore cannot responsibly be calculated.

The unlock model is not modelable from the sources reviewed, not zero. If a token is announced, request the official allocation table and contract/schedule, then model circulating supply at 12, 24, and 36 months under base and high-emission scenarios. Separate unlocked supply from circulating supply and identify minting/upgrade authorities. Do not infer tokenomics from points, node rewards, or community incentives.

3. Verification signals

Public repositories exist for FlowAgent and GhostDriver, allowing code and repository history to be inspected. GhostDriver’s README describes a Chrome extension for natural-language browser automation and notes a modified upstream dependency, which should be included in software supply-chain review.

Not established by reviewed primary sources: independent audit coverage, production uptime/latency, confidence-score calibration, source completeness, sustained paid usage, customer retention, or current maintainer commitments. Public code demonstrates inspectability, not security or product-market fit.

4. Key risks

• Data quality: Confidence scores may be model-generated or heuristic. Without methodology and calibration evidence, they can create false assurance. Request provenance, timestamps, disagreement handling, and benchmarks.
• Technical/security: API compromise, stale feeds, upstream outages, prompt/tool injection, browser-agent misexecution, and dependency vulnerabilities could cause bad decisions or unauthorized actions.
• Execution/adoption: Developers may integrate venues directly or use incumbent data providers. Pricing, latency, coverage, and recurring demand need independent validation.
• Centralization/governance: Dependence on a small operator set for aggregation, scoring, routing, or availability creates censorship and single-point-of-failure risk.
• Incentives/legal: No official token economics located. Historical node/reward mechanics need clarification. Market-data licensing, privacy, financial-promotion rules, and automated trading liability may apply.

5. What would change the assessment?

Request (1) confidence-score methodology and calibration tests; (2) source-level provenance/freshness guarantees; (3) current architecture and service-level metrics; (4) independent security assessment for agent execution; (5) recurring usage/revenue evidence; and (6) written clarification of token plans, node/reward arrangements, and public-sale history.

Disclosure

Holdings, incentives, compensation, and current position: author must complete before publication. This is research, not financial, legal, or tax advice. No price target or return forecast is made.

Methodology

Primary-source-only review of the project-controlled sources above. The official homepage was inaccessible to the research browser. Absence of a found announcement is not proof that no further disclosure exists. Verify eligibility immediately before submission.