DKING → SIRE AMA

The Spaces focused on the final hour of the DEKIN to SAYA token migration, the exact claiming flow, and the roadmap after relaunch. Max (founder/CEO of Score and core contributor to Saya) and Phil (co-founder of Creatorbid) detailed the cutover: once the countdown ends, DEKIN migration closes, liquidity is removed, ETH is converted to USDC, a new SAYA/USDC pool is deployed on Aerodrome (Base), and claiming becomes immediately available via the same Creatorbid relaunch page using the same wallet. Over 83% of supply had migrated at the time of the call. A snapshot at deadline ensures late users can claim 1:1 via a follow-up process coordinated on Discord; do not send tokens to contract addresses. Short-term, a light front end may omit some metrics due to The Graph’s ~24h sync, but trading and claiming will work. Strategically, Saya is launching a Base mini app, seeking Aerodrome whitelisting/incentives, and unveiling Saya v1: a new prediction engine based on Dr. Peter Cotton’s MicroPrediction, where AI agents compete on embeddings while humans supply novel information. Saya will act as both taker and maker across prediction markets, starting with SX Bet, expanding to others, opening new vaults per sport, and adding US sports, tennis, and cricket. Team credibility, legal clarity, and cautious comms (official links only) were emphasized.

Saya relaunch and token migration — full session notes

Participants and roles

• Max — Founder and CEO of Score; core contributor to Saya (formerly operating under DeKing prior to this relaunch). Host of the session.
• Phil — Co‑founder of Creatorbid (the platform running the migration/claim UI and contracts).
• Ghost — Investor/advisor; large Saya holder; represents communities of AI‑enthusiast traders/investors.
• Dr. Peter Cotton — Co‑founder and lead quant behind Saya’s prediction engine; author of MicroPrediction (referenced extensively; not present on the call).
• Community members who engaged or attempted to: Ty, 0,0, Blaziken, Web3 Grandma, Barnstorm, Meme Katsu (asked about staked tokens).

Migration and claim process

Status and deadlines

• Migration window: At the start of the Space there was ~50 minutes remaining; later, ~10 minutes to go.
• Adoption: ~83% of DeKing supply had been migrated into the migration contract by the time of the session, which the team considers a successful uptake.

What happens at countdown end

• Migration function disabled: Once the countdown ends, the Migrate function stops. Do not send DeKing tokens directly to any contract address; transfers to contract addresses are not recoverable.
• Snapshot: Creatorbid’s contract/process takes a snapshot at the end of the window to record holdings and migrations, enabling a safe post‑deadline path for those who missed the cutoff.
• Liquidity operations (automated via the migration contract):
  • Remove liquidity from the DeKing pool.
  • Convert the recovered ETH to USDC.
  • Deploy the new Saya token and seed a new Saya/USDC pool.
• Immediate claims: After liquidity removal and new pool deployment, the Claim flow becomes available. Users can claim Saya 1:1 for migrated DeKing using the same wallet they used for migration. Claiming should be available within the hour after countdown end, essentially immediately following the automated steps above.

Where to migrate/claim

• Single official flow: Creatorbid relaunch page (Creatorbid > Agents > Relaunch). The same page switches from “Migrate” to “Claim” once ready. Always use official links shared by the team.

Front‑end/graph indexing caveat

• The Graph indexing delay: Some dashboard elements (e.g., Treasury amount, endorsements, staking data, leaderboard) may not reflect immediately due to a ~24‑hour Graph sync time.
• Creatorbid will serve a lightweight front end at launch enabling:
  • Claiming Saya
  • Trading and chart visibility
• Temporarily delayed UI elements:
  • Treasury metrics
  • Endorsements
  • Staking
  • Leaderboard visibility
• Core actions (claim/migrate/trade) are unaffected.

Post‑deadline path for late/missed migrations and staked positions

