Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
SHIB Shibarium deploys nine Safe v1.4.1 contracts to expand its multi-sign wallet and programmable smart account infrastructure
Shibarium has deployed nine Safe v1.4.1 contracts to provide developers, protocols, and community-managed projects with a more powerful multi-sign wallet and programmable smart account infrastructure. The Canonical (standard) contract address ensures consistency across the network, while a verified code hash confirms that the deployment on Shibarium exactly matches Safe's officially published warehouse records.
Improve security and development efficiency
According to Mazrael, a member of the Shiba Inu community, all contracts are online and verified through the Shibariumscan browser. He also confirmed that contributors had submitted Pull Request No. 1666 from Safe-deployments to register Shibarium's latest Safe deployment information.
Safe supports the smart account feature, which requires approval from multiple authorized signers before completing a transaction. This mechanism allows the project party to manage the treasury without having to grant full control of the agreed funds to a single wallet holder. This structure not only reduces the risk of private key disclosure, but also enhances the regulatory capabilities of decentralized teams and community management applications. In addition, developers can directly integrate mature wallet tools without having to independently build complex multi-signature systems, thereby significantly reducing development costs.
Cross-network compatibility and technical details
These nine contracts are all deployed on the Shibarium main network through Safe Singleton Factory, using Shibarium's chain identifier 109, and adopting a Canonical address common to all supporting blockchain networks. It is worth noting that the address of SafeProxyFactory is consistent with addresses used on other Canonical chains. This feature allows Safe accounts created on Shibarium to share addresses with corresponding accounts on compatible networks, greatly improving cross-network compatibility.
Previously, Shibarium registered Safe v1.3.0 through the eip155 deployment collection, but the old factory could not provide the cross-network address consistency benefits of the new Canonical deployment. Currently, the address of each deployment matches the Canonical records published in the Safe repository, and the keccak256 hash value generated by the runtime code of each contract is also exactly the same as the Canonical code hash published by Safe. These verification steps ensure that contracts on Shibarium contain the expected code and occupy approved addresses.
Review process and network status updates
Safe reviews Canonical deployment registration applications every two weeks and usually packages the new content it accepts into a monthly release. Therefore, Pull Request No. 1666 still needs to wait for the completion of the standard review process established by Safe before it can be officially included in the warehouse.
Mazrael denied claims that Shibarium activities had decreased, pointing out that the community was still undergoing ongoing maintenance work and infrastructure relocation. Currently, Shibariumscan is undergoing a reset and has indexed approximately 50% of network blocks. On August 11, as operators adjusted their systems after service outages, the browser backend switched to Cloudflare service. Although incomplete indexes may temporarily restrict access to historical records, the underlying network is still functioning normally.
