Launch a coin for any GitHub project. Support open source projects at the earliest stages š
GitHub
- Tweets 335
- Following 0
- Followers 7,825
- Likes 686
Say hi to GitFish š
Tokenize and trade Github repos ā support open source!
Every like and retweet = we'll donate $1 to open source
102
178
904
306,285
GitFish V2 is now live on @Solana.
1 GitHub project -> 1 coin. Popular projects cost more points to launch.
Support open source. Find the next big thing.
P.S. We're airdropping bonus points to V1 users daily over the next five days. The first drop is live ā enjoy!
64
37
243
77,117
Weāve officially completed all $LINUX refunds.
ā
8,889 users refunded
š° 25,030 SOL returned
š 100% recovery rate ā even for those who sold
Appreciate everyoneās patience and support.
Next up: GitFish V2 is coming very soon. Turn on š
LINUX Refund Update
Weāve completed data processing and loss calculations for all users who haven't yet received a refund.
[IMPORTANT] Action required by June 14th 5pm EST:
- If you donāt have any remaining LINUX: Please review your address and total loss in bit.ly/no-remaining-linux
- If you still hold LINUX: Please send it to our admin address (EX7QGHSreah6EUtsPXCcen5R8JUyiVQWgz6aV4UspyMy) and review your total loss in bit.ly/has-remaining-linux
- If you never sold any LINUX but havenāt received a refund: Check if you still hold any LINUX. If yes, send it to our admin address. If not, please contact us via DM.
If you believe your data is incorrect or missing, contact us via DM. If everything looks correct, you donāt need to do anything.
Refund Process & Timeline
After this post, users will have 2 days to review their total losses and report any issues.
If no major issues arise, we will finalize the ārecovery rateā and send partial refunds to everyone on the bit.ly/no-remaining-linux list.
For anyone still on the bit.ly/has-remaining-linux list after the deadline, refunds will be processed once they return their remaining LINUX to the admin wallet.
FAQ
Q: What is the ārecovery rateā?
Recovery rate = total available SOL for refund (~18K) / total losses across all users.
We currently estimate it will be 95%+ (final number depends on any user-reported issues). This means that all users will recover the majority of their losses.
Q: Why are total losses shown in SOL? What if I traded using other tokens (e.g. USDC)?
We only have SOL (from the liquidity pool + auction fees) to refund users. Loss calculations are based on the SOL value at the time of your original transactions.
Q: Why isn't there a hard refund deadline?
We are handling massive on-chain data from thousands of people with many edge cases across various DeFi protocols to trade LINUX. Itās a very complicated process so itās hard to guarantee an exact deadline without overpromising.
That said, we donāt expect many more unhandled edge cases after users complete this data review.
Our current estimation is the majority of refunds will be sent shortly after this review period.
Q: Where will the refund be sent if I have multiple addresses?
Refunds will be sent to the address where you either:
- last sold all your LINUX, or
- sent all remaining LINUX to the admin wallet.
129
17
199
64,583
GitFish V2 + LINUX refund
This past week, we introduced GitFish to the world. We made a bold move to launch our first token, $LINUX, to test the new protocol in public. The launch attracted way more attention than we expected, but we also ran into some significant challenges:
- We introduced a fair launch design to prevent sniping and protect our users. But combined with a long auction duration and uncapped raise, it absorbed the majority of demand by listing and eliminated all wealth effects for traders.
- We were the ones to pick the first repo to launch on our platform. But the choice should have been up to the repo owner and community ā to secure alignment and buy-in for the token.
So hereās what weāre going to do next.
$LINUX refund
First, weāre going to refund all $LINUX bidders and traders, and retire the token.
When designing the GitFish protocol, we built in a special āpool retirementā mechanism to address the problem of āzombie poolsā. A zombie pool is a pool where almost all tokens have been sold back, but some SOL remains locked forever. Retirement allows these funds to be withdrawn, so they can be redistributed to users.
Prior to this announcement, we invoked the retirement mechanism for the $LINUX pool, withdrawing 25,003 SOL to the admin wallet. We will use 100% of the funds, along with collected auction fees (deducting 25% for referrals), to compensate all bidders and traders who have realized a loss, as follows:
- Bidders or buyers who never sold their $LINUX will get a full refund. This includes bidders who never claimed their tokens.
- Those who sold all or part of their $LINUX will receive a partial refund.
A detailed description of the refund mechanism, WIP table of usersā refund, plus supporting data and calculations is available here: github.com/gitfishdev/linux-ā¦
[IMPORTANT] To all users, hereās what you need to do by June 5th 9pm EST (one week's time):
- If you are holding LINUX tokens (including in LP), send it to our admin wallet to be eligible for a refund. Please donāt sell or otherwise transfer your tokens.
- If you havenāt claimed your tokens yet, donāt do it.
- If youāve already sold tokens to the pool, you donāt need to do anything either.
Admin wallet: EX7QGHSreah6EUtsPXCcen5R8JUyiVQWgz6aV4UspyMy
Failing to follow the above means you will forfeit your refund.
GitFish V2
Now thatās out of the way, weāre excited to announce we will shortly be releasing GitFish V2. Weāve been iterating fast based on the learnings of V1, and weāre excited to show you a newer, better version of GitFish.
Here are the headline updates:
- Going forward, tokens will only be launched by repo owners with their consent.
- Weāre making GitFish permissionless with the goal to onboard a lot more repo tokens. Weāre going to stop launching tokens ourselves and focus on helping repo owners launch their own.
- No more uncapped launches. All tokens will now have a much lower raise target. Once the target is reached the sale ends.
Weāre keen to ship something that will resonate with users and would love to hear your thoughts.
Whatās next?
We will be hosting a Twitter Space on Friday 30th May 9am PST to answer questions about the refund process and share more about GitFish V2. Come chat with us.
Sincerely,
GitFish team
124
26
183
131,585
GitFish V2 Update: weāre finalizing the details on GitHub community coins to ensure sustainable upside for both projects and supporters.
In the meantime, weāre launching a new feature today: permissionless tipping.
- For tippers: you can now support any GitHub project with a tip, and add a message to the maintainer if you like.
- For maintainers: connect your GitHub and set up your profile to claim the tips.
Everyone uses open source software, but almost no one pays for it. Go say thanks by leaving a tip!
14
16
98
26,591
A friendly reminder that the $LINUX auction ends in 12 hours ā on 25 May 2025 9am EST. You can continue to add / remove bids up to auction end at no extra cost.
Once the auction finishes, we will migrate 99% raised SOL plus 1/3 token supply to a Raydium pool to enable trading. Allocated tokens will be available to claim immediately.
28
2
80
34,071
LINUX Refund Update
Weāve completed data processing and loss calculations for all users who haven't yet received a refund.
[IMPORTANT] Action required by June 14th 5pm EST:
- If you donāt have any remaining LINUX: Please review your address and total loss in bit.ly/no-remaining-linux
- If you still hold LINUX: Please send it to our admin address (EX7QGHSreah6EUtsPXCcen5R8JUyiVQWgz6aV4UspyMy) and review your total loss in bit.ly/has-remaining-linux
- If you never sold any LINUX but havenāt received a refund: Check if you still hold any LINUX. If yes, send it to our admin address. If not, please contact us via DM.
If you believe your data is incorrect or missing, contact us via DM. If everything looks correct, you donāt need to do anything.
Refund Process & Timeline
After this post, users will have 2 days to review their total losses and report any issues.
If no major issues arise, we will finalize the ārecovery rateā and send partial refunds to everyone on the bit.ly/no-remaining-linux list.
For anyone still on the bit.ly/has-remaining-linux list after the deadline, refunds will be processed once they return their remaining LINUX to the admin wallet.
FAQ
Q: What is the ārecovery rateā?
Recovery rate = total available SOL for refund (~18K) / total losses across all users.
We currently estimate it will be 95%+ (final number depends on any user-reported issues). This means that all users will recover the majority of their losses.
Q: Why are total losses shown in SOL? What if I traded using other tokens (e.g. USDC)?
We only have SOL (from the liquidity pool + auction fees) to refund users. Loss calculations are based on the SOL value at the time of your original transactions.
Q: Why isn't there a hard refund deadline?
We are handling massive on-chain data from thousands of people with many edge cases across various DeFi protocols to trade LINUX. Itās a very complicated process so itās hard to guarantee an exact deadline without overpromising.
That said, we donāt expect many more unhandled edge cases after users complete this data review.
Our current estimation is the majority of refunds will be sent shortly after this review period.
Q: Where will the refund be sent if I have multiple addresses?
Refunds will be sent to the address where you either:
- last sold all your LINUX, or
- sent all remaining LINUX to the admin wallet.
GitFish V2 + LINUX refund
This past week, we introduced GitFish to the world. We made a bold move to launch our first token, $LINUX, to test the new protocol in public. The launch attracted way more attention than we expected, but we also ran into some significant challenges:
- We introduced a fair launch design to prevent sniping and protect our users. But combined with a long auction duration and uncapped raise, it absorbed the majority of demand by listing and eliminated all wealth effects for traders.
- We were the ones to pick the first repo to launch on our platform. But the choice should have been up to the repo owner and community ā to secure alignment and buy-in for the token.
So hereās what weāre going to do next.
$LINUX refund
First, weāre going to refund all $LINUX bidders and traders, and retire the token.
When designing the GitFish protocol, we built in a special āpool retirementā mechanism to address the problem of āzombie poolsā. A zombie pool is a pool where almost all tokens have been sold back, but some SOL remains locked forever. Retirement allows these funds to be withdrawn, so they can be redistributed to users.
Prior to this announcement, we invoked the retirement mechanism for the $LINUX pool, withdrawing 25,003 SOL to the admin wallet. We will use 100% of the funds, along with collected auction fees (deducting 25% for referrals), to compensate all bidders and traders who have realized a loss, as follows:
- Bidders or buyers who never sold their $LINUX will get a full refund. This includes bidders who never claimed their tokens.
- Those who sold all or part of their $LINUX will receive a partial refund.
A detailed description of the refund mechanism, WIP table of usersā refund, plus supporting data and calculations is available here: github.com/gitfishdev/linux-ā¦
[IMPORTANT] To all users, hereās what you need to do by June 5th 9pm EST (one week's time):
- If you are holding LINUX tokens (including in LP), send it to our admin wallet to be eligible for a refund. Please donāt sell or otherwise transfer your tokens.
- If you havenāt claimed your tokens yet, donāt do it.
- If youāve already sold tokens to the pool, you donāt need to do anything either.
Admin wallet: EX7QGHSreah6EUtsPXCcen5R8JUyiVQWgz6aV4UspyMy
Failing to follow the above means you will forfeit your refund.
GitFish V2
Now thatās out of the way, weāre excited to announce we will shortly be releasing GitFish V2. Weāve been iterating fast based on the learnings of V1, and weāre excited to show you a newer, better version of GitFish.
Here are the headline updates:
- Going forward, tokens will only be launched by repo owners with their consent.
- Weāre making GitFish permissionless with the goal to onboard a lot more repo tokens. Weāre going to stop launching tokens ourselves and focus on helping repo owners launch their own.
- No more uncapped launches. All tokens will now have a much lower raise target. Once the target is reached the sale ends.
Weāre keen to ship something that will resonate with users and would love to hear your thoughts.
Whatās next?
We will be hosting a Twitter Space on Friday 30th May 9am PST to answer questions about the refund process and share more about GitFish V2. Come chat with us.
Sincerely,
GitFish team
53
3
75
55,569
The $LINUX auction has ended and liquidity migration to @RaydiumProtocol is complete. Our site is receiving massive traffic at the moment. If you are unable to access the page, please wait for a while and try again later to avoid overloading our servers.
Thanks for your patience ā we'll comment below once it's resolved. Sorry for the inconvenience, and rest assured you will be able to claim your tokens.
54
2
72
26,625
Refunds of ~1428 SOL have just been sent to all users who have participated in the auction but did not claim their $LINUX.
For other groups of users, please be patient as we continue processing your refunds.
GitFish V2 + LINUX refund
This past week, we introduced GitFish to the world. We made a bold move to launch our first token, $LINUX, to test the new protocol in public. The launch attracted way more attention than we expected, but we also ran into some significant challenges:
- We introduced a fair launch design to prevent sniping and protect our users. But combined with a long auction duration and uncapped raise, it absorbed the majority of demand by listing and eliminated all wealth effects for traders.
- We were the ones to pick the first repo to launch on our platform. But the choice should have been up to the repo owner and community ā to secure alignment and buy-in for the token.
So hereās what weāre going to do next.
$LINUX refund
First, weāre going to refund all $LINUX bidders and traders, and retire the token.
When designing the GitFish protocol, we built in a special āpool retirementā mechanism to address the problem of āzombie poolsā. A zombie pool is a pool where almost all tokens have been sold back, but some SOL remains locked forever. Retirement allows these funds to be withdrawn, so they can be redistributed to users.
Prior to this announcement, we invoked the retirement mechanism for the $LINUX pool, withdrawing 25,003 SOL to the admin wallet. We will use 100% of the funds, along with collected auction fees (deducting 25% for referrals), to compensate all bidders and traders who have realized a loss, as follows:
- Bidders or buyers who never sold their $LINUX will get a full refund. This includes bidders who never claimed their tokens.
- Those who sold all or part of their $LINUX will receive a partial refund.
A detailed description of the refund mechanism, WIP table of usersā refund, plus supporting data and calculations is available here: github.com/gitfishdev/linux-ā¦
[IMPORTANT] To all users, hereās what you need to do by June 5th 9pm EST (one week's time):
- If you are holding LINUX tokens (including in LP), send it to our admin wallet to be eligible for a refund. Please donāt sell or otherwise transfer your tokens.
- If you havenāt claimed your tokens yet, donāt do it.
- If youāve already sold tokens to the pool, you donāt need to do anything either.
Admin wallet: EX7QGHSreah6EUtsPXCcen5R8JUyiVQWgz6aV4UspyMy
Failing to follow the above means you will forfeit your refund.
GitFish V2
Now thatās out of the way, weāre excited to announce we will shortly be releasing GitFish V2. Weāve been iterating fast based on the learnings of V1, and weāre excited to show you a newer, better version of GitFish.
Here are the headline updates:
- Going forward, tokens will only be launched by repo owners with their consent.
- Weāre making GitFish permissionless with the goal to onboard a lot more repo tokens. Weāre going to stop launching tokens ourselves and focus on helping repo owners launch their own.
- No more uncapped launches. All tokens will now have a much lower raise target. Once the target is reached the sale ends.
Weāre keen to ship something that will resonate with users and would love to hear your thoughts.
Whatās next?
We will be hosting a Twitter Space on Friday 30th May 9am PST to answer questions about the refund process and share more about GitFish V2. Come chat with us.
Sincerely,
GitFish team
27
5
55
45,321
Another ~1265 SOL has just been refunded to bidders and traders who never sold their LINUX. This is in addition to the ~4.4K SOL we refunded on 3 June, and reflects new data gathered since the last distribution.
To all users who have already sent back your LINUX to us by the deadline, thank you. We are working hard to calculate everyoneās refunds ā there are lots of specific cases to handle, and weāre manually working through all of them to make sure we donāt miss anyone.
If you sent back LINUX after the deadline, we will still refund you. If you havenāt yet sent us your tokens, please do so ASAP.
We will distribute more refunds to remaining users shortly.
38
5
49
49,258
Itās been a crazy 48 hours since launch ā and weāre blown away by your energy and support.
Weāve seen lots of great questions about how the auction process works. To help, weāre releasing a more detailed user manual and FAQ.
One important note: claiming fees by repo owners is always opt-in ā weāll mark the repo with a blue tick once they do.
17
2
49
21,932
We've been working around the clock to determine the best way forward for $linux. A full announcement is coming in the next few hours ā we're finalizing the last details now.
We'll also host a community space this week to answer all questions directly.
27
3
50
15,089
Another ~4121 SOL have just been sent to all bidders and traders who have never sold their $LINUX.
If you haven't sent your $LINUX to the admin wallet yet, please do so ASAP so we can dispatch your refund.
Refunds of ~1428 SOL have just been sent to all users who have participated in the auction but did not claim their $LINUX.
For other groups of users, please be patient as we continue processing your refunds.
95
2
47
39,039
Crypto might actually fix open source funding by aligning incentives.
Pure donations don't scale because there is no upside for supporters.
But what if an open source project's success also meant coin success?
Project success -> coin success -> more fundings -> project achieve bigger success
15
46
10,297
From day one, the @MeteoraAG team has been incredible to work with ā no BS, just fast, hands-on support. They jumped in right away to help us integrate and have been reliable partners ever since. We're using their fee scheduler to help prevent sniping in our platform.
Solid tech and team.
Meteora has the Best Tech. The Best Launchpads.
And today, weāre taking it to the next level.
Weāre dropping 3 massive product upgrades that will change how tokens launch forever:
Presale Vaults
Meteora Invent
Dynamic Fee Sharing
Youāre gonna want to see this.
7
5
41
12,258
For users who haven't reviewed the data yet, please do so ASAP by following the instructions. The refund will be sent out soon after June 14th, 5pm EST.
LINUX Refund Update
Weāve completed data processing and loss calculations for all users who haven't yet received a refund.
[IMPORTANT] Action required by June 14th 5pm EST:
- If you donāt have any remaining LINUX: Please review your address and total loss in bit.ly/no-remaining-linux
- If you still hold LINUX: Please send it to our admin address (EX7QGHSreah6EUtsPXCcen5R8JUyiVQWgz6aV4UspyMy) and review your total loss in bit.ly/has-remaining-linux
- If you never sold any LINUX but havenāt received a refund: Check if you still hold any LINUX. If yes, send it to our admin address. If not, please contact us via DM.
If you believe your data is incorrect or missing, contact us via DM. If everything looks correct, you donāt need to do anything.
Refund Process & Timeline
After this post, users will have 2 days to review their total losses and report any issues.
If no major issues arise, we will finalize the ārecovery rateā and send partial refunds to everyone on the bit.ly/no-remaining-linux list.
For anyone still on the bit.ly/has-remaining-linux list after the deadline, refunds will be processed once they return their remaining LINUX to the admin wallet.
FAQ
Q: What is the ārecovery rateā?
Recovery rate = total available SOL for refund (~18K) / total losses across all users.
We currently estimate it will be 95%+ (final number depends on any user-reported issues). This means that all users will recover the majority of their losses.
Q: Why are total losses shown in SOL? What if I traded using other tokens (e.g. USDC)?
We only have SOL (from the liquidity pool + auction fees) to refund users. Loss calculations are based on the SOL value at the time of your original transactions.
Q: Why isn't there a hard refund deadline?
We are handling massive on-chain data from thousands of people with many edge cases across various DeFi protocols to trade LINUX. Itās a very complicated process so itās hard to guarantee an exact deadline without overpromising.
That said, we donāt expect many more unhandled edge cases after users complete this data review.
Our current estimation is the majority of refunds will be sent shortly after this review period.
Q: Where will the refund be sent if I have multiple addresses?
Refunds will be sent to the address where you either:
- last sold all your LINUX, or
- sent all remaining LINUX to the admin wallet.
13
1
35
10,581
$LINUX referral rewards of ~52 SOL have just been airdropped to users.
If your reward balance was below the minimum threshold of 0.001 SOL, you wonāt have been paid. Your balance will continue to accumulate across future token launches, and we will send out your rewards in future payouts.
Check your rewards and transfer details here:
github.com/gitfishdev/referrā¦
22
1
29
10,365
Now live on @Solana at gitfish.dev
Drop a repo link below (or DM) to request a new token!
4
1
31
14,006
Quick update: we've had to delay our launch today as some GitHub services are currently down.
We plan to be live tomorrow as soon as GitHub is back up.
5
1
26
4,312
278 more SOL sent out just now (for this group of users): github.com/gitfishdev/linux-ā¦
for anyone who have sold, please wait while we process your refund.
thanks for your patience and understanding.
6
22
3,399
Auction ends in 3 days ā gitfish.dev/token/8Bk8Dd1Dhcā¦
1
2
21
13,191
gitfish.dev š
Would not be possible w/o support from @SolanaFndn @MeteoraAG @JupiterExchange @helloSQD @privy_io @heliuslabs @RaydiumProtocol @VECTORDOTFUN @alliancedao + many others!
17
4,831
15 years. 0 VC. 100% Open Source.
#3ļ½Why FEHelper Has Survived 15 Years
When I started FEHelper back in 2011, I never expected it to last this long. Fifteen years later, itās still aliveānot because of marketing hype, but because of a community, a purpose, and countless small acts of trust.
Around 2014, FEHelperās user base on Chrome began to grow more obviously. Users kept sending me requests, ideas, and feedback. Maintaining everything alone became harder. So I decided to open-source it on GitHub: github.com/zxlie/FeHelper. That decision changed everything.
After going open source:
- The repo began receiving Stars and Forks (now ~5.4k stars and ~1.3k forks)
- Developers submitted issues and pull requests; the project entered a real ācommunity maintenanceā phase
- FEHelper started to surface frequently in developer blogs, technology portals like Juejin, CSDN, plugin recommendation lists, and āmust-have frontend toolsā articles
- Users wrote tutorials, shared usage scenarios, recommended the tool to colleagues
- Some enthusiastic users even created WeChat groups for FEHelper, where they discuss bugs, features, usage tips
- Across platforms like WeChat, Douyin (TikTok China), Toutiao, and blogs, users also spread the word, writing short posts or sharing screenshots
Because of this organic energy, I kept carving out time from my day job to fix bugs, optimize features, and respond to feedback. Every issue, every pull request, every messageāand yes, every small donationāwas a reminder that someone was using and believing in what I built.
One touching detail: even though FEHelper remains fully free and open source, many users have sent me small red envelopes (donations) simply to say āthank you.ā I never asked for it, but receiving those gestures was deeply motivating.
Recently, I was invited by @gitfish to officially list FEHelper on their platformābringing it to more eyes and reinforcing its place in the open source ecosystem. For me, that feels like a new chapter unfolding. FH$ (gitfish.dev/repo/zxlie/FeHelā¦)
So why has FEHelper survived 15 years?
Not by chasing trends or marketing pushes, but by real connections with users, by trust built over time, and by small contributions accumulating into momentum.
Forever grateful to everyone who has used, recommended, contributed, or supported FEHelper. Next time, Iāll talk about where Iād like to take FEHelper nextāAI-powered assistants, agent integration, lightweight IDE embedding, and more.
1
20
3,410
1/ Last week, we shipped GitFish V2, letting anyone raise capital and attention for open source projects by launching a coin.
Hereās how it works:
4
5
18
20,989
10k stars in 24hrs. nanochat is going crazy.
open-sourced by Karpathy.
whoās launching a coin to show support ā¤ļø
gitfish.dev/repo/karpathy/naā¦
Excited to release new repo: nanochat!
(it's among the most unhinged I've written).
Unlike my earlier similar repo nanoGPT which only covered pretraining, nanochat is a minimal, from scratch, full-stack training/inference pipeline of a simple ChatGPT clone in a single, dependency-minimal codebase. You boot up a cloud GPU box, run a single script and in as little as 4 hours later you can talk to your own LLM in a ChatGPT-like web UI.
It weighs ~8,000 lines of imo quite clean code to:
- Train the tokenizer using a new Rust implementation
- Pretrain a Transformer LLM on FineWeb, evaluate CORE score across a number of metrics
- Midtrain on user-assistant conversations from SmolTalk, multiple choice questions, tool use.
- SFT, evaluate the chat model on world knowledge multiple choice (ARC-E/C, MMLU), math (GSM8K), code (HumanEval)
- RL the model optionally on GSM8K with "GRPO"
- Efficient inference the model in an Engine with KV cache, simple prefill/decode, tool use (Python interpreter in a lightweight sandbox), talk to it over CLI or ChatGPT-like WebUI.
- Write a single markdown report card, summarizing and gamifying the whole thing.
Even for as low as ~$100 in cost (~4 hours on an 8XH100 node), you can train a little ChatGPT clone that you can kind of talk to, and which can write stories/poems, answer simple questions. About ~12 hours surpasses GPT-2 CORE metric. As you further scale up towards ~$1000 (~41.6 hours of training), it quickly becomes a lot more coherent and can solve simple math/code problems and take multiple choice tests. E.g. a depth 30 model trained for 24 hours (this is about equal to FLOPs of GPT-3 Small 125M and 1/1000th of GPT-3) gets into 40s on MMLU and 70s on ARC-Easy, 20s on GSM8K, etc.
My goal is to get the full "strong baseline" stack into one cohesive, minimal, readable, hackable, maximally forkable repo. nanochat will be the capstone project of LLM101n (which is still being developed). I think it also has potential to grow into a research harness, or a benchmark, similar to nanoGPT before it. It is by no means finished, tuned or optimized (actually I think there's likely quite a bit of low-hanging fruit), but I think it's at a place where the overall skeleton is ok enough that it can go up on GitHub where all the parts of it can be improved.
Link to repo and a detailed walkthrough of the nanochat speedrun is in the reply.
8
17
4,182
Join us Friday at 9am EST nitter.app/i/spaces/1OwxWXEaObMKQ
2
18
5,497
Largest liquidation event in crypto history on the day of our launch.
What are we buying?
5
16
1,944
Going live in 5
nitter.app/i/spaces/1OwxWXEaObMKQ
6
1
12
5,237
Excited to see how crypto is making real impact for open-source developers
大家儽ļ¼ęęÆ FeHelper ļ¼$FHļ¼ēä½č
éæēåļ¼ēē„ļ¼ļ¼å®ęÆäøę¬¾äøŗå¼åč
ęé ēå¼ęŗęµč§åØę件ļ¼éęäŗ 30+å®ēØēå·„å
·ćä»ē¬¬äøēååøå°ē°åØå·²ē»čµ°čæ 10 幓ļ¼å
Øēå·²ęč¶
čæ 20 äøå¼åč
åØä½æēØć
ęčæē¬¬äøꬔēę£ęåå° Crypto ēåé āā ä»å®å
Øę²”ę„触ļ¼å°ēå°é¾äøē¤¾åŗå¦ä½ęÆęåä½č
ļ¼čæē§ä½éŖå¤Ŗéę¼äŗļ¼
5
3
10
3,717
Day 2 bonus points were dropped for all V1 users!
Use them to launch GitHub project coins.
If you are not sure where to start, we made a guide to help you find cool projects: gitfish.dev/guide
4
1
8
2,593
Refund and transfer details here: github.com/gitfishdev/linux-ā¦
9
4,092
If you are interested in launching an open-source x402 project on Solana and need funding, DM is open
Interested in how to build with x402?
Join us tomorrow to learn about x402 and build on Solana for the x402 hackathon
nitter.app/i/broadcasts/1rmGPvbrLā¦
7
2
12
4,287
8/ Over the coming weeks, weāll be running a series of experiments to see where GitFish can create the most value.
If you are excited by this, or building in the open source space, we would love to chat! Just drop us a DM š
And join our TG community at: t.me/gitfish
2
1,218
thanks! really appreciate the feedback ā noted on the X integration idea. keep them coming š
1
4
798
7/ Project maintainers can claim community launched coins to collect earnings (0.5% fees).
This allows them to use the funds to grow the project and give back to early supporters.
More details here: gitfish.dev/guide
2
2
983
This is the referral payout. As for the refund, we aim to finish refunding everyone by June 7th, subject to addressing all edge cases raised by users. We're going to make sure everyone gets the correct refund.
2
2
1,426
please understand this next batch of refund is a lot more complicated. we have been heads down working on it last few days. we also added more data to the refund repo 12 hrs ago: github.com/gitfishdev/linux-ā¦
2
2
522
GitHub repo owners can claim swap fees, and their portion of the token supply (coming soon) to fund project development.
1
2
767
we are waiting for others to send us back $linux. deadline in a week. after it we will calculate how much SOL everyone will get and batch distribute the refund to everyone
2
648
more refunds will be sent out soon. we are working at our maximum capacity to get everyone's numbers correct. the process needs massive onchain data indexing and lots of manual and automated data cleaning up.
2
449
yes you will get it in the next few days.
if you sold your LINUX, it will come in the next batch as the calculation for this group of people is a lot more complicated
your friend is likely in the group of users who never sold their LINUX
1
2
597
Send back any remaining LINUX tokens to the admin address. We should be able to calculate your refund.
1
2
1,145
there is only one user using your referral link and the payout amount is 0.0005 SOL (see github.com/gitfishdev/referrā¦)
Only referrers that have earned at least 0.001 SOL in rewards will be paid in each distribution event.
We will send out accumulated rewards to users once their total balance crosses above the limit.
2
2
97
we will convert the USDT to SOL amount based on the data in that onchain tx to calculate your cost basis. btw the address seems to be an Ethereum address
1
1
164
please be patient and you will receive a refund. we are working at our maximum capacity to get everyone's numbers correct. the process needs massive onchain data indexing and lots of manual and automated data cleaning up.
3
1
952
I replied your DM. you need to send over the remaining LINUX and we will process a full refund to you
1
1
139
your data is now fixed.
{
"address": "82VbpX1KHQ7KNpC37UQkn9chKPeSHRPzUdbro8RTGADL",
"lossInSol": 6.001986692744028
},
37
yes if you sold your LINUX, it will come in the next batch as the calculation for this group of people is a lot more complicated
1
1
84