Looking for Honest Feedback: Am I Experiencing Edgeware Déjà Vu?

Tech Talk
1

A few days ago I shared a detailed overview of what I’ve been building over the last eight months:

After reflecting on it, I found myself thinking about one lesson I learned from Edgeware: sometimes the challenge isn’t building something—it’s building the right thing at the right time.

Unlike many forum proposals, this isn’t a collection of ideas sitting in a notebook. Most of the components described in the post already exist in some form and are running on devnet today.

InterLayer, LiteVerse, the explorer, governance application, wallet, portal, faucet, bridge infrastructure, and the early foundations of InterClaw have already been built and integrated. There is still a lot of work ahead, but the majority of my time over the last eight months has been spent shipping code rather than writing concepts.

That is exactly why I’m asking for feedback now.

Before I spend another year expanding and polishing this stack, I want to understand whether I’m solving problems that actually matter to the broader Polkadot ecosystem.

Questions for the Community

Which part of the stack do you find most compelling?

Which part do you think has the strongest product-market fit?

If you were in my position, where would you focus development efforts next?

Does a Multi-VM architecture solve a meaningful problem, or is it unnecessary complexity?

Is LiteVerse potentially more valuable as a standalone infrastructure layer?

Are decentralized AI agents something Polkadot should be investing attention into today?

One concern I have is what I would call “Edgeware déjà vu.”

Not because the technology is the same, but because I worry about spending years building things that are technically interesting while missing what the ecosystem actually needs right now.

Maybe the stack is too broad.

Maybe I’ve tried to solve ten problems simultaneously.

Or maybe there is one component here that deserves significantly more attention than the others.

I’d genuinely appreciate honest feedback, including criticism.

At this stage I’m not looking for encouragement as much as clarity.

If you had to choose one thing from the entire stack that deserves to survive and grow, what would it be, and why?

Update :

These are some of the product links available for testing. They were previously hidden behind markup in the main post.

Faucet

Supports all internal VM addresses. Built using pallet-faucet with on-chain rate limiting.

Portal

You can use the embedded Alice wallet for a quick demo or connect your own wallet after receiving test tokens.

Current features include:

  • Staking
  • Username registration
  • Wallet binding across internal VMs
  • External chain deposit address generation and management
  • Points and quest system designed to onboard and educate users about InterLayer

Explorer

An explorer that supports all internal VM transactions, tokens, NFTs, atomic bundles, smart contract verification, dashboards, and more. It also includes AI-assisted features used by the InterClaw assistant.

Wallet

A web wallet supporting all internal VM operations, external addresses, usernames, staking, and most portal features.

I also have a Chrome extension and Android wallet in development that follow a similar design. These will be open-sourced.

Governance

A custom OpenGov implementation with additional ideas and use cases designed specifically for InterLayer, investment DAOs, and agent-based operations. More details are available in the main post.

Polkadot.js Apps

Since InterLayer is built on Substrate, you can connect and interact with the chain directly through Polkadot.js Apps.

Direct link:

You can inspect blocks, extrinsics, events, storage, runtime metadata, accounts, governance, and interact directly with the chain.

RPC Endpoints

You can use the main WSS/RPC endpoint or connect directly to individual VM RPC endpoints for testing.

LiteVerse

LiteVerse shares some similarities with Acurast, but it is designed for different use cases.

You can already run and test nodes:

Browser Node

Dashboard

The mobile node link is available in the main post. If you’re interested in running a CLI node, feel free to DM me.

More documentation and guides will be published soon.

InterClaw

InterClaw is an on-chain personal assistant powered by LiteVerse nodes.

You can log in using the embedded Alice wallet and test the current functionality without running a VPS.

To be completely transparent, InterClaw is still in an early stage and is probably around 30–40% complete. Most of my development effort so far has gone into building the core infrastructure and foundational features.

Important Note

Most utility services are currently hosted on Cloudflare’s serverless infrastructure. However, the main node, validator setup, and explorer backend are currently running on a single Contabo VPS.

