Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more

View All Medium Spender

[Medium Spender] Referendum #617

inMedium Spender
a day ago
Deciding

Kusama Proposal: Kitdot Development Funding (Retroactive)

This is a retroactive funding proposal for work I've done over the past 3 months building Kitdot - a TypeScript development toolkit for Solidity on PolkaVM.

Website: https://kitdot.dev/

Vision

PolkaVM's success depends on different language stacks (Solidity, ink!, Move) working interoperably within the same runtime. I'm pushing Solidity tooling forward by removing the complexity barrier that keeps developers away from the ecosystem. Since Kusama Asset Hub is the current production environment for Solidity, this work directly benefits Kusama developers.

What is Kitdot?

Forum post: https://forum.polkadot.network/t/kitdot-build-web2-like-apps-on-polkadot/15303

Kitdot is a rapid prototyping toolkit similar to eth-scaffolding but for PolkaVM. It provides:

1. Web2-like authentication

2. Local environment setup

  • Automated setup for PolkaVM development with solidity on Kusama Asset Hub and Passet Hub
  • Developers don't need to understand hardhat-polkadot or foundry-polkadot configurations

3. AGENTS.md file

  • Complete context for LLM agents to develop and troubleshoot PolkaVM projects

Proven Impact

Kitdot launched at Latin Hack with strong results:

This work led to an invitation as mentor and judge for Sub0. Across both hackathons, I've seen clear demand for more mature tooling, documentation, and resources for rapid prototyping with Solidity on PolkaVM.

Addressing Developer Needs

Common hackathon questions I receive:

  • Where do I get price feeds? Which oracles?
  • Which NFT marketplace to test my NFTs?
  • What are the Uniswap v2/v3 implementations for token pairs?

I've started addressing these gaps. Since oracles are the biggest demand, I deployed one at: https://polkavm-oracle.w3d.community/

Funding Request

I've worked part-time on this for 3 months (~20 hours/week). At my usual ecosystem rate of $66/hour, that's $15,840 USD worth of work.

I'm asking for 1,032 KSM (~$9,999 USD at current prices).

To be clear: I'm going to keep building either way. This proposal is symbolic - it's about getting a green signal from the ecosystem that this work matters and aligns with where the long-term vision is heading. The funding validates the direction more than it compensates the effort.

Next Steps

Future work will follow grant milestones with proper evaluation. I'm developing production-ready templates for PolkaVM:

Both features need a Solidity wrapper for native stablecoins to allow contracts to interact with pallet_assets and let Solidity projects use the stablecoins available on Kusama Asset Hub and Passet Hub. The precompiles for this aren't well documented yet, so I'll create comprehensive examples during development.

Key insight: Solidity without access to native Substrate resources is meaningless to the established EVM market.

Current Status

  • Reached out to grant teams (Open Source Bounty and W3F) with positive responses
  • Developing infrastructure POCs for payment functionality and account abstraction services

Code Repos

Comments (2)

9 hours ago

Hi, thanks for the proposal. First, please avoid postpaid work—always discuss with the community first and get feedback before investing time and requesting funds.
Based on my review, most of this work consists of publishing examples, CLI tools, and basic frontend integration. Any new developer could achieve these results independently using open-source documentation and SDKs. Can you specify exactly where contracts were deployed—was this just an EVM testnet, or something more substantial?
Most wallet integrations with Metamask use their public APIs and documentation—every EVM-compatible project does this. Unless you’re directly collaborating with them or contributing upstream code, this is just standard developer integration, not a unique achievement. If you claim real collaboration, please share evidence (meeting notes, technical calls, PRs, etc.). Otherwise, it’s just regular usage of a common wallet provider.
Also, about the “oracle”—this is a highly sensitive component in any blockchain ecosystem. A real oracle isn’t just showing prices on a frontend; it needs to be secure, trust-minimized, and decentralized because bugs or exploits in oracles have resulted in multi-million dollar losses and attacks across DeFi history. Just deploying a demo or feeding prices from a single source is not enough. For reference, projects like DIA Oracle and Chainlink deploy robust infrastructure with detailed auditing and multiple sources for validation.
This feedback may sound harsh, but it’s just the reality. The work described might be worth a small tip ($50-$100), but it’s nowhere near the $9999 requested. In the age of AI and powerful developer tooling, please propose treasury spends responsibly and transparently.

6 hours ago

@GL7a...rrhX I think the best evidence of collaboration with Metamask team is this commit of fixing from their devrel team: https://github.com/ihsraham/examples/commit/9b6df84922905e83a5f7d43457437ade38c78c42 but If you want me to share the conversations we've had "off the records" I'm happy to do so, just need his authorization first.

On the Oracle topic: I've reached out to friends who work at Chainlink and there are discussions ongoing about it. I don't want to be an oracle provider, that's why I created one simple oracle to help builders go forward with their ideas during hackatons.

Everything I did during the last three months was collaborating with friends from the ecosystem, most of them left a comment in the forum.

This proposal consolidates the contribution I've done in the past months as independent developer trying to push solidity forward here. I started by doing just the documentation and realized we needed more, I've passed through a lot of iterations during development and that's why it took a bit more time than you may think it would be needed. The idea of this project did not came right away.

The contracts I've mentioned from builders were deployed on Passet Hub and you can see +200 links for each project in the link attached in the proposal.

8 hours ago

thanks for the proposal.

Kitdot integrates with Apillon to give you seamless access to Polkadot Cloud infrastructure. Deploy with just API keys - no complex setup required.

  1. Apillon is winding down operations / support.

  2. In general we believe general toolkits/protocols/contracts should only be funded if they are part of a product that demonstrates their novelty or utility.

  3. This feels very Polkadot centric from a messaging perpective. Kusama is an independent network and culture. This may be better suited to an application to Polkadot's Defi / Tooling bounty and/or Velocity Labs.

It might also be worth reviewing Virto Connect and providing a side by side comparison?

6 hours ago

@Decent Partners Yeah I know about it, my friend Johan is doing some working related with Virto and we are aways exchanging experiences since PBA. I think Virto solves a different issue than web3auth. One is for passkeys and the other is to enabling regular users to interact with the blockchain, the security level is not comparable to be honest. My humble opinion is that both should coexist and one does not exclude the other.

The Apillon windind down is very sad and I'm aware of it. I'm going to update the landing page and remove all mentions to it.

I decided to post here because Kusama is the production environment for solidity smart contracts right now.

PleaseLogin to comment

Requested

DOT
103.20K DOT

Voting Period

Decision Period

15 / 28 days

Confirmation Period

0 / 4 days

Summary

0%

Aye

AyeNay

0%

Nay

Aye (1)0.0 DOT

Support0.0 DOT

Nay (0)0.0 DOT

    Polkassembly - Referendum #617