Deploying Move Modules on Aptos: Turnkey Smart Contract Deployment

You spent weeks writing Move modules for a DeFi protocol on Aptos, but at deploy you got a type compatibility error. Or you forgot to replace an address placeholder — the contract went to mainnet with the wrong owner. Such mistakes are costly: gas savings after optimizing Move code reach 30%, and reentrancy attacks, which account for 15% of EVM hacks, are semantically impossible in Move. We are a team of blockchain engineers with 7 years of experience, having deployed 40+ contracts on Aptos, and we know how to avoid these pitfalls.

Main Problems When Deploying Move Modules

The first problem is resource type safety. In Move, a resource cannot be copied or destroyed by mistake, but this imposes design constraints. In Solidity, balances are stored in mappings. In Move, you need to rethink the architecture. The second problem is upgrade policy. Many choose compatible by default without understanding its limitations. If you need to change a function signature — only immutable or redeploy with migration. The third problem is address management. Named addresses in Move.toml must be fixed before deployment. An address error is one of the most common causes of failures (about 30% of cases).

A typical case: a client accidentally deleted a field from a resource in a new module. The publication went through, but old data became inaccessible. We had to deploy a new module and migrate the state. To avoid this, use aptos move compatibility-check.

How to Deploy a Move Module on Aptos?

A typical Move module looks like this:

module my_addr::token {
    use std::signer;

    struct CoinStore has key {
        balance: u64,
    }

    public fun initialize(account: &signer) {
        move_to(account, CoinStore { balance: 0 });
    }

    public fun deposit(account: &signer, amount: u64) acquires CoinStore {
        let store = borrow_global_mut<CoinStore>(signer::address_of(account));
        store.balance = store.balance + amount;
    }
}

After writing the code, use the Aptos CLI. Initialize the account and publish:

aptos init --network mainnet --profile prod
aptos move publish \
  --package-dir . \
  --named-addresses protocol=0xPROTOCOL \
  --profile prod

It is important to pin the rev of dependencies in Move.toml for reproducibility:

[package]
name = "MyProtocol"
version = "1.0.0"
upgrade_policy = "compatible"

[addresses]
protocol = "_"

[dependencies.AptosFramework]
git = "https://github.com/aptos-labs/aptos-core.git"
rev = "mainnet"
subdir = "aptos-move/framework/aptos-framework"

Comparison of Compatible and Immutable Upgrade Policies

compatible offers flexibility but requires discipline: you cannot delete a field from a resource. immutable is a bulletproof guarantee, but at the cost of being unable to fix bugs.

Move vs Solidity: Which Is Safer?

Move delivers gas savings of up to 30% and eliminates an entire class of vulnerabilities. After deploying five of our modules on Aptos mainnet, not a single incident has been recorded.

Why Use Move for DeFi?

Move is designed for asset safety. In Solidity, a calculation error can lead to the loss of an entire pool. In Move, resources are protected at the language level. For example, a flash loan attack is impossible in Move because a resource cannot be temporarily borrowed without preservation. Additionally, transaction cost on Aptos is roughly 10 times lower than on Ethereum, thanks to batch transaction processing.

How to Set Up CI/CD for Deployment?

For automation use GitHub Actions: install aptos CLI, compile, test, publish to testnet, manual trigger for mainnet. The workflow includes a compatibility check before upgrade. This reduces the risk of human error.

What the Deployment Work Includes

• Security audit of Move module (static analysis via Slither for Move)
• Writing unit tests and Prover specifications (modules must pass formal verification)
• Configuration of Move.toml: dependencies, named addresses, upgrade policy
• Publishing the module and verification on explorer
• Setting up a multisig for the deployer account (Aptos native multisig)
• Documentation for function calls and integration

Timelines — from 2 to 7 working days depending on module complexity. The cost is calculated individually — contact us for a project assessment.

Work Process: From Audit to Deployment

1. Analysis: we study your project, contract specification, identify potential issues.
2. Design: architecture of Move modules, upgrade policy selection, CI/CD setup.
3. Development: we write modules, tests, Prover specifications (if needed).
4. Testing: unit, integration, fuzzing (Echidna for Move).
5. Deployment: publish to testnet, then mainnet with multisig.
6. Post-deployment: verification, monitoring, documentation.

Order Deployment with Security Guarantee

Our team has 7+ years of experience in blockchain development and 40+ successful deployments on Aptos. Get a free consultation — we will assess your project and propose the optimal solution. Contact us through our website.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.