Kosmo KRC20
354 posts

Kosmo KRC20
@KosmoKRC20
The hottest KRC20 fair-mint to date IS NOW 100% MINTED!



Kaspa won’t become a top 5 crypto just because it has the best tech There must be some form of mass adoption But where will this actually come from? – Will builders migrate from Ethereum once we have vProgs? Possibly, but there must be a strong incentive for them to bridge to Kaspa that I don’t believe currently exists – Are we completely reliant on @KaspaKii to solve Kaspa’s security budget? I hope that KII succeeds in its efforts to implement Kaspa into real-world use cases, but relying on one entity to cover the entire security budget is definitely a risk (and not very decentralized) – How else does #Kaspa achieve adoption? My ideal solution is that Kaspa fulfills Satoshi’s vision of P2P digital cash, where businesses across the globe accept Kaspa as payment But the truth is that this endeavor has made little progress over the last two years I want $KAS to succeed as badly as anyone But as Kaspa enters its fifth year of existence, development remains at roughly the same level as year one We cannot ignore the plummeting hashrate Kaspa needs to start seeing adoption… NOW If we as a community can’t clearly answer questions about usage, security budget, and TVL, how do we expect to convince others to join the network?







I don’t see any problem with cryptok’s request, and no problem with the decline. Those are all legit negotiable numbers. Re some of the comments - It makes no sense to attack a brilliant volunteering contributor who built and maintained a beautiful platform with top-of-the-class ux, just bcs he decided to move on and has his principles/aspirations. --- Thx @cryptok777 for everything you have done for Kaspa and I genuinely hope you find the time and place to rejoin this ride, bcs I can promise you it will be there waiting for you when you do <3



All $KAS Krew - KAS.fyi which was graciously created and maintained by @cryptok777 - a real nice guy who has had enough and he's over it :( He is asking $150,000 to hand over the reins. After careful consideration by @kasmediadotcom and a few other key players, we have declined. Instead we pledge to back @asaefstroem and write a ground up new gen2 explorer kasfyi.io which will be forward compatible with VPROGs all l2's sync composability real-time decentralization all the APIs and new Opcodes




The bottom line of the recent discussion about vProgs and based rollups over $kas ------- Kaspa is a highway. Smart contracts are commuters on that highway. vProgs provide a shiny new combustion engine technology. Commuters can drive cars that have this new fancy engine. Having your own car is sweet, but maintaining a car is not for everyone. It constantly needs fuel, you need to fix it when it breaks, renew it's licence every year, etc.. For many people, the benefits of owning their own car are not worth the hassle. So what do the do? They take the bus. The bus is an L2: a single, large vehicle, that (permissionlessly) drives many people at once. Based on their needs and preferences dome people use cars while other use busses. Nothing contentious about that except that for some reason, some people are convinced that supporting busses somehow undermines the importance of engines. Silly huh? Ok, let's shed the analogy and explain this properly. There are three very common misconceptions: 1. vProgs and rollups provide the same service 2. Rollups compete with vProgs 3. vProgs provide a better user experience With this misconception, it is too easy to interpret any support for rollups as criticism towards vProgs. But that's not the situation at all. vProgs revolutionize the way (almost) *any* off-chain VM interacts with the base layer. But this off-chain VM should, y'know, exist. Moreover, it requires provers that constantly create ZK proofs, which is expensive and complicated. The service provided by an L2 is to maintain a single, VM where many projects can deploy, and a prover network that sequences (on the base layer!!!) all these projects combined. The name "rollup" just refers to how all these projects are aggregated into a single state. An L2 can (and probably should) be deployed as a vProg. It is essentially a single vProg that many projects share. On the UX side, there is no difference. You can make an SC over an L2 have indistinguishable UX from an independent vProg. Between "deploy my own vProg" or "use an L2" there is no one-size-fit-all answer. It highly depends on the projects needs. To facilitate a lot of adoption and migration, you *have to provide options*. Currently, @Igra_Labs are the only ones seriously working to deliver such options. They discuss deploying as a vProg explicitly in their WP, which makes them *the most important application for vProgs that is currently under development*. Yet, they are construed as "a competition" to vProgs. This wild misconception is detrimental not only to Igra, but to any future developer who might want to build busses for the Kaspa highway. But busses need engines, and passengers need busses, and the highway? It faces a risk of shutting down if it can't get enough passengers soon. So in what way does it make sense to oppose busses?














