Deploying Smart Contracts on Sui: From Writing to Launch

Deploying Smart Contracts on Sui: From Writing to Launch

We have been deploying smart contracts on Sui since mainnet launch — over 50 packages on various networks so far. Our experience: 10+ years in blockchain development, including Ethereum, Solana, and Sui. This guide covers how to migrate a dApp from EVM to Move, avoid common pitfalls, and launch a contract on mainnet.

Sui uses Move — a language developed at Facebook for Diem. Official Sui documentation: Move is a safe language for smart contracts. The key difference from Solidity: resources (objects) cannot be copied or accidentally destroyed — this is guaranteed by the type system at the compiler level. If you are used to EVM, the first days will be uncomfortable: forget about mappings address => uint256, here everything is built around objects with explicit owners.

Thanks to gas optimization, you can save up to 30% on fees, and a typical project pays for itself in 2 months.

Why is Move safer than Solidity?

In Solidity, vulnerabilities like reentrancy, incorrect address verification, or overflow are common headaches. Move solves this at the language level: objects cannot be copied (no dup), each object has a unique ID and owner. Even if a developer wants to write vulnerable code, the compiler will not allow it — for example, you cannot accidentally transfer an object to the wrong address without an explicit transfer::transfer call. This reduces the need for expensive audits, but does not eliminate them entirely.

Sui object model

In Sui, there is no global state in the classical sense. Everything is objects. Each object has a unique ID, version, and owner:

• Owned objects — belong to a specific address, only that address can use them in transactions
• Shared objects — accessible to everyone, but create contention and require consensus (slower)
• Immutable objects — frozen forever, accessible to everyone for reading

This is important when architecting: if your contract requires shared state (like an AMM with a common liquidity pool) — shared objects are inevitable and transactions go through consensus. If state can be split per user — use owned objects and get parallel processing without consensus.

Comparison of object types:

What difficulties arise when migrating from EVM to Move?

First — abandoning mappings. Instead of mapping(address => uint256), you need to design objects with explicit owners. Second — understanding the init function: it is called once during deployment, analogous to a constructor. Third — getting used to the Capability pattern instead of msg.sender. Fourth — gas: Sui has no gas oracle, cost depends on object types (owned cheaper than shared). Fifth — debugging complexity: the local test framework is good, but production logging requires Tenderly-like solutions (Sui has Sui Explorer, but not as deep).

Tooling and project structure

Step-by-step guide to get started:

1. Install Sui CLI from the official repository:

cargo install --locked --git https://github.com/MystenLabs/sui.git --branch mainnet sui

2. Create a new package and write code:

sui move new my_package
sui move build
sui move test

The package structure includes Move.toml with dependency and address settings, modules in sources/, and tests in tests/.

Example Move.toml:

[package]
name = "my_package"
version = "0.0.1"
edition = "2024.beta"

[dependencies]
Sui = { git = "https://github.com/MystenLabs/sui.git", subdir = "crates/sui-framework/packages/sui-framework", rev = "mainnet" }

[addresses]
my_package = "0x0"

Capability pattern — access control

In Move, there is no msg.sender like in Solidity. Permissions are passed through capability objects:

module my_package::admin {
    use sui::object::{Self, UID};
    use sui::tx_context::TxContext;

    /// Admin capability — whoever holds the object is admin
    public struct AdminCap has key, store {
        id: UID,
    }

    fun init(ctx: &mut TxContext) {
        transfer::transfer(AdminCap { id: object::new(ctx) }, tx_context::sender(ctx))
    }

    /// Only the holder of AdminCap can call
    public fun privileged_action(_cap: &AdminCap, /* ... */) {
        // logic
    }
}

The init function is the entry point during deployment, analogous to a constructor. It is called automatically once.

Deploying a package

# Standard deployment or with offline signing
sui client publish --gas-budget 100000000 --json
sui client publish --gas-budget 100000000 --serialize-unsigned-transaction | sui keytool sign --address <ADDRESS> --data -

After deployment, you get a packageId — the immutable address of the package. In transactions, you reference functions as <packageId>::<module>::<function>.

Upgradability

Sui supports package upgrades, but with restrictions. Upgrades are controlled via the UpgradeCap object. Command:

sui client upgrade --upgrade-capability <UPGRADE_CAP_ID> --gas-budget 100000000

Upgrade policies:

For production: transfer UpgradeCap to a timelock contract or multisig (Sui supports multisig via the MultiSig scheme). If no updates are planned, make UpgradeCap immutable via package::make_immutable.

Testing and inspection

Move has a built-in test framework that allows writing unit tests with transaction simulation. After deployment, verify objects through the blockchain explorer.

What our work on deploying smart contracts on Sui includes

We cover the full cycle: from auditing your code to deployment with monitoring.

• Audit and refactoring — checking for typical Move vulnerabilities, gas optimization
• CI/CD setup — automatic build, testing, and deployment via GitHub Actions
• Multisig integration — configuring UpgradeCap management via multisig or timelock
• Documentation — describing all functions, events, and objects
• Technical support — assistance in the first weeks after deployment

Evaluate your project — write to us. Order turnkey deployment and get a consultation from an engineer.

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.