vibe coding (making projects fully with AI) is not a good way to create apps wherever money is involved, especially in cryptocurrency, and with $kas L2s coming, it will become a problem in the community as well.
allow me to explain (no offense to anyone intended):
people that rely fully on AI to create applications usually have little to no coding experience, while these tools allow them to create apps, which otherwise would require hiring expensive developers, it creates many problems
a) huge security issues
you can tell AI to ensure thorough security, but it's not a guarantee. it's either going to miss the lesser-known vulnerabilities or leave the dumbest security flaws imaginable. I've seen cases like this happen on #kaspa too. user money + security flaws is definitely not a good combo, it will get exploited sooner or later.
b) trash code
AI models generate questionable quality code, sometimes throwing everything in a single file, bloating code with comments that have absolutely no meaning or use hacky ways to get things done, a project like that is basically unmaintainable by a human at a later date.
c) app stack chosen by ai
when creating a new project, an experienced developer will know exactly what frameworks and libraries to use for this specific use case, taking their popularity, ease of use, performance in the context.
in the case of vibe coding, it's usually AI that chooses the above, and it usually operates on the same stack (Postgres+NextJS), I've seen cases where Postgres was used for a local indexer instead of a local database...
these are just a couple of issues that can happen when coding with AI, while it's definitely a great way to make your ideas come to life it should never be fully trusted to create production-grade projects. while you can certainly minimize the risk with proper prompting, it can never be mitigated entirely.
by the way, I didn't mean to say boo ai is terrible it will destroy humanity don't use it, it's a great tool which I use myself, but anybody which uses it should be aware of the underlying risks associated with it.
to whoever vibe codes production apps: consider this post to be a warning, always make sure your app is safe, preferably tested or audited by a real person, loss of user funds is the last thing you want to experience 😉
@coderofstuff_@husi_mete The point of not having docs etc. was to avoid "non-technical" people running their own pools for just profit. Releases I agree but it's more like a "template" for creating something more -- master always can be considered stable(It's already used by KaspaFunding for their pool).
a small technical correction -- its a frontend for interacting w a theoretically decentralized protocol via distributed trustless(if you reviewed the code) wallet.
Kaspian now supports KRC-20 as a DApp(Possibly first DApp of Kaspa). 🎉
Public beta is available for testing in here: https://t.co/e8SlcFoAHL
The code is open source and available on GitHub: https://t.co/Hl2QNjHL8S
I’ll be sharing more technical details in the coming days. 🤓
The GitHub repository for KasplexBuilder (https://t.co/oK4dys8qxO) includes a README that explains how to use these classes in conjunction with the rusty-kaspa WASM SDK.
Will be released on npm soon.
Happy coding! 🤓
KasplexBuilder is a library that helps you interact with the Kasplex indexer and create inscriptions.
It makes the integration of KRC20 easier for developers.
It includes two built-in classes:
Indexer class provides a typed interface for communicating with the indexer via the HTTP-JSON protocol.
Inscription class facilitates the creation of inscriptions with type definitions and allows exporting them to a WASM ScriptBuilder for further use.