Kinode pfp

Kinode

@kinode

16 Following
36 Followers
Kinode pfp
0 reply
0 recast
1 reaction
Kinode pfp
0 reply
0 recast
1 reaction
Kinode pfp
1 reply
1 recast
4 reactions
Kinode pfp
0 reply
1 recast
2 reactions
Kinode pfp
0 reply
1 recast
1 reaction
Kinode pfp
0 reply
1 recast
1 reaction
Kinode pfp
0 reply
0 recast
1 reaction
Kinode pfp
0 reply
0 recast
1 reaction
Kinode pfp
0 reply
0 recast
0 reaction
Kinode pfp
1 reply
0 recast
1 reaction
Kinode pfp
0 reply
0 recast
1 reaction
Kinode pfp
0 reply
0 recast
0 reaction
Kinode pfp
Kinode makes it easy to get your dApp up and running -- it's like playing with legos. “It is so much easier to build decentralized applications with Kinode. 80% of the boilerplate you would normally deal with, such as identity, interacting with global state, persistence, and general extensibility is taken care of. LLMs have changed the way apps are developed, but still have serious limitations. Using Wasm+WASI with Kinode’s permissioning system provides a great scaffolding to define the problem in a way that LLMs strengths’ come through, and their weaknesses are mitigated. The extensibility part becomes very apparent as the amount of apps we're working with increases. With Kinode, the amount of glue code we have to write is minimal and easy: development feels less like performing an organ transplant, and more like playing with legos.” — Zena, Uncentered Systems
0 reply
0 recast
2 reactions
Kinode pfp
0 reply
0 recast
0 reaction
Kinode pfp
0 reply
0 recast
3 reactions
Kinode pfp
0 reply
0 recast
0 reaction
Kinode pfp
1 reply
0 recast
0 reaction
Kinode pfp
0 reply
0 recast
1 reaction
Kinode pfp
(1/2) Kinode's composability is tightly linked with its permissions system. Each component of Kinode can be configured with specific permissions, ensuring they can only access the resources they need — a big deal in decentralized computing where security and trust are paramount. In fact, we're very proud of Kinode's capabilities-based security model. In Kinode, each process is isolated and only given the capabilities it requires to function, minimizing security risks. Permissions are defined by the developer and enforced by the kernel, ensuring that even if one component is compromised, the impact on the system is minimal. Despite our strict security, the permissions model is designed for smooth integration between components. The balance of security and flexibility is what makes Kinode's composability so powerful. So that's composability & our permissions system.
1 reply
0 recast
2 reactions
Kinode pfp
(1/2) In light of renewed interest in the peer-to-peer network space, we thought we'd tell you more about what we are building at Kinode. One of our big goals at Kinode is to help Web3 dApps live up to their promise of being permissionless and truly decentralized. It turns out there's a lot that you can't (or shouldn't) do with a blockchain—some processes are better left to an offchain computing environment. Kinode *is* that off-chain computing environment. Kinode is permissionless, composable, and—because each version is backwards compatible—built to last. We've built with the developer experience front of mind. Our stack is very legible. Kinode is written in Rust and executed in Wasm. Elsewhere we incorporate other standard and widely used languages and technology. We write contracts in Solidity, we incorporate zero-knowledge with Succinct Labs, we've built a sandbox for running Python for AI, etc.
1 reply
0 recast
1 reaction