# Nozomi (@NozomiNetwork) on x

- id: koinon:creator:x_nozominetwork
- url: https://koinonlink.com/kol/x/NozomiNetwork
- schema_version: 1.4

## Identity
- platform: x
- handle: NozomiNetwork
- platform_url: https://twitter.com/NozomiNetwork
- website: http://www.nozomi.network
- entity_type: creator
- person_id: Cross-platform identity not resolved for this creator.

## Reach
- followers: 2847
- following: 143
- posts_total: 9558
- posts_observed: 17
- posts_per_day: 11.325
- account_age_days: 844
- verified: true
- size_tier: nano

## Engagement
- status: peak_post_only
- peak_post_engagement_rate: 0.00948
- best_post_interactions: 27
- measurement_source: x_post_interactions
- measurement_formula: interactions on one post — likes, or likes + reposts + replies depending on the discovery path (the two are not distinguishable in the stored data)
- comparable_pool: peak_interactions
- status_note: We have only the single best observed post, so no mean exists. peak_post_engagement_rate is an UPPER BOUND, systematically higher than an average — never compare it against an average rate.
- unit_note: engagement_rate and peak_post_engagement_rate are ratios (0-1); avg_interactions_per_post and best_post_interactions are absolute counts. Read status before reading any number: a null rate has several different causes and status says which one applies here.

## Content
- category: finance
- subcategory: crypto
- category_confidence: 0.9
- category_source: derived_from_recent_content
- topics: Web3 fundraising patterns and credibility, Traction vs roadmap discussions, Runway and bottom-up vs top-down raises, GTM advisory and community raises
- bio: 🌸 The Home of Web3 Founders🌸 
🌸 GTM Advisory, VC intros, Community Raises 🌸

## Audience (inferred)
- status: present
- description: Web3 founders and early-stage startup teams actively raising funds or seeking GTM/community raise advice
- roles: sales
- seniority: decision_maker
- pain_points: Losing credibility by giving inconsistent answers across pitch questions, Over-relying on roadmap talk when traction is weak, Unclear runway planning that signals top-down vs bottom-up approach
- posts_analysed: 3
- confidence: 0.4

## Commercial (inferred)
- audience_buyer_fit: 0.8
- promotion_intent: 0.7
- open_to_collaboration: false
- contact: Koinon does not publish creator contact details.

## Quality signals
- authenticity_score: 69
- authenticity_basis: engagement_observed
- credibility_score: 69
- flagged_for_review: false
- koinon_bd_grade: A — measures Koinon partner-outreach fit, not creator quality
- interpretation: Signals for triage, not verdicts. A flag means the profile is worth a manual check.

## Evidence
- [x_nozominetwork#7cc60e2c] One of the easiest ways to spot whether a raise was built top-down or bottom-up: Ask about the runway. Top-down founders: "We want 18 months". Bottom-up founders: "We need 14 months to hit this milestone, plus 4 months of buffer because legal and engineering timelines slip". Same (https://twitter.com/NozomiNetwork)
- [x_nozominetwork#7aaf997b] The easiest way to lose credibility in a fundraising meeting: Give a different logic for every question. Why this amount? One answer. Why not less? Different answer. Why not more? Different answer. Strong founders have one underlying reason. Everything traces back to the mileston
- [x_nozominetwork#6b2fbb5d] A Web3 fundraising pattern: The weaker the traction, the more founders talk about the roadmap. The stronger the traction, the more founders talk about users. Investors notice this too. That's why the conversation eventually ends up on adoption, revenue, retention, or usage. The m

## Provenance
Every inferred field below carries how it was produced. Facts stay facts; inferences stay inferences.

- audience.description: source_type=ai_inferred, confidence=0.4, freshness_days=76, method=llm_persona_from_recent_content
- audience.roles: source_type=ai_inferred, confidence=0.4, freshness_days=76, method=llm_persona_from_recent_content
- audience.seniority: source_type=ai_inferred, confidence=0.4, freshness_days=76, method=llm_persona_from_recent_content
- commercial.audience_buyer_fit: source_type=ai_inferred, confidence=0.6, freshness_days=80, method=llm_scorer — Relative signal within Koinon indexing, not a market-wide score.
- commercial.promotion_intent: source_type=ai_inferred, confidence=0.6, freshness_days=80, method=llm_scorer
- quality.anomaly_flags: source_type=heuristic, confidence=0.5, freshness_days=108, method=profile_snapshot_and_engagement_ratio_heuristic — Means "worth a manual check", NOT confirmed fraud. Flags can be wrong and are not a verdict about the person.
- quality.authenticity_score: source_type=heuristic, confidence=0.5, freshness_days=80, method=Profile-shape heuristic from a single snapshot (follower count, following ratio, account age, posting volume, verification), reduced for engagement red flags where post engagement was collected. Where only a follower count is available the score saturates at 58. — The input set differs by platform; do not compare this score across platforms.
- quality.koinon_bd_grade: source_type=ai_inferred, confidence=0.5, freshness_days=108, method=llm_partner_fit_classifier + fit_score >= 0.6 AND authenticity >= 60 => A; fit_score >= 0.4 AND authenticity >= 45 => B; else C. authenticity < 30 or a promotional-pattern flag => quarantine. — Koinon partner-outreach fit, not creator quality.
- reach.followers: source_type=observed, confidence=0.95, freshness_days=108, method=platform_profile

## Freshness
- profile_checked_days_ago: 108
- content_analysed_days_ago: 80
- audience_updated_days_ago: 76

## AI retrieval
- indexing_requests: 10
- user_triggered_requests: 0
- note: Being indexed in bulk is not the same as being retrieved to answer a question.

## This profile
- Claim or correct: https://koinonlink.com/claim?k=x_nozominetwork
- Request removal: https://koinonlink.com/claim?k=x_nozominetwork
- Terms: https://koinonlink.com/for-ai