• The team will open a support path (via Discord ticket) for holders who missed the migration or have tokens locked in staking/unstaking cycles.
• Process (as described by Max):
  • Team uses the snapshot to confirm your DeKing balance at countdown end.
  • They allocate a 1:1 Saya entitlement to the project’s treasury wallet on your behalf.
  • You’ll be asked to send DeKing to a specified burn/recovery address when able; upon confirmation, the team releases your corresponding Saya.
• No hard final deadline yet: Max emphasized patience and community fairness. A final disposition date (if ever needed) would likely be a community decision. In the near term, the priority is making whole any legitimate holder who missed the window.

Exchange/liquidity and Base ecosystem plans

Launch venue and incentives

• Pool venue: Saya’s initial liquidity will launch on Aerodrome (Base).
• Whitelisting and incentives: The team is coordinating with Aerodrome to get the Saya/USDC pool whitelisted early to access liquidity incentives. They are also working closely with the Base team.

Base App mini‑app

• Saya has been invited to the Base App beta and is building a Saya mini‑app for distribution within the Base App. This aligns Saya with the Base ecosystem as a first‑class builder and is seen as strategically “super bullish.”

Technology roadmap — Saya v1 (major engine upgrade)

From DeKing to Saya v1: what’s changing

• The relaunch is not just a token migration/rebrand; it ushers in a fundamentally new prediction engine (“Saya v1”), slated for late September if timelines hold.
• Legacy approach (v0.x):
  • Traditional modeling and “competition” style approaches among human ML engineers (akin to common ML competitions).
  • Community‑contributed modeling used both in early subnets and earlier versions of the agent.
• Saya v1 approach (inspired by Dr. Peter Cotton’s MicroPrediction):
  • AIs compete with each other to discover and refine information in embedding space.
  • Human ML engineers focus on injecting novel, high‑quality information rather than trying to “beat” the models directly.
  • Emphasis on information acquisition and integration, leveraging advances in LLMs that can already extract and structure vast web‑scale information.
  • The team is preparing a paper describing the mechanism; they described it as a new system not yet built elsewhere.

Role of Score’s subnet (computer vision) vs. Saya (prediction agent)

• Clear separation of concerns:
  • The subnet (by Score) performs computer vision, outputting structured data (e.g., player positions on the field), which are high‑value features for modeling.
  • Saya (the agent) ingests those and many other features to make predictions and manage strategy.
• Saya is a customer of the subnet; they are not duplicating products. Data from the subnet remains crucial as a strong signal among many inputs to Saya v1.

Tokenomics linkage between Saya and the subnet

• Because Saya leverages “Subnet 44” data/capabilities, Saya’s tokenomics include buying Subnet 44 tokens (using a portion of performance/management fees) to compensate the subnet and align both projects.
• Result: The Saya treasury will accumulate Subnet 44 tokens as part of this flywheel.

Why switch now? Tech readiness

• The team emphasized the switch to the MicroPrediction/LLM‑centric framework is driven by the pace of LLM capability improvements.
• In short: the technology has reached a readiness point where this approach should materially outperform traditional methods, especially where broad information collection matters (sports, certain commodities, etc.).

Scale and new sports

• With Saya v1, integrating new sports is primarily a matter of attaching new APIs/data feeds.
• Planned additions: American sports, tennis, cricket, and more. Each sport will be paired with its own vault(s).

Prediction markets strategy (maker and taker)

Base and Coinbase ecosystem

• The team is already in constructive dialogue with Base; they intend Saya to be a highly active token/project on Base. Coinbase/Base will publish their own comms separately.

Taker and maker roles

• Saya v1 agents will:
  • Taker: Execute bets on venues like Polymarket and web3 sportsbooks.
  • Maker: Create markets where feasible, acting as market makers to source better pricing and earn maker fees/spreads when appropriate.
• Impact: Being both maker and taker improves capital efficiency and access to liquidity, which the team identified as a critical constraint in web3 betting markets.

Venue integrations and routing

