[Feedback wanted] XCMSend

1yr ago

6 Comments

Content
AI Summary

Halloy Hydra Community,

We are a team of builders and participants across various communities within the polkadot/substrate ecosystem.

We are brought together with a shared purpose, which is to turn nascent cross-chain infrastructure into a powerful and useful “playground of possibilities”.

Mission

The mission is to make it accessible and seamless to build cross chain workflows, across XCM(hrmp) and cross-chain infrastructure.

We want it to be useful for people of all levels (for technical, non-technical as well as generalists) within the ecosystem, (think of an open-source Zapier but for cross-chain Dapps).

Above is a very simple bagpipe to send DOT(Polkadot) to HydraDx.

Create “Bagpipes”

The nodal based canvass will allow users to weave together “Bagpipes”, which are complex workflows of actions that would typically take a sweat and resources by technical people to put together.

Bagpipes can be as simple as sending or swapping assets, but it gets more interesting as you weave together more complex workflows. These workflows can then be for personal use, shared with other members of your team, or turned into cross-chain DApps.

Examples to stimulate some ideas

One near term example is swapping DOT(on polkadot) for USDt (on asset hub), which sounds pretty boring and simple, but currently it requires sending your DOT to hydraDx from your wallet; then swapping on hydra; then sending to asset hub.

This currently takes multiple actions across probably more than one platform. With a bagpipe this can be done all in one signing ceremony and on one platform (once we integrate hydra swaps).

3 actions on ~2 platforms into one action in one place

Minutes not weeks

In the not-so-distant future, as we add more functionality (from different chains) into the canvass environment, anyone will be able to rapidly put together workflow possibilities that many of us have yet to consider.

As the variety of features (that you can drag and drop onto the canvas) compounds, so do the possibilities increase (exponentially).

It can take minutes rather than days or weeks to put novel and useful workflows that will contain a variety of features from various chains, including: assets, DEX, GOV, NFT, Identity, Scheduling, staking, trading etc.

The project is open source under the MIT license and you can access XCMSend by:

1: Build it yourself(docs: https://xcmsend.github.io/deployments/debian.html)
2: Use the public instance at: https://app.xcmsend.com/
3: use the public docker image(https://hub.docker.com/r/xcmsend/xcmsend)

We would love for you to try it out, to get a sense of the vision and possibility and to provide some constructive feedback we can use, and which will inform what features we build and prioritize.

What we’ve done

We’ve integrated the basic functionality so that you can send hydraDx to polkadot and other parachains.

Enabling Swaps

Polkadot (DOT) ->xTransfer-> HydraDx (DOT) ->Swap-> HydraDx(USDt) -> xTransfer -> AssetHub.

Near Term priority

The next order of tasks we want to prioritize is swapping functionality.

Weaving together influential communities (Near Term) Roadmap

HydraDx
Interlay
Wormhole
…

What we’d love to do

After gaining community feedback on our new project, we wish to seek treasury funding for enabling swaps using the HydraDx SDK, Omnipool, and spot price orders.

This swapping feature will enable anyone to interact with the Omnipool dex and build them into their “Bagpipe” workflows.

Useful links:

https://xcmsend.github.io/chapter_1.html

https://hub.docker.com/r/xcmsend/xcmsend

https://github.com/XcmSend/app-v0.0.1

https://decentration.medium.com/a-workflow-builder-adds-a-playground-on-top-of-cross-chain-infrastructure-25222617ed8

Note: The UX is still in beta, so do only keep amounts small until we release our stable version.

Thanks and please share some feedback in the comments!:)

Edited

Comments

7NzN...tBec

hey how are you, thank you very much for the interest and it is good to see these initiatives

However, I think that the model you mention is very similar to what is planned in the HydraDX roadmap.

"XCM swaps" ( check the last items on https://hydradx.substack.com/p/hydradx-monthly-september-2023

Can you indicate how it would be different?

7NzN...tBec

hey sir, so far it still seems more like a use of our sdk than adding new features, so honestly so far I'm not very excited, but will check all

Do you already have an estimate of who and how many are going to use this SDK? Is there interest in it?

7P5H...SViP

hey @Jose Crypto , we are not proposing to improve the SDK. Your hydraDx core team would be best suited for that.

We are a team asking the question,

"how can we make pallets across all the parachains more accessible and connectable, all in one place?".

We're focussed on what can be built over cross-chain infrastructure, and aiming to remove the inefficiencies in each community's product/app silos, connecting all the APIs in one builder like "zapier for web3".

We are token free and open-source, and getting some decent interest from initial users, and just beginning to add features.

Re: funding strategy, the main product features gets grants from the main treasuries (Polkadot, W3F, Kusama), this is for building the main canvas based platform and all the main blockchain primitives, such as gov, multisig, staking, etc; but for specific parachain pallet features (like swaps) we are going to request grants from the respective parachain community treasuries (if they have one).

So though it may not scratch the itch for SDK enhancements, as we provide more examples for everyone to use, it should become apparent how much value it can be to hydradx community and the ecosytem as a whole.

Edited

7Min...QaAa

Another good use case for enabling swaps for XCMSend using the omnipool, would make it a lot easier for new users to convert DOT on polkadot, swap it with omnipool and send it to the parachain, enabling users to do so in a simple drag and drop interface. A good case study of this can be found here: https://xcmsend.github.io/teleport/interlay.html

Another cool use case is letting web2 and frontend developers create an interface, drag and drop together a scenario with xcmsend then execute the transaction using xcmsend as a backend. Without needing to learn how to integrate with polkadot, its typesystem and polkadot.js, developers can now just drag and drop the transaction flow, and feed the scenario with custom input from their frontends. Opening up a lot of possibilities for people to create an application that interacts with the dotsama ecosystem.

Up 1

7P5H...SViP

Check out our intro post on polkadot forum:

https://forum.polkadot.network/t/powerful-no-code-cross-chain-xcm-dapp-builder/4767