Welcome to the weekly update on new software design from the Paloma community of developers.
REMINDER WARNING:
The Hatchling Paloma Network of “Messenger” (v1.12.2) and the Pigeon relay module are on v1.10.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
messenger
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 “Messenger” to experience weekly chain halts and chain restarts for upgrades. We also expect numerous undiscovered 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.
During recent Palomabot transaction monitoring the Volume team has identified that not all Pigeons supply attestation to a message, which can lead to missing evidence to form consensus, and relayed messages not being acknowledged on Paloma, leading to state desync of systems. In those cases, message are actually being relayed, but since they are not acknowledged on Paloma, might be relayed over and over again. Paloma already has safeguards for enforcing relaying, and will introduce enforcement of attestation next.
The Volume team does not want to slow down Paloma to accommodate failing attestation of pigeons on target chains. Rather, the team wants to provide pigeons with logging on attestation performance and also jail pigeons on failed attestation within the required time frame so that all pigeons are incentivized that their RPC endpoints and nodes are performing as required.
To prevent non-performing pigeons from slowing down the attestation of executed relays and valset updates, the proposed solution adds additional information and UI/UX enhancements for validators to understand how their validators participate in message attestation and building consensus. The proposed paloma upgrade will include logging of failed attestation for Paloma pigeon validators to understand that their validator is not attesting. Validators that fail to attest will be jailed and logging will include the attestation jailing reason and the target chain affected.
The Vitwit team continues integration testing Cosmos SDK 0.5.0 with the upgraded Paloma and Pigeon binaries on a three-node private testnet. This end-to-end testing covers all Paloma and Pigeon code, relaying messages on EVM chains, deploying remote contracts, and migrations. The team is running multiple test cases simultaneously and making great progress. As expected some bugs have been found and fixed already and the team will continue until all test cases are covered.
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:
AI-generated RED Pigeon waiting to lever up as the market continues to retrace. Start your bot today at
Welcome to Paloma message attestation enforcement and Cosmos SDK 0.50.0 integration testing. A new Paloma is ready to spread wings and a new fee market for validators, not yet seen in the Cosmos. We look forward to sharing the progress of testing the new Paloma as we prepare for public testnest and mainnest.
We continue to fly with the flock! COO! COO!
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: