Skip to content

Releases: ergoplatform/ergo

Ergo Protocol Reference Client 4.0.33

04 Jul 15:45
8066c84
Compare
Choose a tag to compare

Ergo Protocol Reference Client 4.0.33. It contains following PRs:

  • #1662 - the node can expose its open API to other peers , by setting scorex.restApi.publicUrl value , e.g. scorex.restApi.publicUrl = "http://213.239.193.208:9053"
  • #1706 - mass payment methods added to ergo-wallet Java API (along with an example)
  • #1737 - maxInclusionHeight and maxConfirmations parameters added to /scan API methods
  • #1760 - fix for possible parallel downloading issues when downloading block sections via a header taken from syncV2 message
  • #1762 - random test failures in ErgoNodeViewSynchronizerSpecification fixed

Contributors: @pragmaxim , @kushti

5.0.0 RC1 (for testnet)

30 Jun 15:30
17c17a5
Compare
Choose a tag to compare
Pre-release

5.0.0 RC1 release for testnet.

It has auto-voting for 5.0 soft-fork by default, starting from height 4,096.

Please note, from this release the node has 9021 port for p2p interactions for the testnet by default (before, it was 9020). Magic network bytes also changed. Testnet relaunched with this release.

Ergo Protocol Reference Client 4.0.32

30 Jun 09:24
205eabf
Compare
Choose a tag to compare

Ergo Protocol Reference Client 4.0.32. It contains following PRs:

  • #1709 - lazy UTXO set tree loading on node startup
  • #1728 - comparing pay-to-reemission trees by proposition in the testnet
  • #1730 - tests for forks switching
  • #1733 - PeerInfoSerializer code cleaning
  • #1735 - EIP-27 code improvements
  • #1738 - minor refactoring of P2P code
  • #1740 - catching possible null from getAddress
  • #1744 - apply new best header from syncV2 message, if it is there, and download corresponding block sections immediately
  • #1747 - peer filtering rules code externalized (tests added)
  • #1748 - invalidation for transactions with size above limit

SHA-256 sum (for sbt assembly on top of Java 8): 7666530ddf59630657626378ba0cc49f67ce0b6e8e38ce27d15e4b16077c02d1
Contributors: @jellymlg , @knizhnik , @kushti , @pragmaxim

Testnet Release With Fixed Post-EIP27 Sync

06 Jun 11:52
acd9a66
Compare
Choose a tag to compare

This release is corresponding to 4.0.31 with #1728 (a fix for #1726) merged. The PR being merged allows for syncing with the longest known testnet blockchain where both v0 and v1 pay-to-reemission contract syntax trees appear now.

The testnet is full of forks anyway, for reliable bootstrapping, please use trusted peers via following config:

scorex {
 network {
    knownPeers = [
	"213.239.193.208:9020",
        "195.201.82.115:9020" 
    ]
    peerDiscovery = false
  }
}

