Notify only
Designed to follow activity without preparing a transaction. You decide when to act.
you are in the top
Lintcha — copy-trading
Lintcha is preparing Copy for selected wallets and launchpad activity on Robinhood Chain in @lintchabot. Automated BUYs remain off while safety checks continue.
Funds remain in your self-custody wallet. Never share a seed or private key in Telegram or with Lintcha. Auto-BUY will require user-set limits; SELL will remain manual.
Lintcha is AFK. The website and published snapshot remain available. Telegram, live reads and wallet connections are paused.
Copy-trading controls are being prepared in @lintchabot. Auto-BUY stays off until delegation, provider and safety checks pass.
Core tools: live · Copy-trading: auto-BUY off until every gate passes · $LINTCHA: live on pons
Designed to follow activity without preparing a transaction. You decide when to act.
Planned: copy matched BUYs only within your caps, allowlists, slippage and expiry after all safety gates pass.
Manual-only by design: each approval and SELL would require separate wallet review and confirmation.
Copy starts with an explicit source you select. Lintcha does not invent a portfolio, rank traders or follow an account behind your back.
Add a public address you want to watch. Its matching BUY activity can become an alert or enter your bounded copy rule.
Follow supported public BUY activity from launchpads such as pons. Every venue enters through an explicit allowlisted adapter.
Choose notification-only or bounded auto-BUY for each source. Nothing is copied until that rule is active.
A matching transaction would be only a trigger. Submission remains off until current-state simulation, independent RPC agreement and an active user policy can be verified.
Accept only activity from the wallet, venue, chain and BUY pattern named by your rule.
Build a fresh quote, estimate the transaction and require independent providers to agree before signing or broadcast.
Reject anything outside the spend, slippage, router, spender, selector or expiry boundary you set.
Broadcast is off. After qualification and explicit enablement, a permitted BUY would be submitted once; uncertain states would be reconciled without a blind retry.
Auto-copy requires a narrow, visible and revocable permission. This path is designed around those boundaries and remains off until the checks pass.
The planned SELL path would use a fresh quote and require separate review and explicit wallet confirmation. Auto-SELL is unavailable.
Synthetic checked-in fields, not a launch. The current published snapshot is read by the same engine as your own input.
snapshot ended .
This section states what the collector read, how each field is normalized before it is hashed, the two tables that fold spellings and hosts, the floor under every count, and what the index holds. The tables are written from the engine's own files at build time, so they cannot drift from the code that runs in your browser.
One day: the 24 hours ending at the latest finalised block at the time of the run, found by bisecting block timestamps, so the window is stated as a block range and two UTC timestamps, 2026-09-10 23:24 to 2026-09-11 23:24. A day was the window one pass over the launch log covered at the endpoint's sustained pace; a longer window would say more about strings and nothing more about launches.
For each guarded refresh, the code records one finalized block number and hash, makes one pass over the launch log of the pons factory on Robinhood Chain, then reads every identity field at that numeric state. Before the writer can run, an owned publication guard re-reads the events through two smaller page layouts with different boundaries, compares every canonical raw row, strictly re-reads sample transactions and identity returns, and must rebuild the same tables and summaries. These are alternate queries to the same configured endpoint, not an independent-provider proof. The snapshot printed on this page carries that identity-state record and passed the publication guard before it shipped. Addresses and raw strings remain inside the processes; a successful refresh writes only counted hashes and its own run figures.
www., trailing slashes and the fragment removed; the path keeps its case. Any other scheme is kept whole, whitespace collapsed only.^0x[0-9a-f]{40}$; checksum case is cosmetic. The zero address counts as empty; anything else that fails the pattern is not readable.An entry is kept when 2 launches or more carry the value, so absence reads as no other launch in the window carrying it. The fee recipient has a second floor, 2 deployers or more, because the same recipient under one deployer is a person relaunching, and that is neither shown nor stored.
Per namespace, the first eight bytes of the hash of the normalized value as sixteen hex characters, and against it three fields: n, how many launches carry it; d, from how many distinct deployers; first, the UTC date of the earliest. The two skeleton namespaces add v, the number of distinct spellings in the group. No address, no raw string, no timestamp beyond a date.
Lintcha is becoming Copy-first: follow selected activity, receive alerts or copy matched BUYs inside limits you control. The original launch-reading tools remain Lintcha Core and stay read-only. Here is what is already testable in the tree, what must pass before auto-BUY opens, and what comes after. No dates.
The index is rebuilt by a weekly guarded run and can also be refreshed by a deliberate manual dispatch. Its age still varies when a run fails closed. The page states that age in words beside every result, as well as printing the block range and timestamps from which it was derived.
A count from a stale window is not wrong. It is a true statement about a day that has ended, and the page says which day. But somebody pasting a launch that happened this morning is comparing it with a set that does not contain this morning, and the sentence they read does not warn them. That is the gap, and it is ours, not the endpoint's.
What is in now: the age of the window beside every result and a state-pinned rebuild behind the published snapshot. The guarded refresh runs weekly and can also be dispatched manually. It can become more frequent only as often as a suitable endpoint sustains without weakening the guard. The window will not be widened to make the counts look bigger. If a rebuild fails, the page keeps the old window and says its age rather than showing a partial one.
One Telegram identity, with read-only Core and an isolated Copy service. Core does not hold keys or trade. Copy is an opt-in path under preparation, with its own route, database, audit and kill switches. Auto-BUY is off until bounded permissions, user limits and safety checks are verified. SELL remains manual by design. Never enter a seed or private key in Telegram or on the Lintcha backend.
$LINTCHA is live on pons. Creator fees from its trading are intended to go to one wallet, and that wallet is meant to pay for the endpoint plan, the box the bot runs on and the hours that go into the index. Nothing else is attached: no share, no cut, no vote. It cannot gate the MIT-licensed code, buy an earlier reading or buy a better one, because there is one published index for everyone.
Commits show what shipped and when. The hash printed above identifies the shipped index bytes, and the numbers artifact records the finalized identity state and window used to build them. The strict command re-reads that state and window, rebuilds the index and compares the hash; any incomplete read or failed guard is a refusal, not a reproduced result. The vendor table names every file copied from lintcha with its hash, and a test recomputes all of them on every push. If something here goes quiet for weeks, ask about it in public.
No dates. Here, shipped means implemented and testable in the repository. Deployment, provider qualification and production trading each need separate verification. Auto-BUY remains off until its delegation, provider, simulation and safety gates pass.
Auto-BUY is off. If enabled after safety checks, only matched BUYs from selected sources within active limits would proceed to simulation and one submission. SELL will remain manual.
Public wallets and supported public BUY activity from launchpads can become sources. You select the source and choose notification-only or bounded auto-BUY; Lintcha does not silently discover or rank traders for you.
No. Funds remain in your self-custody wallet. Never share a seed or private key with Lintcha or Telegram. The planned auto-BUY path requires a bounded, revocable permission; SELL is designed as a separate manual wallet action.
Auto-BUY is off. The service has a global broadcast stop; per-user pause and revocation must be verified before production trading.
No. Auto-SELL is unavailable. The planned SELL path requires a fresh quote, wallet review and explicit confirmation.
No. It tells you whether the strings a launch publishes are shared with other launches of one day, how many, from how many deployers, and since when. Whether a launch is safe, honest or worth anything is not something strings can say, and this page does not say it.
No. What you paste stays in your browser, and the comparison runs there against the table it fetched. Nothing is stored and no cookie is set. The page does make one request: the first time you check, it fetches that table from this domain, and nothing after that.
Yes. The engine, the collector, the index writer, the tests and this page are in the repository linked in the footer. The engine is written in lintcha and copied here unchanged; a table in the repository names every copied file with its hash.