You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please feel free to ask any questions in Discord or as a comment below
Raiden on rollup (Optimism, zkSync, similar)
This task is quite demanding as it might require some changes to how the smart contracts are written etc. It could however be a good learning experience if you’ve already decided to use the hackathon to get familiar with rollups.
Raiden on xDai
Deploy the Raiden smart contracts to xDai and modify the client code to allow the xDai chain to be used. Additionally, a tool similar to the Raiden Wizard for xDai would be great to have in order to provide a smooth and easy onboarding experience.
Modify Raiden contracts to earn interest on deposits
Currently, ERC20 tokens deposited into Raiden are locked and sitting idle in a smart contract. It would be interesting to explore options for activating these tokens in a way that they could earn interests on platforms similar to yearn, Aave or Compound.
Build a plugin payment “widget” for using the Raiden light client for payments on websites
The idea here is to build and design an easy to use widget that online vendors and shops can just add to their website in order to have the option to pay for goods or services with Raiden. Think of it a bit like when you pay for something using PayPal.
Build a Metamask like plugin/extension for using Raiden LC in the browser
A browser extension that allows users to do Raiden payments from the browser in the same way as with Metamask
Alternatively, investigate and implement integrating Raiden directly into MM
Build tools for easy onboarding, potentially batch on boarding.
Raiden onboarding is quite expensive and requires 3 or more transactions to register with the Raiden Service Bundle as well as opening channels. Investigating and potentially implementing tools for batching transactions and/or other neat tricks to save some gas fees are very relevant with Raiden.
Use Raiden in tandem with another L2 payment solution to offer different payment options suitable for a requested type of payment.
If you’re interested in hacking on and getting familiar with some different L2 payment solutions this task could be interesting for you. The idea is to build a hub that onboards users to different L2 solutions simultaneously and tries to decide on behalf of the user which payment method will be cheapest for a specific payment type.
Hack using the Raiden Light Client SDK to power payments
This idea spans widely and is focussed on directly using the Raiden Light client for any kind of payment use case. So if you have a specific use case in mind, don’t hesitate to reach out on Discord and pitch it to the team.
Redesign the Light Client dapp.
If you’re more interested in designing and UX/UI of payment systems then fear not. The Raiden team would love to see a fresh new look and improvements to the UX/UI of the dApp. It could also be an entire new dApp built from the ground up.
Off chain minting similar to the Raiden Reddit scaleoff solution
Continue working on the Raiden Reddit Scale-off solution and work on a solution for doing off-chain ERC20 token minting
Make a website for creating payment requests
This would be similar to https://link.zksync.io/ or PayPal’s payment request functionality, where a user can create payment requests and share it. When the receiver clicks the link they are redirected to perform the payment with just one click.
Atomic swaps are currently not natively supported in Raiden, but it’s possible to make an interface that allows for atomic swaps between two different tokens. This is a bit of a challenging task, but also very interesting, so please reach out to the team if you are interested in this.
The text was updated successfully, but these errors were encountered:
List of inspiration and ideas to hack on Raiden
Please feel free to ask any questions in Discord or as a comment below
The text was updated successfully, but these errors were encountered: