composability
/composability612
this channel is dedicated to all things Composability -- fetching data, combining data, creating systems and apps that are data aware: cross-chain, cross-dapp, cross-protocol, onchain, offchain.
Open question: how do we incentivize crypto apps and onchain experiences to be composable and remixable, so we’re not just accumulating a junk drawer of useless collectibles in our wallets?
Loading...
The power of composability:
A Fully Autonomous Agent has arrived in Conquest.game!
🤖 Yakuza is a smart contract driven entirely by player actions. No one in control.
And while most AI agents run on someone else's machine, Yakuza runs on decentralized networks
https://x.com/conquest_eth/status/1888999490616476159
A Fully Autonomous Agent has arrived in Conquest.game!
🤖 Yakuza is a smart contract driven entirely by player actions. No one in control.
And while most AI agents run on someone else's machine, Yakuza runs on decentralized networks
https://x.com/conquest_eth/status/1888999490616476159
We published a post today, penned by @ellied, on solving for fragmented liquidity with asynchronous and synchronous composability.
https://hackmd.io/@EspressoSystems/composability-circ
https://hackmd.io/@EspressoSystems/composability-circ
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
“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
(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.
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.
