v2.1.1

What's Changed

• Add nonce override by @byte-bandit in #1275
• chore: update README by @byte-bandit in #1276

Full Changelog: v2.1.0...v2.1.1

v2.1.0

What's Changed

• feat: deploy user smart contracts by @maharifu in #1200
• feat: add all skyway endpoints to REST GW by @maharifu in #1272

Full Changelog: v2.0.1...v2.1.0

v2.0.1

What's Changed

• fix: set senderAddress in SLCs from CW by @maharifu in #1267
• chore: add release notes to v2.0.1 by @maharifu in #1270

Full Changelog: v2.0.0...v2.0.1

v2.0.0

Paloma 2.0

Version 2.0 of Paloma introduces Pigeon Feed, our platform for automatic gas management, relayer incentives and reimbursements!

What's Changed

• feat: Pigeon Feed by @byte-bandit in #1262

Full Changelog: v1.15.7...v2.0.0

v1.15.7

What's Changed

• fix: compass attestation with ERC20 tokens by @maharifu in #1253
• chore: update README to point to v1.15.7 by @maharifu in #1254

Full Changelog: v1.15.6...v1.15.7

v1.15.6

What's Changed

• fix: add legacy skyway message by @maharifu in #1234
• fix: sort validators with same score by address by @maharifu in #1235
• feat: add node sale contract details in paloma by @maharifu in #1236
• chore: add optional BUILD_TAGS to Makefile by @maharifu in #1237
• chore: Fix testnet node address in readme by @verabehr in #1239
• feat: record pigeon version on valset by @maharifu in #1240
• chore: update README to v1.15.6 by @maharifu in #1242

Full Changelog: v1.15.5...v1.15.6

v1.15.5

What's Changed

• chore: rename eth references @byte-bandit in #1228
• feat: lightnode licenses by @maharifu in #1229
• fix: feegrant order in light node licenses by @maharifu in #1230
• fix: add chain to skyway nonces genesis by @maharifu in #1232
• fix: sort validators with same score by address

Full Changelog: v1.15.4...v1.15.5

v1.15.4

Paloma 1.15.4 introduces relayer selection based on performance data, a big step towards Pigeon feed, our relayer rewards program! Make sure you have fees configured for your relaying services for each chain! See palomad tx treasury upsert-relayer-fee --help for more information!

Fee settings are configured per chain, and stored as float point percentile representations of the total cost of a relayed transaction. For example, a relayer fee of 1.0 entitles the relayer to 100% of the estimated costs for a relayed transaction, whereas a fee setting of 1.15 entitles to a total of 115% of the costs, making a profit of 15%. These funds can later be claimed by directly interfacing with the Paloma bridge on remote chains.

In order to stay eligible for relaying messages, you will need to setup a fee value of at least 1.0. In order to become profitable, your fee setting needs to be above 1.0. There are no other limits on which fees you set. The network will automatically chose relayers with lower fees based on the current weight settings as defined by governance (check palomad q evm chains-infos for the current relay weights for each chain).

Example fee setup for Paloma main net

ADDRESS = <Operator Address>
FEE = <Fee setting> #e.g 1.1
palomad tx treasury upsert-relayer-fee arbitrum-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee base-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee blast-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee bnb-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee eth-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee gnosis-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee matic-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes
palomad tx treasury upsert-relayer-fee op-main $FEE --from $ADDRESS --fees 250ugrain --gas auto --yes

What's Changed

• fix: message attestation with wrong sign data by @maharifu in #1223
• feat: lightnode sale by @maharifu in #1224
• Enable performance based relayer selection by @byte-bandit in #1226
• chore: update README for v1.15.4 by @byte-bandit in #1227

Full Changelog: v1.15.3...1.15.4

v1.15.3

What's Changed

• fix: remove obsolete parameters from skyway module by @byte-bandit in #1217
• fix: verifyTX on message attestation by @maharifu in #1218
• chore: upgrade IAVL to 1.1.4 by @byte-bandit in #1219
• chore: update readme by @byte-bandit in #1221

Full Changelog: v1.15.2...v1.15.3

v1.15.2

What's Changed

• chore: VerifyAgainstTX implementation by @maharifu in #1203
• chore: print formatted queue messages on remove by @maharifu in #1204
• feat: Prevent parallel delivery of same sender msgs by @byte-bandit in #1205
• chore: rename gravity module by @byte-bandit in #1206
• chore(deps): bump goreleaser/goreleaser-action from 5 to 6 by @dependabot in #1181
• chore(deps): bump google.golang.org/grpc from 1.63.2 to 1.65.0 by @dependabot in #1208
• chore(deps): bump cosmossdk.io/tools/confix from 0.1.0 to 0.1.1 by @dependabot in #1109
• fix: add gravity proposals so they can be decoded by @maharifu in #1213
• chore: change bridge-tax to be per token by @maharifu in #1212
• feat: remove retry limit from erc20 transfers by @byte-bandit in #1214
• chore: update readme by @byte-bandit in #1215

Full Changelog: v1.15.1...v1.15.2