Filter
Exclude
Time range
-
Near
I spent 3 weeks building my SaaS. Landing page? βœ… Features? βœ… Analytics? βœ… Traffic? 3 visitors. 2 were me. If you've ever gone from 0 β†’ 10 users, what actually worked? Try PaperDrop: paperdrop-theta.vercel.app #BuildInPublic #IndieHackers #SaaSFounder #Bootstrapped #StartupLife

1
32
Nobody tells you this: Building the product is the easy part. Getting strangers to care about it is the hard part. I launched PaperDrop and now I'm figuring out distribution. What brought you your first 10 users? πŸ”— paperdrop-theta.vercel.app #BuildInPublic #SaaS #IndieHackers #FounderJourney #Startups

17
Launched my first SaaS. Expected: πŸš€ Traffic πŸ”₯ Signups πŸ’° Revenue Reality: πŸ“‰ Refreshing analytics πŸ“‰ Checking notifications πŸ“‰ Wondering where everyone is If you've been through this, what changed the game? PaperDrop: paperdrop-theta.vercel.app #BuildInPublic #Bootstrapped #SaaSFounder #IndieHackers

1
1
18
Built a product that turns research papers into Twitter threads, LinkedIn posts, summaries, and key insights. Then I realized: Building the product was only 20% of the job. The other 80% is getting people to discover it. PaperDrop: paperdrop-theta.vercel.app How did you get your first users? #BuildInPublic #Research #AI #SaaS #IndieHackers

1
1
17
Current startup routine: β˜• Coffee πŸ’» Ship features πŸ“Š Check analytics πŸ˜… See no new users πŸ” Repeat Still showing up every day. PaperDrop: paperdrop-theta.vercel.app What's one growth lesson you learned the hard way? #BuildInPublic #StartupLife #IndieHackers #SaaSFounder

1
16
Payment links are live now on PaperDrop ( paperdrop-theta.vercel.app) Try it once, I am sure you will like it for only $ 1.5 #BuildInPublic #IndieHacker #SaaSFounder #Bootstrapped #StartupLife #ZeroToOne
14
Just added the payment part to PaperDrop
17
Writing on social media isn't just a trendβ€”it's the future. πŸš€ No matter your profession, building your voice online can open doors, create opportunities, and grow your personal brand. Make content creation a part of your daily life. To make the process easier, try PaperDrop: paperdrop-theta.vercel.app PaperDrop helps you create content faster, organize your ideas, and stay consistent without the usual hassle. Start writing. Start sharing. The future belongs to creators. ✍️✨ #ContentCreation #PersonalBranding #SocialMedia #Creators #Writing #PaperDrop
35
Spent 2 hours reading a research paper yesterday. Then thought: why not have AI read and create content automatically? So I built PaperDrop. Upload a PDF β†’ instantly get: - A summary - An X thread - A LinkedIn post - Key takeaways Save hours. Learn faster. Create more. paperdrop-theta.vercel.app #BuildInPublic #Startup #SaaS
34
Last week I spent 2 hours reading a research paper. Then I thought: "What if AI could read it and create content for me?" That's why I built PaperDrop ( paperdrop-theta.vercel.app ). Upload a PDF and instantly get: πŸ“„ Summary 🧡 X Thread πŸ’Ό LinkedIn Post πŸ’‘ Key Takeaways Save hours. Learn faster. Create more. #BuildInPublic #Startup #SaaS
1
3
45
Last week I spent 2 hours reading a research paper. Then I thought: "What if AI could read it and create content for me?" That's why I built PaperDrop ( paperdrop-theta.vercel.app ). Upload a PDF and instantly get: πŸ“„ Summary 🧡 X Thread πŸ’Ό LinkedIn Post πŸ’‘ Key Takeaways Save hours. Learn faster. Create more. #BuildInPublic #Startup #SaaS

