Grant Application: Polkadot ElizaOS Plugin - Revive Pallet Extension

[tylermcwilliams]

Project Abstract

Enabling AI agents to interact with Polkadot's Revive pallet smart contracts.

This Revive Pallet Extension extends our successfully delivered Polkadot ElizaOS Plugin (M1, M2) to enable AI agents to interact with smart contracts deployed on Polkadot's Revive pallet. This follow-up grant addresses the specific guidance provided by Web3 Foundation reviewers during our original grant process (PR #2518), who recommended focusing on pallet-revive integration and direct chain interactions.

The plugin provides intelligent address routing between H160 and AccountId32 formats, dual-mode contract deployment and interaction, contract event monitoring, and basic analytics integration. It leverages both Revive's Ethereum RPC endpoints and native Substrate interfaces to provide AI agents with Revive interaction capabilities.

Grant level

• Level 1: Up to $10,000, 2 approvals
• Level 2: Up to $30,000, 3 approvals
• Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

• The application template has been copied and aptly renamed (project_name.md).
• I have read the application guidelines.
• Payment details have been provided (Polkadot AssetHub (USDC & DOT) address in the application and bank details via email, if applicable).
• I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
• 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.
• The initial PR contains only one commit (squash and force-push if needed).
• The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
• I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

[diogo-w3f]

@tylermcwilliams Thanks for the submission. Before we proceed, please address the following to align with the W3F template and ensure clear acceptance criteria:

• Payment details. Please confirm the “Payment (USDC)” address is a Polkadot AssetHub address and keep the “(USDC)” suffix. If different from the DOT address, provide the correct AssetHub address explicitly.

• Contact section. Add a Website URL (or state “n/a” if not applicable).

• Team code repos. Add links to:
  The foundational Polkadot ElizaOS Plugin repository you’re extending.
  The repository where this Revive pallet extension will live (if different).

• Milestone acceptance criteria
  Define explicit, testable acceptance signals for deliverables. For example, for “Official ElizaOS Integration,” acceptance should be: PR opened to the official repo + recorded/demo of functionality + user-facing docs. The merge itself can be a stretch goal to avoid dependence on third-party timelines.

For each deliverable, include how reviewers will verify it (e.g., CLI/API example, sample config, expected output).

• 0c. Testing and Testing Guide (mandatory)

Please explicitly state in this application that Deliverable 0c will include:

• A Local Testing Guide (how to run tests locally, commands, basic coverage expectations).
• Any required RPC endpoints/networks and environment variables documented for reproducibility at delivery time.
  We do not require these assets now, but they must be delivered with each Milestone under 0c.

Once these updates are in, we can proceed with the review.

[tylermcwilliams]

Hey @diogo-w3f thanks for the feedback, I updated the application with all your requested changes and it should be good to go now. I also took the opportunity to slightly reword certain parts of the application that seemed a bit unclear.

Let me know if anything else needs adjustment.

[diogo-w3f]

@tylermcwilliams thanks! The application is ready to review, I'll ping the committee to review it.

[semuelle]

Thanks for the follow-up application, @tylermcwilliams. One question beforehand: what's the current status of the plugin? Do you have any user metrics yet?

[tylermcwilliams]

Hi @semuelle

The foundational plugin is live and actively maintained at https://github.com/Esscrypt/plugin-polkadot. It was successfully merged into the official ElizaOS ecosystem after completing both milestones.

Regarding user metrics - we don't have specific adoption numbers to share. ElizaOS itself is still very early stage and doesn't provide analytics or usage tracking infrastructure for plugins yet. The plugin is functional and available, but given how nascent the ecosystem is, meaningful metrics are hard to come by at this stage.

That said, we're continuing to build strategically. Our next phase is a JAM protocol-based extension for the plugin - we're already working on JAM protocol client implementation. This Revive extension positions us well for that integration. We're also exploring the possibility of a user-facing ElizaOS agent built specifically for the Polkadot ecosystem.

Let me know if you need any other details!

[diogo-w3f]

@tylermcwilliams please note that the grants guidelines have recently changed
. It would be helpful if you could provide information showing how your project fits what we’re looking for, and how it avoids the categories listed under What Doesn’t Fit Our Program.

[tylermcwilliams]

Thank you for raising these concerns, @diogo-w3f. I'd like to clarify how this project aligns with the updated guidelines.

Direct Alignment with Priorities
This project addresses two areas you've explicitly prioritized: AI applications and pallet-revive integration. In fact, during our previous grant evaluation (PR #2518), your reviewers specifically recommended we focus on Revive capabilities as a follow-up—which is exactly what we're proposing here.

Proven Track Record
We've demonstrated our ability to deliver. Our foundational plugin was successfully completed, merged into the official ElizaOS ecosystem, and is actively maintained. This proposal builds directly on that established foundation.

Genuinely Polkadot-Specific
This work tackles challenges unique to Polkadot's architecture. Revive's dual-mode architecture (Ethereum RPC + Substrate) and H160 <-> AccountId32 address routing create integration complexities that simply don't exist on other chains. We're solving Polkadot-specific problems, not applying generic patterns from elsewhere.

Technical Infrastructure, Not Marketing
This is infrastructure that enables AI agents to interact with Revive contracts—not a token-focused project or marketing effort without technical substance. By building this foundational layer, we're creating value that enables applications to drive real ecosystem activity.

Open Source and Community-Focused
All our work is fully open source and designed to benefit the entire ecosystem. Our previous deliverables are publicly available, and this proposal follows the same approach—building shared infrastructure that anyone in the community can use and contribute to.

We've shown our commitment through successful delivery and ongoing maintenance of our previous work. If there are specific aspects you'd like us to address in the application itself, we're happy to incorporate that feedback.