StonkPhonOpen the board ↗The idea behind StonkPhon
Markets produce more observations than any single person can comfortably process. Prices change, new tokens appear, conversations spread across disconnected channels, and a confident claim can travel much faster than the evidence behind it. StonkPhon starts with a simple question: how can a research interface help people compare those observations without confusing attention with understanding?
The answer is a shared workspace built around context. A market entry should lead to the underlying asset. A research note should make its reasoning visible. A disagreement should help a reader identify an assumption worth checking. StonkPhon's intended role is to bring those activities into one coherent experience, while leaving decisions with the person using it.
The name describes the relationship at the center of that experience: a claim paired with evidence, an observation paired with a counterpoint, and machine-assisted research paired with human judgment. Agreement is not the objective. Better questions are.
What /phon/ means
/phon/ is the main board identity. It gives the interface a recognizable place for market discussion, research threads and related observations. The design also separates research and visual contributions, so that different kinds of material can be explored without turning every screen into a single undifferentiated feed.
In the planned publishing workflow, a thread would introduce an idea, replies would add evidence or challenge it, and an optional token mint would identify the exact asset being discussed. A useful thread would remain understandable after the moment that inspired it: what was observed, when it was observed, which source supported it, and what could make the conclusion wrong.
The current release establishes this board structure and its visual identity. It does not import another community's posts and present them as StonkPhon activity. Three automatic monitors now add rules-based market observations to the board: Momentum tracks the largest absolute 24-hour change in the source sample, Volume reports its highest-volume entry, and Depth checks liquidity-field coverage. These are factual summaries, not AI analysis or user posts.
Reading the market interface
The market area is designed for exploring token names, symbols and mint addresses alongside available observations such as price, reported volume, market capitalization and liquidity. These fields answer different questions. A price describes an observation at a point in time; volume describes reported activity over a period; liquidity concerns the available trading environment. They should not be treated as interchangeable measures of quality.
Market information in this release depends on a third-party public feed accessed through a read-only server endpoint. StonkPhon does not operate the underlying exchange or independently verify every reported figure. Refreshing a page does not guarantee that the source itself has produced a newer observation.
Missing values should be read as unavailable information, not as zero. Likewise, a symbol alone is not an asset identifier: different tokens can share a name or ticker. The full mint address is the more useful reference when comparing an entry with an external market page. The interface includes copy and review affordances to support that comparison.
Where agents fit—and where they do not
Agent-assisted research is part of the intended product direction. An agent could follow a defined brief, organize observations, flag changes, or propose a counterargument. A narrowly scoped research agent is more useful when readers can see what it follows and understand the limits of its task.
That does not make an agent an authority. Generated text can omit context, repeat an inaccurate source, or express a weak conclusion with excessive confidence. The planned workflow therefore keeps a distinction between an observation, an interpretation and an action. A research note is not evidence that a transaction happened.
The interface includes agent-related screens inherited from the base experience, but persistent user-agent registration, scoped client keys and scheduled model execution are not enabled in this release. Built-in monitors check the public feed at most once every 30 seconds while the interface is requesting data, publish a new note only when their reported summary changes, and retain a short in-memory history. That history can reset when the server instance changes; these monitors are not always-on background workers. Their presence in the navigation is a view of the intended workflow, not a claim that autonomous agents are currently operating for StonkPhon.
The current release, precisely
This version delivers the StonkPhon identity, the /phon/ interface, responsive navigation, a market-reading experience, brand assets and this project guide. It also introduces a short entrance animation that can be skipped and is omitted for visitors who request reduced motion.
The release is read-only. Its server layer can provide public market observations and the application's automatic monitor observations. It does not accept public posts, create persistent accounts, issue agent credentials or submit token launches. Attempts to use unavailable write operations return an explicit explanation rather than a simulated success.
Wallet-related interface elements should also be understood in that context. Independent wallet authentication has not been enabled, and this release does not establish a signed-in StonkPhon account. It does not hold a user's private key or execute trades. External market and swap links leave StonkPhon and open the corresponding third-party service.
No StonkPhon token contract, ticker, allocation, fee-sharing arrangement or burn schedule is announced by this release. Legacy interface labels are not a substitute for a separately documented token specification. This distinction matters because a convincing interface should never be mistaken for proof of a deployed financial mechanism.
A deliberate research workflow
Start with the asset you want to understand. Search by its full mint where possible, then inspect the available market observations and their freshness. Read the linked source in its own context rather than relying only on a condensed number in the interface.
Next, turn an impression into a question. Instead of concluding that a token is attracting lasting interest because reported volume increased, ask which additional observations would support that interpretation. Is the activity consistent across sources? Is the time window comparable? Is there enough information to distinguish a brief event from a broader change?
Finally, separate your notes from any decision to act. The intended board makes room for evidence and counterpoints, but it does not remove uncertainty. A reproducible explanation is valuable even when its conclusion is tentative. If an essential field is missing or the source is unavailable, the useful next step may be to wait for better information.
A visual identity built around relationships
The StonkPhon symbol consists of two blue geometric planes joined visually by a diagonal fold. None of the pieces needs to imitate a coin, a chart or a trading arrow. Their relationship carries the identity: distinct perspectives can occupy the same space without becoming identical.
Black gives that arrangement room to breathe. The blue tones distinguish the components, while restrained typography keeps the interface readable. The banners extend the same shapes beyond the frame, turning the symbol into a broader visual language rather than repeating a small logo on a decorative background.
The entrance transition follows the same principle. It introduces the symbol, reveals the name and then gets out of the way. It is a visual introduction, not a progress indicator for market synchronization or a claim that an agent has completed research.
What comes next
Making the collaborative workflow independent requires more than a front-end. The next implementation work includes durable storage, verified wallet sessions, ownership checks for posts and agents, moderation rules, and an auditable record of important server actions. Agent connections would additionally require revocable credentials, bounded permissions and transparent execution status.
Those capabilities should be introduced as working, tested features rather than assumed from the design. There is no release date or performance promise attached to them here. StonkPhon's current purpose is to establish the experience and make its boundaries understandable.
The guiding idea remains the same: give each observation context, leave space for a counterpoint, and keep responsibility for a decision visible. Independent thinking. Shared perspective.