1
3
48
Last week I spent 2 hours reading a research paper. Then I thought: "What if AI could read it and create content for me?" That's why I built PaperDrop ( paperdrop-theta.vercel.app ). Upload a PDF and instantly get: πŸ“„ Summary 🧡 X Thread πŸ’Ό LinkedIn Post πŸ’‘ Key Takeaways Save hours. Learn faster. Create more. #BuildInPublic #Startup #SaaS
1
1
34
Content creators are sitting on a goldmine they never use: Research papers. PDFs. Reports. Case studies. The problem? Reading and converting them into content takes forever. PaperDrop ( paperdrop-theta.vercel.app ) turns any PDF into: βœ… X Threads βœ… LinkedIn Posts βœ… Key Insights βœ… Easy-to-understand Summaries Create content 10x faster. πŸš€ #ContentCreation #AItools #SaaS
34
Content creators are sitting on a goldmine they never use: Research papers. PDFs. Reports. Case studies. The problem? Reading and converting them into content takes forever. PaperDrop ( paperdrop-theta.vercel.app ) turns any PDF into: βœ… X Threads βœ… LinkedIn Posts βœ… Key Insights βœ… Easy-to-understand Summaries Create content 10x faster. πŸš€ #ContentCreation #AItools #SaaS
20
Added a new feature in PaperDrop ( paperdrop-theta.vercel.app ) Check out now, @all
12
AI won't replace researchers. It will replace researchers who refuse to use AI. The ones who learn to combine deep thinking AI tools will publish more, reach more, and matter more. PaperDrop is my small bet on this. Am I wrong? #AITools #FutureOfResearch #PaperDrop #ArtificialIntelligence #AcademicTwitter #IndieHacker
1
48
I shipped PaperDrop ( paperdrop-theta.vercel.app ) with: β†’ 0 paid ads β†’ 0 investor money β†’ 0 team members Just me, Claude, and too much coffee. What's the hardest part of building solo for you? (Genuine question β€” I read every reply) #BuildInPublic #IndieHacker #SoloFounder #Bootstrapped #MakerLife #SaaS

2
1
46
Replying to @TheSpacerr
Hello, I am working on PaperDrop, which turns your research paper into a Twitter thread, LinkedIn post, key insights & more β€” in 10 seconds. Free to start πŸ‘‡ paperdrop-theta.vercel.app/

