A Study on Shared Objects in Sui Smart Contracts

TL;DR

This paper investigates the usage patterns and contention levels of shared objects in Sui smart contracts, providing insights into their impact on transaction efficiency and application design.

Contribution

It offers the first detailed analysis of shared object usage in Sui, highlighting low contention and moderate dependencies, aiding platform optimization.

Findings

Shared objects are extensively used in Sui smart contracts.

Contention levels for shared objects are generally low.

Most applications show moderate dependency on shared objects.

Abstract

In many smart contract architectures, every contract or object is mutably shared by default. The Sui smart contract platform bears the unique feature of distinguishing between shared and owned objects. While transactions operating on shared objects require consensus to sequence reads and writes, those involving only owned objects are independent and may bypass consensus; thus, the latter are less prone to this throughput bottleneck. However, it may not always be possible or desirable to avoid using shared objects. This article aims at identifying and investigating decentralized applications that require shared objects. Utilizing the Sui Rust SDK to query programmable transaction blocks, we analyze the frequency of transactions involving shared objects, shared resource contention levels, and most "popular" applications that contain shared objects. The presented results are reproducible and show the extensive usage of shared objects in Sui, low contention levels, and moderate dependency among shared objects in atomic transactions. This novel study of shared object use cases in a relatively new smart contract platform is important for improving the efficiency of such object-based architectures. This work is relevant for smart contract platform designers and smart contract developers.