The problem Hamster solves

The development process of a web3.0 project is still complicated nowadays which needs to be optimized and automated. This invisibly blocks many developers from entering the StarkNet space. To empower more developers to realize their web3.0 dreams, Hamster provides the one-stop infrastructure, developer toolkit framework in web3.0. It enables developers/teams to achieve a cost-effective and automatic development as well as O&M processes, including contract template, code/contract check, deployment, node service, CI/CD and more, empowering projects in StarkNet to improve their coding and delivery speed, quality and efficiency, as well as product reliability & safety.

With Hamster:

• It lowers the development threshold for all projects developing within StarkNet ecosystem
• Code/Contract security and quality are highly ensured, avoiding potential security risks and financial losses
• DApps run at full speed and update iteratively through DevOps using automation technology
• ~35% cost and 40% time of development are saved with support of Hamster

Hamster is applying the infrastructure track of the network state virtual hackathon.

Challenges we ran into

Since the complete dev. process of a Web3.0 project is relatively long and lots of tiny points to be optimized. There are many things to consider when designing the product. Our core dev team has over 25 years of experience in the corresponding field, which backed up the Hamster’s product.

The starknet iteration is relatively intense, and some documents and cases cannot keep up with the iteration speed, so it takes some time to learn and verify.
It is difficult to use the starknit wallet for declare transaction（ https://github.com/argentlabs/argent-x/issues/1735 ）, not yet resolved
The starknet contract declaration requires complete compiled files, not ABI..This file is relatively large and difficult to store and use. And the compiled file cannot generate classHash. We use starkli to calculate classHash