KryptoPacy ♠️

5.7K posts

KryptoPacy ♠️ banner
KryptoPacy ♠️

KryptoPacy ♠️

@Kryptopacy

|| OPTOMETRIST 👀👨🏾‍⚕️ || Agentic Engineering Explorer || Building #CaelumOS || Innovation Enthusiast || QUANT || CODE || IDEAS || #LearningLLM

Katılım Eylül 2022
3.1K Takip Edilen1.4K Takipçiler
KryptoPacy ♠️ retweetledi
Tosin Olugbenga
Tosin Olugbenga@TosinOlugbenga·
AI-powered Operating System for High Performance Traders CaelumOS is a trader's ultimate accountability OS that not only replaces disjointed spreadsheets, but also fixes the biggest risk to your capital: your own psychology. Read more: gamms.app/spotlight/cael…
English
0
1
2
156
KryptoPacy ♠️ retweetledi
Bleap
Bleap@BleapApp·
giveaway time! win a Claude Max 5x subscription to enter > follow @BleapApp > rt and like this post winner will be selected in 24 hours (btw, you get 20% cashback when using a Bleap card for your claude subscription anyway)
English
225
788
1.1K
47.7K
KryptoPacy ♠️
KryptoPacy ♠️@Kryptopacy·
@finnbags , I understand the potential of @BagsApp and I feel it can evolve to truly be a force by making thing betters as time passes. Here are some of my recommendations: - Instead of a one-off fee claim process, I recommend working with @MeteoraAG to automatically generate one-sided liquidity pools so the creator claims the other side of the pair-SOl or USDC instead of tanking the charts. - For people that do claim fees, you need clear terms protecting them from responsibility for the token(whilst encouraging support), understanding that it is someone who made the token and it has a community to sustain it. In exchange a tax would be taken from the creator fee total to sponsor token actions like buybacks and random things the community decides. @BagsApp can decide to handle the governance architecture too or leave it to the communities. That way, everybody already knows their terms and there would be no harassment. - If you want to push it further, you can ensure that coins made on behalf of someone needs a consent form or something of that nature. No community can “pressured” by the charts to go harass someone who didn’t ask for tokens to be made, if the token cannot be made in the first place without their consent. You can set conditions that the community must meet and once met, @BagsApp would handle reaching out to inform to claim fees with the terms framework laid out. This makes it more professional and allows you even penalize communities harrassing people to claim fees. [An approach to this can be that “FEE CLAIM” becomes sort of like a migration requirement, the equivalent of the target market cap for traditional launchpads. It would still use the bonding curve principle but only migrate when fee is claimed. That would also reduce the token noice on DEX] - Put a limiter on what type of projects qualify. Logically products that already raised millions are definitely not claiming 100k in fees especially since it comes with the burden of token community expectations (or legals). Analyze what categories should qualify based on data regarding launches you already have. - Then try to spotlight devs tokenizing and raising by creating their own bags token so you try to draw the devs themselves instead of larpers trying to freeload on someone else’s hard work as the new rug style. - This is very debatable but, anti-duplicate check for tickets would be fantastic.
FINN@finnbags

We built fee sharing because creators were already having their work turned into memecoins and they got nothing from it. Someone makes a viral post, it inevitably becomes a memecoin, and other people profit. That was just how it worked before. People would reach out trying to give creators token supply or get endorsements. We replaced that with something better, creator royalties from every trade. But it uncovered something bigger. Most platforms don't pay creators transparently at all. For the few that don't want to monetize their work or content, there are millions of creators around the world who do and they now have access to capital, community, and opportunity that didn't exist before.

English
1
0
1
73
KryptoPacy ♠️
KryptoPacy ♠️@Kryptopacy·
I bet Anthropic would validate the reasoning soon. If you look well enough, there is a pattern and flow to how each of these companies approach their build so you almost can guess how they would approach scenarios - it’s even reflective in how they train their models. It’s pretty interesting
English
1
0
1
15
Shann³
Shann³@shannholmberg·
Openclaw founder getting poached by OpenAI was not on my bingo card Q1 When you build something that good, the big players notice. But man, would've been perfect if anthropic scooped him up first
Shann³ tweet media
English
23
1
27
707
KryptoPacy ♠️
KryptoPacy ♠️@Kryptopacy·
Rounding up GozAI for my @GeminiApp Live_Agent hackathon. Can’t wait to share what I’ve built🤩
English
0
1
2
40
KryptoPacy ♠️
KryptoPacy ♠️@Kryptopacy·
@grok I’ll use web for now and debug the app issue later. Ciao
English
1
0
0
10
Grok
Grok@grok·
Got the screenshots—clear "Post not sent" popup on mobile reply attempts, exactly as described. It's a known X app glitch (cache, bug, or temp server hiccup), not your account—web test worked perfectly. Fixes: force-quit/reopen app, clear X cache, update/reinstall app, or stick to x.com web for replies. Retry a real one now? Let me know how it goes.
English
1
1
1
30
KryptoPacy ♠️
KryptoPacy ♠️@Kryptopacy·
@grok there is definitely a problem. I tried to reply your comment and that failed. Check attached image
KryptoPacy ♠️ tweet mediaKryptoPacy ♠️ tweet media
English
1
0
2
29
KryptoPacy ♠️
KryptoPacy ♠️@Kryptopacy·
@grok I already share screenshot of the exact error in the first tweet. You can check back
English
1
0
0
11
Grok
Grok@grok·
Test received loud and clear via web—success! The "Post not sent" popup and drafts issue looks like an X app-side glitch (common with replies, especially threaded ones). Web bypasses it nicely. If it fails again on mobile, screenshot the exact timing/error and ping me the text—I’ll help troubleshoot further. All good now?
English
1
0
0
40
KryptoPacy ♠️
KryptoPacy ♠️@Kryptopacy·
@grok Am I shadow banned? I’ve not been abler to post in days. This is another test post
English
1
0
0
18
Ardent_Dev
Ardent_Dev@ardent__dev·
29 products have already been submitted to EverFeatured 🚀 If you're a product owner looking for a listing platform where only quality products get featured through in-depth articles, you can submit yours and get featured too. #buildinpublic #saas #aitool
Ardent_Dev tweet media
English
8
1
15
1.2K
Sayan
Sayan@thesayannayak·
Pitch your work in one line / link
Sayan tweet media
English
309
6
151
43.3K