Nemo Protocol Submission

[SpokieKid]

💪 Project Abstract

Nemo is an innovative protocol that turns multichain wallet activity into personality-driven AI agents. By analyzing a user’s DeFi, NFT, DAO, and governance interactions across Polkadot parachains, Nemo generates a custom AI persona—complete with MBTI-style traits and a soulbound NFT stored on AssetHub. These AI twins can answer questions in your own on-chain “voice,” evolving as your behavior changes.

Unlike traditional copy-trading tools, Nemo builds a personality-first, social-financial network. Users can monetize their on-chain identity by allowing others to chat with their AI persona—whether for alpha, entertainment, or insight. By blending behavioral analytics, memetic culture, and chain-native identity, Nemo introduces a playful and deeply personalized layer to the Polkadot ecosystem.

✅ Application Checklist

• The application template has been copied and aptly renamed (project_name.md).
• I have read and followed the program guidelines.
• I understand that grants are capped at $10,000 USD per application with a maximum of $15,000 USD per project in exceptional cases.
• I understand that each milestone is capped at $5,000 USD and must be delivered within 3 months.
• I understand that payments are made only after successful milestone delivery.
• I have clearly explained what the funding is going towards (e.g. 30 hours of a full time employee at $X / hour).
• The software delivered for this grant will be released under an open-source license specified in the application.

[FFilipUnique]

Hi @SpokieKid. Please reconsider that the grant funding above $15k will be considered only for special cases. If you can conform to an amount up to or below $10k it would be more in line with the Fast Grants propositions.

[SpokieKid]

Hi @SpokieKid. Please reconsider that the grant funding above $15k will be considered only for special cases. If you can conform to an amount up to or below $10k it would be more in line with the Fast Grants propositions.

BP updated with budget in line with requirements, thanks!

[FFilipUnique]

@SpokieKid can you clarify a few points for us:

Due to AssetHub’s current limitations (no native smart contract logic), the evolution logic is offloaded to an external dApp smart contract"

What does "offloaded" mean? Where is the smart contract being built and executed (on what chain)?

Could you outline for us your go to market strategy and future plans for growth?

regarding this statement

All profiling is processed on the client side or through secure middleware, and the final persona can be minted in a privacy-preserving manner.

Could you be more specific on this point? In what manner, i.e. what steps are you taking to ensure that the privacy is not leaked. On what is the "secure middleware" mechanism based? How is the private data maintained? Which private data do you need to retain and how do you keep track of it (centralised database or some other machanism)?

Did you do any market profiling or surveys to asses interest in a product of this kind? What we are interesested in is, do you see this solution as one that might interest many users or are you targeting a small subset of token owners? Who is the ideal user profile? What is the reasoning behind the demand model? In relation to q#3, if you consider this something everyone might benefit from how do you see the adoption happening?

[SpokieKid]

@SpokieKid can you clarify a few points for us:

Due to AssetHub’s current limitations (no native smart contract logic), the evolution logic is offloaded to an external dApp smart contract"

What does "offloaded" mean? Where is the smart contract being built and executed (on what chain)?

Could you outline for us your go to market strategy and future plans for growth?

regarding this statement

All profiling is processed on the client side or through secure middleware, and the final persona can be minted in a privacy-preserving manner.

Could you be more specific on this point? In what manner, i.e. what steps are you taking to ensure that the privacy is not leaked. On what is the "secure middleware" mechanism based? How is the private data maintained? Which private data do you need to retain and how do you keep track of it (centralised database or some other machanism)?

Did you do any market profiling or surveys to asses interest in a product of this kind? What we are interesested in is, do you see this solution as one that might interest many users or are you targeting a small subset of token owners? Who is the ideal user profile? What is the reasoning behind the demand model? In relation to q#3, if you consider this something everyone might benefit from how do you see the adoption happening?

1. About “offloaded to an external dApp smart contract”

AssetHub is designed as a system parachain for basic asset storage and management. It does not support custom smart contracts, so logic like dynamic metadata updates or behavioral-driven evolution cannot run on-chain there.

We therefore offload this logic to a smart contract deployed on Moonbeam, a smart-contract-compatible parachain in the Polkadot ecosystem.

This contract reads updated behavior profiles (stored on IPFS), and updates the metadata pointer (CID) on AssetHub NFTs via authorized transactions — enabling evolution while maintaining AssetHub as the canonical asset layer.

2. Go-to-Market Strategy and Target Users

Our early users are on-chain trader KOLs who publicly share their trading styles. Nemo lets them mint AI personas reflecting their strategy, turning behavior into brand. Followers can chat with these personas to understand their trading logic — forming a new kind of social trading layer based on replicable identity.

3. On Privacy & Middleware Profiling

We follow a local-first, privacy-respecting approach:

• Behavior is analyzed on the client by default, inside the browser
• When middleware is used (with user consent), it:
• Does not log wallet addresses
• Returns anonymous behavioral summary (risk, asset preference, activity score, MBTI)
• Stores no identifiable information

The middleware is built using Node.js + Redis, without any persistent database for user identity.
NFT metadata includes only IPFS links and personality tags — never wallet information.

4. Market Research and Demand Modeling

We’ve conducted informal user interviews with over 30 crypto-native users. The feedback shows:
Over 70% are excited by the idea of having a personality-driven identity layer tied to their wallet behavior
KOLs and memecoin creators see strong storytelling and engagement potential with AI-driven personas

We have not conducted an open beta yet, but are preparing an invite-only Alpha with handpicked users.

Our target users include:

• Crypto KOLs and social content creators
• Active NFT/DeFi wallet holders
• Users seeking personality-based expression and brand-building

We believe behavior-based personas will become key primitives in the evolving crypto social layer, and early adopters will drive the wave forward.

[FFilipUnique]

@SpokieKid Thank you for the answers. It clarifies a lot of points, much appreciated. There is one more question we have that would help in assessing your project. Would you consider the challenge of building the contracts for your project as native Polkadot, not parachain EVM-based?

[oshakarishvili]

Closing this due to inactivity.