An AI bot to participate in DeFi on StarkNet with txn simulation, DEX integrations, token gating, and more
Prize Pool
Prize Pool
Transacting in crypto is hard - gas fees, block explorers, swap routes, slippage, and more cause too much technical jargon. We see AI x Crypto as an intersection that can make this much simpler. StarkBot is an AI powered DeFi chatbot that takes a first step towards solving these problems and making crypto more accessible to everyone by enabling an easy to use approach to being onchain.
Fetch token balances of connected wallet
Transfer tokens
Swap tokens
STRKBOT
token which is used to pay fees for the botNOTE: If testing during judging, you will need
STRKBOT
token for executing swaps. You can mint STRKBOT token for free for now by calling themint
function on the contract here - https://sepolia.voyager.online/contract/0x05ab9c6b81f1d1a7aac290940584a9d26c49ac1014097ef3bf11710445ebf285#writeContract
We faced a few challenges/issues while building this project.
swap
function.starknet.js
are not the same as Nethermind's RPC request/response types for simulateTransactions
. This caused us a lot of trouble and at the end we were unable to get simulation working properly as by the time we figured out the differences it was a bit late.One thing we really wanted to add was transaction simulation through Nethermind for both past transactions and also transactions that the user is about to make.
We got past transaction simulation working, see lib/starknet/nethermind.ts
for that. But, pending transaction simulation did not work due to some weird incompatibilities we could not understand.
Using Argent X wallet, the actual calldata sent onchain is different from what we get when using starknet.js' buildInvocation
or transaction.getExecuteCalldata
for some reason - which keeps throwing simulation errors then because theres 3-4 additional calldata arguments than what gets sent onchain. We could not determine the root cause of this after hours of trying to fix it.
We spent too much time on trying to figure this out, and at the end did not have enough time left to finist the UI and summarization aspect of even past transaction simulations - so simulation is no longer a feature we support at the time of submission.