FancyRat retweeted
Today, I shipped TWAP orders on solana:96ZXmfUBwCPUVpuZGLw1nmRH5ET9oXWfxEZRXLBQzosg.
CA: 96ZXmfUBwCPUVpuZGLw1nmRH5ET9oXWfxEZRXLBQzosg
The reason behind this is that sometimes, when you buy or sell a large order, it can definitely pump the chart significantly or completely nuke it. Instead, when you buy or sell in smaller chunks, with buys and sells happening gradually, it becomes much easier to manage the chart. That is what I have shipped.
I am also building my own liquidity pools for Nyraa launches. When users swap through Nyraa’s pools, a portion of the trading fees charged by the pool can go to the Nyraa treasury. This means that instead of depending on external LPs, Nyraa can provide liquidity itself and earn fees. We can decide how much liquidity to provide for each token pair, when to add or remove liquidity, and at which price range to deploy capital.
Also, since Nyraa will have its own liquidity, aggregators can consider Nyraa’s pools as another route for certain trades. If the pools have deep and competitive liquidity, users can get better execution. As trading activity increases across popular token pairs on Nyraa, the LPs can generate fees. This revenue can then be used for the treasury, development, buybacks, or ecosystem incentives. We will use this for $NYRAA and other top tokens on Nyraa through buybacks and burns.
Users will also benefit from significantly lower slippage because the deeper the liquidity, the lower the price impact. They will also see less difference between the expected price and the actual execution price. We will also be able to maintain liquidity for our important token pairs instead of depending entirely on external LPs.
We will also integrate these pools into our swap and bridge.
Imagine a $20K market cap solana:96ZXmfUBwCPUVpuZGLw1nmRH5ET9oXWfxEZRXLBQzosg looking more bullish than any other launchpad.
We are only 15 days old, and we still haven’t graduated. The only thing we need right now is for some big players to notice Nyraa, because all I can do is keep shipping and building what the community wants, including things that no other launchpad has built yet.
> Since launch, we have already burned more than 4% of the total supply of $NYRAA.
> You can swap, bridge, use Private Swap, and even use Shield Swap on Nyraa. We have added Solana, BNB Chain, Robinhood Chain, Ethereum, Elysium, and HyperEVM to our swap page, and we will be adding more chains soon. We also use more than 20 DEX routers for swaps. This means Nyraa checks different routers and executes your swap or bridge through the route that gives you the best available rate, the deepest liquidity, and the lowest slippage. Private Swap uses a one-time address without revealing the asset you receive, while Shield Swap allows you to send assets to another wallet without directly linking the receiving wallet.
After that, we made several frontend changes to make Nyraa work like a home-screen app. Now, Nyraa works much faster than many other trading platforms and launchpads.
We are getting around 200–400 new visitors every day, and because of that, we have already brought in approximately 70 users. We are growing every single day.
We also integrated stop-loss and take-profit features into Nyraa. Most platforms like FOMO and Pumpfun are unlikely to bring this kind of technology because a large part of their revenue comes from these activities.
After that, we integrated Lighter for perpetual trading, which means users can trade on Lighter while staying on Nyraa. We will also soon integrate perpetual trading platforms like RiseX, Arcus, and TXFlow so users can farm points and participate in their airdrop seasons directly through Nyraa. We are building this as a social trading platform where users can do all of this in one place.
Then we launched PnL cards on Nyraa, allowing users to share their profits and losses with others and show their trading journey.
After that, we launched our referral program, through which any user can invite their friends to Nyraa and earn 30% of the fees generated by them. The process is very simple and fast. Whenever your referred friends trade and fees are charged, your 30% share is sent directly to your wallet instantly.
We also launched token creation on Robinhood Chain with stocks and commodities as paired assets.
Then we started offering Zcash-native, Solana-powered private launches on Nyraa. Whenever you create a coin, Nyraa generates a fresh wallet that has never interacted with your Nyraa wallet or profile. This means your identity as the creator stays private.
After that, we made it possible to launch a token paired with any existing token on Solana. You simply need to enter the contract address of the token you want to use as the pair. As far as I know, we are among the first launchpads to offer this.
Then we integrated Hyperliquid’s native Elysium chain into Nyraa, which also made token launches on Elysium possible.
We also launched the bank deposit feature, which means users can now add funds to Nyraa directly from their bank accounts.
After that, we launched the option to connect and log in using an X account.
Then we launched the Nyraa feed, where users can share their trading ideas, convictions, and market updates. They can write posts, add tickers, send voice notes, and even use GIFs. Other traders can read their posts and interact with them. We are also the first trading platform to bring this kind of experience together in this way.
So, all I want to say is that even though our market cap is much lower than that of other launchpads out there, we haven’t left any stone unturned. We have given this project more than 100% of our effort, and we have kept delivering new things every single day.
FancyRat retweeted
TWAP orders are now live on Nyraa.
You can now buy and sell tokens in smaller chunks instead of placing one large order. Since Nyraa is a social trading app, you can use this feature to trade even low-cap coins.
Try it.
nyraa.xyz/
FancyRat retweeted
We have officially crossed 200 members on Telegram!
Join our Telegram community to connect directly with Nyraa community members and the team.
t.me/nyraa_xyz
FancyRat retweeted
solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump will go up and will go down but you will not shake me out my conviction stands strong heck I just got more everyone will see how big this is one day @kennethreitz42 GitHub is huge and so is the lore behind the token just wait!
FancyRat retweeted
price dipped on solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump today and my conviction hasn’t moved at all. let me explain why.
if you’re new here, requests is the python library that lets an app talk to a server. @kennethreitz42 wrote it in 2011 because doing http in python was painful, and it just passed 40 billion downloads. it’s still pulling around 50 million a day. stripe, google, azure, dropbox, twilio, they all ship python sdks that depend on it. even the early openai and anthropic sdks ran on it.
kenneth is the biggest holder of solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump. he built the site himself, put the CA in his own github bio, and the creator fees go toward his work. there’s an official account @Requests_Token, and every claim on the site links to something you can check on chain or on pypi. you rarely see that level of transparency on a coin this small.
so about today. i went through the trades and nobody big dumped. it’s small sells on thin liquidity, and there were actually more buys than sells. kenneth’s own bag, around 10% of supply, is locked on streamflow and can’t be touched until feb 14. funny enough that’s the exact day he published requests 16 years ago.
and he’s still building while the chart does whatever it does. this week he added mcp support to his web framework and made httpbin usable by ai agents. that’s not a guy who’s checked out.
remember when people were launching coins around open source repos and the fees went to the devs who built them? the whole idea was giving something back to people whose work everyone already uses. this is that idea, except the dev is actually here, holding, building, and the library is one of the most used pieces of software on the planet.
meanwhile random memes with no story go to 7 figures in a day, and this one is sitting under $30k with only a few hundred holders.
that’s extremely undervalued to me. same conviction, just a cheaper price.
requeststoken.org
CA: 6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump
dyor nfa
FancyRat retweeted
solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump
Ngl, the way people talk about “utility” in this market is getting weird.
I remember the 2025 meta when people were launching coins around established open-source projects and popular GitHub repos, directing creator fees to the developers behind them. A big part of the appeal was giving something back to people who had already built things others used.
Plenty of people understood that idea without demanding a whole new product or token utility roadmap.
Now I look at solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump and wonder where that mindset went.
@kennethreitz42 created Requests, a Python library with more than 15 years of history behind it. He’s publicly involved with the community token. There’s an official website, an official X account, @Requests_Token, and creator fees go to @kennethreitz42.
There’s an actual connection to the original creator that anyone can verify. Personally, I think that deserves a lot more recognition than it’s getting.
Meanwhile, I keep seeing projects I’d call utility slop reach million dollar mc. A website, some technical buzzwords, a roadmap full of promises, and people are already aping because they’re scared of missing the next runner.
Whether the product actually works, whether anyone needs it, whether the token has a meaningful role, all of that can apparently wait until after they buy.
Nobody gives a f* if it’s LARP or slop as long as the chart keeps going up, right?
Then solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump comes up, and suddenly token utility is the deciding factor.
Look, asking about utility is completely fair. The library and the token are separate. People using Requests doesn’t automatically create demand for solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump, and the token doesn’t inherit the library’s adoption just because they share a name.
I understand that.
What I don’t understand is accepting attention, community and a story as reasons to value one coin, then treating those same reasons as worthless when discussing another.
If supporting an established creator through trading fees made sense to you before, what specifically makes it unacceptable here?
And if utility really is your standard, apply it properly. A project putting “utility” in its docs should have to explain what works, who uses it and why the token needs to exist. A promise of utility shouldn’t get a free pass just because it sounds technical.
An honest community token shouldn’t have to invent a product to compete with projects whose products barely exist.
@kennethreitz42 involvement doesn’t mean the market owes solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump a particular price. But his track record and public involvement matter to me. So does the idea of a community recognising someone who has already contributed something useful.
If your main thesis is momentum, that’s fine. Just call it momentum. If you’re buying because you think the narrative will catch on, say that.
But don’t dress up FOMO as deep research, then become a utility purist the moment someone brings up solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump.
All I’m asking for is a consistent standard.
FancyRat retweeted
Ngl, the way people talk about “utility” in this market is getting weird.
I remember the 2025 meta when people were launching coins around established open-source projects and popular GitHub repos, directing creator fees to the developers behind them. A big part of the appeal was giving something back to people who had already built things others used.
Plenty of people understood that idea without demanding a whole new product or token utility roadmap.
Now I look at solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump and wonder where that mindset went.
@kennethreitz42 created Requests, a Python library with more than 15 years of history behind it. He’s publicly involved with the community token. There’s an official website, an official X account, @Requests_Token, and creator fees go to @kennethreitz42.
There’s an actual connection to the original creator that anyone can verify. Personally, I think that deserves a lot more recognition than it’s getting.
Meanwhile, I keep seeing projects I’d call utility slop reach million dollar mc. A website, some technical buzzwords, a roadmap full of promises, and people are already aping because they’re scared of missing the next runner.
Whether the product actually works, whether anyone needs it, whether the token has a meaningful role, all of that can apparently wait until after they buy.
Nobody gives a f* if it’s LARP or slop as long as the chart keeps going up, right?
Then solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump comes up, and suddenly token utility is the deciding factor.
Look, asking about utility is completely fair. The library and the token are separate. People using Requests doesn’t automatically create demand for solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump, and the token doesn’t inherit the library’s adoption just because they share a name.
I understand that.
What I don’t understand is accepting attention, community and a story as reasons to value one coin, then treating those same reasons as worthless when discussing another.
If supporting an established creator through trading fees made sense to you before, what specifically makes it unacceptable here?
And if utility really is your standard, apply it properly. A project putting “utility” in its docs should have to explain what works, who uses it and why the token needs to exist. A promise of utility shouldn’t get a free pass just because it sounds technical.
An honest community token shouldn’t have to invent a product to compete with projects whose products barely exist.
@kennethreitz42 involvement doesn’t mean the market owes solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump a particular price. But his track record and public involvement matter to me. So does the idea of a community recognising someone who has already contributed something useful.
If your main thesis is momentum, that’s fine. Just call it momentum. If you’re buying because you think the narrative will catch on, say that.
But don’t dress up FOMO as deep research, then become a utility purist the moment someone brings up solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump.
All I’m asking for is a consistent standard.
FancyRat retweeted
I believe there is no python dev who doesn't know what $request library is 👀
The Giant is still sleeping 🤯
$requests by @kennethreitz42
#16 @tableau
@tableau Python tooling is another place where Requests shows up.
The Tableau Server Client (TSC) library lets developers manage published workbooks, data sources and other Tableau resources through Python.
One practical example is refreshing a published data extract after new data becomes available.
After signing in and retrieving the relevant data source, a script can trigger the refresh with:
server.datasources.refresh(datasource)
TSC submits that command to Tableau’s REST API through a Requests session. Tableau runs the refresh job, while Requests handles the HTTP communication used to submit it.
You can trace this in the source code. The client defaults to requests.session as its session factory, and its endpoint layer sends POST requests through that session.
The package also lists requests>=2.32 as a required dependency.
For a reporting workflow, this means a Python script can request an extract refresh once the upstream data is ready. Requests provides the HTTP connection between that script and Tableau’s API.
Another concrete example for the solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump series, this time in the tools used to automate business reporting.
The HTTP session implementation:
github.com/tableau/server-cl…
The required dependencies:
github.com/tableau/server-cl…
FancyRat retweeted
Not sure how and why solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump larping at 33k
Literally @kennethreitz42 launched who is the dev of python requests used by billions
50k plus stars, used billions of time
The largest GitHub on chain ever, larger than SOL, ETH AND BNB BTW
6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump
REPRICING
FancyRat retweeted
#16 @tableau
@tableau Python tooling is another place where Requests shows up.
The Tableau Server Client (TSC) library lets developers manage published workbooks, data sources and other Tableau resources through Python.
One practical example is refreshing a published data extract after new data becomes available.
After signing in and retrieving the relevant data source, a script can trigger the refresh with:
server.datasources.refresh(datasource)
TSC submits that command to Tableau’s REST API through a Requests session. Tableau runs the refresh job, while Requests handles the HTTP communication used to submit it.
You can trace this in the source code. The client defaults to requests.session as its session factory, and its endpoint layer sends POST requests through that session.
The package also lists requests>=2.32 as a required dependency.
For a reporting workflow, this means a Python script can request an extract refresh once the upstream data is ready. Requests provides the HTTP connection between that script and Tableau’s API.
Another concrete example for the solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump series, this time in the tools used to automate business reporting.
The HTTP session implementation:
github.com/tableau/server-cl…
The required dependencies:
github.com/tableau/server-cl…
#15 @ApacheAirflow
A scheduled data pipeline still needs a way to talk to external APIs.
In @ApacheAirflow HTTP provider, the Python Requests library handles that job for its synchronous HttpHook.
Airflow lets developers schedule and monitor workflows. Think of a daily job that fetches new orders from an API, processes the response and passes the results to another task.
With the API connection configured and the hook set to GET, fetching those orders could look like:
hook.run(endpoint="orders")
Inside the hook, Airflow imports Session from Requests, creates Session(), prepares the HTTP request and sends it through session.send(...).
The provider also explicitly lists requests>=2.32.0,<3 as a required dependency.
That gives us both pieces of evidence: the package declares Requests as a requirement, and the implementation uses it to execute HTTP calls.
Airflow coordinates the workflow. Requests handles the HTTP exchange in this synchronous hook.
I’m adding this to the solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump series because it shows another practical role for the library: fetching the external data that an automated workflow needs before its next task can run.
The HTTP hook implementation:
github.com/apache/airflow/bl…
The required dependencies:
github.com/apache/airflow/bl…
FancyRat retweeted
solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump
6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump
By @kennethreitz42
FancyRat retweeted
How can someone send coins with random images to a 7 figures in a single day? 🤯
Meanwhile there's a $requests coin with the deepest and largest history in the tech industry? 💥
#15 @ApacheAirflow
A scheduled data pipeline still needs a way to talk to external APIs.
In @ApacheAirflow HTTP provider, the Python Requests library handles that job for its synchronous HttpHook.
Airflow lets developers schedule and monitor workflows. Think of a daily job that fetches new orders from an API, processes the response and passes the results to another task.
With the API connection configured and the hook set to GET, fetching those orders could look like:
hook.run(endpoint="orders")
Inside the hook, Airflow imports Session from Requests, creates Session(), prepares the HTTP request and sends it through session.send(...).
The provider also explicitly lists requests>=2.32.0,<3 as a required dependency.
That gives us both pieces of evidence: the package declares Requests as a requirement, and the implementation uses it to execute HTTP calls.
Airflow coordinates the workflow. Requests handles the HTTP exchange in this synchronous hook.
I’m adding this to the solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump series because it shows another practical role for the library: fetching the external data that an automated workflow needs before its next task can run.
The HTTP hook implementation:
github.com/apache/airflow/bl…
The required dependencies:
github.com/apache/airflow/bl…
FancyRat retweeted
朝起きたら、 solana:6ceuPfcE67PLs3Z6CbJpFpqNyAevVocP2zsDkbM1pump 少し下落していたので、何回かに分けて買い増し！
2%保有になりました！🍟
ハードウォレットに格納しておこうかな。
