feat: use latest initiad & initia.js

[beer-1]

Summary of Changes

• Allow usage with the latest Initiad release
• Update dependency to the latest initia.js
• Fix to correctly pass local decimal values when creating MoveOFTAdapter on Initia
  • In many cases, tokens on Initia have 0 decimals because the IBC transfer module does not support transmitting decimal metadata

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​rimraf@​6.0.1 ⏵ 6.1.0	+1			+4

View full report

[cursor]

PR Summary

Updates Initia support and OFT adapter initialization across contracts, SDK, CLI, and examples.

• Move contract: oft_adapter_fa::initialize now accepts local_decimals: Option<u8> and defaults to metadata decimals when not provided
• SDK/CLI: initializeAdapterFAPayload updated (Aptos/Initia clients) to pass localDecimals; new OFTAdapterFaInitParams.localDecimals; init task prints and forwards shared/local decimals; removed Initiad version gating in build/deploy
• Examples: README/scripts use deploy-move/OFTAdapterInitParams.ts with localDecimals; send command flags cleaned; EVM deploy adds gasLimit; .gitignore includes deployments
• Configs: Switch example EVM network to bsc-testnet; adjust ULN confirmations and enforced gas; update omni-graph libraries/addresses
• Deps/lockfile: Bump @initia/initia.js to ^1.0.0 in devtools-move and refresh transitive packages

^{Written by Cursor Bugbot for commit 19754b9. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

[cursor]

Multi-sig args incorrectly handle undefined localDecimals as zero

Medium Severity

The multiSigArgs for initializeAdapterFAPayload uses localDecimals || 0, which converts undefined to 0. This loses the semantic distinction between "not specified" (should be Option::None, meaning use default decimals from metadata) and "explicitly 0 decimals" (should be Option::Some(0)). When multi-sig users export and reconstruct transactions, this causes incorrect behavior where the contract uses 0 decimals instead of the token's metadata decimals.

 

[cursor]

Aptos SDK passes three arguments to two-parameter contract function

High Severity

The initializeAdapterFAPayload function in aptosOFT.ts and oft.ts now passes three arguments (tokenMetadataAddress, sharedDecimals, localDecimals || 0) to the contract's oft_adapter_fa::initialize function. However, the Aptos contract at examples/oft-adapter-aptos-move only accepts two parameters (token_metadata_address: address, shared_decimals: u8). This parameter count mismatch will cause all Aptos OFT adapter initialization transactions to fail at runtime.

Additional Locations (1)

• packages/devtools-move/sdk/oft.ts#L76-L81