Polkadot Auto-teleport XCM SDK

[exezbcz]

Project Abstract

Polkadot XCM UI Library: ParaPort combines SDK and UI components designed to streamline the interaction with XCM. 
This SDK acts as a robust tool for dApps, leveraging the simplicity of React and Vue components. It addresses the challenge of querying and processing information from XCM pallets. It bridges the gap between developers' knowledge and their need to create interconnected dApps in the Polkadot ecosystem.

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)

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[exezbcz]

I have read and hereby sign the Contributor License Agreement.

[takahser]

@exezbcz thanks for your submission. Could you ellaborate how your project differs from this library: https://github.com/DecentroDev/polkadot-sufficient-assets

[exezbcz]

@exezbcz thanks for your submission. Could you ellaborate how your project differs from this library: https://github.com/DecentroDev/polkadot-sufficient-assets

Hey @takahser,

Thanks for your comment.
Although these projects may appear similar, there are many distinctions.

Firstly, ParaPort is an end-to-end SDK and library to solve XCM teleportation.

As you can see on the image above, Paraport solves all these complex steps above where as PSA only solves the case the user clicks on the button and it spawns an XCM transaction to be signed. Therefore, every complex operation needs to be done by the developer again. Only autoteleport utils in KodaDot have around one thousand Lines of code that would need to be copy-pasted, and it is trivial to make mistakes in that.

Secondly, ParaPort handles balance calculations on both sides, so users won't get stuck with the XCM or won't get destroyed by a minimal existential deposit.

Last but not least, ParaPort strongly emphasizes the UX aspects of the entire SDK. It's designed to minimize flow interruptions when users are trying to complete their primary task. Instead of forcing users to navigate away to handle token transfers, ParaPort creates a streamlined experience by handling these operations within the context of the user's intended action. This means fewer modal popups, fewer context switches, and a more cohesive user journey when performing cross-chain actions.

[takahser]

@exezbcz sry, I'm struggling to get on top of my backlog; will try to review this PR again by the end of this week.

[keeganquigley]

Hi @exezbcz thanks for the application. @dudo50 since you were one of the authors on the research paper, I'm wondering if you can comment on its usefulness?

[dudo50]

Hey @keeganquigley , thanks for tagging me.

I am not aware of this project, nor was I contacted in advance that something like this is being written as a grant proposal.

The proposal's description and headline make it unclear whether the solution is an XCM SDK or an XCM UI Component. I suggest @exezbcz update the wording to be more accurate so we can give a more informed evaluation.

If I understand correctly, this is a proposal for a cross-chain UI component for dapps. The usefulness of plug and play UI components that can cross-chain smoothly is definitely needed within ecosystem as it eases onboarding for dapps, where developers just grab the plugin that suits them the most and they don't really need to know by what it is powered (whether ParaSpell or other ecosystem SDKs), they just want it to be smooth and user friendly for their dapp users.

If the proposed solution mimics the incentives proposed in the LiquiSpell paper, then I personally see its benefit.

Our XCM Tooling at ParaSpell is already mature enough to offer solid ground for this work.

I also see that the team is from KodaDot. KodaDot has been our partners and first implementers since we began development in ParaSpell. We have good experience with their team.

@keeganquigley this is as much as I know/ can tell you regarding this proposal at the moment.

Hope it helps.

If any further questions arise, feel free to ask.

Thanks!

On the other note:
@exezbcz I would like to suggest you, if the incentive is approved to contact us. ParaSpell offers free implementation support for everyone.

With kind regards,
Dudo