Last updated: 11/29/2022 Next update: on or about 12/29/2022
To keep Sui builders up-to-date with the latest happenings, we provide the following list of developer-facing changes planned in the next ~30 days. While we strive to be accurate, the timing to release the planned features is subject to change. We provide more thorough documentation and references for each feature release to Sui Devnet. Please continue to monitor Devnet release notes as the source of truth for features deployed to Devnet. This document informs you about the currently planned upcoming changes to Sui.
- We plan to add the ability for developers to depend on packages from third-party package managers. More information in the following sections.
- We continue to make stability and performance improvements to our JSON RPC APIs.
- We intend to introduce signing support soon.
- Remove the requirement for a user signature from
sui_dryRunTransaction
. Breaking Change. - Add RPC support for Dynamic Fields. Issue.
- Fold
getRawObject
method intogetObject
method, and use theDataEncoding
argument to choose between parsedJSON and BCS encoding types. - Add new
getCoin
andgetBalance
methods. - Standardize the return type of
u64
,u128
, andu256
values tostring
. - Replace the
get_object_owned_by_object
method with theget_dynamic_fields
method. - Add the
object_type
field toTransactionEffect
responses. - Add the object version and digest field to
Publish
events schema. - Remove the
merge_coin
,split_coin_equal
, andsplit_coin
RPC endpoints. - Event API: Support using AND/OR operators to combine query criteria.
- Introduce intent signing support. This includes an
intent
struct to serialize and sign in addition to the transaction data. Issue. - Add support to compute transaction digest.
- Improve source discoverability.
- Add the ability for developers to verify source code dependencies against their on-chain counterparts when publishing packages.
- Enable third-party package managers like Movey to resolve dependencies in Sui Move packages. This enables library developers to distribute their packages under easy-to-identify names. This also removes the error-prone need for developers to remember the GitHub repository, revision, and subdirectories for all their dependencies.
- Better debug printing for structs (including field names + nice formatting).
- Improve error messaging.