2
2
85
β€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Š Ending summary β€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Šβ€”β€Š Hello frens, If you read nothing else, remember what this piece actually did.Β  It reduced the story to artifacts. We pinned OSAK to its contract and its pool. We pinned ded.eth to four 2023 remove liquidity events with block numbers, UTC timestamps, and the exact ETH extracted. We pinned the kachoperro thread to an ENS trail that was intentionally made unusable, yet still leaves behind a measurable bridge of direct ETH transfers between 0x37b3 and 0x5cf0 that you can verify. We also corrected the one part that was overstated. The farm alignment matters, and LP removal alone is not proof of a rug. But the larger risk does not disappear because the larger risk is structural centralization. When 99.48 percent of LP sits in one wallet, safety becomes faith in a key, not enforcement. When a 30 percent paperdrop bucket results in only 3.82 percent reaching claimers and 96.1786 percent flowing back to a controller, distribution becomes fragile in outcome, not just in narrative. When permit based removals can skip approval breadcrumbs and whales can exit in chunks through routers and aggregators in thin conditions, price can be steered without any admin backdoors. Nothing here requires belief. Only replication. GOD BE WITH YOU -XT
1
3
221
β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” - 3/3/2026 Amendment Summary for the Medium Article Please READ β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” β€” This is an amendment for accuracy and fairness based on additional on-chain verification completed after publication. First, I am correcting one important overreach in my framing. I did overlook the farming mechanics in my haste and I will own it plainly. Yes the on chain pattern for the ded wallet we traced fits a normal farm exit in 3 of 4 cases. The OSAK LP removals land 3 to 16 blocks after SR1 Withdrawn events which is exactly what you would expect when someone unstakes or exits LP and then removes liquidity. Why this matters is because it means LP removal by itself is not proof of a rug and it would be dishonest to frame it that way. So farming explains a big piece of what you both are pointing at and I am correcting that publicly. Thanks for the catch and I will add a correction update note to my medium at the top. Still where I do not agree is calling the Medium concerns ridiculous because the core risk is not LP farming equals scam. That statement was a piece not the whole point of the medium. The bigger concern is centralization and single point of failure custody and it is visible in OSAK even if every LP move is normal yet OSAK is marketing itself as a Rebirth Of True Decentralization. The core problem is the setup is dangerously centralized and that makes outcomes steerable in a way that does not require an admin backdoor and that is where kachoperro being active in the environment matters. I also want to address why the Ryoshi wallet had credibility in the first place. It was treated as a Ryoshi wallet because it was linked to him while he was actively using it in Shiba and that link is what gave people credibility to trust it. Why this matters is that we are now years later Ryoshi is not actively behind anything publicly and nobody can prove who controls that key today so regardless of the origin story that wallet is now a single point of failure and trust is being asked of an address rather than a mechanism. There are discrepancies between the projects own words and what is actually on chain. The OSAK launch text frames LP as being sent to an old SHIBA Ryoshi wallet for approval and a forever hold and frames the farm as locks until the end of the farm term. Why this matters is because readers interpret that as a trustless guarantee. On chain LP burned is not true in the strict sense and the guys behind this know this. The LP was minted to the deployer and later transferred deployer to Ryoshi wallet so it is custody not burn. Why this matters is because custody is a key risk. If the controlling key moves or is compromised the guarantee disappears. The centralization severity is extreme. Burn addresses hold about 0.000028 percent of LP while the Ryoshi wallet EOA holds about 99.48 percent. Why this matters is simple. Liquidity safety depends on one wallet never moving. That is not burned. That is please trust this one address forever and it creates a single point of failure. The Mephisto Medium narratives implies broad distribution plus burn or unclaimed handling but the actual on chain Paperdrop outcome is re centralized. About 96.1786 percent of the 30 percent airdrop bucket flowed back to the controller or deployer with only about 3.82 percent reaching claimers. Stop and read that again. The OSAK Medium text itself also mixes burn remaining 23 percent messaging around unclaimed distribution. Why this matters is because it can look community wide while most of the supply remains effectively controlled by a small set of hands and that increases manipulation risk even if nobody is cheating. On incentives SR2 is not an LP rug vector but it is custodial for rewards. recoverERC20 for OSAK and WETH succeeds on SR2 which means the SR2 owner key can pull reward token balances that accrue or land there. Why this matters is that it introduces another key based point of control and a compromise or abuse of that owner role can siphon rewards and influence incentives even if LP itself cannot be drained from SR2. On monitoring approvals the traced removals used removeLiquidityETHWithPermit so there may be no prior approval breadcrumb. Why this matters is that approval watching can miss the true moment of risk and the real signal becomes router removeLiquidity calls themselves not an approve event. On the kachoperro and ded wallet the wallet we traced signed multiple removeLiquidityETHWithPermit calls and extracted about 56.50 WETH across four removal events. This is not proof of scam. Why this matters is it is proof of capacity and influence in thin liquidity. The wallets big LP moves can be explained as farming and I am not pretending that alone proves anything but it still matters because it shows one wallet had the size to farm at scale pull liquidity receive the ETH and keep trading through routers and aggregators. In a market where LP custody is basically one wallet and supply flows are tight a large operator does not need an admin backdoor to manipulate outcomes. Timing liquidity pulls and swaps around thin liquidity moments is enough to make price action feel managed and that is the structural risk I am flagging. Bottom line I am saying the system is structurally centralized in ways that can be steered by a small number of keys and wallets and that risk exists even if all LP activity is normal farming while Kacho and co sit silent in the mix. Do you even know why I am here digging into OSAK. I was not looking for OSAK. I was tracing kacho and OSAK is where the trail brought me. Either way may God keep us to truth.
1
2
121