edgar retweeted
What it feels like when you already locked in week 2 of the treasure hunt ⚡#Hyperhunt
edgar retweeted
🚨Big News
We are HYPED to announce our partnership with @PlayShadowWar
Shadow War is building the future of gaming on Hyperware.
Ready to see the future of decentralized gaming unfold?👀
SHADOW WAR x @Hyperware_ai here to level up the battlefield
🚀 AI-driven gameplay
🎮 Player-created worlds
🛡️ Secure, onchain tournaments
The future of gaming starts now 🔥
📰 Find out more : shadowwar.com/blog/shadow-wa…
edgar retweeted
Check out the latest episode of Crazy Wisdom, where host Steward Alsop (@StewartalsopIII) interviews our lead developer, Nick (@nick1udwig) on the evolution of AI-powered coding, the rise of agentic software development, and the security challenges that come with giving AI more autonomy.
Nick also discusses a Hyperware product in the works which combines the power of AI with practical development tools to act as your AI coding intern. It allows you to edit local files, make commits, and handle PRs seamlessly—and with its Hyperware integration, you can even control your development environment from your phone.
Links to listen below:
edgar retweeted
We've rebranded from Kinode to @Hyperware_ai
Why Hyperware? Because its where you build Hyperstructures
Web3 was destined to be more than a casino. Calling all cypherpunks, ancaps, decentralization enthusiasts, freedom lovers
Welcome home
edgar retweeted
✸ For years, we've forced decentralized applications into a model that wasn’t designed for them.
» Blockchains were never meant to handle everything ➘ from consensus to storage to compute, yet developers continue to contort dApps to fit within these constraints.
The result?
➥ Bloated architectures, inefficient global state synchronization, and an over-reliance on centralized infra for anything beyond basic transaction execution.
@kinode flips this paradigm on its head. ⛓
⛓ Instead of asking blockchains to do what they were never designed for, Kinode provides the missing peer-to-peer compute layer that Web3 desperately needs.
🧵🧵
edgar retweeted
An historic day
@kinode 1.0.0 release has been cut
We're going to let this stew for a bit and see if we can shake any bugs out before releasing 1.0.0. Don't expect release for at least 24hr, more if we find bugs to squash
github.com/kinode-dao/kinode…
edgar retweeted
It’s wild to see how far MemeDeck has come in the past 90 days. I’m fortunate to have seen the rapid innovation of @drunkplato and the team before this project took off.
@99CENTS__ will continue to leverage this platform as it serves as a creative staple for our Communi-TEA.
edgar retweeted
Reimagining the Internet: Urbit v Kinode
Urbit is a decentralized, peer-to-peer computing platform that enables a self-hosted, user-owned internet experience. It reimagines the internet with a unique stack combining decentralized identity, networking, and a custom operating system.
Despite its ambitious vision, Urbit has faced technical challenges, a steep learning curve, and difficulty in attracting a broader community. In response, Kinode emerged as a more pragmatic alternative, re-engineering Urbit’s ideas to address these shortcomings.
Urbit’s Ambition and Challenges
@urbit set out to build a P2P platform with user-owned identities through Azimuth, its Ethereum-based decentralized identity layer. Its custom stack includes Hoon (Urbit’s programming language) and Arvo (its OS kernel). Yet, several obstacles emerged:
Arvo's Performance Issues: Slow processing and subpar user experience have limited Urbit’s practicality for daily use.
Steep Learning Curve: Hoon’s unconventional syntax, coupled with the complexity of setting up a server, has discouraged many developers and users, stalling community growth.
Falling Address Space Value: The decline in value of galaxies, stars, and planets (part of Urbit’s identity system) since 2022 suggests a cautious shift in community outlook on the project’s trajectory.
Urbit’s attempt to overhaul the entire computing stack made it difficult for developers to build practical applications on top of its platform.
Kinode: A Pragmatic Alternative
Initially, a project called Uqbar focused on building a ZK-Rollup on Urbit but pivoted due to Urbit’s limitations. Now, they are developing @kinode, an alternative P2P OS designed to be more accessible and less complex than Urbit. With this new direction, they aim for quicker market entry, improved performance, and easier adoption by developers.
Key Differences:
Integration with Existing Tech: Built in Rust that uses Wasm for its userspace processes. This allows developers to use familiar programming languages, unlike Urbit’s reliance on Hoon.
Performance-Focused: Kinode’s architecture prioritizes efficiency and a smoother user experience, addressing Arvo’s shortcomings.
Selective Reinvention: Kinode focuses on blending existing technologies to create a P2P OS, avoiding the complete stack overhaul that complicated Urbit.
This approach aims to balance the vision of a P2P OS with practical implementation, appealing to developers seeking usability and performance.
Community Reception and Potential
Kinode’s departure from Urbit has drawn mixed reactions. Some view it as abandoning Urbit’s ideals, while others see it as effective acceleration. Kinode’s team believes that Urbit’s insistence on rebuilding the stack limited its progress, whereas they aim for faster, more tangible results.
Meanwhile, Urbit’s influence extends beyond direct competitors like Kinode. For instance, @ZorpZK, a project originating from Uqbar, is building @nockchain, a Layer 1 blockchain that uses Urbit’s computational model (Nock) in a blockchain context rather than as a general-purpose OS. Nockchain leverages ZK Proofs as a form of useful proof-of-work, showing how Urbit’s technologies are inspiring diverse applications across decentralized infrastructure.
Challenges and Opportunities for Kinode:
Community Growth: Kinode’s more accessible development environment has the potential to attract a broader base of developers, possibly reaching the critical mass that Urbit has yet to achieve. Nonetheless, it faces strong competition from Urbit's small but highly committed community.
Server Management: Urbit and Kinode both require self-hosting for full self-sovereignty, though they offer cloud options like Tlon and Valet for easier onboarding. Adoption may depend on balancing the convenience of cloud hosting with the push toward self-hosting for a truly sovereign, personal internet.
Sustainability of the Model: Urbit raised funds primarily through sale of address space (galaxies, stars) alongside investments in Tlon and grants to the Urbit Foundation. Kinode, on the other hand, may pursue sustainability by selling TLZs (Top-Level Zones), similar to the sale of TLDs in Web2. If Kinode establishes itself as a serious platform for developers, these TLZs could become valuable assets, though time will tell.
Conclusion
Urbit’s vision of a decentralized internet is ambitious, but its commitment to reinventing every layer of the computing stack has made it challenging to achieve. Curtis Yarvin (~sorreg-namtyv), who founded Urbit back in 2002, recently returned after a five-year hiatus to lead strategy, ushering in a pivotal moment that divides optimism and skepticism. Meanwhile, Kinode pursues a similar vision with a practical focus on usability and existing technologies, offering healthy competition and a promising alternative. Who will prevail remains uncertain, but for now, the race goes on…
edgar retweeted
Election.exe has started.
Prepare for total political meme saturation across all platforms until November 5.
We don't make the rules but we do make it easier to shitpost the election!
edgar retweeted
🚨 Wifejak is trending at the #3 spot on @MemeDeckApp! 🚨
Meme chefs, let's see your best Meme Deck wifejaks 🧑🍳🎨
$WIFE #wifejak #MemeDeck
edgar retweeted
I like the typography, I repost
This Post is from an account that no longer exists. Learn more
edgar retweeted
Kinode coding update: kit and extensions and websockets and Minecraft
I want to get a bidirectional pipe going between any Minecraft server and Kinode, and the basics are coming together now.
First, shoutout to @nick1udwig for the work on Kit, the Kinode build/dev tool. The best compliment I can give is that I don't think about it while I'm using it.
Kit lets me compile, install on nodes, and run a local EVM RPC. It Just Works, and totally abstracts out any Rust/Wasm/WIT stuff. (Can easily do the same for Javascript, Python, and later C to Wasm).
Programming Ethereum and Kinode: 2016 Flashbacks
Now that the Kinode system is more stable, I'm getting into programming on it more. That might sound weird given my position on the project, but there's a lot that has to be done in the day-to-day, and I don't get to code nearly as much as I would like.
The first thing I wanted to do was recreate one of the most magical 2016-17 coding experiences: writing Ethereum programs that could be deployed and would Just Work. Sitting onchain, you could rely on that functionality being there.
Following the Kinode "Writing Data to ETH" tutorial, I was immediately impressed at how good the Foundry tooling is, and how well it fits into Kinode Rust processes. Alloy is immature but sick af.
Tightly integrating fakechains to the devX via Anvil is really cool too.
Next up is creating an onchain hub for a game/experience I've been wanting for awhile.



























