Flint Trade: quoting infrastructure for Solana market makers, with SpreadProtect leaving execution to the user

This review uses the source record dated 2026-10-12. Announcements describe that period and should not be read as current mint or participation invitations.

What is the project

Flint Trade aims to connect a Solana market maker's quoting logic to ready-made transaction infrastructure. In sources dated September 6, 2026, the project says its infrastructure handles gas, priority fees and transaction delivery, while pricing logic belongs to the market maker.

According to an official announcement, taker flow comes from aggregators such as Jupiter, DFlow and Titan. The market maker supplies its own prices and connects its quotes to a server; Flint operates the prop AMM layer between them. This product description does not describe the same use as an investment product someone joins simply by purchasing a token.

No transactions were made through an account connected to the infrastructure for this review. Quote refresh speed and its cost have therefore not been measured beyond the scope described by the product.

What the project says

Flint introduces three quoting strategies. OrderList is described for new listings without a reliable price source; OracleOffset for liquid pairs with a reliable oracle; and LinearDistribution for wide, more passive price ladders. The project's message is that the market maker decides which logic to use.

SpreadProtect is a concrete example of this separation. The announcement says a repricing transaction may arrive late during upcoming slots led by a validator with poor network topology. The service sends a slot interval and spread multiplier in advance. It explicitly calls this an advisory: the market maker's software may apply, scale or ignore the suggestion.

SpreadProtect is therefore not described as a mechanism that automatically protects a user's quote or prevents losses. There is a decision point between the signal produced by the product and the strategy applied by the user's software.

A separate security announcement says the admin key stays cold, quoting uses a hot key, withdrawals require separate authority and dashboard logins are read-only. These are the permission boundaries reported by the project; key permissions and contract implementation were not verified independently in this review.

Team and funding

The official account announces work with Asymmetric Research to complete a STRIDE assessment. This wording should not be read as a completed report, a favourable audit result or a funding round announcement; no such outcome is shared in that source.

What to watch

The report and scope of the STRIDE work matter for the next check. Key permissions, which key signs which transaction and withdrawal boundaries should also be examined separately using an operational account.

For quoting infrastructure, a speed claim alone is insufficient: refresh costs, transaction delivery conditions and how SpreadProtect suggestions are applied should be explained. Example price screens on the site were not turned into realized trading performance for a market maker in this article.

Conclusion

Flint's official account describes market makers retaining control of their strategy while using external Solana transaction infrastructure. Implementation of SpreadProtect suggestions and the practical effect of the stated security boundaries were not independently tested in this article.