yup Bitcoin's UTXO model is fundamentally different, gasless doesn't apply there the same way. To clarify what the Starkzap SDK actually does: it operates on Starknet, which is an account-based L2 that settles on Ethereum. Bitcoin assets on Starknet are bridged representations, not native UTXOs (although Starknet will soon have a trust-minimized bridge with Bitcoin thanks to Alpen, removing trust assumptions)
So when we say gasless, we mean the Starknet transaction fees are sponsored via a paymaster. The user doesn't need to hold STRK or ETH to transact. The cost is covered by the app or a paymaster service like AVNU (just like Amazon covers shipping costs). That's a design choice the app builder makes depending on their business model. On the stablecoin side: any stablecoin deployed on Starknet works with the SDK, and the paymaster covers the transaction fees if configured. The technical execution is what matters, and that's what the SDK focuses on. The code is open-source if you want to see how it's handled under the hood.
it really depends on what you're building, but when I tested it out I had a simple webapp that tracks how often I blink, and it took me 30min to everything live and deployed on Starknet.
It actually works with any asset that is listed onchain. So tokens such as ETH and others also work. As long as the token is live on the Starknet network, it can be used. I think the cool thing is that some tokens have interesting yield strategies, so you can cherry-pick the strategies you like the most and want to add to your app.
yep, noticed many web2/SaaS devs struggle with blockchain integrations. So it's in Typescript to make it easy to ship. In theory, you can cherry-pick the blockchain features you need for your app (e.g., you're a tradFi stock exchange app and want to add perpetual contracts for index and tradFi assets, so you select the 'perps' module in the SDK) and you don't have to re-design or architect yourself smart-contracts
High-level architecture:
Accounts are smart contract wallets on Starknet
Fees are covered via a paymaster contract
It's meant for any builder, you don't have to be a blockchain expert to build with it.
Transactions are batched and submitted atomically, so you keep the UX of your existing app.