Welcome to the weekly update on new software design from the Paloma developer community.
REMINDER WARNING:
The New Hatchling Paloma Network of
tumbler
(v1.15.3) and the Pigeon relay module are on v1.12.3 Paloma is just over one year old and its Cosmwasm and EVM contracts are still unaudited and undergoing continuous upgrades on the protocol and its smart contracts. The GRAIN token is available on the Paloma mainnet but is not yet trading on exchanges. Although the flock is flying on the
tumbler
mainnet, it is still subject to the continued development of Paloma’s cross-chain messaging system and the security guarantees offered by the GRAIN token. We expect
tumbler
to experience weekly chain halts and chain restarts for upgrades. We also expect numerous undiscovered bugs and vulnerabilities. No one on this project controls or influences the price of GRAINs. The community will strive to preserve the mainnet state, which includes balances, but considers this mainnet high-risk. Proceed with caution.
The original parameters from Gravity are superseded by Skyway’s module storage on multiple remote chains instead of one target EVM chain. This feature will enable users to send multiple tokens across the Paloma bridge to multiple chains in one transaction, and Paloma will enable developers to execute multiple bridge transactions across multiple chains with one transaction.
We have implemented ERC-20 bridge transfer retry limits on Paloma. If, after three attempts, the transfer fails, Paloma will stop retries. This change will make sure that ERC20 transfers are being retried continuously instead of stopping after two retries to try and attempt to prevent a deadlock. There might still be a need for a manual unlock down the road. Additionally, we will stop processing Skyway bridge messages when we have an ongoing contract deployment. This will remove the risk of desynchronization of the nonces on the old and new compass-evm light client.
Paloma
tubmlr
network halted at block height
20200073
. The vote to deploy GRAINs denom to Arbitrum’s L2 was the critical event that occurred just before the chain halt’s block. The initial investigation focused on the recent renaming of the Gravity module to Skyway. All test paths in Private Testnet (including a full version update) ran successfully. Furthermore, the denom was identified to be in the store and queriable. Nodes had the record in the store, as well as the params. As such, the mismatch did not appear to be related to the store or the upgrade. It seems that the root hash of the store for the module was different, leading to AppHash errors.
Research in the Cosmos forums revealed similar issues around chain halts due to root store differences. The Cosmos team recommended that projects upgrade to IAVL 1.1.4. Paloma’s versions were no longer recommended. All Cosmos chains will need to upgrade to this new version of IAVL.
Stay up to date and follow the Paloma public repositories and the commits of ongoing upgrades to the Paloma Cosmos-SDK blockchain and the Pigeon relay module here:
Lahore is a breed of fancy pigeon known for its impressive size and gentle nature. Like other varieties of domesticated pigeons, Lahores are descendants of the rock pigeon.
Source:
This week, work on Pigeon Feed Phase II was completed. Work now begins on Pigeon Feed Phase III. This includes upgrading the Compass-EVM, Paloma, and Pigeon for recording fee rewards for validators.
To learn more about Paloma, please visit
To follow the project on Github, please star the project:
To participate in the community, please join the Paloma Discord: