{"id":125235,"date":"2025-03-17T15:15:37","date_gmt":"2025-03-17T15:15:37","guid":{"rendered":"http:\/\/cryptospotters.net\/?p=125235"},"modified":"2025-03-17T15:15:37","modified_gmt":"2025-03-17T15:15:37","slug":"move-is-now-primed-to-grow-defi","status":"publish","type":"post","link":"http:\/\/cryptospotters.net\/?p=125235","title":{"rendered":"Move is now primed to grow DeFi"},"content":{"rendered":"

Source: Cointelegraph.com NewsOpinion by: Alex Nguyen, CEO at VibrantX
\nThe Move programming language\u2019s origin is not super cypherpunk. Facebook (now Meta) created Move after the Libra\/Diem team compared major smart contract languages (Bitcoin Script, Ethereum Virtual Machine bytecode languages) and decided their formidable in-house tech talent could make a new language built on years of private and public sector research.
\nThe original team, including founders Mo Shaikh, Avery Ching, and their engineering team, left Facebook to continue as a fully independent, open-source project headed up by Aptos Labs and supported by the Aptos Foundation.
\nImportantly, Meta\u2019s failed Libra experiment left us with a programming language specifically designed for crypto finance. Move on Aptos is now open-source, and the Aptos Foundation is a commercially driven organization that welcomes builders from all backgrounds.
\nMove is now the best programming language for verifying the absence of bugs and checking for modifications and leaks, which is how most blockchains get hacked.
\nThis verification relies on two key features of Move on Aptos: (1) \u201cbackward compatibility\u201d and (2) the concept of an \u201cauditor at runtime.\u201d
\nBackward compatibility means future-proofing
\nMove on Aptos is fast and cheap, creating a competitive user experience, especially for decentralized finance (DeFi) applications. Aptos aims for a high transaction throughput, with theoretical capabilities reaching up to 160,000 transactions per second (TPS) through its parallel execution engine, Block-STM.
\nAptos\u2019 sub-second finality means transactions are confirmed quickly, enhancing the user experience in time-sensitive applications.
\nTo be fair, other chains also have these qualities. Move on Aptos is, however, designed to be \u201cbackward-compatible.\u201d\u00a0
\nFuture upgrades won\u2019t disrupt existing projects. This helps developers feel more confident building long-term solutions without worrying about things breaking because of a Move upgrade.\u00a0
\nMove smart contracts are designed to be upgradeable without affecting the user experience, which is essential for mainstream adoption. This enables teams to implement bug fixes and new features with zero disruption.\u00a0
\nRecent: Crypto startups can\u2019t just rely on solid tech to win VC funding: OKX
\nSmart contract flexibility through Move on Aptos\u2019 specific security features results in better and faster product shipping. Being more flexible, Move on Aptos can quickly adapt to support new ecosystems.
\n\u201cBytecode\u201d verification prevents leaks
\nSolidity contract hacks have been prevalent over the years. When building Web3 technology for markets worth billions or even trillions of dollars, it\u2019s crucial to have a security system that will protect projects from resource leaks, invalid memory access and other unauthorized modifications.\u00a0
\nAs it was initially developed for Meta\u2019s Diem project, Move is designed for safety, resource management and performance, making it attractive for developers looking for a secure yet robust language for smart contracts.
\nWhen deploying code using Move, the code will be verified across several crucial coding conditions like proper resource management, type correctness and reference safety. No matter what happens to the code, it will be verified first to prevent any faulty or malicious smart contracts from running.\u00a0
\nThis is the power of Move\u2019s built-in bytecode verification.
\nReal-time verification of the absence of bugs
\nRenowned computer science pioneer Edsger Dijkstra noted, \u201cProgram testing can be used to show the presence of bugs, but never to show their absence!\u201d\u00a0
\nMove\u2019s formal verification capabilities let developers actually prove that there are no bugs in specific code according to preset specifications.\u00a0
\nMoveVM is less battle-tested than Ethereum\u2019s virtual machine, but as Rushi Manche, founder of Movement Labs, has explained, Move requires much less code auditing. The MoveVM runtime can act as an \u201cauditor at runtime.\u201d
\nThe verifier inside the MoveVM ensures that the transaction code is not harmful and that it cannot create, duplicate or destroy resources not allowed by the signer(s) of the transaction. In other words, MoveVM is an \u201cauditor at runtime\u201d rather than a human smart contract auditor.\u00a0
\nToday, Move on Aptos is more than just a smart contract language. Move on Aptos is the longest-standing, most recognized and widely used version of Move, boasting one of the fastest-growing developer communities and a rapidly growing ecosystem of infrastructure, tooling and projects.
\nQuickly verifying code before deployment created the conditions for the Move on Aptos ecosystem. From a flawed Web2 beginning, Move is now primed to grow DeFi.
\nOpinion by: Alex Nguyen, CEO at VibrantX.
\nThis article is for general information purposes and is not intended to be and should not be taken as legal or investment advice. The views, thoughts, and opinions expressed here are the author\u2019s alone and do not necessarily reflect or represent the views and opinions of Cointelegraph.Read More<\/a><\/p>","protected":false},"excerpt":{"rendered":"

Source: Cointelegraph.com NewsOpinion by: Alex Nguyen, CEO at VibrantX The Move programming language\u2019s origin is not super cypherpunk. Facebook (now Meta) created Move after the Libra\/Diem team compared major smart… <\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5],"tags":[],"_links":{"self":[{"href":"http:\/\/cryptospotters.net\/index.php?rest_route=\/wp\/v2\/posts\/125235"}],"collection":[{"href":"http:\/\/cryptospotters.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/cryptospotters.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"http:\/\/cryptospotters.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=125235"}],"version-history":[{"count":0,"href":"http:\/\/cryptospotters.net\/index.php?rest_route=\/wp\/v2\/posts\/125235\/revisions"}],"wp:attachment":[{"href":"http:\/\/cryptospotters.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=125235"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/cryptospotters.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=125235"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/cryptospotters.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=125235"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}