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

Medium Risk
Touches Initia deployment/address derivation and token-decimals initialization paths; incorrect derivation or decimals could break deployments or produce wrong transfer scaling, though changes are localized to tooling/examples/tests.

Overview
Updates Initia Move tooling to no longer enforce specific initiad versions, bumps @initia/initia.js to ^1.0.0, and changes Initia deployments to derive the correct deployer/object address via RPC/CLI queries (new getInitiaDeployCount test added).

Extends FA adapter initialization to accept an optional localDecimals (Move initialize now takes Option<u8>; SDK payload builders updated accordingly), and updates Initia example configs/docs (adds localDecimals: 6, fixes deploy script name, adds --native-token send flag handling, tweaks network defaults/confirmations, and includes deployments/ in .gitignore).

Hyperliquid example/docs are refreshed (rename FeeAbstraction to PreFundedFeeAbstraction, natspec tweaks, dependency bump), and Solana wiring now warns when the signing authority (incl. Squads vault) doesn’t match the OFT admin/delegate (adds @sqds/multisig).

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

[cursor]

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

[nazreen]

@beer-1 , can you confirm what the main blocker that this PR is meant to solve?

I might ask you to separate out the client only changes, as the contract changes might take longer to approve.

[beer-1]

Hey @nazreen,

There are three points

• Use latest initia.js to use coin type 60 instead of 118
• Allow to set local decimals when you create OFTAdapter on initia because IBC tokens do not have decimals information, so it will be created with 0 decimals always.
• In object code deployment, we have added some interface and address computation method. so in current version of cli, we cannot deploy move contract without this fixes.

We already deployed the contract with this fixes locally, but good to merge this for future usages.

[nazreen]

@beer-1 what's the significance of the value 2 here?

[beer-1]

same reason with this https://github.com/initia-labs/initia/blob/0621b9de571ffde395da7671ad261cf1b4e32557/cmd/move/deploy.go#L110

so sequence number will be increased during this deployment tx.

and in contract we are using sequence+1 as object seed here