For this proposal, we’ll be reaching out to a set of bridges and liquidity providers to apply for grants in order to fund the development of protocol specific wrappers in order to integrate them into Swidge and increase the ecosystem’s awareness of Polywrap.
Polywrappers will be written in Rust, compiled to WASM and deployed to IPFS so they can be consumed by the JS SDK by any developer. The wrappers of the different protocols will initially be taken care of by us, with the possibility of anyone to become maintainer in the future, or anyone to create wrappers for new protocols as things grow.
- Where and how does your project fit into the ecosystem?
Swidge enables any developer to use cross-chain liquidity in a safe and abstracted way, while having the certainty that every piece of the system is decentralized.
dApp builders can benefit from our SDK, initially in JS and later on in more languages, so they wouldn’t need to learn how to interact with specific protocols and how to move assets to different chains in order to execute transactions against those protocols.
- Who is your target audience?
The initial target is to give service to the Swidge.xyz platform, which is an any-to-any swap service provider and acts as a showcase and way for us to develop new user experience workflows. The Swidge protocol is created to be a substantial piece of infrastructure that any developer can use to move any asset and interact with any protocol across any chain.
- What need(s) does your project meet?
Swidge meets the needs of dApp developers who want a simple way to integrate different liquidity protocols from a variety of chains into their dapps. With our SDK developers will be able to interact with any protocol in an abstracted manner, simply executing standardized methods on the SDK.
- Are there any other projects similar to yours in the ecosystem?
There are many projects trying to solve interoperability of liquidity protocols across chains, but so far everyone is relying on centralized logic in order to take decisions on which is the best route, and in many cases even to encode the transaction for the on-chain contracts, which is a huge liability and a single point of failure on what should be part of a decentralized financial infrastructure.
Swidge comes to solve this issue by giving the user ownership of the last piece of the system, the transaction encoding process. With Polywrap wrappers holding the logic of the algorithm that checks the possible paths and generates the calldata required for the contracts, we eliminate any single point that could be risky and exploitable at a big scale.
On top of that, thanks to the nature of WebAssembly, being sandboxed and safer than other runtimes on the browser, it adds a layer of security to these delicate steps where transaction generation could be spoofed with different receiving addresses.
- Fabian Weber
- Sandro Puig
- Contact Name: Fabian Weber
- Contact Email: email@example.com
- Website: https://swidge.xyz/
Starting business development to add new DeFi wrappers and expand the Polywrap ecosystem. Goal: obtain grant funding for building new DeFi wrappers.
- Estimated duration: 1 month
- In FTE: 1 Business developer
- Costs: $4,305
|1||Wormhole proposal||Described below|
|2||cBridge proposal||Described below|
|3||Stargate proposal||Described below|
|4||Axelar proposal||Described below|
|5||1inch proposal||Described below|
|6||OpenOcean proposal||Described below|
|7||0x proposal||Described below|
- Working through the documentation of the protocol
- Prepare a detailed proposal with the roadmap of implementation
- Coordinate with the Polywrap team to make proposal, supply possible requirements and receive feedback of the application
|Wormhole proposal||Working through documentation||1|
|Wormhole proposal||Prepare proposal||0.3|
|Wormhole proposal||Apply and coordinate proposal demands||0.2|
|cBridge proposal||Working through documentation||1|
|cBridge proposal||Prepare proposal||0.3|
|cBridge proposal||Apply and coordinate proposal demands||0.2|
|Stargate proposal||Working through documentation||1|
|Stargate proposal||Prepare proposal||0.3|
|Stargate proposal||Apply and coordinate proposal demands||0.2|
|Axelar proposal||Working through documentation||1|
|Axelar proposal||Prepare proposal||0.3|
|Axelar proposal||Apply and coordinate proposal demands||0.2|
|1inch proposal||Working through documentation||1|
|1inch proposal||Prepare proposal||0.3|
|1inch proposal||Apply and coordinate proposal demands||0.2|
|OpenOcean proposal||Working through documentation||1|
|OpenOcean proposal||Prepare proposal||0.3|
|OpenOcean proposal||Apply and coordinate proposal demands||0.2|
|0x proposal||Working through documentation||1|
|0x proposal||Prepare proposal||0.3|
|0x proposal||Apply and coordinate proposal demands||0.2|
|Total per SP||$410|
By submitting this proposal, I understand that the DAO and my sponsor will be evaluating whether my work meets the acceptance criteria. If it does not, the DAO will determine what percentage of the proposal cost to pay, if any.
I also understand that I may not begin work until it is confirmed that the Snapshot proposal has passed.
[ X ] I agree