Ergo Protocol Reference Client 4.0.42

Ergo protocol reference client 4.0.42. It contains:

• #1819 - transaction validation cost is now considered in p2p layer, it is not sending more than some limit (12M total cost) per block while sending transactions one-by-one (so backpressure for the mempool validation is implemented in this PR). Also, default max transaction cost for the mempool lowered down to 4.9M (was 5M).

Contributors: @kushti

Ergo Protocol Reference Client 4.0.41

Ergo protocol reference client 4.0.41. It contains following PRs

• #1599 - more efficient byte operations in AVL tree proof generation
• #1786 and #1812 - different memory pool optimizations and anti-spam protection mechanisms
• #1814 - it is possible now to set via ergo.node.mempoolSorting setting how mempool is sorted (by fee/ transaction size or fee/ transaction cost)

Voting for 5.0 soft-fork:

This version is voting for 5.0 soft-fork automatically. To vote against it, set in the config:

ergo {
  ...
  voting {
    120 = 0 // vote against 5.0 soft-fork
  }
}

you can combine vote against soft-fork with other votes , e.g.

ergo {
  ...
  voting {
    120 = 0 // vote against 5.0 soft-fork
    8 = 1000
  }
}

Contributors: @ApexTheory , @knizhnik , @kushti

Ergo Protocol Reference Client 4.0.40

Ergo Protocol Reference Client 4.0.40. It contains following PRs:

• #1802 - validation errors now always have block section id and type id
• #1808 - improvements in block section delivery checking logic

Voting for 5.0 soft-fork:

This version is voting for 5.0 soft-fork automatically. To vote against it, set in the config:

ergo {
  ...
  voting {
    120 = 0 // vote against 5.0 soft-fork
  }
}

you can combine vote against soft-fork with other votes , e.g.

ergo {
  ...
  voting {
    120 = 0 // vote against 5.0 soft-fork
    8 = 1000
  }
}

SHA-256 checksum: 7277e07098ffcc0a75809a05fc10f515039a73bb8210b0886450c2c9dfcd652c

Contributors: @kushti , @pragmaxim

Ergo Protocol Reference Client 4.0.39

Ergo Protocol Reference Client 4.0.39. It contains following PRs:

• #1750 - prioritize blocks downloading when better chain reported by peers by not downloading transactions during that period
• #1800 - fixes for different issues regarding public API URL
• #1805 - randomized mempool sorting by transaction size or execution cost. Order is decided during node startup.
• #1806 - fixed declared address parsing for IPv6

Voting for 5.0 soft-fork:

Node now voting for 5.0 soft-fork automatically. To vote against it, set in the config:

ergo {
  ...
  voting {
    120 = 0 // vote against 5.0 soft-fork
  }
}

you can combine vote against soft-fork with other votes , e.g.

ergo {
  ...
  voting {
    120 = 0 // vote against 5.0 soft-fork
    8 = 1000
  }
}

SHA-256 checksum: d248ff88a83cf09f42d7209d6a1449299c98ea846da4ca9e99b6cc77aa7b5500

Contributors: @kushti , @pragmaxim , @satsen

Ergo Protocol Reference Client 4.0.38

This release is identical to 4.0.37 but doing auto-voting for 5.0 soft-fork starting from block 823297.

Contributors: @kushti

SHA-256 checksum: 15d805db1c6a93d9f595ae8bbb883a9fedcee6980850a4980b72b31f4c8cd8e9

Ergo Protocol Reference Client 4.0.37

Ergo Protocol Reference Client 4.0.37. It contains following PRs:

• #1661 - by default the node is not storing proofs of correctness for UTXO state during bootstrapping, before a block which is by ergo.node.adProofsSuffixLength blocks behind blockchain tip. Default value for adProofsSuffixLength is 114688. After bootstrapping, the proofs suffix is not being pruned (thus still ever growing)
• #1752 - after EIP-27 activation height, emission box is tracked by its NFT (which is more efficient than syntax trees comparison)
• #1791 - the node can vote for 5.0 soft-fork now (supporting only 4.x protocol). Manual voting is required, please see details below. Voting will be started not sooner than @ 823,297 (first block of epoch #804)
• #1792 - node is checking that a new best header is extracted from sync info network message only once, and only if it is not requested already in another way (by making a query to delivery tracker)

To vote for 5.0 soft-fork with this release, set in the config:

ergo {
  ...
  voting {
    120 = 1 // vote for 5.0 soft-fork
  }
}

you can combine vote for soft-fork with other votes , e.g.

ergo {
  ...
  voting {
    120 = 1 // vote for 5.0 soft-fork
    8 = 1000
  }
}

SHA-256 checksum: 3e85e904b649f598b84b55b4330fbf215e51e88387ee6e0b43cbd3daa079f191

Contributors: @jellymlg , @knizhnik , @kushti

5.0.0 RC2

5.0 Release Candidate 2 reference protocol client release. It has recent 4.x codebase changes merged, and also preliminary mainnet voting rules from 5.0-voting branch are included

Ergo Protocol Reference Client 4.0.36

Ergo Protocol Reference Client 4.0.36. It contains following PRs:

• #1769 - after enough time passed we clear status for potentially stalled peer. Helps when the peer is still recognized as connected (but in fact could be disconnected), but the node can query it still because peer status from the past looks good
• #1779 - locally submitted transaction now checked synchronously
• #1785 - "Stats collector got strange input: SemanticallySuccessfulModifier(ADProofs..." log messages eliminated

maxDeliveryChecks value by default set to 100

Contributors: @jellymlg , @kushti , @pragmaxim

SHA-256 checksum (when built with Java 8): 0a787a5d1bab76b42f4f63d1389965f24d82eac89ea9695ef1b6b9dd723eb3c8

Ergo Protocol Reference Client 4.0.35

Ergo Protocol Reference Client 4.0.35 release. It contains following PRs:

• #1765 - public API URL announcement got back, now serialized as a peer feature
• #1767 - P2P code simplified, global sync message lock removed
• #1772 - in case of non-delivery of a block section, the node is quickly switching to another peer now (and dropping connection with non-delivering peer)
• #1776 - P2P layer simplified by hardcoding some settings.

Config changes

Following settings removed from the config: scorex.network.maxHandshakeSize , scorex.network.maxPacketSize, scorex.network.maxInvObjects

New setting scorex.restApi.publicUrl added, you can announce public API URL to the p2p network via this setting.

Semantics of scorex.network.maxDeliveryChecks changed, now this is a global limit for non-delivery, if you are overriding default value with a small value, please remove overridden value or increase it.

Contributors: @ccellado , @kushti , @pragmaxim

SHA-256 sum: 0eb0c119bdffb6b22a1ee8ad8fa6154665d3d7fb33f6c590716e0e1e3e2f84ba

Ergo Protocol Reference Client 4.0.34

This release is rolling back changes introduced in #1662 , as updates in peer spec serialization are causing problems it seems. Aside of that, this release contains code refactoring done in #1763 .