Not named by the project: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Token market
Follow puts Lemniscate on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
Building ranks ahead, and the market already notices it, among comparable projects: its building is ahead of 98.5% of them, its market attention ahead of 79.2% (a gap of 19.2). What the Discovery Gap is
It compares building with market attention; it is not a prediction and not a reason to trade.
More detail
Product usage
Fact1 of 1 watched contract active · 1 call to the contracts' own functions over the 3 of 7 days HEY holds; the other 35,640 of 35,641 calls were ERC-20 token transfers and approvals, which trading alone produces; the rest unknown, not zero.
Counted from the chain. Usage says the contracts are used, not that anyone is building.
Contracts
Fact1 contract on record for code changes, 1 with published source code; no implementation or interface change recorded.
Not yet known
Unknown2 gaps: Official site changes (not tied to the project yet), Market history (not enough yet). Its website is not yet confirmed as the project’s own.
“Shipping” by the activity rule: 4 counted ships in the last 30 days, the newest 2026-11-05.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsUpdate 26: Faster first load on phonesUpdate 23: Dark modeCode changes this week (since Mon 2 Nov) · 32 commits+1 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found counted building from the project's own sources.
Not named by the project: HEY has not confirmed that the project stands behind this contract — HEY knows it from a launchpad record, and the site that record named does not name it.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedNot named by the project: HEY knows it from a launchpad record, and the site that record named does not name it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Active market.
Active market: the pool holds liquidity and the token traded in the last day.
Source5 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Research coverage: HEY can answer 13 of the 15 research questions that apply.
13 of 15 applicable dimensions measured.
Identity
IdentityMeasuredRead 1d ago.
Building
Building activityMeasuredRead 1h ago.
RepositoriesMeasured
ReleasesMeasuredRead 1h ago.
TimelineMeasured
Official site
Official site changesNot tied to the project yetIts website is not yet confirmed as the project’s own.
Contracts
Contract creationMeasuredRead 2h ago.
Contract activityMeasuredRead yesterday.
Published source codeMeasuredRead 2h ago.
Contract interfaceMeasuredRead 2h ago.
Market
Current marketMeasuredRead 2m ago.
Market historyNot enough yetNo daily market history recorded yet.
Supply distributionMeasuredRead yesterday.
LocksMeasuredRead 3h ago.
Market checksMeasured
Not applicable here: Official docs, API description, Repository details, Published packages, Package advisories, Protocol economics.
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
Why it matters: One of 4 counted ships in the last 30 days: building continued, not a one-off.
The site now opens much faster on a phone with a slow connection. The first screen used to wait for every photo on the page before it showed anything; now it waits only for what you can actually see, and loads the other photos as you scroll. Pages also use less mobile data on…Show allShow less
The site now opens much faster on a phone with a slow connection. The first screen used to wait for every photo on the page before it showed anything; now it waits only for what you can actually see, and loads the other photos as you scroll. Pages also use less mobile data on arrival: the home page needed about 2.1 MB before it was ready, and now needs about 1.0 MB.
Record ship:7e0394cd… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.
Release, read from the team’s GitHub · no deployment linked›
What it names
The team’s release names it: “Update 26: Faster first load on phones” (update-26).
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it 2026-11-05 02:18 UTC; HEY first knew on 2026-11-05.
Not known
HEY does not hold the commit the release was cut from.
HEY has not observed a deployment of this change.
Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.
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: 10 weeks 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.
2 releases in lemniscatedev/lemniscate today
GitHub release
Show all 2 releasesHide the releases
Update 25: TypeScript SDK for the public API
GitHub release · Source-backed
Developers can now use a ready-made TypeScript library to talk to the Lemniscate API instead of writing requests by hand. It knows the shape of every answer, turns errors into clear messages, respects the API's request allowance and can follow live prices. It only reads data and…Show allShow less
Developers can now use a ready-made TypeScript library to talk to the Lemniscate API instead of writing requests by hand. It knows the shape of every answer, turns errors into clear messages, respects the API's request allowance and can follow live prices. It only reads data and prepares transactions for you to sign; it never touches your keys, and before returning a transaction it checks that it targets the Lemniscate contracts. It is not published on npm: install it from the sdk/ folder of the…
Update 24: Monthly statement download (CSV and print/PDF)
GitHub release · Source-backed
You can now get a monthly statement for any wallet. Pick a month and the Statements page shows what the account bought, sold, deposited into the Writer Pool, which options it held at month end and the holding cost paid in kind. Download it as a CSV for your records, or print the…Show allShow less
You can now get a monthly statement for any wallet. Pick a month and the Statements page shows what the account bought, sold, deposited into the Writer Pool, which options it held at month end and the holding cost paid in kind. Download it as a CSV for your records, or print the page and save it as a PDF from your browser. This is a $LMNI Holder perk: hold 100,000 $LMNI in the connected wallet to unlock it. Trading, deposits and withdrawals stay open to everyone.
Lemniscate now has a dark mode. It follows your device setting by default, and a sun or moon button in the header lets you switch for this browser; your choice is remembered only in your own browser. The look keeps the same deep navy, gold and cream, with cream text on navy and…Show allShow less
Lemniscate now has a dark mode. It follows your device setting by default, and a sun or moon button in the header lets you switch for this browser; your choice is remembered only in your own browser. The look keeps the same deep navy, gold and cream, with cream text on navy and a softer gold for small text so it stays readable. Every page and every workspace tab was checked in both modes on a phone-sized screen (all routes) and spot-checked on desktop.
Update 22: Indexer reorg-safety report on the status page
GitHub release · Source-backed
Sometimes a blockchain briefly replaces its latest few blocks with a different version. This is called a reorganisation, and the indexer is built to detect it and rewind safely. The status page now reports how it is coping: how many reorganisations it has handled, the deepest…Show allShow less
Sometimes a blockchain briefly replaces its latest few blocks with a different version. This is called a reorganisation, and the indexer is built to detect it and rewind safely. The status page now reports how it is coping: how many reorganisations it has handled, the deepest one, and when it last checked. If one were ever too deep to repair automatically, the page would say so plainly.
Update 21: Strike grid, breakeven and "pays off if" lines on the chart
GitHub release · Source-backed
The option chart on the dashboard now shows where an option pays for itself. As you pick a strike in the strike grid, the chart draws today's price, the cost to buy one unit as a dashed line, and a marked breakeven price. The side of the breakeven where the option has paid for…Show allShow less
The option chart on the dashboard now shows where an option pays for itself. As you pick a strike in the strike grid, the chart draws today's price, the cost to buy one unit as a dashed line, and a marked breakeven price. The side of the breakeven where the option has paid for itself is shaded, and a line under the chart says it in words, for example "Pays off if NVDA is above $184.53". The same chart appears on Shield for the protection strike you choose. These are the same numbers as the…
Update 20: Accessibility pass (keyboard and screen readers)
GitHub release · Source-backed
The whole site can now be used without a mouse. A "Skip to main content" link appears on the first Tab press, every button, link and field shows a clear outline when you reach it with the keyboard, and the menu opens, closes with Escape and gives focus back to its button. Screen…Show allShow less
The whole site can now be used without a mouse. A "Skip to main content" link appears on the first Tab press, every button, link and field shows a clear outline when you reach it with the keyboard, and the menu opens, closes with Escape and gives focus back to its button. Screen readers now hear the page change when you move between pages, headings follow a sensible order, and text colours were darkened slightly so small grey and gold text is easier to read. Our test suite now runs an automated…
Update 19: Agent tools for volatility and receipts
GitHub release · Source-backed
AI agents that use the Lemniscate agent server (MCP) get two more read-only tools. One shows the volatility numbers behind every option price for a stock, including when each was posted and when it expires. The other shows the hourly receipts, a fingerprint covering every trade…Show allShow less
AI agents that use the Lemniscate agent server (MCP) get two more read-only tools. One shows the volatility numbers behind every option price for a stock, including when each was posted and when it expires. The other shows the hourly receipts, a fingerprint covering every trade, volatility post and pool value in that hour, as published by the Lemniscate API (not written on chain). Neither tool can trade or move funds. Stated plainly: the agent server is in the public repository and you can run it…
The API now tells every client how much of its request allowance is left and when it resets, and it lets clients and the CDN check whether data changed before downloading it again. Apps and bots that read prices get faster answers and use less of their allowance; nothing about…Show allShow less
The API now tells every client how much of its request allowance is left and when it resets, and it lets clients and the CDN check whether data changed before downloading it again. Apps and bots that read prices get faster answers and use less of their allowance; nothing about prices or trading changes.
You can now turn on browser alerts in Settings. When they are on, your browser shows a notification when the daily holding cost of one of your positions moves by 25% or more, when the market session changes on a name you hold or are viewing, or when a sell that was queued for a…Show allShow less
You can now turn on browser alerts in Settings. When they are on, your browser shows a notification when the daily holding cost of one of your positions moves by 25% or more, when the market session changes on a name you hold or are viewing, or when a sell that was queued for a fresh price is filled. Alerts are off until you choose to turn them on, you can pick which kinds you want, and there is a test button. They work while the dashboard is open in a browser tab; they are not push messages and…
There is a new Volatility page. Option prices depend on a volatility input that is posted on chain for each stock and speed. The page charts how that input moved over 7, 30 or 90 days, marks the posts that included an event bump such as earnings, and lists the latest posts with…Show allShow less
There is a new Volatility page. Option prices depend on a volatility input that is posted on chain for each stock and speed. The page charts how that input moved over 7, 30 or 90 days, marks the posts that included an event bump such as earnings, and lists the latest posts with the transaction that carries each one. This is a $LMNS Holder perk: hold 100,000 $LMNS in the connected wallet to unlock it. Trading, deposits and withdrawals stay open to everyone.
You can now check any trade yourself. Every hour Lemniscate seals all trades, volatility posts and pool NAV snapshots into one Merkle root, which its API publishes. On the new Receipts page, paste a transaction hash and your own browser recomputes the trade's fingerprint and…Show allShow less
You can now check any trade yourself. Every hour Lemniscate seals all trades, volatility posts and pool NAV snapshots into one Merkle root, which its API publishes. On the new Receipts page, paste a transaction hash and your own browser recomputes the trade's fingerprint and walks the proof up to that hour's published root. If a single number had been changed, the check would fail. Stated plainly: the roots are published by the Lemniscate API, not written on chain, so the check proves the trade…
The Activity tab now has a filter bar. Search by name, kind, ticket number or transaction, pick a kind (bought, sold, Shield, queued sells, Writer Pool, agent trades), pick a name, and choose a date range. The list narrows as you type, and a counter says how many of the loaded…Show allShow less
The Activity tab now has a filter bar. Search by name, kind, ticket number or transaction, pick a kind (bought, sold, Shield, queued sells, Writer Pool, agent trades), pick a name, and choose a date range. The list narrows as you type, and a counter says how many of the loaded items match. Filters work on what is already loaded on the page; "Load older activity" brings in more. This is a $LMNS Holder perk: hold 100,000 $LMNS in the connected wallet to unlock it. Trading, deposits and withdrawals…
When the indexer falls behind, for example after a restart or a provider hiccup, it used to read the chain one slice at a time and then wait before the next slice. It now reads several slices at once and then writes them to the database strictly in order, and it comes back…Show allShow less
When the indexer falls behind, for example after a restart or a provider hiccup, it used to read the chain one slice at a time and then wait before the next slice. It now reads several slices at once and then writes them to the database strictly in order, and it comes back immediately while it is still behind. The result is the same data, reached sooner, so the app and the status page are current again faster after an interruption.
Update 12: Keeper gas tuning, accrual batch sizes from measured gas
GitHub release · Source-backed
The keeper regularly updates every open option series in batches of at most 45 series per transaction. That cap stays. What changed: the keeper now measures how much gas each series really costs on chain, and when a batch of 45 would not fit comfortably inside its gas budget it…Show allShow less
The keeper regularly updates every open option series in batches of at most 45 series per transaction. That cap stays. What changed: the keeper now measures how much gas each series really costs on chain, and when a batch of 45 would not fit comfortably inside its gas budget it picks a smaller one. It writes the chosen size to its log. That lowers the chance that a batch is too big for a block. Batches never exceed the 45-series cap (before this update the keeper always sent 40; when gas allows…
You can now download the whole option chain of any listed name as a spreadsheet (CSV) or as data (JSON). Every strike, both speeds, calls and puts, with the buy price, sell price, daily cost, breakeven and the Greeks per option unit, all taken from the same moment as the chain…Show allShow less
You can now download the whole option chain of any listed name as a spreadsheet (CSV) or as data (JSON). Every strike, both speeds, calls and puts, with the buy price, sell price, daily cost, breakeven and the Greeks per option unit, all taken from the same moment as the chain on the dashboard. It is meant for people who want to look at prices in their own tools. This is a $LMNS Whale perk: hold 1,000,000 $LMNS in the connected wallet to unlock it. Trading, deposits and withdrawals stay open to…
There is now a readable reference for the Lemniscate API at /v1/docs on the API host. It lists every route in the published API specification (/v1/openapi.json), what to send, what comes back and an example request, and it is built from the same specification the API publishes…Show allShow less
There is now a readable reference for the Lemniscate API at /v1/docs on the API host. It lists every route in the published API specification (/v1/openapi.json), what to send, what comes back and an example request, and it is built from the same specification the API publishes, so it always matches what the service really does. It works on phones and in dark mode.
Each position on the Positions tab now has a History button. It shows two charts for that option: its value over time and how many effective units you hold over time. You can see the units shrink with the continuing holding cost, and the steps where you bought, sold or moved…Show allShow less
Each position on the Positions tab now has a History button. It shows two charts for that option: its value over time and how many effective units you hold over time. You can see the units shrink with the continuing holding cost, and the steps where you bought, sold or moved tokens. This is a $LMNS Holder perk: hold 100,000 $LMNS in the connected wallet to unlock it. Trading, deposits and withdrawals stay open to everyone.
Update 8: Writer Pool NAV history chart with funding received
GitHub release · Source-backed
The Writer Pool tab now has a history section. It charts the pool's NAV and the NAV per share over 7 days, 30 days, 90 days or all time, plus the funding the pool received each day. Funding received is an estimate, and NAV can fall as well as rise: hedge results and market gaps…Show allShow less
The Writer Pool tab now has a history section. It charts the pool's NAV and the NAV per share over 7 days, 30 days, 90 days or all time, plus the funding the pool received each day. Funding received is an estimate, and NAV can fall as well as rise: hedge results and market gaps move it too. This is a $LMNS Holder perk: hold 100,000 $LMNS in the connected wallet to unlock it. Trading, deposits and withdrawals stay open to everyone.
The dashboard now gets price changes pushed to it the moment the service sees them, instead of waiting for the next 15-second refresh (that refresh still runs as a fallback). When a price, the market session or the buy state of the name you are looking at changes, its option…Show allShow less
The dashboard now gets price changes pushed to it the moment the service sees them, instead of waiting for the next 15-second refresh (that refresh still runs as a fallback). When a price, the market session or the buy state of the name you are looking at changes, its option chain and your quote refresh right away. If the live connection is not available, the page quietly goes back to checking every few seconds, so nothing is lost. This is a $LMNS Whale perk: hold 1,000,000 $LMNS in the connected…
Update 6: Shield preview, protection level vs cost
GitHub release · Source-backed
Before you add a Shield, the Shield page now shows a small table: how much protection you would get at 5%, 10% and 15% below today's price, and what each costs. For each level it shows the listed strike, the estimated cost now, the cost per day, the cost over 7 and 30 days, and…Show allShow less
Before you add a Shield, the Shield page now shows a small table: how much protection you would get at 5%, 10% and 15% below today's price, and what each costs. For each level it shows the listed strike, the estimated cost now, the cost per day, the cost over 7 and 30 days, and the price below which it pays off. If no strike is listed near a level, it says so. The table follows the number of units you type, and "Choose" picks that level for you. The exact amount is still quoted before you…
Update 5: Clear messages for every failed transaction
GitHub release · Source-backed
When a transaction cannot go through, the dashboard now tells you why in plain words instead of showing a code or a vague "failed". For example: the price moved past your slippage limit, this option has reached its size limit, new purchases are paused, or you are asking to…Show allShow less
When a transaction cannot go through, the dashboard now tells you why in plain words instead of showing a code or a vague "failed". For example: the price moved past your slippage limit, this option has reached its size limit, new purchases are paused, or you are asking to protect more Stock Tokens than you hold. Each message also says whether your funds moved. If a transaction was sent and then reverted, the page looks up the reason from the chain and explains that too.
The dashboard now shows an earnings calendar. For each stock it lists the next report date and exactly when new buys pause around it, in your local time. Existing options keep running and can always be sold. Daily options pause for the whole report day, Weekly options for a…Show allShow less
The dashboard now shows an earnings calendar. For each stock it lists the next report date and exactly when new buys pause around it, in your local time. Existing options keep running and can always be sold. Daily options pause for the whole report day, Weekly options for a short window around the report.
Update 3: Backup RPC connection, on by default, used only when the main one fails
GitHub release · Source-backed
Lemniscate reads the chain and sends its housekeeping transactions through the official Robinhood Chain public RPC. We added a second, independent backup connection that is used only when the public RPC fails: every call still goes to the public RPC first, and the backup answers…Show allShow less
Lemniscate reads the chain and sends its housekeeping transactions through the official Robinhood Chain public RPC. We added a second, independent backup connection that is used only when the public RPC fails: every call still goes to the public RPC first, and the backup answers only the calls the public RPC just refused or could not reach. When the public RPC answers again, traffic goes straight back to it. Free RPC providers limit how many blocks one log query may cover, so the indexer asks the…
This week HEY looked inside 3 of 32 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.
The full change record holds 1 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 0x63b5C2B1eB93Ad62EA06560370f4f317eE1b97D3 on Robinhood Chain
https://get-lemniscate.tech/Context onlyContext only because HEY reached this site through a launch record or a listing and nothing yet ties it to this token; it counts once the site names the token’s contract, a GitHub claim names one of the project’s repositories, or a moderator confirms one of them.
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
Questions HEY can answer about Lemniscate — as of 5 Nov
FactUpdate 26: Faster first load on phones — GitHub release, today.Evidence →
Is 0x63b5C2B1eB93Ad62EA06560370f4f317eE1b97D3 Lemniscate’s own contract?
UnknownNot named by the project: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership.Details →
What does HEY not know about Lemniscate?
Unknown2 gaps: Official site changes (not tied to the project yet), Market history (not enough yet). Its website is not yet confirmed as the project’s own.
Posted on X (20)
Posts by @uselemniscate, as HEY last read them. Context only: a post is never counted as building and never sets the activity status.
2026-11-05filters and search on the Activity tab. Search by name, kind, ticket or transaction, or pick a kind, a name and a date range. The list narrows as you type, across what's loaded. A $LMNI Holder perk on @RobinhoodApp Chain.
2026-11-05Our last 24 hours on Lemniscate, in under a minute. 15 updates: costs before you buy, safer defaults, faster prices, your history, API docs, and a Receipts page to check any trade yourself. Options that never expire, on @RobinhoodApp Chain. $LMNI https://…Announced on X: SDK or API change
2026-11-05keeper gas tuning. The keeper now measures what each option series really costs in gas. If a batch of 45 wouldn't fit its gas budget comfortably, it sends a smaller one and logs the size. Cap stays at 45 (it used to always send 40).
2026-11-04Almost 100 of us now. $2,500 in rewards is still up for grabs. Options that never expire, on @RobinhoodApp Chain. Join the army. $LMNI
2026-11-04export any option chain as CSV or JSON. Every strike, both speeds, calls and puts, with buy/sell price, daily cost, breakeven and Greeks. Whale perk: hold 1,000,000 $LMNI. Trading, deposits and withdrawals stay open to everyone.