Because of this, you may occasionally notice some delay when using WSS/RPC endpoints or explorer-related services.

2

Hi bharath looks interesting can you share the repository/crates links, specially the Multi VM architecture, would like to see the code involving the afore mentioned feature packed substrate pallets.

3

I cant see that entire stack you are referring to. But from the list of web3 native infra components you listed above, I would 100% choose **bridge infrastructure.
**
After Hyperbirdge fiasco, Polkadot eco is in dire need of a suitable, fast and reliable bridge to other ecosystems. Atm, the ecosystem is dry of liquidity, it needs an easy way for stables to hit the blockchains, for wrapped tokens to fill user wallets and even for RWAs to be wrappedly deployed on Asset Hub. And a bridge, in the terms i described above, is the only path forward.

4

Hi,

Read throw your proposal, mentions remz and shankar from edgeware(+1 | good guys).

Right now users can run evm and risc-v on polkavm, movevm has been some work on(not sure what status is.. )

Since you aim for interoperability maybe you could focus on getting solana binaries/programs to compile to polkavm? then i guess you could just create a rpc wrapper for it. Maybe try to narrow down focus and getting the solana programs to run better(hopefully without all the casino bs) on polkavm? (just thoughts)

~fllpchan

5

Hi, thanks for checking it out.

I’m currently cleaning up and documenting the repositories before making them public. A lot of the code was built rapidly over the last few months, so I want to make sure everything is properly organized and documented first.

I’m aiming to have the repositories ready by the end of this month.

6

Thanks for the suggestion.

One distinction worth mentioning is that InterLayer’s primary onboarding model is not a traditional wrapped-asset bridge.

Instead, every user receives unique deposit addresses across networks such as Bitcoin, Ethereum, Solana, and custom chains. These addresses are generated and secured through MPC infrastructure and mapped directly to the user’s InterLayer account.

When assets are deposited, LiteVerse watchers monitor the external chains, validators verify the deposits, and the user’s unified balance inside InterLayer is updated.

The goal is to provide a familiar CEX-style onboarding experience while supporting multiple external chains through a single account and balance layer.

Another advantage is that these multichain addresses are not limited to deposits and withdrawals. Since they are tied to a user’s InterLayer identity, they can become programmable accounts. User-authorized agents can interact with external chains, trade on DEXs, manage treasury operations, execute payments, and automate workflows while operating within user-defined permissions and policies.

The deposit infrastructure focuses on liquidity aggregation and account abstraction. At the same time, developers remain free to build independent bridges, liquidity protocols, and interoperability solutions targeting any VM environment within InterLayer.

I’ve also updated the main post with links to the currently available products, explorer, wallet, portal, governance, Polkadot.js endpoint, RPCs, LiteVerse, and InterClaw so it’s easier to explore the existing stack before judging the remaining pieces. I’ve attached a simple diagram below that may explain the deposit and liquidity flow better than my original post.

1000160851
10001608511536×1024 189 KB

7

Thanks for the feedback.

InterLayer takes a slightly different approach. The runtime itself is built on Substrate, with MEL (Multi-VM Execution Layer) acting as an orchestration layer above multiple execution environments.

1000160857
10001608571024×1536 172 KB

Rather than compiling Solana programs into PolkaVM, SVM is already integrated as a first-class execution environment alongside EVM, Move, CosmWasm and PolkaVM.

The goal is for these VMs to interoperate through MEL and shared runtime services while remaining independently executable.

Additionally, many of the runtime components are being designed as modular FRAME pallets, which means they can potentially be open-sourced and reused by other Substrate or PolkaVM-based chains without requiring the full InterLayer stack.

You can also inspect chain activity through the explorer, Polkadot.js/apps or test directly through the available RPC endpoints and scripts. I’ve updated the main post with the relevant links if you’d like to take a look.

I’m currently cleaning up and documenting the repositories before making them public, but I’m happy to discuss specific implementation details in the meantime.