SUI – Unsafe Methods Not Supported

Sui RPC methods prefixed with unsafe_ (such as unsafe_paySui, unsafe_payAllSui, unsafe_moveCall, unsafe_publish) are not supported on Tatum nodes.

The unsafe_ methods are scheduled for deprecation by the Sui team.

Why are these methods “unsafe”?

The unsafe_ namespace was originally intended for low-level experimentation and advanced testing. These methods bypass safety checks and abstractions, meaning developers take full responsibility for correctness and risks.

Because of the risks, and the fact that the Sui core team plans to remove them, Tatum will not whitelist or support unsafe_ RPC methods.

Recommended Alternatives

Instead of relying on unsafe_ methods, use the supported Programmable Transaction Builder functions.

For example:

• Replace unsafe_paySui / unsafe_payAllSui → use pay_sui
  • This function allows you to send SUI tokens to one or more recipients while explicitly specifying amounts.
  • It operates within the safe transaction flow and is maintained by the Sui core team.

Reference implementations:

• pay_sui.rs (source)
• pay_sui unit tests
• Sui developer guide: sign and send a transaction

Key Takeaways

• unsafe_ methods are not available in Tatum’s Sui RPC nodes.
• They are planned for deprecation upstream and should not be relied upon.
• Use the ProgrammableTransactionBuilder API (pay_sui, moveCall, etc.) for all supported transaction flows.