# What is Juno? *** Juno is a signal-native interface built for the Solana ecosystem. It focuses on making wallet-level activity interpretable by surfacing structured moments and reducing unnecessary complexity. #### Purpose The blockchain is fast, dense, and reactive. Most tools mirror that.\ Juno does the opposite. It listens slowly and filters hard.\ Its purpose is to show only what matters, token movement, risk behavior, timing shifts, and high-context events tied to addresses you care about.\ It doesn’t react to volatility. It reflects on behavior. *** #### Identity Juno is not a portfolio tracker. It is not a signal group or price scanner.\ It doesn't trade, speculate, or alert for the sake of attention.\ It is designed to sit quietly beside a wallet, observe the movement around it, and summarize what it sees with intention. Everything about it is built for signal recognition, not metrics. *** #### Philosophy Juno believes attention is expensive. Interfaces should reduce cost, not add to it. It removes unnecessary metrics, hides irrelevant data, and avoids drawing conclusions for the user. Instead, it gives structured, minimal context that invites interpretation. Its goal is not to tell you what to do. Its goal is to show you what changed, and let you decide. *** #### Name Juno is named after the Roman figure associated with foresight, perception, and protection. Meaning that Juno is always watching, but never interrupting. It stores what matters, speaks when spoken to, and remains silent when there’s nothing worth saying. *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://junonode.gitbook.io/junonode/01-orientation/what-is-juno.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.