If you don't take risks you won't drink any champagne
Joined March 2022
- Tweets1.8K
- Following1.2K
- Followers69
- Likes3K
cryptoProlo99 🦇🔊 retweeted
Quand on pille les travailleurs français pour se payer 15 000 €/mois de salaire hors avantage en tout genre, qu’on utilise la police pour nourrir ses poules et qu’on refuse de publier ses notes de frais, on est directement responsable de ce qui arrive @YaelBRAUNPIVET.
Les actes de violences auxquels nous assistons aujourd’hui sont d’une gravité exceptionnelle.
Alors que de nombreuses villes ont été le théâtre de pillages, d’incendies volontaires et d’exactions insupportables, je tiens à apporter tout mon soutien à nos forces de l’ordre mobilisées pour protéger les Français.
J’appelle au calme et au dialogue. La démocratie donne à chacun le droit de faire entendre sa voix, jamais celui de s’en prendre aux personnes et aux biens.
cryptoProlo99 🦇🔊 retweeted
Pretty funny to see everyone blame this (rightly condemned, to be clear) on whatever their political bogeyman is: I've just seen people say that this is because of, take your pick, "communism," "Islamism," "third worldism," "Russia," and "China".
As if France needed any outside help to riot... Maybe some people need to brush up on our history, or read Victor Hugo's "Les Misérables"...
This isn't to romanticize the rioters in the least. A reminder that in Les Misérables there's the figure of Thénardier, a horrendous scoundrel who exploits the chaos around him, robbing corpses and fleecing anyone he can.
Every chaotic moment in French history has its share of Thénardiers, and this one is no exception.
It's just too easy, and actually useful to those in power, to blame this on outside forces. At the end of the day, this anger was made in France, is happening in France, and can only be solved in France.
And, as painful as it is to hear, if one studies history, this is pretty much exactly what's expected at the stage France is at.
People have studied this. Whether you take Ray Dalio’s six-stage cycle theory, Peter Turchin’s "elite overproduction" thesis or the Chinese dynastic cycle framework, they all come to the same conclusion: when debt piles up, public services crumble and those in power become incapable, the streets eventually explode.
In fact it's almost eerie how France ticks almost every box of most cycle theories:
- Fiscal distress (debt is 119% of GDP and we now pay more to borrow than Italy or Greece),
- Crumbling public services: a reminder that these protests (now turning into riots) started with high school students protesting over the state of education
- Political paralysis and a legitimacy crisis (Macron has an insane 82% disapproval rate, he's definitely lost the Mandate of Heaven...)
- Popular immiseration with a record poverty rate at 15.4% and a median wage at only €2,190 net per month for a full-time private sector employee (you can't even afford to rent a decent flat in any major French city with this)
"Third worldism" or "Islamism" isn't the cause of any of this: French governments didn't borrow like there's no tomorrow (the last balanced budget dates back to 1974!) because the "Muslim Brotherhood" told them to, and it wasn’t Putin or Xi who left French classrooms without teachers...
Sadly the reactions - scapegoating - are ALSO typical of this stage of the cycle: Dalio lists among the classic markers of Stage 5 the emergence of "scapegoat classes who are commonly believed to be the source of the problems" (linkedin.com/pulse/delving-s…), alongside a "loss of truth in the public domain," with people more interested in hunting for culprits than looking for solutions.
So what is the solution? Well, the way the Chinese dealt with it was basically a reset - regime-changing themselves with a new dynasty claiming the Mandate of Heaven, usually after decades of rebellion and war. Not exactly a hopeful prospect...
There is also the exception where a dynasty managed what the Chinese call a ä¸ĺ…´ (zhĹŤngxÄ«ng, "restoration"): profound reform from within before the whole house came down. It succeeded a few times (e.g. the Tongzhi restoration during the Qing dynasty) but usually could only buy a few more decades, rarely more.
In 1945, the writer Huang Yanpei famously asked Mao how to break free of the cycle (cn.vlex.com/vid/constitution…), framing it in those terms: "People are careful and hard-working at first, for bold measures are the only possible ways to break through difficult conditions. But when things gradually get better, people begin slacking off: laziness may spread through a long history and is impossible to be corrected when it becomes a common practice. Gradually expanded territory requires corresponding increases in talent, but when the latter is insufficient, the central control will become weak. In a word, no one can escape the 'vicious cycle' of dynastic rise and collapse."
Mao replied that democracy was the answer, because "as long as the people can supervise the government, the government dare not slacken." And Xi later added a "second answer" (chinadailyhk.com/hk/article/…): a system capable of "resolute self-reform".
The jury is still out on whether China has broken the cycle, but if France has any hope of escaping it, it will need both answers at once: a government that truly answers to its people, and very resolute self-reform.
One thing the answer definitely isn’t: turning on each other. In all these cycle theories, division and scapegoating appear on the way down, never on the way back up.
⚠️🔴 À REGARDER JUSQU'À LA FIN
JE NE PEUX PAS DÉCRIRE CE QUE JE VIENS DE VIVRE À MARSEILLE.
#17octobre
cryptoProlo99 🦇🔊 retweeted
Coup de gueule, parce que c'est bientôt le week-end, que c'est bien d'être très clair, et que sur X on peut vraiment dire ce qu'on pense.
Quand je lis des X des commentaires sur le Tesla Roadster du genre "à quoi ça sert", voila ce que j'ai envie de répondre :
À quoi ça sert ? À rien, petit imbécile aigri sans curiosité. Exactement comme ta vie, et probablement comme ta Renault Clio de 2014 et tes opinions sur Internet dont on se contrefout.
Oui, c’est un jouet de 1 000 chevaux qui fait 0-100 en moins d’une seconde, qui se colle au plafond, qui saute par-dessus un Semi et qui a des propulseurs SpaceX. C’est l’équivalent automobile d’un avion de chasse : ça ne sert à rien pour aller chercher le pain, et c’est précisément pour ça que c’est magnifique. Les gens qui demandent « à quoi ça sert » face à ça sont les mêmes qui auraient regardé les frères Wright et dit « ouais mais ça fait pas le café ».
C’est une vitrine technologique, un halo car, une démonstration de ce qui est possible quand tu arrêtes de faire des SUV gris pour des comptables et des fonctionnaires.
Ça ne va pas remplacer ta Tesla Model Y, ça va juste te rappeler que pendant que toi tu critiques du fond de ton canapé, d’autres construisent des trucs extraordinaires qui n’ont aucune raison d’exister… et c’est exactement pour ça qu’ils existent.
Continue à dire « à quoi ça sert ». C’est exactement le cri de guerre des gens qui n’ont jamais rien fait d’exceptionnel de leur vie, et probablement jamais rien fait du tout.
Je te plains, quelle vie médiocre tu dois avoir.
cryptoProlo99 🦇🔊 retweeted
Je vais dire quelque chose qui risque de déplaire à beaucoup de monde, mais tant pis.
Je crois qu’une partie de notre société est en train de perdre quelque chose de bien plus grave que sa compétitivité économique.
Elle est en train de perdre sa capacité à rêver.
Hier, Tesla a présenté une démonstration spectaculaire autour d’une voiture capable de quitter le sol. Un prototype, certes, pas encore la voiture volante de Retour vers le futur.
Mais quand mĂŞme, bordel. On parle de technologies qui semblaient relever de la science-fiction quand nous Ă©tions gamins.
Et ce matin, en regardant certaines réactions françaises, qu’est-ce que je découvre ?
« Ça sert à rien. »
« Musk est un raciste. »
« Ça ne règle pas les problèmes de recharge. »
« Ça n’efface pas ses saluts nazis. »
Mais sérieusement, qu’est-ce qui nous est arrivé ?
À quel moment avons-nous perdu cette âme d’enfant qui nous faisait ouvrir grand les yeux devant une invention ?
Et le plus triste dans tout ça, c’est qu’on semble avoir oublié notre propre histoire.
La France, c’est le pays des frères Lumière, qui ont contribué à faire naître le cinéma.
C’est le pays de Louis Pasteur, dont les travaux ont révolutionné la microbiologie et la vaccination.
C’est le pays de Nicéphore Niépce, pionnier de la photographie.
C’est le pays des frères Montgolfier, qui ont envoyé l’être humain dans les airs à bord d’une montgolfière.
C’est le pays de Blaise Pascal, qui concevait déjà une machine à calculer au XVIIe siècle.
C’est aussi le pays du TGV, et l’un des deux pays qui ont donné naissance au Concorde.
Vous imaginez ce que représentaient ces inventions à leur époque ?
Des humains qui osaient accomplir ce que beaucoup pensaient impossible.
Des gens qui n’acceptaient pas les limites de leur temps.
Des visionnaires, des ingénieurs, des scientifiques, des entrepreneurs qui voulaient repousser les frontières du réel.
Nous avons été ce pays-là .
Alors comment avons-nous pu en arriver à un point où notre premier réflexe devant l’extraordinaire semble parfois être de chercher pourquoi il faudrait le mépriser ?
SpaceX récupère des fusées qui reviennent se poser sur Terre ? On parle immédiatement d’Elon Musk et de ses provocations.
Des robots humanoïdes commencent à réaliser des tâches physiques de plus en plus complexes ? « Ça va détruire des emplois. »
L’IA ouvre des perspectives gigantesques pour la médecine, la science, l’éducation et la création ? « Ça pollue, ça vole le travail des artistes, ça sert à tricher. »
Un entrepreneur annonce vouloir réaliser quelque chose d’incroyable ? « Encore un milliardaire qui veut s’en mettre plein les poches. »
Mais est-ce qu’on réalise seulement ce qui est en train de se passer ?
Nous vivons une époque où des fusées réutilisables se posent après leur mission, où l’IA accélère certaines découvertes scientifiques, où des robots apprennent à évoluer dans notre monde, où des personnes seules commencent à créer des choses qui nécessitaient auparavant des équipes entières.
Et devant tout ça, on serait devenus incapables de dire simplement : « Putain, c’est incroyable. Comment est-ce qu’ils ont réussi ça ? »
Je ne demande pas qu’on admire aveuglément les milliardaires. Ni qu’on ferme les yeux sur les conséquences sociales, environnementales ou politiques de leurs projets.
On peut condamner les propos d’Elon Musk tout en reconnaissant les prouesses des ingénieurs de SpaceX et de Tesla.
On peut défendre les travailleurs tout en trouvant la robotique fascinante.
On peut vouloir encadrer l’IA tout en étant émerveillé par ses possibilités.
L’esprit critique n’a jamais obligé personne à devenir cynique.
Et c’est justement ce cynisme qui me désespère.
J’ai parfois l’impression qu’on a remplacé l’admiration par la jalousie, le goût du risque par la peur de l’échec, l’ambition par la suspicion et le rêve par le sarcasme.
cryptoProlo99 🦇🔊 retweeted
Every week someone tells me they vibe-coded their app over the weekend and don't need developers anymore.
Before it touches a paying customer, make sure it includes:
> a schema someone designed, instead of one the AI improvised table by table
> login that still works when someone puts a plus sign in their email
> password reset links that expire and work once
> MFA, plus a recovery path for the user who lost their phone
> sessions that time out, and a way to kill every session for one user
> SSO for the enterprise customer who won't sign without it
> SAML, because that customer's IT team doesn't do magic links
> SCIM, so a fired employee loses access the moment IT offboards them
> roles and permissions deeper than "admin" and "everyone else"
> checks that stop user A from reading user B's data by changing one number in the URL
> tenant isolation, so one customer's bug never shows another customer's records
> an admin "log in as this user" button for support, with an audit trail on every use
> rate limits on login, so nobody can guess passwords at scale
> lockouts that stop attackers without locking out your CFO the night before the board meeting
> database migrations that run forward and roll back
> migrations that don't lock the main table at 2pm on a Tuesday
> indexes, because the query that was instant on 50 test rows times out on 5 million real ones
> connection pooling, so a traffic spike doesn't exhaust the database
> backups every night
> a restore from those backups, tested, because a backup you've never restored is a hope
> point-in-time recovery for the day someone runs a delete without a where clause
> soft deletes, so "I deleted it by accident" is a support ticket and not an incident
> validation on the server, not just in the form
> timezones stored right, so the 9am reminder doesn't fire at 4am
> the customer with an apostrophe in their last name
> emoji, accents and right-to-left text in every field
> money stored as integers, because 0.1 + 0.2 doesn't equal 0.3 in floating point
> currency, rounding and tax rules for every country you sell into
> a data model that survives your second customer asking for "one small change"
> idempotency keys, so a retried payment doesn't charge the card twice
> deduplication for the user who clicks submit four times
> pagination that still works on page 400
> exports, because sooner or later every customer wants their data in a spreadsheet
> imports that survive the CSV someone saved in 2009
> retention rules, and code that deletes what your contract says you'll delete
> secrets out of the code, out of the repo and out of the AI chat history
> rotating every key the AI pasted into a config file last month
> confirming every package the AI installed exists and is the one you meant
> dependency scanning, because the AI pulled in libraries nobody reviewed
> input sanitization everywhere a user can type
> protection against SQL injection, XSS, CSRF and the rest of the OWASP list
> file uploads that get scanned, size-limited and stored where they can't execute
> CORS rules that aren't "allow everything"
> security headers on every response
> encryption at rest and in transit
> least-privilege access for everyone, including the AI agent holding production credentials
> logs that record who did what, without recording passwords, tokens or card numbers
> a penetration test before your enterprise customer's security team runs their own
> answers to the security questionnaire every enterprise buyer sends, with evidence behind each one
> a disclosure process for the day a stranger emails you a vulnerability
> a plan for the day a laptop with production access gets stolen
> SOC 2, which means policies, evidence and an auditor, not a checkbox
> HIPAA, the moment a single patient record touches your system
> a BAA with every vendor that touches that data, including your AI model provider
> audit trails that show who viewed a record, not just who changed it
> PCI scope, and card numbers kept out of your database
> GDPR deletion requests that reach every table, backup and log
> data residency for the customer whose contract says EU only
> quarterly access reviews someone signs off on
> dev, staging and production environments that match each other
> infrastructure written as code, so the setup lives somewhere other than one person's memory
> a deploy pipeline that runs the tests before anything reaches customers
> one-click rollbacks, because Friday deploys happen
> zero-downtime deploys, because your customers don't have maintenance windows
> feature flags, so you can ship the code without shipping the feature
> autoscaling for the Monday morning spike
> a CDN, so the app loads fast in Singapore too
> DNS, SSL certificates, and renewals that don't expire on a Sunday
> background job queues, so slow work doesn't freeze the page
> retries with backoff, so one flaky API call doesn't become a lost order
> a dead-letter queue for the jobs that fail every retry
> cron jobs that don't run twice the day you add a second server
> caching, and clearing that cache when the data changes
> SPF, DKIM and DMARC, so your password resets don't land in spam
> bounce and complaint handling on every transactional email
> storage rules, so you stop paying to keep 2021's temp files
> cost alerts, so a runaway agent loop shows up the same day and not on the invoice (we learned this one for $1,382.59)
> a disaster recovery plan, written down and tested once a year
> a second region, if your contract promises uptime one region can't deliver
> structured logs you can search at 3am
> error tracking that groups the same bug instead of sending you 4,000 emails
> uptime checks from outside your own network
> alerts that page a human, tuned until they stop paging for nothing
> dashboards for latency, error rate and throughput
> tracing for one slow request across every service it touches
> an on-call rotation, and a person who picks up
> runbooks, so the engineer on call knows what "queue depth critical" means
> postmortems that change something
> a status page customers check before they email you
> unit tests written by someone who knows what the logic should do
> integration tests for every third-party API you depend on
> end-to-end tests for signup, checkout and the other flows that make you money
> load testing before the launch email goes out
> test data that looks like production without being production data
> regression tests, so fixing bug 41 doesn't bring back bug 12
> testing on the five-year-old laptop your biggest customer's ops team still uses
> accessibility compliance, because the enterprise contract requires it
> subscriptions, upgrades, downgrades and proration
> failed-payment retries and dunning emails
> invoices with the customer's PO number on them, because procurement won't pay without it
> sales tax and VAT
> refunds, credits and partial refunds
> usage metering that matches what you bill, to the cent
> annual contracts with custom terms your billing logic never planned for
> revenue reports your finance team can reconcile
> webhooks that verify signatures
> webhooks that retry, with a log of every failed delivery
> a versioned API, so you can change it without breaking your customers' integrations
> API keys customers can create and revoke
> API rate limits that protect you without blocking real integrations
> a plan for the day a third-party API changes its response format without telling you
> OAuth token refresh, because tokens expire at the worst possible moment
> a sandbox where customers can test their integration
> protection against prompt injection in every field that reaches the model
> customer and patient data kept out of prompts that leave your network
> a model spend cap per customer, so one heavy user can't run up your bill
> evals, so you find out when a model update makes your answers worse
> a fallback for the afternoon your model provider goes down
> a migration plan for the day your model gets deprecated
> prompt and output logs for debugging, minus whatever you're not allowed to keep
> a human approval step for anything the AI does that can't be undone
> pages that load on hotel wifi
> empty states, loading states and error states on every screen
> error messages a customer can act on, instead of "something went wrong"
> forms that keep what people typed when one field fails validation
> emails that render in every mail client your customers use
> notifications people can turn off
> undo
> keyboard navigation and screen reader support
> translations, with dates and numbers formatted for each locale
> a back button that does what people expect
> code a human can read
> code review on every change
> a branching strategy, so two people can work without overwriting each other
> monthly dependency upgrades, so you're never two major versions behind
> framework upgrades before the old version stops getting security patches
> deleting the dead code the AI left behind from its first three attempts
> splitting up the 2,000-line file the AI kept appending to
> architecture decisions written down, with the reasons
> a README that gets a new engineer running locally in under an hour
> documentation for whoever inherits this
> an admin panel for your ops team
> support tooling, so customer success can answer questions without pinging engineering
> a changelog customers can read
> terms and a privacy policy that match what the code does
> every account, domain and repo in the company's name, not the name of whoever built the prototype
> a bus factor higher than one
Oh, and besides keeping all of this working every day, forever… your vibe-coded app will still need people who know what they're doing:
> reading every line the AI wrote before it ships (a senior engineer)
> designing the data model before your second customer breaks it (a backend engineer)
> explaining why the AI's fix for one bug created two new ones (a senior engineer, again)
> deploys, rollbacks, servers and the cloud bill (a DevOps engineer)
> answering the page at 3am when payments stop (whoever's on call)
> patching the framework the week a vulnerability goes public (security)
> walking an auditor through how patient data moves (security and compliance)
> testing what the AI says it tested (QA)
> running a migration on a live database without losing a row (a backend engineer)
> saying no to the feature that breaks three others (a tech lead)
> turning "works on my laptop" into "works for every customer at once" (an architect)
> debugging the code when the AI that wrote it can't (a senior engineer)
> remembering why it's built this way, a year from now (someone who was there)
…wishing them the best 🫡
cryptoProlo99 🦇🔊 retweeted
REA is most dangerous thing on the internet right now...
It lets your AI agent reverse engineer any app, down to the binary
If you use it correctly, you can rebuild any feature you pay for, for FREE
In this article, I show you how:
cryptoProlo99 🦇🔊 retweeted
Introducing Baskets, powered by @useDiversiFi.
You can now launch coins on Solana paired with multiple quote assets, through a single basket token.
FRONTIER is now live, combining $OPENAI, $META, $ANTHROPIC, $SPCX and $GOOG.
Only on StonkFun.
cryptoProlo99 🦇🔊 retweeted
perhaps one of the most durable parts of pstack are its engineering principles: very concise skills (~10-20 loc) that distill down good practices into its core.
as models get smarter, i expect most of pstack skills to compress into short principles or workflows (a generic list of steps) and that i will be able to delete a few of them.
how it works is that /poteto-mode contains a short index of available principles and tells agents "In your reply, name each principle that shaped a decision and the specific choice it changed." this is why you'll often see a Principles Named or Used section at the end of the agent's response
many of these principles were extracted from my sessions correcting agents since the start of this year. some are inspired by problems i see people talk about, like Attack the Premise, inspired by @VictorTaelin's post xitter.cf/VictorTaelin/status/20…
you can also use the principles as skills if you want greater control, by invoking /principle-
github.com/cursor/plugins/bl…
I'm a newcomer to @poteto's plist; But it seems to me that there is some very significant wisdom encoded in there. I suspect you could teach a master class on the principles.
cryptoProlo99 🦇🔊 retweeted
you don't need a Mac to build iPhone apps anymore.
Xtool is an open-source Xcode replacement that builds, signs and installs iOS apps from Linux, Windows or macOS.
Paste this into Claude Code:
"Install xtool (github.com/xtool-org/xtool) and run xtool setup.
Create a SwiftUI app called [NAME] that [WHAT IT DOES].
Keep it to 3 screens, native iOS components, dark mode support.
cryptoProlo99 🦇🔊 retweeted
okay now that we're past that tired discussion, let's talk about how we get agents to write more correct code (note: this won't mean the code will be Good, but it should at least work)
this is the entrypoint into your most basic agentic loop: verification. it means giving your agent the ability to verify its own work, most commonly by actually running and interacting with it like a real user would. whether your interface is a cli/api/ui/whatever, you want to start here so that your agents can close the loop. if you want you can even have your agents model the problem in TLA+ and attempt to verify if you have things like state machine bugs.
the point is to give yourself confidence in the agents' work by them producing some kind of artifact that proves that 1) that the work is correct, 2) that it matches what you intended, and 3) is easier to review than reading the whole PR. most commonly this would be a video and/or screenshots for UI work.
everything else like skill packs are really bonus and optional, all you need is a way for your agents to verify their own work to start using them more autonomously. some caveats are that not all domains can be verified easily yet, and that verification is just approximation and can still be wrong. it's no different than trusting that a human actually ran the code they wrote and trusting it
so start here!
pstack now includes 2 skills i recommend everyone use or copy:
/create-verification-skill
github.com/cursor/plugins/bl…
/maintain-verification-skill
github.com/cursor/plugins/bl…
if you don't already have one, /create-verification-skill creates a skill that teaches your agent how to run, control, and debug your app.
it also creates something i call the feature map: a map of all the features in your app and how to get to it and use it from a user's pov. it allows agents to navigate and use the app just like a real user which greatly increases its ability to verify its own work. but of course, this feature map goes out of date very quickly.
run /maintain-verification-skill as a daily automation with cursor cloud agents. this skill will check your app for changes and keep your feature map up to date.
having a strong verification skill will end up becoming critical infra for your team and become the foundation of boosting everyone's productivity and quality and also enable more interesting automations to be built.
install cursor.com/marketplace/curso… and you'll get auto updates for my skills. enjoy!
cryptoProlo99 🦇🔊 retweeted
lets talk about $stonk properly
the market is starting to price this thing like a random memecoin when the actual tokenomics are way more interesting than that
current price is around $0.136
mcap roughly 106-108M
ATH was ~0.40, so we’re already ~66% off the highs
now the part that matters:
1B initial supply
~204m already burned
~796m left
no classic “team unlocks coming to nuke you” overhang
and the platform is using real revenue to buy $stonk off the open market and burn it
roughly 60% of platform revenue goes back into buybacks/burns
last 30d:
~$26m protocol revenue
~$13m buybacks
last 7d:
~$2.5m revenue
~$1.3m buybacks
even using the weaker 7d numbers, that annualizes to roughly $69m in buybacks against a ~$108m mcap
obviously you don't straight line that forever, but the point is simple:
this is not some token where “buybacks” are a future promise
the mechanism is already live
supply is already shrinking
20%+ of total supply is already gone
at current valuation, the market is basically betting that StonkFun activity keeps collapsing
and maybe it does
but if revenue stabilizes and volume comes back, this becomes a very different valuation very quickly
for context, $pump trades at a much richer multiple while $stonk currently sits at a fraction of that valuation despite having a very aggressive buyback structure
technically the chart is still ugly, no point pretending otherwise
we’re below the major EMAs and the old ~$0.15 support got lost
but this is exactly the type of setup that has potential to make you rich overnight, high risk, high reward
fundamentals still producing real cash flow
token supply going down every day
price getting nuked
everyone losing interest
if $stonk reclaims the $0.15-$0.155 area while revenue/buybacks stop making lower lows, i think the market will have to reprice this thing pretty hard
for me the bet is simple:
if StonkFun survives the current cooldown and usage starts expanding again, $108m mcap looks stupidly cheap
weakly chart to put some perspective onto things
remember: once shit starts moving, its gonna take few 4h candles to reverse this entire downtrend
cryptoProlo99 🦇🔊 retweeted
23 free github repos memecoin traders use instead of paying for bots
all open source. i checked every one: real teams, real code, nothing asks you to paste a private key into a stranger's app
track wallets
1.) handi-cat → telegram bot that pings you when any solana wallet buys or sells
2.) insider-monitor → watch a list of wallets, discord alert on every balance change
3.) vybe top traders → find the most profitable wallets in any token
4.) vybe trader pnl → full pnl of any wallet + the wallets linked to it
5.) stampede → robinhood chain: see what wallets sold right before they bought the next coin
check a coin before you buy
6.) dexscreener-cli → hot token scanner in your terminal, no api key
7.) dexscreener (python) → pull any pair into your own scripts
8.) rug-check-mcp → claude checks a CA for rug risk
9.) gmgn agent skills → GMGN's official data for AI agents: smart money, KOL holders, bundlers
claude & ai agents
10.) helius core-ai → official helius plugin, claude reads solana onchain data
11.) solana-agent-kit → connect any AI agent to solana
12.) tradingview-mcp → charts, TA and backtests inside claude
13.) elizaOS → the framework behind ai16z and the AI agent coins
build & backtest (burner wallet only)
14.) chainstack pump.fun bot → open source pump.fun sniper from chainstack
15.) pump public docs → pump.fun's official docs to build your own bot
16.) hummingbot → trading bots for jupiter, raydium, meteora + 100 CEXs
17.) freqtrade → backtest a strategy on years of data before you risk money
18.) ccxt → one api for 100+ exchanges
don't get drained
19.) revoke.cash → kill old token approvals
20.) rabby → wallet that shows what changes before you sign
21.) phantom blocklist → 2,300+ sites phantom flags as drainers
22.) scam sniffer database → 357K phishing domains
23.) metamask phishing list → the list metamask uses to block fake sites
how to spot a fake repo: the #1 github result for "solana copy trading" was created in 2013. solana launched in 2020
old account + thousands of stars + a telegram link in the description = drainer
bookmark this
cryptoProlo99 🦇🔊 retweeted
We've all seen the regular stats about how bad @Pumpfun tokens are. About how the vast majority of traders lose money.
But the gigabytes of data I've been assembling over the past few days paints a much darker picture.
I've spun up a VPS and am in the process of backfilling a hoarde of data (burning a ton of Helius credits) and comparing @Pumpfun to @LaunchOnSF
Because of how many tokens are launched every single day the backfill process is still running, although I do have enough data to start being statistically accurate.
I'm capturing data for the entire last month as well as logging all new data in real time. An expensive project, but a valuable one.
For example, I already have learned:
Tokens that have graduated on @LaunchOnSF are 3X more likely to still be active within 24 hours than graduated tokens on @Pumpfun
That jumps to 5X a week after graduation.
While both launchpads have a less than 2% graduation success rate what happens next is the most telling.
Pump fun also has a much higher rate of "fake liquidity" (support being placed and then pulled before rug) than Stonk tokens.
How do I know?
My system is also tracking every single liquidity event. It's watching and logging every time people play games with liquidity in order to manipulate a chart.
More insights will be shared with the greater amount of data I capture/backfill.
This will be interesting.
cryptoProlo99 🦇🔊 retweeted
If you’re going to build a personal agent, a Meal & Grocery Agent should be near the top of the list.
Not to throw random recipes at you. To take the weekly “what are we eating?” problem and turn it into an actual system.
Think about what that takes off your plate:
› Fewer last-minute dinner decisions
› Meals that actually fit your schedule
› Better use of what’s already in the fridge, freezer, and pantry
› One organized grocery list built around the plan
› Easier adjustments when the week changes
› A simple way to keep leftovers and ingredients from disappearing from the plan
Here’s the blueprint for building one.
› Plan meals around the nights you actually have time to cook
› Work around your household’s likes, dislikes, and usual meals
› Use what you already have in the pantry, fridge, or freezer
› Combine what’s missing into one grocery list
› Rework the plan when your schedule changes
› Keep track of leftovers and ingredients you still want to use
Then you make it yours.
› How many people you’re feeding
› Favorite meals
› Cooking time
› Equipment you actually use
› Foods you want to avoid
› How often you’re okay repeating meals
› Optional budget targets
The blueprint below gives you a starting structure for the routines, memory, tools, rules, automations, and outputs behind the agent.
Build the structure once. Then shape it around how your household actually eats.
cryptoProlo99 🦇🔊 retweeted
1/ Agent cursors were never much to look at.
Today we're introducing 6 new cursor motions in Cua Driver, each hand-crafted and perfectly timed. We studied how people aim a mouse, built 82 motions in a playground, and kept the best six.
It's all open source: github.com/trycua/cua