and remove peers/ folder (along with history , state , wallet/registry sub-folders in data folder before restart, in case of resync.

Ergo Protocol Reference Client 4.0.31

31 May 10:32
1935c95
Compare
Choose a tag to compare

Ergo protocol reference client 4.0.31. It contains following changes:

  • #1646 - support for tokens whitelist, with auto-burn for non-whitelisted tokens. Whitelist is switched off by default and can be reconfigured via
    ergo.wallet.tokensWhitelist setting. If tokensWhitelist = null (by default), there's no whitelist enabled, so the wallet keeps all the tokens. If tokensWhitelist = [] , all the tokens are blacklisted, and so all the tokens in the inputs will be burnt on a transaction made. If, for example, tokensWhitelist = ["03faf2cb329f2e90d6d23b58d91bbb6c046aa143261cc21f52fbe2824bfcbf04","003bd19d0187117f130b62e1bcab0939929ff5c7709f843c5c4dd158949285d0"] (SigUSD, SigRSV) , then all the tokens in the inputs, except of SigUSD and SigRSV, will be burnt.

  • #1717 - as EIP-27 locked in now (and clients of versions 4.0.29 and 4.0.29 recognize it), client code could be simplified by removing lock-in logic. This version considering unconditional EIP-27 activation @ certain height (777,217 in the mainnet).

  • #1719 - if emission box somehow lost during tracking, find it again in block transactions

Also, if mining = true, chain.reemission.checkReemissionRules must be true from now . So if your node is mining, please check that your config has the following setting:

ergo{
  chain {
    reemission {
      checkReemissionRules = true
    }
  }
}

Contributors: @ccellado , @kushti

SHA-256 checksum: 83fd655d0123fa5f2de120f5c37682da0178149d57d048e70cca343e1c034ae6

Ergo Protocol Reference Client 4.0.30

23 May 11:47
3fa0ed3
Compare
Choose a tag to compare

Ergo protocol reference client version 4.0.30. It contains following PRs:

  • #1683 - fix for #1687 (int can't be casted to byte for a custom scan), maxPeerHeight added to /info
  • #1691 - a small correction in sync info serialization (format is the same)
  • #1703 - sync progress card added to the /panel
  • #1715 - fix for slow headers application (#1714)

Contributors: @deadit , @jellymlg, @kushti , @satsen

SHA-256 checksum (if built with Java 8): 25eb9f9add83b28d7767f4d09d203c20f3714df85afb072494a65bf8117f74d1

Ergo Protocol Reference Client 4.0.29

18 May 12:40
2eda574
Compare
Choose a tag to compare

This release has support for EIP-27 lock-in and rules. Please check EIP-27 for details: ergoplatform/eips#52

To vote for EIP-27, use the following setting:

ergo {
  voting {
    8 = 1000
  }
}

To check EIP-27 rules after successful activation, the following setting is needed, which is off by default but needed for mining nodes (to be on proper chain in case of chain-split where old nodes can generate blocks not compatible with EIP-27):

ergo {
  chain {
    reemission {
      checkReemissionRules = true
    }
  }
}

To make proper EIP-27 compatible transactions in the presence of re-emission tokens in the node wallet, another setting is needed:

ergo {
  wallet {
    checkEIP27 = true
  }
}

So combined config (for a pool node also doing payments) could be like:

ergo {
  networkType = "mainnet"
  node {
    mining = true
  }
  voting {
    8 = 1000
  }
  chain {
    reemission {
      checkReemissionRules = true
    }
  }
  wallet {
    checkEIP27 = true
  }
}

Also, this release has a new setting to switch peer discovery off (discovery is on by default), for that, use the following setting:

scorex {
  network {
    peerDiscovery = true
  }
}

Ergo Protocol Reference Client 4.0.28

17 May 14:11
7be8e2d
Compare
Choose a tag to compare

Ergo protocol reference client 4.0.28. It contains:

  • #1676 - from now, log level can be changed via ordinary config, e.g.
scorex {
 logging {
    level = "WARN"
 }
}
  • #1685 - /wallet/transactionsByScanId/{scanId} API method now has additional flag to include unconfirmed transactions into results
  • #1689 - /scan/spentBoxes/{scanId} API method added, to get boxes being spent for a custom scan. Please note, by default the wallet is not storing boxes being spent, so if please enable storing boxes being spent if you want to get them via this method as:
ergo {
  wallet {
     keepSpentBoxes = true
  }
}
  • #1690 - wallet DB rollback not called anymore (during fork resolutions) when wallet is not initialized
  • #1693 - FAQ section is filled with one from the website
  • #1697 - bug with /nipopow/proof/{m}/{k}/{headerId} API method ignoring headerId parameter fixed
  • #1701 - lock done for wallet rescans, to avoid possible rescans done in parallel
  • #1704 - In case of recoverable failure, status in ErgoNodeViewSynchronizer now cleared. This fixes a bug with node being stuck when receiving headers out-of-order etc.

Also, sigma-state (ErgoTree interpreter) dependency updated to 4.0.6 , which solves the issue ergoplatform/sigmastate-interpreter#778

Contributors: @Athanaze, @kushti , @pragmaxim , @ross-weir

Ergo Protocol Reference Client 4.0.27

04 May 09:03
1b85ad5
Compare
Choose a tag to compare

Ergo protocol reference client 4.0.27. It contains:

  • #1665 - wallet rescan can be started from any given height
  • dustLimit is set to null by default. With previous setting by default wallet skipped token minting transactions.

Contributors: @kushti, @pragmaxim

SHA-256 checksum (if built with Java 8): 5b99fd65110c3a62f4d08e28aaa6a9142f6199887087a9ce546d866621b98caa

EIP-27 Experimental Release Candidate 2 (RC2)

03 May 10:35
c228b41
Compare
Choose a tag to compare

This is still experimental version with EIP-27 support (other than that, compatible with master branch).

Mainnet data is fixed now.

You can use this version on both testnet and mainnet.