Why DeepMove

The Problems

Building Move applications is hard. Developers need to deal with lots of problems besides of learning move language.

• when run sui move build, everytime the move compiler will try to pull sui-framework repos from remote git urls, however the repo may be quite big and in windows os this process may be stucked up for quite a while

Deepmove solves it by making the remote move deps into local deps, therefor there will only one time pull request from remote git repos, moreover deepmove use git sparsecheckout, so it will only checkout the sui-framework directory instead of the whole sui repos

• when publish and upgrade move packages in sui cli, you will do a lot of things, you first need to setup sui cli wallet for publish and get enough sui coins and switch to the right network env, after you publish your package, you want to upgrade it, you must first remember the move package objectid onchain, and then you can pass it to the upgrade commands. Moreover, when you published in testnet env, and you want to publish in mainnet env, you must do the above things again

Deepmove solves these progresses all in simple commands, you setup your SUI_PRIVATE_KEY in .env file, and get sui coins in your favouite wallet, then you can just go publish and upgrade using the following commands

publish testnet
publish mainnet
upgrade testnet
upgrade mainnet

• when you develop dapp in typescript language, and you have your move contract defined with complexed Move Structs, therefor you must deal with bcs serialization schema definitions in typescript, it is all need manual coded, and it is not quite easy for developers newer to move languages

Deepmove solves it by deepauto framework, with wasm based move bcs analysis, it will transalte Move Structs、Move Functions into typescript class、typescript functions, developers can use these bindings directly

Developer Experience

Deepmove allowing dapp developers to focus on building high-quality and performant experiences for Move based blockchains — by focusing on developer experience, performance, feature coverage, and stability.

Feature Coverage

Deepmove wasm vm runtime not only support move_stdlib_natives, it also support sui_framework_natives and the crypto natives are all well tested in wasm vm runtime