Explore Hub: Exchange Listings

The primary keyword for this update is MOONSHOT pre-IPO perpetual. Bybit announced on August 7, 2026 that it will list the MOONSHOTUSDT Pre-IPO Perpetual Contract, allowing leveraged exposure to Moonshot AI (the company behind the Kimi AI assistant) before its anticipated IPO. The call auction starts at 11:00 a.m. UTC on August 7.

What Happened

Contract specs include a 0.01 tick size, up to 10x leverage, USDT settlement, an estimated share count of 1,000,000,000, and a funding rate capped at 0.005% every 4 hours during the pre-IPO period before reverting to the standard mechanism.

The event dates above come from the cited sources; this page was checked against those sources on August 8, 2026 UTC before publishing. The event date and the publish date are intentionally separated: the event date comes from the cited source, while this page is published in UTC during the August 8 news window.

Why It Matters

For CryptoSigy, the useful angle is contract specification and early liquidity risk rather than AI-stock direction. Pre-IPO perpetuals are synthetic, do not grant share ownership, are subject to a Rebase when the share count is confirmed in an S-1 filing, and can be delisted or settled if the IPO is canceled or restructured.

The owner fit controls the framing. Exchange and venue events stay on CryptoSigy as listing, liquidity, fee or contract-risk context; protocol and ecosystem events stay on Radar when the useful question is chain operations, governance or security infrastructure.

What To Watch Next

Watch the call auction behavior, first-session depth, the funding cap transition after conversion, leverage limits, and any Rebase or settlement announcement from Bybit.

If the official source updates contract specs, fee terms, deadlines, block heights or protocol details, rebuild the decision from the updated source rather than from a stale headline.

The editorial filter is exchange listing, pre-ipo perpetual spec, liquidity and leverage risk control.. Treat this as decision context, not as a prediction, recommendation or promotional note.

Date discipline matters: published and updated timestamps are generated at publish time in UTC, while event dates in the body come from the cited source.

Risk reminder: betting and crypto decisions can cause financial loss. Use official sources, keep stakes or position sizes controlled, and avoid treating one update as a complete strategy.

Before acting on the update, compare the official notice with the live product, market or protocol surface. If contract specs, fee terms, route availability, lineup status or governance details differ, the live source should override the older assumption.

The practical output is a watchlist, not a verdict. Readers should know which timestamp, rule, venue field or protocol dependency must be checked next before the update has any operational value.

Continue this cluster

Continue this cluster with related source-backed updates that keep the same owner-specific decision frame.