Copy n paste papi application

[illegalcall]

Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).

Application Checklist

• The application template has been copied and aptly renamed (project_name.md).
• I have read and followed the program guidelines.
• I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
• The software delivered for this grant will be released under an open-source license specified in the application.

[keeganquigley]

Thanks for the application @illegalcall this looks really good imo. Just one question, can you explain in detail the smart contract section in M2? If I understand correctly, you would implement rEVM for functionality with the upcoming Asset Hub launch in addition to Moonbeam and ink!?

[illegalcall]

Hey @keeganquigley
glad you liked copy n paste papi
Okay to answer the question, the basic idea is when we deploy a smart contract or a pallet call, we want to make it easy and accessible to interact with it, with our tool you will be able to directly interact with it.

We were in PBA bali and we faced this problem, so we started working on it, got feedback from fellows that it would be good for the community too.

[illegalcall]

Hey @keeganquigley did you manage to check this out?
Happy to discuss more on this.

[niklasp]

@illegalcall thank you for the comprehensive application.

Before going forward I have several questions:

1. There are some overlaps with existing apps in the ecosystem. Are you aware of https://papi-simulator.aipop.fun/ that was funded by Open Source Fast Grants. Also the papi explorer . What do you think are overlapping features and are you open for collaborations / alignment?
2. Work is shifting to doing lots with AI agents instead of manually coding. I value the creation of manual playground tools but the decision would be easier for me if you considered agentic coding strategies too. e.g. also shipping markdown that includes all the logic you are building into the ui in text form. Have you tried how your proposed solution can improve working with GPTs and papi?
3. Currently the tool is more of informative qualities for experienced developers that know which storage query or extrinsic they want to run. Can you imagine adding a demo section, where specific "use cases" or tutorials are displayed.
4. Do you plan to expand the available networks. I would e.g. find Polkadot Asset Hub + Polkadot People useful additions.
5. Would you consider implementing a code editor as well so that users can change the api calls and play around? Afaik the only tool available is for polkadot.js here and there has been a cancelled RFP around that subject.
   
6. I saw your forum post and papi teams response. Very good that you reach out to the community in advance. Do you have any goals to increasing the visibility of your tool once it is done?
7. Including docs comments and links to the docs on all calls / queries / events would really help https://docs.rs/pallet-nfts/37.0.0/src/pallet_nfts/lib.rs.html#826 also making those searchable could improve UX. Can you imagine adding that feature?

Bugs I have encountered with preview UI

• clicking connect wallet with two installed wallets opens all screens. let users select which wallet they want to connect

Also can you remove the "upfront" in your M1?

[niklasp]

@illegalcall

[illegalcall]

@niklasp Thank you so much for the great questions. I am sorry for the delayed response as i was on a trip, I am back now. Let me give a response in a couple of hours today.

[illegalcall]

1. Yes, I've tried both! I built this tool at PBA Bali because I was frustrated jumping between dev.papi.how docs, GitHub examples, and VS Code trying to figure out PAPI. My classmates had the same problem.
   The issue was only partly PAPI being complex - majorly it was discovering what's available and understanding how it actually works. I talked with the PAPI creators and other ecosystem leaders about this, and they also recognized the problem and encouraged me to pursue this tool.
   What my tool focuses on:

• Interactive exploration - Browse all available pallets/methods visually
• Live blockchain interaction - Connect your wallet and actually DO things (stake, vote, transfer)
• Instant code generation - Get production TypeScript for what you just executed
• Project scaffolding - create-papi-app CLI to start building immediately
  The key part: You can use it as a functional blockchain interface AND get the exact code for your actions. Example: Stake 100 DOT through the UI → Get the TypeScript for that operation.
  Yes, there's some overlap with existing tools, but I see them as complementary. Each tool serves different needs in the developer journey, and I'd love to integrate rather than compete.

2. Yes, I was considering this too, I feel like this will really make agentic coding feasible. I've used Claude Code with PAPI and seen the struggle - fragmented docs, nested types, hard for AI to discover patterns.
   So I will build

• MCP Server - Let Claude/Cursor/Continue query PAPI docs directly
• Markdown Exports - AI-optimized docs for LLM context

3. Yes, I am thinking of adding a use case dashboard (click "Token Transfer dApp" → generates code). Still looking for more feedback and requests on whats important and useful.

4. Yes, definitely! While I was building this, Jakub from Hydration saw my tool and really liked it, he asked me to add support for hydration, so I did it immediately.

5. Yes, I like it, for the first version, thinking of having single-file editing and live execution. Studied Subshell - they have a code-only REPL. Mine will be bidirectional: use the UI → generates code → edit it → execute. Best of both worlds.

6. Thank you, yes, I am considering this strategy that, I'll share on quick updates about features being built on X, a little bigger updates on LinkedIn and technical articles on Medium, create tutorials and videos, present at events, and post progress reports on the forum.

7. Yes! I'll extract Rust doc comments from metadata and link to official docs. Also adding fuzzy search with ⌘K shortcut to quickly find pallets, methods, and events even with typo.

About the bug you mentioned, Thanks for catching this! Will fix asap.

Thank you for reading @niklasp

[niklasp]

@illegalcall Can you please add the points that you agree with to your application so we can reevaluate with the changed scope

[illegalcall]

Hi @niklasp, thanks for the guidance. I’ve added the points we discussed and updated the application accordingly. Appreciate your help refining the proposal, I’m excited to move forward with next steps.

[ditavia-br]

@illegalcall Thanks for the application. We are nearing the end of our runway, so we’ll need to wait for clarity on the budget before moving forward with any remaining applications. We’ll get in touch as soon as we have an update.

[illegalcall]

Hey,

Thanks for the update, totally understand and appreciate you letting me know.

Are there any other grant programs or ecosystem teams you’d recommend I talk to where this could be a good fit? Even a few pointers would be super helpful.

I’ll keep building in the meantime and look forward to hearing from you once there’s more clarity.