Detection & launches
From a monitored signal to an automated pairing.
Launches are intended to be operated by Exposure’s engine. The market browser is where users discover them.
Discovery inputs
The working design uses two inputs: activity from monitored serial deployers, and a tweet tracker. These feed the narrative-detection process.
A signal is a starting point. It still needs to be interpreted, matched to a market and handled by the launch rules.
Automated by Exposure
The proposed engine seeks and copies a detected narrative with its respective market pairing. That is why the platform has no visitor-facing Create feature.
A new coin should be paired with its relevant market token. In the working example, an Elon-related narrative becomes FLOKI / ELON, rather than replacing the base ELON / exposure market.
“Copy” describes the narrative-launch concept. It does not mean an external project’s original contract, liquidity pool or ownership is automatically transferred to Exposure.
Rules still to finalize
The implementation needs explicit rules for monitored sources, duplicate narratives, market assignment, launch conditions, failures and launch timing. These rules have not been finalized in this documentation.
The website does not yet monitor wallets or tweets, submit transactions, create contracts or deploy pools. See Product status for the current status of the website and launch engine.