STONX is a token-governed liquidity marketplace and metaDEX operating on Robinhood Chain through Ekubo’s Ve33 extension. It focuses on improving liquidity for tokenized-stock markets while supporting pools built on Ekubo Core. Liquidity providers deposit assets into concentrated-liquidity pools and can earn STONX emissions while their liquidity is active. STONX holders can lock tokens, direct emissions to a selected pool, and vote on the swap fee that pool charges. Trading fees accrue to the voters supporting each pool, while Ekubo Core supplies the underlying AMM execution, settlement, and accounting.
Follow puts Ekubo Stock Liquidity Token on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
Fact1 of 1 watched contract active · 14,421 calls in 7 days — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches.
Counted from the chain. Usage says the contracts are used, not that anyone is building.
Ekubo: TVL $1.3M · fees 24h $1.1K · revenue 24h $32 (DefiLlama, 2026-10-30); +1 more protocol. Registry context, not a measure of building.
Contracts
Fact2 contracts on record for code changes, 1 with published source code; no implementation or interface change recorded.
Not yet known
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer.
Project names this contract: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedProject names this contract: a deploy record in the project’s own repository names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Low liquidity.
Low liquidity: the pool holds less than $5,000 of liquidity.
Source9 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Low liquidity”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Discovery Gap: Not measured — 24h volume under $1,000.
Not measured — market too thin: the tracked token's market reads “Low liquidity” but traded $4.75 in the 24 hours of its reading, under the $1,000 a measured market needs. A Discovery Gap is measured only on an active market that is more than a launch curve and trades at least $1,000 a day: a thin market's attention percentile sits near the floor, so its gap would measure the thinness, not the building.
SourceThe score row: the Build Momentum percentile and the market-attention percentile, both taken over the projects with a market reading.ReadWhat HEY derivedNot measured — market too thin.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Research coverage: HEY can answer 18 of the 21 research questions that apply.
18 of 21 applicable dimensions measured.
Identity
IdentityMeasuredRead 46d ago.
Building
Building activityMeasuredRead 1m ago.
RepositoriesMeasured
ReleasesMeasuredRead 45d ago.
TimelineMeasured
Official site
Official docsSource unavailableIts website did not answer.
API descriptionSource unavailableIts website did not answer.
Official site changesSource unavailableIts website did not answer.
Code and packages
Repository detailsMeasuredRead 1d ago.
Published packagesMeasuredRead 25m ago.
Package advisoriesMeasuredRead 1d ago.
Contracts
Contract creationMeasuredRead 10h ago.
Contract activityMeasuredRead yesterday.
Verified sourceMeasuredRead 19h ago.
Contract interfaceMeasuredRead 19h ago.
Market
Current marketMeasuredRead 3m ago.
Market historyMeasuredRead today.
Supply distributionMeasuredRead 2d ago.
LocksMeasuredRead 50m ago.
Market checksMeasured
Protocol economics
Protocol economicsMeasuredRead today.
A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.
Market figures are context only and never change activity status. Methodology
Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: a week before HEY began reading this project’s sources — not yet read, not zero.
Build timeline
A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.
This week HEY looked inside 1 of 7 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 2 automated commits (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 2 of 4 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.
This week HEY looked inside 1 of 13 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 15 automated commits (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 1 of 7 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 2 automated commits (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 1 of 17 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.
This week HEY looked inside 1 of 17 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 13 automated commits (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 1 commit to see what changed: 1 changed code. 8 automated commits (bot accounts or a repeating scripted message) not counted.
Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only. 5 automated commits (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 3 of 29 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 8 automated commits (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 1 of 5 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 19 automated commits (bot accounts or a repeating scripted message) not counted.
Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only. 7 automated commits (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 1 commit to see what changed: 1 changed code. 3 automated commits (bot accounts or a repeating scripted message) not counted.
This week HEY looked inside 1 of 5 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 8 automated commits (bot accounts or a repeating scripted message) not counted.
94 changes on HEY’s record for Ekubo Stock Liquidity Token: 43 releases · 1 token check change · 1 contract change · 2 build pace changes · 47 other changes in 2 more kinds.
NewMarket8h ago
Token market moved from Active market to Low liquidity
The full change record holds 15 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)
The token’s market, checks, locks and stamps below are context only: none of it changes activity status or Build Momentum.
Contract 0x570C5aa79c798E7A418412cC8399ae5bcCe570C5 on Robinhood Chain
Two market sources describe different markets for this token; HEY is holding it for review.
Market
Low liquidity
Last day with trading
2026-10-29
Two market sources describe different markets for this token; HEY is holding it for review rather than choosing one.
Signal conflict
The project is building while its token trades with little liquidity.
This describes the token market, not whether development has stopped.
seen 2026-09-24Trading fell from 201 trades a day (the seven days to 2026-08-02) to 2.3 a day in the seven days to 2026-10-08, in HEY's decoded on-chain trades.
seen 2026-10-08The project is building while its token trades with little liquidity. Token market status: low liquidity. This describes the token market, not whether development has stopped.
From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-10-30 06:52 UTC · How HEY checks this
Questions HEY can answer about Ekubo Stock Liquidity Token — as of 30 Oct
Is 0x570C5aa79c798E7A418412cC8399ae5bcCe570C5 Ekubo Stock Liquidity Token’s own contract?
FactProject names this contract: A deploy record in the project’s own repository names this contract on Robinhood Chain.Details →
What does HEY not know about Ekubo Stock Liquidity Token?
Unknown3 gaps: Official docs (source unavailable), API description (source unavailable), Official site changes (source unavailable). Its website did not answer.
Sources
12 places HEY reads for Ekubo Stock Liquidity Token
Website
https://ekubo.org/OfficialHEY lost access 14d ago; nothing has been read since.
Website
https://ekubo.org/STONXFrom a launch or market listingHEY lost access 16d ago; nothing has been read since.
Security context: 3 audit reports found. An audit shows an audit took place; it is not a guarantee of safety.
Recorded, not counted (12)
HEY keeps these on record as context. None counts toward the activity status or Build Momentum; each says why.
GitHub releaseBuild 90ba0a231525416338b797dea393f38529d146492026-09-11Recorded, not counted: it was cut from a rolling tag (latest, nightly, a dated or hashed build), which names a moving build rather than a release.
GitHub releaseBuild a9d35e511c43fdec190414ef57975c18920c47152026-09-11Recorded, not counted: it was cut from a rolling tag (latest, nightly, a dated or hashed build), which names a moving build rather than a release.
GitHub releaseBuild c075dff71710d2bab438843cef2d2871013f0c9c2026-09-11Recorded, not counted: it was cut from a rolling tag (latest, nightly, a dated or hashed build), which names a moving build rather than a release.
GitHub releaseBuild a3c0aa952d61de72408533bac435c0fc5c033e2b2026-09-11Recorded, not counted: it was cut from a rolling tag (latest, nightly, a dated or hashed build), which names a moving build rather than a release.
GitHub releaseBuild f3b30c5ed2c0741d89f5fd216ab5dd2d4352a02c2026-09-11Recorded, not counted: it was cut from a rolling tag (latest, nightly, a dated or hashed build), which names a moving build rather than a release.
GitHub releaseBuild 783a04ee0f6278ea6e63c93a83659c03b4b023ca2026-09-11Recorded, not counted: it was cut from a rolling tag (latest, nightly, a dated or hashed build), which names a moving build rather than a release.
GitHub releaseBuild f9c180ff46f17f1746633f0ac73bb2862741f7d12026-09-11Recorded, not counted: it was cut from a rolling tag (latest, nightly, a dated or hashed build), which names a moving build rather than a release.
GitHub releaseBuild c915417e65f5190bf00900d2c7900eb8fcd15d982026-09-11Recorded, not counted: it was cut from a rolling tag (latest, nightly, a dated or hashed build), which names a moving build rather than a release.
GitHub releaseBuild 6129007d429955ba4ce121a23051999a88e3a7c62026-09-11Recorded, not counted: it was cut from a rolling tag (latest, nightly, a dated or hashed build), which names a moving build rather than a release.
GitHub releaseBuild eb2945e8d12cdef1ccccead23f317dfa34558a292026-09-11Recorded, not counted: it was cut from a rolling tag (latest, nightly, a dated or hashed build), which names a moving build rather than a release.
Named in code or runs on a hook, read from public code and the chain: a link, never a partnership or an on-chain interaction. A code link is a reference: the code names the token, which shows neither a dependency nor use; only a hook link is a pool running on the other’s hook. As data
Token Passport
No partner protocol has stamped this token in what HEY reads yet.
Each stamp is a fact HEY reads on chain or from the partner’s public data. It changes no status, Build Momentum, Discovery Gap, Radar, badge or order, and nobody pays for one. What a stamp is
Posts by @EkuboProtocol, as HEY last read them. Context only: a post is never counted as building and never sets the activity status.
2026-10-16How a private swap executes on @Starknet: shielded funds leave STRK20, swap against the same public pools as everyone else, and return shielded, in one transaction. If the minimum output isn't met, it reverts and nothing leaves the privacy pool. The full picture, including shado…
2026-10-14Private swaps, and now private LPing 🥷 Shadow Accounts are now live on Ekubo, allowing anyone to provide liquidity, earn trading fees, and manage LP positions without publicly linking their activity to their main wallet. A private DEX, without fragmenting liquidity. https://t.co…
2026-10-11Shield an asset, swap it against the deepest liquidity on @Starknet, and nobody sees who traded or how much. Live now at
2026-10-08Every Ekubo swap on Starknet is proven by STARK proofs, which are hash-based and expected to withstand quantum computers. If Starknet becomes the quantum-resistant L1 it is now considering, its DeFi won't be starting from zero. The largest DEX on the network is live today at htt…
2026-09-22You can now swap privately via Ekubo Protocol on Starknet! Try it out here:
