Ticker Spring
Copy SPRING contract address
Loading live Ticker Spring data
Ticker Spring brings tokenized-stock vaults, baskets, limit orders and Spring Orders into one onchain experience. This guide explains the essentials without the protocol jargon: what each product does, what it costs, and who has checked the code.
Deposit USDG into a vault and receive vault shares in return. The strategy supplies liquidity around a tokenized stock market, collects trading fees, and adjusts its range as the market moves.
Select the company or ETF vault that fits your interests.
Your vault shares track your portion of the vault.
See holdings, fees, activity, and your position in one place.
Use the available withdrawal path shown by the app.
Buy one token and own every stock or coin inside. A basket keeps its own weights, and the trades that rebalance it pay its holders.
Browse by theme: stocks, crypto or both, with what each one holds.
ETH, USDG or any token in the basket, in one step.
It tracks everything inside. Holders earn 70% of the basket's 1% swap fee.
For USDG, ETH, or the basket's own tokens.
Make your own. Anyone can make a basket from the trade list: pick the tokens, set the weights, name it and put in the first deposit. It shows under Unverified until Ticker Spring reviews it.
Make a basket →Swap any stock token, or set a limit order that fills inside the swap itself: a trade through your price fills your order.
Trade any stock token at the price shown before you sign.
Pick a price on any token. A trade through it fills your order. 2.5% of what fills.
Up to 20 buys on the way down, or sells on the way up, from one ticket. Each fills once.
An order that hasn't filled can be cancelled, and what it holds comes back.
Spring Orders sit under Trade. Pick a token, set a ladder of buys under the price, each with its own price and USDG amount, and choose how far over your average buy price it sells. Our Uniswap v4 strategy hook fills each order when trades reach its price, and every fill puts up the next one. Any token whose price can be read from its main USDG pool works: the first Spring Order on a token also opens its order book, one more step in your wallet.
Spread buys from one price to another, evenly by percent or by dollars, with equal amounts or more at the lower prices. Move or resize any level.
Everything you bought sells at your gain over your average buy price, and the sell moves to your new average as each buy fills. Or use a sell ladder: 2 to 4 parts, each sold at its own gain over the average.
When everything has sold (every part, with a sell ladder), your buys go back up at the same prices, or it stops there. A buy above where it sold waits and may go back up on a later round that sells above it. You choose before you start.
Orders fill when trades reach your price; a fill completes at 95%. You confirm each step in your wallet.
Already running a strategy? It shows in My orders on the Spring Orders page with your wallet connected, where you can close it or collect what it holds.
Open Spring Orders →What has been reviewed, by whom, and how to check every contract yourself.
Our vaults were audited by Sherlock in October 2026, and both auditors signed off the fixes.
Scope · 13 contracts
Baskets are Balancer V3 weighted pools, running Balancer's own audited contracts, unchanged.
A deposit proceeds only when the Chainlink price is fresh and the pool remains within its permitted range.
Weekends favor safety: price-dependent actions wait for fresh prices.
Check it yourself. Every contract is listed with its Etherscan link, and the vaults with their verified source.
See the contracts →Ticker Spring combines live market data with onchain limits and clearly separated controls. If required information is not available, sensitive actions wait instead of guessing.
Every vault operates within defined limits for price movement, trade size, and acceptable execution loss.
Day-to-day operation, emergency controls, and protocol treasury responsibilities use separate roles.
Important configuration changes follow a review window instead of taking effect immediately.
Vaults include multiple withdrawal and recovery paths so users are not dependent on a single trade route.
Tokenized-stock markets follow a 24/5 schedule. Ticker Spring uses Chainlink as an independent reference before accepting a price-dependent action, rather than trusting a pool price by itself.
A deposit proceeds only when the Chainlink price is fresh and the pool remains within its permitted range.
When stock feeds stop updating, deposits and other price-dependent actions can pause until fresh pricing returns.
Users can withdraw their proportional underlying tokens without waiting for a stock sale. A one-click USDG conversion waits for a live protected price.
Rebalances compare current pool conditions with Chainlink before assets are repositioned.
What each product charges, who earns it, and where Ticker Spring's share goes. Vault depositors and basket holders keep their share of earned fees first.
of protocol revenue buys back and burns SPRING.
| Product | What you pay | Who earns it |
|---|---|---|
| Vaults | No deposit fee; traders pay the pool’s swap fee | 70% depositors · 30% protocol |
| Baskets | 1% swap fee on trades through a basket | 70% holders · 30% protocol |
| Buying or selling a basket | No Ticker Spring fee; the market’s price impact applies | — |
| Limit orders | 2.5% of what fills, shown before you sign | Protocol |
| Spring Orders | 1% per fill | Protocol |
| AI agents | The same fees as everyone, nothing extra | — |
As Ticker Spring grows, each product can split its protocol revenue its own way, depending on what it costs to run. Revenue pays for servers, audits and the keepers' ETH gas, and a product with many keepers needs more of it.
These are the 18 user-facing V7 vault contracts deployed on Robinhood Chain. Each address opens on Etherscan, and its matching public source is available through Sourcify.
Balancer V3's own contracts run the baskets, unchanged; Ticker Spring's add-ons buy, sell and make a basket in one step.
At launch, 71% of the SPRING supply is purchased for the protocol reserve and enters a 90-day vesting period. This limits launch-day concentration and keeps the allocation aligned with long-term ecosystem growth.
These reserve tokens will not be sold on the open market.
100% of protocol revenue is used for SPRING buybacks and burns. Vault participants keep their share of earned fees. The protocol’s share buys SPRING and permanently removes it from circulation.
The roadmap connects liquidity, credit, and strategy automation into a broader onchain financial toolkit.
Grow supported markets carefully, deepen the lending experience, and make portfolio management feel seamless across both products.
Introduce a strategy designed to collect opportunities from the market while reducing directional exposure.
Combine vault positions with lending in a guided looping strategy built to pursue a higher blended return.
A new feature is being built around AI, DeFi, and Uniswap V4 hooks. Development is expected to take about 30 days, with more revealed closer to release.
You receive transferable vault shares representing your portion of that vault’s assets and activity.
Vaults seek to earn fees by supplying useful liquidity to tokenized-stock markets. Results change with activity, positioning, and market conditions.
Deposits and automated price-dependent actions can pause when Chainlink stock prices are not current. You can still exit into your proportional underlying tokens; conversion of stock into USDG resumes when protected pricing is available.
A vault puts your USDG to work as liquidity for one stock and earns trading fees. A basket is one token that holds several stocks or coins at set weights; holders earn the fees from the trades that rebalance it.
100% of protocol revenue is used for SPRING buybacks and burns. This is the protocol’s revenue, separate from the share of earned fees retained by vault participants.
Lending is being introduced as a companion to the vaults. It will let supported vault shares serve as collateral while USDG suppliers can earn borrower-funded interest.
Follow @tickerspring and return to this page as new markets and strategies are released.
AI agents can read everything Ticker Spring offers and act on it: the vaults, limit orders and ladders, and grid and ladder strategies. Every action is prepared for you to sign. Your agent does the reading and the legwork; you stay in charge of the money.
Ticker Spring runs two Model Context Protocol servers: a Data server that only reads, and an Actions server that prepares transactions without sending anything. Add one or both to the AI tool you already use.
claude mcp add --scope user --transport http tickerspring-data https://mcp.tickerspring.com/mcp/data
claude mcp add --scope user --transport http tickerspring-actions https://mcp.tickerspring.com/mcp/actions
Then start Claude with claude. --scope user makes them work from any folder.
Customize → Connectors → Add → Add custom connector, then paste a server address. Add each server, then turn them on in a chat from the + menu → Connectors.
Add the servers to ~/.cursor/mcp.json under mcpServers, each with its url.
Agents can start from skill.md, llms.txt and the OpenAPI description.
The Data server answers questions. The Actions server prepares transactions and returns a sign link, along with the same calls ready for your own wallet.
Spring Orders, a buy ladder that sells everything over your average buy price, are set up on the Spring Orders page.
When an agent wants to act, it prepares the transactions and hands them to you. Nothing has been sent until you sign.
It repeats back the action, the vault or market with its full address, the amounts, fees and slippage, and waits for your clear yes.
The link opens on tickerspring.com. The page rebuilds every transaction itself and describes it in plain words.
Approvals are for exact amounts. Each step shows its progress, and a step is never sent twice.
Every prepared request also comes as EIP-5792 wallet calls, for an agent that signs with its own wallet.
Agents can ask what changed since their last check: deposits filled, withdrawals completed, orders placed, filled or ready to claim, grids and ladder strategies that traded or closed. One call returns the changes and a marker for the next check.
Agents pay the product fees you see on the site: the vault fee share, the limit-order fee and the grid fee. A few heavy tools, such as long backtests, can ask for a small USDG payment per call over x402 when Ticker Spring turns that on; everything else is free to use.
Agents work with the same vaults as everyone, alongside limit orders, ladders and grids.
Ticker Spring's servers never hold keys or sign. Every transaction is signed by you.
The sign page rebuilds every transaction and refuses anything that differs from the request.
Any tool that supports MCP servers over HTTP, including Claude Code, Claude desktop and Cursor. Agents with their own wallet can also use the HTTP API directly.
No. Agents prepare transactions; nothing is sent until you sign.
No. They pay the same product fees as everyone else.
Your positions show on the site as usual, and agents can ask for what changed since their last check.
Open the Agents page, add the servers to your AI tool, and ask it what it can do on Ticker Spring.