• First integration for automated execution: SX Bet (chosen for early engagement and a strong API).
• Expansion plan: Add Polymarket and other prediction/sportsbook venues; goal is to route and execute across multiple venues to aggregate liquidity and optimize outcomes.
• Business development: The team welcomes introductions to web3 sportsbooks and will reward valuable integrations to accelerate coverage.

Community, communications, and safety

• Only use the official Creatorbid relaunch page for migrate/claim.
• Do not send tokens to contract addresses or random addresses post‑deadline; these funds are likely unrecoverable.
• The team will publish more Spaces, including a dedicated tech deep‑dive with Dr. Peter Cotton to explain the new LLM‑driven mechanism.
• Team transparency: Ghost urged more proactive storytelling about the team’s credentials to combat “meme coin” assumptions. Max agreed; with legal/rebrand hurdles cleared, they plan to be more vocal about the team and partnerships (including a hedge fund collaboration to be disclosed when possible). The message: Don’t trust—verify; the team will provide proofs.
• Merch: Saya merchandise drop is imminent via the website.

Q&A highlights

• Post‑deadline migration (Meme Katsu’s case: tokens still staked):

  • Covered via a Discord support route; snapshot protects entitlements; 1:1 Saya allocation will be honored once DeKing is sent to the designated address. No immediate hard deadline to claim.

• What happens to unmigrated supply after the window?

  • Unmigrated DeKing reflected via snapshot and handled via the post‑deadline claim process. A final cutoff is not set; likely a community decision in the future. The priority is fairness and allowing reasonable time for holders who weren’t online.

• How exactly does Saya pay the subnet, and what does “subnet pays Saya” mean?

  • Clarified: Saya consumes subnet data as a paying customer. Through tokenomics (performance/management fees), Saya buys Subnet 44 tokens—creating an economic loop. Saya’s treasury will hold Subnet 44 as part of that linkage.

• Claim timing specifics:

  • Claim is enabled immediately after automated steps: DeKing liquidity removal, conversion to USDC, and deployment of the Saya/USDC pool. Use the same wallet as migration.

• Front‑end availability and missing metrics at T0:

  • Light UI goes live on Creatorbid for claim and trade; Graph‑dependent metrics (treasury, endorsements, staking, leaderboard) may render within ~24 hours post‑launch.

• Why transition to Peter Cotton’s MicroPrediction‑inspired approach now?

  • LLMs have matured; information collection is as critical as modeling. The new AI‑vs‑AI competition in embedding space plus human curation of new information is expected to deliver step‑change performance.

• Venues and routing details:

  • Initial execution via SX Bet; rapid expansion to Polymarket and other venues. Agents will both take and make markets to improve liquidity access and returns.

Key takeaways and action items

• Immediate user actions:

  • If you haven’t yet claimed: Watch the Creatorbid relaunch page; claim unlocks right after the automated liquidity steps. Use the same wallet used for migration.
  • If you missed the window or your tokens are staked/unstaking: Open a Discord ticket; the snapshot covers you for a 1:1 Saya allocation once you complete the recovery steps.
  • Safety: Only use the official Creatorbid page; never send tokens directly to contract addresses.

• Near‑term milestones:

  • Claim live within the hour after countdown end (pool: Saya/USDC on Aerodrome/Base).
  • Graph‑backed UI metrics (treasury/endorsements/staking/leaderboard) to populate within ~24 hours.
  • Increased comms on Base/Aerodrome whitelisting and liquidity incentives.
  • Tech deep‑dive Space with Dr. Peter Cotton.
  • Merch drop via the website.

• Medium‑term roadmap:

  • Saya v1 engine release targeted for late September (subject to change).
  • Addition of new sports (American sports, tennis, cricket, etc.) with corresponding vaults.
  • Broadened venue integrations (SX Bet -> Polymarket and others); build both taker and maker capabilities.
  • Continued alignment with Base ecosystem, including the Saya mini‑app in Base App beta.