Confidential · Internal Prep · Do Not Distribute

MSC × Kintsugi — Technical Sync

Dimi (CTO) ↔ Khoosoo (MSC) · Daniel facilitating · Wed Jun 10, 2026

MOU v2 — EXECUTED Mutual NDA — EXECUTED 6/7 Injective — pre-submission

      Paper is done — MOU and NDA both signed. Wednesday is the
      Dimi ↔ Khoosoo technical sync: get MSC’s motocross data into Dimi’s hands,
      agree the on-chain attestation pipeline, and shape Milestone 1
      (“live pipeline”) — without pinning its date (that’s gated on Injective’s KPI schedule). Your job on
      the call is to facilitate, keep it on the data, and protect the two terms that stay open.
    

01 What to get done on the call

This is a build session. Items 1–3 are the technical wins; 4 is shape-not-date; 5 closes the loop.

Get the data into Dimi’s hands UNBLOCK THE BUILD

The whole pipeline is downstream of one thing: a real MSC feed Dimi can work against. Jun 4 Iron Horse motocross data is already-published results → not gated by MSC’s legal read, so it can move now.

› API or file/export? › What schema / fields / formats? › Can MSC hand a Jun-4 sample feed to Dimi this week?

› The Chinese data system is being translated to MN/EN — what does it output, and in what encoding?

Agree the on-chain attestation pipeline DEFINE THE PATH

Injective’s oracle module is near-zero lift on their side: injective-price-oracle (Go binary, dynamic TOML feeds, governance-gated relayer). Map MSC feed → relayer → attested + queryable on Injective. Settle the boundary: who runs the relayer, where the feed is hosted, push cadence.

MSC feed→LocalTruth adapter (Dimi)→injective-price-oracle relayer→attested on Injective

Scope transponder + live-data ingestion SPEC IT

MSC is testing a transponder/timing system for motocross, with intent to extend to horse racing — a Mongolia-first if it lands, and the real data-quality story.

› Transponder output format + latency? › The arena broadcast runs a 30-sec delay for data protection — does that delay also gate the feed we ingest?

Gate flag: live transponder ingestion waits on MSC’s Mongolian legal read (public-chain publication where downstream use is real-money betting). Published results don’t. So: build the pipeline on Jun-4 results now, design for live ingestion later.

Shape Milestone 1 — but don’t date it SHAPE, NOT DATE

Milestone 1 (firm) per the Terms Module = MSC event data attested on-chain through the automated relayer — not a manual one-off — and queryable on Injective, for ≥1 event series. Use the sync to agree what technically counts as “done.” Do not set the target date — it’s “not earlier than the Injective milestone that funds the build,” and Injective’s KPI schedule isn’t firm yet.

Set cadence + next step CLOSE THE LOOP

Leave with: who owns what before the next sync, a target for first data on-chain (~Jun 10 if the sample lands), and a read on the on-site Mongolia working session. Hand Dimi and Khoosoo a direct channel so they don’t route everything through you.

02 Where we stand — both papers signed

No admin left. This is the operative state going into the sync.

MOU v2EXECUTED (DocuSign 541C4F56…). Khosbayar 6/7, Daniel 6/5. Binding: §4 Confidentiality · §5 Data license · §9 Exit. Splits 70/30 + 80/20 are reference floors, not binding.

Mutual NDAEXECUTED 6/7 (DocuSign BDE903D2…). Both Founders/CEOs. Singapore law, 2-yr term + 3-yr survival. §5 keeps data licensing OUT — that’s the MOU’s job. Covers data formats, transponder/timing, on-chain pipeline, commercial terms.

Terms ModuleDrafted (Jun 6) to settle the two open items — milestone dates + “real revenue.” Dates + de-minimis figure left BLANK on purpose, pending Injective KPIs + this sync. Drops into the definitive agreement later.

License scope (§5, binding)

Motocross + summer horse racing only. Delayed data first, live transponder later. Revocable: 12-mo “real revenue” checkpoint, with on-chain-permanence carve-out (already-attested data stays immutable; only future attestation stops).

