1. initial state
2. path not found
3. path found
4. initiate ibc transfer
5. approve ibc transfer
6. successful ibc transfer
7. checking the transfer on the block explorer
8. un-escrow token example
9. list of active channels
10. Starway.monster - your new DeFi perspective to cross-chain portable value
12. What is starway.monster
13. Starway.monster architecture
13. Our team
14. Starway.monster statistics during HackAtom hackathon
15. Thank you for your attention
We believe that decentralization and an ability to fully control your own funds/data/assets hinges on quality of blockchain solutions available in the marketplace. At the same time, a plethora of limitations of existing solutions plagues users’ ability to unlock the full potential of value portability across the web coupled with lower fees and better usability. The latest mainnet release of IBC protocol is one of the many industry attempts to lower the boundaries/frictions for secured value transfer has inspired our small team to build an easy-to-use, secured and credible solution … Starway.monster, a service that represents your new DeFi perspective to cross-chain portable value.
What it does:
1) Your ability to identify verified interchain pathway for your secured token transfers (by route or by fee);
2) Your ability to make IBC transfers across Cosmos Network;
3) Your ability to find a verified un-escrow pathway to obtain a native token;
4) Your ability to instantly un-escrow your wrapped tokens via transferring them back to a native token Zone/Hub.
How we built it:
We used Keplr wallet, Kubernetes cluster, Hasura, RabbitMQ, blockchain watchers, PostgreSQL, Angular, Java, Golang, Nginx, ArgoCD, GitHub Actions and some other.
Challenges we ran into:
- We had to keep different versions of watchers for different blockchains located in different branches (cosmos-watcher repositories on GitHub), as the versions of internal libraries are often non-compatible;
- Cosmjs is not able to send IBC transfers that leads to manual tweaks and pertinent implementation;
- Tendermint rpc client does not support ssl and does not allow using different transport. For that reason, connecting an rpc endpoint with ssl requires additional efforts to solve the issue;
- Several blockchains does not provide any data on denomtrace via rpc;
- When parcing the blocks there was a bug in Cosmos SDK, we resolved the issue.
Accomplishments that we're proud of:
We managed to deliver fully functioning web application that anyone can instantly access via visiting Starway.monster web page coupled with an ability to make real IBC transfers (i.e. musslenet-4 – swap-testnet-2001). Once you have a long denomtrace (i.e. wrapped[wrapped[wrapped…(native token)]] ) or like an onion with many layers, it is important to find a way back to the token native zone from the sink zone and be assured that your IBC transfer will be executed.
What we learned:
- We familiarized with how to integrate your wallet with the logic of IBC transfers;
- We identified a solution how to find an optimal pathway for your token transfers;
- We familiarized with the Starport and understand how to quickly test various ideas by easy and fast blockchain launch and development;
- We familiarized with how to test blockchain and analyze its performance.
What's next for Starway Monster:
Irrespective of the results of the Hackathon, we believe the solution/part of it may find its place in the Cosmos Network ecosystem and will serve its users’ needs based on Web3 fundamental principles along with an increased transparency, effectiveness and user-friendliness. We plan to work on it further on and looking forward to IBC protocol further upgrades and a wider adoption by the ecosystem players.