# MayckO.On (@CreatorsOfChaos) on x

- id: koinon:creator:x_creatorsofchaos
- url: https://koinonlink.com/kol/x/CreatorsOfChaos
- schema_version: 1.4

## Identity
- platform: x
- handle: CreatorsOfChaos
- platform_url: https://twitter.com/CreatorsOfChaos
- website: http://mayckongiovani.xyz
- entity_type: creator
- person_id: Cross-platform identity not resolved for this creator.

## Reach
- followers: 1298
- following: 1290
- posts_total: 8676
- posts_observed: 2
- posts_per_day: 1.422
- account_age_days: 6100
- verified: false
- size_tier: nano

## Engagement
- status: peak_post_only
- peak_post_engagement_rate: 0.00385
- best_post_interactions: 5
- 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: software
- subcategory: devtools
- category_confidence: 0.9
- category_source: derived_from_recent_content
- topics: Distributed financial systems, Provisional finality and credit exposure, Reversal architecture and compensation, ZK hardware acceleration, Post-quantum cryptography infrastructure
- bio: Principal Systems Engineer specializing in post-quantum cryptography, distributed systems, and security-critical infrastructure.

## Audience (inferred)
- status: present
- description: Specialized systems engineers and developers focused on distributed financial systems, cryptography, and ZK hardware optimization
- roles: dev
- seniority: practitioner
- pain_points: Designing liquidity and finality mechanisms in distributed financial architectures, Managing reversals, liabilities, and side effects in irreversible transaction systems, Accelerating ZK proofs via hardware like FPGAs and ASICs with algorithms such as Pippenger's
- posts_analysed: 3
- confidence: 0.4

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

## Quality signals
- authenticity_score: 42
- authenticity_basis: engagement_observed
- credibility_score: 42
- flagged_for_review: false
- koinon_bd_grade: C — 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_creatorsofchaos#b52c03aa] "Liquidity Under Provisional Finality: Availability, Credit, and Exposure in Distributed Financial Systems" by Mayckon Giovani #DEVCommunity https://t.co/MXMnZOclxf (https://twitter.com/CreatorsOfChaos/status/2049241358129594512)
- [x_creatorsofchaos#647ed7a0] "Reversal Architecture in Distributed Financial Systems: Compensation, Liability, and Irreversible Side Effects" by Mayckon Giovani #DEVCommunity https://t.co/lu3DBWGD4L
- [x_creatorsofchaos#6f6de3ea] The ZK hardware race is obsessed with accelerating Multi-Scalar Multiplications (MSM) using FPGAs and ASICs. Everyone implements Pippenger's algorithm to parallelize the bucket accumulations. But here is the semantic blind spot, if your hardware parallelization lacks formal equiv

## 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=110, 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=110, 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=110, method=platform_profile

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

## AI retrieval
- indexing_requests: 13
- 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_creatorsofchaos
- Request removal: https://koinonlink.com/claim?k=x_creatorsofchaos
- Terms: https://koinonlink.com/for-ai