22 federations

Scoped OUT — separate later conversations. Don’t widen scope in the sync.

03 Talking points & context

Open — set the room for a build session

“Both docs are signed, so let’s not spend this on terms — let’s get Dimi looking at real motocross data and figure out how it lands on-chain.”

Keep Khoosoo in his register

Math undergrad; engages on specs deeper than typical sports-side counterparts. Let him and Dimi go technical — don’t flatten it.
But he sells on ecosystem / global framing (“Polymarket / Kalshi go global, Mongolia gets prepped first”), not chain-tech. Frame the build as the proof that unlocks that.
MSC pays for data (Sportradar + Genius) and monetizes nothing yet; no formal CTO. The on-chain pipeline is the wedge that turns his cost center into a product — and Dimi is the standing engineering arm he doesn’t have.

Injective — relay accurately, it gates Milestone 1

If it comes up: structure + envelope locked ($50–60K convertible, KPI-gated, oracle slice $20–25K),
      Achilles reviews the refined KPI doc Mon Jun 8, official submission after — verbally strong, not yet approved.
      Don’t say “funded.” It matters here because the Milestone 1 date can’t be set until Injective’s KPI schedule firms.
      Note: the long-pending Dimi × Injective technical sync is a separate thread — flag if it should ride alongside this.

04 Do-not-say / landmines

📅

Don’t set the Milestone 1 date. Shape what “done” means technically; leave the date blank. It’s downstream of Injective’s KPI schedule.

🚫

Don’t call the Injective grant “approved” or “funded.” Pre-submission. “Verbally strong, in final KPI refinement.”

🛰️

Don’t commit to live transponder data on-chain yet — it waits on MSC’s Mongolian legal read. Only already-published results move now. Design for live, ship on published.

🪙

Don’t headline token-as-revenue. It’s in the Terms Module as one line, kept soft — collides with the same betting/securities legal read. Let Khoosoo raise it.

🤐

His name is fine in direct-party docs but not cleared for wide external decks. Don’t commit to public naming without consent (via Georgina/Taivan).

🔗

Don’t reopen the 22 federations or widen scope. The signed MOU parked them. Stay on motocross + summer horse racing.

05 Open threads to leave with

MSC owns

Sample Jun-4 motocross feed to Dimi. Confirm API + formats + transponder spec. Run the Mongolian legal read on live-data publication.

Kintsugi / Dimi owns

Build the adapter + relayer path against the sample. Target first data on-chain ~Jun 10. Offer plain technical description for MSC’s counsel.

Joint — TBD

Milestone 1 date (after Injective KPIs). “Real revenue” definition + de-minimis figure. On-site Mongolia working session date.

Watch

Injective: Achilles reviews Mon Jun 8 → submission → KPI schedule firms. That unblocks the Milestone 1 date.

06 Counterparty cheat-sheet

Who

Bat-Erdene Khosbayar (“Khoosoo”) — Founder/CEO, Mongolian Sports Corporation. Math undergrad, Univ. of Mongolia. Sports mgmt in Switzerland + Saudi before MSC. Is the technical lead on MSC’s side — no separate “Hassan.”

Don’t confuse

Two Bat-Erdenes. Khoosoo = MSC (counterparty). Bat-Erdene Dashdemberel = Ajnai / Capitron / MEA (unconsented lead). Also MSC ≠ MEA (the equestrian federation).

MSC = what

Mongolia’s only sports-management co (~2021). 14 FT staff, 22 federations. Owns motocross + summer horse racing data outright; only a conductor on Naadam.

Iron Horse motocross

5-round league. Team Yamaha (4× world champ) + Team KTM. 1.9km track ~50km from city. Arena broadcast + 30-sec delay for data protection. Chinese data system being translated to MN/EN.

Card deals

Panini (postponed) + Coyo (China’s largest collectible-card co). Relevant to the NFT-card line.

HKJC bridge