Jester | News

описание

News and announcements for the JesterBot Ecosystem

← к каналу @JestTech

1 053

подписчиков

Охват к подписчикам

11,7%

ERR

Реакции к просмотрам

0,00%

0 на 27 постов

Пересылки к просмотрам

1,07%

Постов в день

1,3

всего 29

Где отзываются чаще

доля реакций к просмотрам

16:34TL;DR? We are not deleting everything and starting again. We spent three years building Jester into something much larger than Jester. The products stay. The technology stays. The community comes with us. The structure around all of it is what is changing.0,00%
16:34Quick FAQ Is Oroboros staying? Yes. Oroboros is staying. It will continue as our perpetual and prop trading frontend, built on top of [REDACTED] infrastructure. The goal is to get Oroboros to v1 and stable before the full relaunch. Is Saylis staying? Yes. Saylis is staying. Saylis remains our onchain markets frontend and will use the same underlying [REDACTED] research, strategy, risk and execution infrastructure as the rest of the ecosystem. Is Crucible staying? Yes. Crucible remains the research and backtesting side of the ecosystem. If anything, it becomes more important as agents increasingly use it to test, compare and optimize strategies before deployment. Is Tesseract staying? Yes. Tesseract remains focused on prediction markets and the broader information/timeline side of the system. Are all the products being renamed [REDACTED]? No. [REDACTED] is the infrastructure and company underneath the products. Oroboros stays Oroboros, Saylis stays Saylis, Crucible stays Crucible, Tesseract stays Tesseract. They are different interfaces and products built on the same underlying system. What happens to Jester? Jester is not just being deleted from existence. The name has simply become too small to describe the entire company. Jester will move closer to its original lineage around strategies, algorithms and intelligence instead of being the name stretched across every product we build. Are my strategies/automations going away? No. We are not throwing away three years of development and starting again. Existing strategy, automation, portfolio, risk and execution infrastructure is what [REDACTED] is being built around. Do I need to move to a completely different platform? No. The whole point is basically the opposite. Oroboros, Saylis and the other interfaces will continue operating while the infrastructure underneath them becomes increasingly unified. Is Telegram staying? Yes. Telegram is another interface into the system. The long-term idea is that the terminal, Telegram, agents, MCP, APIs and third-party applications can all interact with the same [REDACTED] infrastructure. Is this just a new website and logo? No. The branding is probably the least important part. The company structure, revenue model, tokenomics, APIs, agent architecture and positioning are all changing to match what we have actually built. Is the existing JEST token immediately changing? No. Nothing is happening immediately. The full token migration/relaunch comes later, with proper details, snapshot rules, contracts and instructions published beforehand. Do I need to do anything with my tokens right now? No. Do not send them anywhere. Do not respond to someone DMing you claiming you need to migrate early. When there is something holders need to do, we will announce it properly. Are existing holders getting abandoned? No. The point of the migration is to bring existing eligible holders forward into the new structure, not erase the existing community. Is the 2% token fee staying? The tokenomics are being redesigned as part of the relaunch. One of the major goals is to stop making the operating company almost entirely dependent on token trading fees while preserving a strong buyback/value-accrual mechanism for the token. Full tokenomics will be released before migration. Why not just keep the current token and change the company name? Because the current structure is increasingly working against us. It makes operating revenue volatile and makes fundraising, marketing, market-making, partnerships and outside investment unnecessarily difficult. We have outgrown both the original brand and the economic structure around it. Will [REDACTED] have subscriptions? Yes. The current direction is free access plus paid tiers for serious operators, with increased compute, agents, automation, infrastructure access and reduced usage/execution costs. Will agents have to buy subscriptions? Not necessarily. External agents will also be able to consume individual [REDACTED] services through API/MCP and eventually pay for specific capabilities through x402. A machine should be able to pay for the exact thing it needs instead of pretending to be a human SaaS customer. Are you abandoning retail users to chase enterprise? No. Our own products are still important. The difference is that they are no longer the only way [REDACTED] can succeed. A normal trader can use Oroboros while a completely different company embeds the same [REDACTED] infrastructure into its own application. Does this mean Oroboros/Saylis could eventually use the same account and agents? They partially already do, that is the direction. The products are increasingly becoming different surfaces over the same underlying identity, portfolio, research, strategy, risk, agent and execution infrastructure rather than isolated applications. When does all of this actually happen? Gradually. We are already consolidating the technology and branding, but there will not be a full relaunch until Oroboros reaches v1 and is stable, and the API/MCP system is mostly bug free and stable. We would rather launch the new system when it is actually ready than rush a token and branding change. So what am I losing? Ideally, nothing useful. Oroboros stays. Saylis stays. Crucible stays. Tesseract stays. The strategies and infrastructure stay. What changes is the system underneath them, the company around them, and the economics supporting all of it.0,00%
16:34That is also why the [REDACTED] name fits better. Jester still matters, and we are not pretending that the last three years did not happen. Jester is where all of this came from, and the name will continue to exist, albeit closer to its original lineage, around strategies, algorithms and some of the intelligence that started the entire project. But Jester had become a name being stretched across a trading terminal, an API, a research system, an execution network, an agent framework and eventually an entire infrastructure layer. [REDACTED] gives us room to describe the machine around all of those things. It is something deliberately constructed through skill and intelligence, which is basically what this entire system has become: artificial operators using artificial intelligence to build, test, coordinate and execute strategies through infrastructure we built for them. The closest comparison for what we are trying to become is also no longer a signal bot, a trading strategy, or even something like TradingView. It is something more like Cursor. Cursor did not replace programming languages, GitHub, cloud providers, databases or the rest of the software stack. It changed the environment through which intelligence interacts with all of those things. That is much closer to what [REDACTED] is supposed to do for finance. We do not need to replace exchanges, brokers, wallets or even the models people want to use. Those things can all continue existing. [REDACTED] sits between the intelligence and the financial infrastructure that intelligence needs to operate. It gives agents research, memory, backtesting, strategies, risk, coordination, execution and one consistent environment connecting the whole process. The interface matters, but the infrastructure underneath the interface is the actual company. We are also not doing the full token relaunch tomorrow. This is important because there is no point in changing the name, migrating the token, doing a giant marketing push and then pointing everyone toward software that is still half-finished. Oroboros needs to reach v1 and be stable. The API and MCP system needs to be mostly bug free and stable. Execution needs to become boring. Risk needs to become boring. Agent permissions need to be clear. The infrastructure needs to survive people and agents doing things we did not anticipate. That matters much more than getting the new brand out quickly. Between now and then the branding will gradually change, products will continue consolidating onto the [REDACTED] infrastructure and we will keep shipping, but the full relaunch happens when we have something we are actually comfortable putting the [REDACTED] name on. The part I keep coming back to is how absurd the progression looks when you lay it out. We started with one TradingView strategy. Then we needed a bot. Then execution. Then automation. Then backtesting. Then better risk. Then portfolio management. Then agents. Then research. Then agent coordination. Then APIs. Then MCP. Then multiple applications. Then somewhere along the way we realized the applications themselves were no longer the most important part, the infrastructure was. None of that was really the original plan. We just kept solving the next problem until the thing in front of us had become something completely different from where we started. Three years later, I think the product, the technology, the business model and the brand are finally beginning to describe the same thing. There is still a ridiculous amount of work left, and I do not want to pretend otherwise, but the direction is much clearer now than it has ever been.0,00%
16:34There is another part of this relaunch that is much less exciting than autonomous agents, but probably just as important. The economics of Jester have been terrible. For most of the project's life we have been overwhelmingly dependent on fee generation around the token itself. The existing Jester token has a 2% fee on transfers, and that mechanism did what it needed to do early on. It helped us bootstrap the project and got us much further than we probably had any right to get with the resources we had. But it is an awful thing for an increasingly large software and infrastructure company to depend on. If token volume is high, everything is great. If token volume slows down, operating revenue slows down with it, while servers keep running, market data still costs money, agents still consume compute, execution infrastructure still has to work and development does not magically stop. We have spent years building an increasingly complicated financial technology stack while relying almost entirely on one extremely volatile source of revenue, and that has been destroying us. There is another consequence of that structure that has become increasingly obvious as we have tried to grow. It makes basically everything outside of building the product harder too. Raising capital is harder. Bringing in serious marketers is harder. Finding strategic partners, market makers, liquidity providers and people who can actually help us scale is harder. The first thing anyone looking at Jester has to understand is a relatively complicated token structure where the company is still heavily dependent on trading activity around the token itself. Before we can even properly explain the technology, we are already explaining the tax, the fee flow, where the money goes, why the company is funded this way, and how any of that connects back to the actual platform. It made sense as a way to bootstrap something when Jester was much smaller. It makes considerably less sense when what we are trying to finance is an actual software and infrastructure company. More importantly, it means the structure people see from the outside does not really match the business we have built underneath it. We can talk about autonomous agents, APIs, MCP, execution infrastructure, enterprise deployments, millions in routed volume and three years of actual development, but if the economic model still looks like "people trade the token and that funds the project," then everything else has to fight against that first impression. That is increasingly becoming a problem. We want to be able to sit down with an investor, a broker, a marketer, a developer or an enterprise customer and explain a business they immediately understand: people subscribe to the software, agents pay to use infrastructure, companies license or embed it, execution generates revenue, and the token has its own separate economic loop. The technology has already moved well beyond the original Jester structure. The company around it now needs to do the same. [REDACTED] changes that by giving us more than one way to make money. The new system is being designed around multiple independent but complementary revenue streams. There will be traditional subscriptions for serious users and teams, usage-based API and MCP access for developers and systems, and individual autonomous agents will be able to pay directly for specific [REDACTED] capabilities through x402 instead of requiring a full subscription. An agent might pay a few cents for a market scan or risk evaluation, more for a backtest, and significantly more for large-scale optimization or simulation workloads. There will be execution-based revenue tied to activity flowing through the system. There will also be native front-end generated revenue, where our own interfaces, JESTER , Telegram, the terminals and future embedded experiences, charge for premium workflows, advanced tooling and execution-linked features. On top of that, there will eventually be enterprise and embedded infrastructure agreements for companies that want to build on top of [REDACTED], and there are obvious future markets around compute, data, strategy marketplaces and third-party autonomous agents. The important part is that these are not random businesses bolted together because we needed more things to sell. They all originate from the same infrastructure. A user subscribes, their agents research, research consumes compute and infrastructure, strategies are tested, successful strategies are deployed, execution generates activity, external agents independently pay to access the same tools, our own front ends generate revenue through premium interaction layers, and other platforms can embed the system into their own products. The same underlying machine can generate revenue several different ways depending on who is using it and what they are trying to do. We are no longer dependent on a single transaction inside a Uniswap pool to sustain the company, and that by itself changes the entire shape of the business. Humans and agents should probably pay differently as well. Humans understand subscriptions, so there will be normal subscription tiers for people who want to seriously use [REDACTED], with higher limits, more compute, larger agent fleets, more automations and lower execution costs as you move up. But machines do not need to pretend to be humans. An external agent does not need to create an account, open a pricing page, enter a credit card and decide whether it wants the monthly plan. It should be able to discover an [REDACTED] capability, see the price, decide whether the result is worth paying for, make the payment and receive the result. Maybe it needs a market scan for a few cents, a risk evaluation for a few cents more, a backtest for twenty-five cents or a large optimization job for a few dollars. If rebuilding that capability itself would cost far more than simply paying [REDACTED] for it, the decision is obvious. That creates a market which can eventually be much larger than the number of humans who ever open one of our applications. There could be thousands or hundreds of thousands of agents using [REDACTED] infrastructure without ever becoming traditional [REDACTED] users. This also lets us give the token a much healthier job. The token should not have to pay our server bill. [REDACTED] should be capable of becoming a profitable software and infrastructure company because the software and infrastructure are useful. Subscriptions, API usage, MCP usage, x402, execution, enterprise deployments and front-end revenue should sustain the company. The token can then focus on capturing value from the economic activity created by the network rather than being forced to finance the whole thing. Our current philosophy remains heavily weighted toward buybacks, with most token-related fee generation going back toward the token and only a small amount being retained operationally. The difference is that when [REDACTED] itself becomes profitable, we do not have to constantly choose between using economic activity to support the token and using it to keep the company alive. [REDACTED] makes money. The network generates activity. The token captures part of that activity. Those systems reinforce each other, but none of them has to be broken for the others to survive.0,00%
16:34Jester is Becoming [REDACTED] Jester is becoming [REDACTED] Systems. This has been coming for a while, and to be honest, it is less of a rebrand than it is finally admitting that what we have built is no longer the thing we originally named. Jester started as one TradingView strategy and a bot. That was basically it. At that scale, the name was perfect. But over the last three years the strategy became a platform, the platform needed execution, execution needed risk, risk needed portfolio context, then we added backtesting, optimization, market data, automation, research tooling, machine learning hooks, multiple venues, APIs, MCP, autonomous agents, agent coordination, multiple front ends, and all the infrastructure underneath those things. Eventually Jester stopped describing the whole system and started describing one part of it. [REDACTED] is the name for what the system has actually become. The biggest change is not even the technology, it is how we think people are going to use it. Originally, we assumed people would be talking to the bots, opening Crucible, inspecting strategies, running backtests, tweaking parameters and generally controlling everything themselves. That made sense when agents were still mostly a novelty and the human was obviously going to remain at the centre of the loop. Over the last year that assumption has changed very quickly. Agents are becoming capable enough that the human should increasingly be defining the objective, the capital, the permissions and the risk constraints, then letting the system do the work. Research the market, form a hypothesis, build a strategy, test it, compare it against alternatives, reject the bad ideas, understand the portfolio it is entering, apply risk, deploy it, monitor it and adapt. Other agents can challenge the thesis, specialize in execution, watch portfolio exposure, or handle completely different parts of the process. The human does not need to micromanage every step. The system should be able to orchestrate it. That is the real shift behind [REDACTED]. We are no longer trying to build a smarter trading bot. We are building an environment where financial agents can actually operate. The simplest way to describe the system is research, coordination, risk and execution, all connected through the same infrastructure. Research is where agents investigate markets, generate and test strategies, compare ideas, optimize parameters and determine whether something is actually worth deploying. Coordination is how those agents share context, delegate work and operate as part of the same market loop instead of existing as isolated chat windows. Risk is the layer that prevents autonomy from becoming stupidity. Sizing, leverage, exposure, stops, drawdown, portfolio state, account policy and venue constraints all need to be enforced before an agent is allowed to touch capital. Then execution is the final step, where a strategy actually leaves the research environment and becomes a live action in a market. The goal is to carry context all the way from "I wonder if this works" to "this is now deployed with real capital inside defined risk." This also changes how we think about our products. Oroboros, Saylis, Crucible, Tesseract and JESTER are not really separate systems. They are different surfaces into the same infrastructure. Oroboros is the perpetual and prop trading interface, and right now it is probably the clearest expression of the full [REDACTED] loop, from manual trading through assisted operation and eventually fully autonomous execution. Saylis is the onchain side, where the same underlying system can be used to research and operate across decentralized markets. Crucible is the research environment, where strategies are backtested, compared, optimized and hopefully broken before real money ever gets near them. Tesseract handles prediction markets and the broader world model layer, because not every market question begins with a candlestick. JESTER is another interface into the system, but JESTER itself is not [REDACTED]. Neither is Telegram, neither is Oroboros, neither is the web terminal. Those are clients. [REDACTED] is underneath all of them. That distinction matters because it means our own front ends do not have to be the only way this technology wins. We would obviously love Oroboros and Saylis to become large products, but they do not have to replace every broker or trading platform in the world. Questrade does not necessarily have to be our competitor. Wealthsimple does not necessarily have to be our competitor. Interactive Brokers does not necessarily have to be our competitor. They already have users, accounts, interfaces and distribution. What they may not have is the autonomous research, risk, strategy and agent infrastructure underneath all of it. So keep the frontend. Use [REDACTED] underneath it. Use our backtesting, our risk engine, our execution layer, our agent coordination, or just one small piece of the system. The goal is not to force the entire financial world into one [REDACTED] application. The goal is to build infrastructure useful enough that a lot of different applications, brokers, agents and financial systems can use it. That is why the new positioning is the infrastructure behind autonomous finance. It is also important to say that this is not a whitepaper for something we intend to start building after the relaunch. The system already exists. During Jester's alpha we have routed more than $9 million in real trading volume through the infrastructure. We have had real operators running strategies, automation and real capital through the system. We have had real execution problems, real risk problems, real bugs and real failures, and we have had to actually solve them. Over 2 years we have rebuilt pieces of the architecture again and again because every time the scope expanded we discovered another layer that had to exist underneath everything else. There is a very large difference between building an agent that can say "I think BTC is bullish" and building the infrastructure that lets that agent safely do something about it. Most of what we have spent the last few years building is the second part. The timing of this is also kind of hilarious. The broader AI industry has been moving through almost the exact same progression. The first generation of agents was basically giving an LLM some tools and letting it loop until something happened. Then everyone rediscovered workflows because deterministic systems were more reliable. Then the harnesses got much better, agents became capable of longer-running work, and now the industry is moving toward systems where agents have defined tools, permissions, workflows, memory, specialized environments and infrastructure around them. That is basically where we have been heading with finance. We did not begin three years ago with some grand thesis about agent harnesses. We were trying to solve the next problem in front of us, and those problems kept forcing us toward this architecture. Now the rest of the industry is arriving at many of the same conclusions, which makes the direction we have been moving in feel much less strange than it did even a year ago.0,00%
17 авг.- Change: Agent preferences area lists all provider/status controls and prompt schedules. - Fix: Agent links now move between tabs smoothly; prompts and toggles respond to sign-in state. - Fix: Autopilot and preferences no longer accidentally scroll or hide elements when switching. - Change: Help info now clearly separates agent features from automation controls. - Change: Trade ticket is simplified, showing all trade steps in order and only the most useful controls. - Fix: Mobile and sheet headers now display correctly in all trade layouts. - Feat: Users can fully delete their accounts, and see a summarized map of their data. - Change: Terms of service and labels updated to match new features and current state. - Fix: Leverage in trade tickets now respects market caps, displays correct amounts, and clarifies when more size is added. - Fix: Automated strategy changes are limited to the strategies set by the user. - Change: Help and admin features better reflect current product; unused tools cleaned up. - Fix: PnL in positions now matches the displayed values everywhere; formatting for gains/losses is consistent. - Change: Side navigation scrolls quietly, with controls pinned for easy access. - Fix: Trade history, chart controls, and tabs all behave correctly and are easier to use. - Feat: Stop loss/take profit levels can be adjusted directly in the app, with instant feedback. - Feat: Usage of advanced calls is tracked and visible for subscription features; future paid features are already handled in error states. - Fix: Security and grant confirmations cannot be bypassed via partner tools; only approved users can confirm. - Fix: Goals and permission titles are cleaned before saving; incomplete or failed record saves close safely. - Fix: Security restrictions now block unauthorized grant actions; records store changes safely with accurate state. - Feat: Some automated permissions work without user approval, but killer actions still need real confirmation. Advisory reports are attached when available. - Change: Clicking a position loads it for review; editing or closing works as before. - Change: Main app status bar combines all info into a single easy-to-read strip. - Feat: Shared account login now works across all main product areas. - Feat: Simple entitlement checks now block or allow product features based on user’s level; most features stay open for regular users. - Feat: Entitlement plans and scopes can be enforced; daily limits and upgrades are available for advanced use cases. - Fix: Order cancel actions wait for valid results; empty responses are no longer treated as success. - Change: Live service refuses test mode in production; health checks show when running in non-live mode. - Change: Tools that update state are clearly labeled, and advanced editing needs extra confirmation. - Fix: App build pipelines ignore incompatible code for required styles. - Change: Demo accounts are clearly labeled everywhere, including sample data. - Change: Assisted trading shows improved charts for strategy visualization. - Docs: Updated and consolidated technical and compliance documentation for partners and internal use. - Fix: Custom external providers keep full path info for model and chat access. - Fix: Daily strategy picks avoid banned or restricted choices and always fill from valid options. - Fix: Automation dashboards always show active subscriptions and actions. - Fix: Telegram controls point to the live product, and positions load reliably even with large data. - Fix: Slow info fetches don’t block full data loads; users see results as soon as available. - Fix: Managing account connections now always keeps last known details, even if the service glitches. - Fix: Provider key manager stays loaded even on service hiccups. - New: Analytics now includes a tool to recommend risk levels for optimal results. - Improvement: App loads market, strategy, and chart data much faster with better caching and parallel loading.0,00%
17 авг.v0.7.2 - Fix: Oroboros Automation shows an open trade on the fleet row (pair, side, and trade source) instead of staying on Scanning. Live Hyperliquid ticks no longer drop strategy attribution. - Change: Oroboros Portfolio and Analytics are one rail item. Account, Performance, and Backtests are chips on that page. ?nav=analytics still opens Performance. - Change: Oroboros Agent hub is one toolbar — Chat / Research / Mesh / Prefs sit with New, History, Keys, and Refresh. The extra Jester Agent title bar is gone, and the chat side rail (portfolio snapshot, strategies, session) is gone. - Change: Oroboros Agent prompt chips live once, above the composer. The empty-state bubble and Quick actions rail no longer repeat the same shortcuts. - Change: Oroboros hides the execution status footer on mobile so the bottom nav has the last row. Desktop still shows connection, exposure, risk, and latency there. - Change: Oroboros left-rail Status is now Chat — a flyout sidebar for Agent conversation without leaving the current page. Connection and venue facts stay in the footer status bar on desktop. - Change: Oroboros Autopilot is an operational desk — compact status, live telemetry, equal-height mandate cards, active roster with Why selected, and activity instead of a settings explainer. - Change: Automation Ask Agent sits next to Autopilot activity; Refresh is an icon. Hyperliquid-down banners stay amber with Retry when other venues still work. - Change: Oroboros pages share one toolbar, chip switcher, and hub chrome instead of per-page mastheads. - Change: Oroboros pages no longer repeat the nav title in a section header. Toolbars, switchers, and in-page labels stay. - Change: Oroboros pair pickers now share one market dialog (search, favorites, HIP-3). Native pair dropdowns on Strategies, Signals, Fleet, and Automations are gone. - Change: The header PAIR control only shows on Trade, where it updates the chart and trade ticket together. Other pages no longer carry a global pair that does nothing on screen. - Fix: Oroboros Signals inspector chart scales from candles plus SL/TP, keeps post-signal bars, and maps sl/tp aliases so levels actually draw. - Fix: Oroboros signal trade charts fit the candle+SL/TP band instead of zooming out to 5× stop distance, and snap the canvas to the device-pixel grid at 125% Windows scaling. - Change: Oroboros Home and Automation Overview put Strategies beside Live activity on wide screens, same desk pattern as Portfolio and Autopilot. - Perf: Oroboros Strategies Discover paints ranked metrics immediately, then staggers rows in and hydrates sparklines in the background instead of waiting on 250 full backtest reads. - Fix: Autopilot strategy mandate uses visible 1 / 2 / 3 choices instead of native dropdowns whose text vanished on Windows. Copy now says how many stay live vs how many can be replaced each day. - Change: Oroboros Propr challenges now have a dedicated Challenges page. Master and mirror selection is no longer nested on Automation Overview. - Change: Oroboros Agent Mesh is one desk — fleet map, group-board chat, and briefs together, same as MiniApp. Feed/Board tabs and the empty-board split are gone. - Change: Oroboros Agent chat no longer shows a portfolio snapshot in the side rail — equity and risk stay on Portfolio. - Change: Oroboros Agent uses one toolbar — Chat / Research / Mesh / Prefs sit with New, History, and Keys. The extra “Jester Agent” title bar and empty-state byline are gone. - Change: Oroboros Assisted ticket is numbers-first — SHORT, BTC · 1H · MKT, SL/TP/size — without repeating “Assisted Trade Proposal”, Bearing, Strong Sell, and market entry in the same sheet. - Fix: Oroboros Trade chart fills the plot stage and stays sharp at 125% Windows scaling. The canvas no longer sits in a padded height: 100% flex child (that left a short, soft 1.25× bitmap); it tracks the stage and snaps CSS size to the device-pixel grid. - Change: API keys now have limited access depending on type. Some keys can view or act, others are limited further. - Change: Flatten actions are now staged; confirmation is needed before trades close. - Change: Trade confirmations happen instantly within the app. Some partner trade actions are rate limited; main tools stay unlimited. - Change: Account actions by default notify subscribers; this can be turned off. Disabled automations do not notify. - Change: Some advanced functions can no longer close or flatten trades directly; closing now follows new staged steps. - Fix: Confirming staged actions now uses the correct process and handles rate limits safely. - Fix: Wallet stats use only closed trades for calculations; open trades and duplicate clicks are handled properly. - Fix: Trade sizes use accurate prices; coin rounding issues fixed. - Fix: Telegram no longer sends false notifications when trade data is incomplete; only real trade closes are notified. - Fix: Account management setup no longer repeats info and accounts are better maintained during changes. Prompts always match the right account. - Change: Desktop login process works the same everywhere, keeping users signed in locally. - Fix: Trade close notifications no longer disappear due to formatting errors; fallback text and proper formatting are used. - Fix: Portfolio equity charts display correct data and match main account numbers. - Fix: Health checks and metrics now report actual system states. - Fix: New trades aren’t sized using old data if key info is missing. - Fix: Signals process mirrored strategy names smoothly and don’t lose results. - Fix: Live price and market data now respond immediately and reliably. - Fix: Strategies list loads quickly the first time without delays. - Change: Portfolio equity curve can be exported and shared as an image. - Fix: Document pages now scroll fully; layout fixes for long content. - Fix: Automation overview merges info into a single summary for clarity. - Fix: Trade tools show all info under the chart; parts don’t overlap. - Fix: Trade forms always scroll properly. - Fix: Trade analysis and information appear side-by-side on wide screens. - Fix: Main dashboard layout keeps sections where expected and does not overlap. - Change: Autopilot tools combine all settings and strategies in one place; activating actions stay prominent. - Fix: Autopilot strategy controls now reflect the real limits set by the user. - Change: Agent platform mesh and board features are combined into a single, switchable view. - Fix: Mesh state updates instantly; repeated posts are eliminated. - Change: Strategy discovery shows ranked candidates with badges and graphs; easy comparison tools are available. - Fix: Filtering and sorting strategies works as expected, and missing info no longer distorts results. - Change: Analytics research combines summary charts and leaderboards for easy insights; filtering is kept local. - Fix: Portfolio clearly warns about incomplete loads and health issues; partial or failed data is explained. - Change: Research section highlights ongoing work and keeps completed reports organized. - Fix: Research tools keep going after sign-ins; deployments and saves work smoothly. - Fix: Autopilot daily limits now allow more than one strategy change per run if within allowed range. - Change: Portfolio view combines all info into one page, displaying health, history, allocation, risk and activity together. - Fix: Portfolio no longer endlessly retries failed history loads; status and controls are easier to find and use. - Change: Signals screen becomes a live feed with context and ticket actions; assisted reviews are supported. - Fix: Signal feed now only hides aged trades when they’re really missed; closing one strategy doesn’t block others. - Change: Automation tools now show all automations as a list with detailed state info; operations like delete are easier to find. - Fix: Automation lists use real data for gains and losses; unusual ties and zeroed markets are handled. - Change: Automation overview uses simple controls for running and pausing automations. - Change: Agent area collects all advanced features in one place for easy navigation.0,00%
14 авг.https://x.com/JestTech/status/20881272410162548970,00%
14 авг.v0.7.0 - Fix: Broken indicators repaired; async logic now handled properly. - Change: Signal and execution process stays synchronous for sync strategies, improving speed. - New: Signed-out users now see a delayed/preview mode with banners and sign-in prompts. - New: Public view allows delayed signal lists; signed-out users see delayed data, with fallback if empty. - Fix: Main app panes fill available space for better layout. - Improvement: Indicator calculations now optimized for better performance. - Improvement: Live data lookups are direct and efficient; snapshots are reused; debug only emits when needed; closing logic prefers current data. - Fix: Settings for mirrored accounts now show all options; switching master or adding mirrors is easier. - Change: Default risk controls use ATR-based stops/profits; manual tickets use same defaults. - Fix: Autopilot off fully disables new trades and risk logic respects current state; handles missing/mixed data safely; scheduler pauses on loss. - Fix: Portfolio charts now display correct account value over time on accurate axes; removes placeholder data. - Change: Pair trading control is now handled by subscriptions and manual selection; automation checks updated. - Fix: Mobile pair selection improved; dialogs display correctly; accidental dismiss/touch events handled. - Change: Asset-scanning operations are now queued for responsiveness. - Fix: Stuck or slow background tasks are aborted, do not affect main workflow. - Fix: Missing historical data is skipped, not treated as zero, for accuracy. - Fix: Strategy fails gracefully if funding data is missing, not run as zero. - Improvement: Background testing now matches inline configuration for consistency. - Improvement: Slippage is calculated from a single data set for efficiency. - Fix: All fee and slippage settings now unify into one source; environment mismatches fixed. - Change: Performance reporting now uses equity-based returns for consistency. - Change: VWAP resets daily, avoiding moving averages that shift every bar. - Change: Long-running caches refresh more frequently for up-to-date results. - Fix: Live data waits longer for better initialization; failures are now logged clearly. - Fix: Admin logins now require secure credentials; weak logins allowed only with explicit override. - Security: Third-party package updated for security. - Fix: App links now always open in external browser when leaving main app. - New: New strategy added to catalog. - Fix: Empty responses on trade closes are now treated as failures, not successes. - New: Additional venue supported with improved pricing and fee logic. - New: Platform fees applied after live trades where required. - Fix: Wallet export sends recipient public key. - New: New trading integration added. - Fix: Audit improvements—mirrored actions, account detection, error and warning handling, discovery/fallback, and complete data flows. - Fix: Leaderboard promotions now prefer reliable cached parameters, skip missing data, and restore lineup if upgrades fail. - Fix: Risk markers now cover data timeouts so limits are correct; unclear states fully block new activity. - Fix: Deployed capital now uses margin, not notional size; incorrect exposure reports fixed; unknown capital blocks trades. - Fix: Batch processes run mandates before unlocking; consistency and history loading improved. - Fix: Daily risk tracking no longer uses potentially wrong data, avoids false blocks, and clears invalid loss values. - Fix: Automated alerts now show correct emojis after encoding fix. - New: Account settings now editable directly in main app, no launch required. - Fix: Strategy views use full width as intended. - Improvement: Strategy browser defaults to high-quality/popular results; can switch catalog scope. - Fix: Info returns soft errors if integration is not available, avoiding hard failures. - Fix: Strategy ranking falls back to less comprehensive data gracefully. - Fix: Live strategy engine fully preserves state and identity, handles incomplete data correctly, aligns history and reporting, and blocks missing or irrelevant data. - Fix: Institutional/data reliability passes—no redundant processing, job assignment improved, shallow clones, legacy splits removed, capped cache, timeouts properly abort, missing data omitted, faster job closing.0,00%
10 авг.v0.6.19 - New: Oroboros Account settings now let you manage your Agent API key, including viewing, generating, revealing, and revoking it. - New: Oroboros Automation now supports adding, editing, pausing, running, and deleting scheduled prompts directly in Agent Preferences. - New: External MCP connections for end users; a Quick Start guides you through setup. - New: PnL cards now support the "saylis" brand and palette, with vanity addresses and site URLs configurable. - Change: Allocation and exposure checks for strategies now use margin or deployed capital, improving accuracy for leveraged entries. - Improvement: Daily top-pick promotions handle cached boards more reliably and skip over missing optimizer data gracefully. - Improvement: Top-pick and "Pick-for-me" logic now upgrades your active picks when there are stronger options, even if your roster is full. - Improvement: Remember-me sessions are now consistent and last the intended duration, avoiding early logouts after transient authentication issues. - Improvement: Account and setup status is updated and reflected more quickly after changes, such as approvals or delegation syncs. - Improvement: High-timeframe data displays and loading are more resilient, showing the last known value while updating and handling slow or failed requests smoothly. - Improvement: Navigating docs and articles within Oroboros is now smoother, updating content client-side without full page reloads. - Improvement: Oroboros documentation pages now scroll correctly, even for long articles. - Improvement: Provider keys and configuration restore reliably after deployments and merges, ensuring your environment stays in sync. - Improvement: Opening Oroboros via Telegram or other authorized links now logs you in automatically, preserving session continuity. - Improvement: Hold notices for certain strategy actions (already in position, laddering off) are shown as soft messages, clarifying why an action didn't proceed. - Visual: PnL card graphics display with correct proportions, links consistently use the intended vanity format, and claimed usernames are preferred for handles. - Visual: Dropdown menus remain readable on Windows, ensuring option text is visible regardless of OS color scheme.0,00%
8 авг.v0.6.18 - Fix: On mobile, Autopilot no longer covers Positions in Oroboros Home; Edit/Close stays tappable. Rail and main are now a single flex stack on narrow screens. - Fix: In Automation Overview, Recent Activity, Schedule, and Quick Actions no longer overlap or collapse from the same spot on mobile. - Fix: Manual/Assisted trade ticket sections keep their content size on mobile (no shrinking below content). - Fix: Mobile layout pass — main sections now use fit-content flex stacks instead of fixed-height grids. Automation split cards and toasts clear the bottom nav. Setup sheets respect safe area.0,00%
7 авг.v0.6.17 - Fix: PnL cards — improved text layout, reliable images, consistent branding and links. - Fix: Telegram commands stayed inactive during startup, though alerts still worked; now properly waits for setup before handling messages. - Fix: Telegram webhooks are now protected from being set by accidental local runs unless explicitly allowed. - Fix: User settings and daily automation display correctly after deploys; type mismatches in user IDs could cause resets or missed updates. - Fix: Preferences startup is more robust — first loads are provisional, real settings update over time, and state is merged safely. - Fix: Account synchronization covers all exchanges even when data types differ. - Fix: Performance views display ROE, realized values, and timeframe more clearly; recent results always appear so returns aren't confusing. - Fix: Automation and strategy sections now only display percent returns when actual portfolio values are known, avoiding misleading mixed numbers. - Fix: Duplicate rows in live performance are resolved more accurately, prioritizing results with reliable data.0,00%