Skip to content

Releases: team-exor/eiquidus

v1.102.0

15 Jun 00:48
@joeuhren joeuhren
v1.102.0
dae3966
This commit was signed with the committer’s verified signature.
joeuhren Joe Uhren
GPG key ID: 19066824FBCF96C7
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.102.0 Latest
Latest

We are proud to announce the release of eIquidus explorer v1.102.0. The most notable change here is the orphan block fix from commit 09fa919 which was one of the last big bugs left in the system.

Although the orphan block fix introduced some new database changes, it is not necessary to reindex your existing explorer since it is smart enough to handle new and existing explorer setups.

NOTE: As of commit de0da04, if you were running via pm2 or forever when updating the explorer with this change, it is necessary to manually stop the explorer with npm run stop-pm2 or npm run stop-forever and then start again after the code has been updated to allow NODE_ENV to be set to "production". Without doing this, the explorer will still be run in "development" mode until pm2 or forever is fully stopped and restarted.

How to Upgrade

  1. Download the updated code changes with the cmd: npm run update-explorer
  2. Review the changes to the settings.json.template file and consider adding and configuring the newly added settings. NOTE: An effort has been made to allow previous settings.json files to work using default values for new settings, without actually adding the newest config changes, but you may receive deprecation warning messages when you start the explorer and you may also still need to manually fix image paths and change default settings where applicable.

Notable Changes

Assets 2
Loading

v1.101.0

10 Jul 01:56
@joeuhren joeuhren
v1.101.0
42a59ab
This commit was signed with the committer’s verified signature.
joeuhren Joe Uhren
GPG key ID: 19066824FBCF96C7
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.101.0

We are proud to announce the release of eIquidus explorer v1.101.0. This is mostly a maintenance release with various improvements and bug-fixes. The update script has been perfected so that manual restarts of the explorer are no longer necessary after updating since the update script now handles restarting automatically.

The only database change for this release was a small change to the networkhistory collection to split difficulty into difficulty_pow and difficulty_pos. However, a number of new settings were added to the settings.json file that you may want to review and configure appropriately.

NOTE: If you have existing NetworkHistory data from before the v1.100.0-57b6dd7 update, it will be automatically assumed to be POW. If it was actualy POS, you will need to either manually fix the data in mongo or simply wait a couple hours while syncing to eventually push the old data out of the chart.

How to Upgrade

  1. If you are running an older version than v1.100.0-bae4d50, you must first shut down the explorer manually before updating to prevent problems [SEE IMPORTANT NOTE BELOW]
  2. Download the updated code changes with the cmd: git pull (or npm run update-explorer if using a more recent version that supports this cmd)
  3. Review the changes to the settings.json.template file and consider adding and configuring the newly added settings. NOTE: An effort has been made to allow previous settings.json files to work using default values for new settings, without actually adding the newest config changes, but you may receive deprecation warning messages when you start the explorer and you may also still need to manually fix image paths and change default settings where applicable.

IMPORTANT NOTE: If you were running an explorer version that is older than v1.100.0-bae4d50 and you did not shut down the explorer before performing a code update, you will be unable to shut down or restart the explorer using the usual built-in cmds due to breaking changes. Therefore, you will need to type out the full stop cmd this one time only, and from now on going forward you should no longer need to even stop the explorer for any update, as it is now built into the update cmd.

If running using pm2 and you cannot stop the explorer, you can stop using the following full cmd syntax:

Windows:

pm2 stop ./bin/instance

Linux and other OS's:

node node_modules/pm2/bin/pm2 stop ./bin/instance

If running using forever and you cannot stop the explorer, you can stop using the following full cmd syntax:

All OS's:

node node_modules/forever/bin/forever stop ./bin/cluster

Notable Changes

Assets 2
Loading

v1.100.0

29 May 21:57
@joeuhren joeuhren
v1.100.0
e1a7336
This commit was signed with the committer’s verified signature.
joeuhren Joe Uhren
GPG key ID: 19066824FBCF96C7
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.100.0

We are proud to announce the release of eIquidus explorer v1.100.0. Truth-be-told, the last version was bumped all the way to v1.99 thinking that v2.0 was right around the corner, but more and more fixes and features kept getting added to the list and there are still a few missing features that we feel should be included before we can call it v2.0. From now on the plan is to release more frequent updates instead of having a massive list of changes between versions.

Some changes were made to the data structure for features such as P2PK scripts/txes and decoding tx OP_RETURN values, but it may not be necessary to do a full reindex if coming from v1.99.0 unless you are looking to take advantage of those specific changes.

How to Upgrade

  1. If you are running an older version, first shut it down.
  2. Download the updated code changes with the cmd: git pull
  3. Review the changes to the settings.json.template file and consider adding and configuring the newly added settings. NOTE: An effort has been made to allow v1.99.0 settings.json files to still be compatible with v1.100.0, but you will receive many depreciation warning messages when you start the explorer and you may still need to manually fix image paths and change default settings where applicable.

Notable Changes

Read more
Assets 2
Loading

v1.99.0

06 Feb 01:40
@joeuhren joeuhren
v1.99.0
fd7be80
Compare
Choose a tag to compare
v1.99.0

We are proud to announce the release of eIquidus explorer v1.99.0. This version has many new breaking changes to the data structure and therefore a full reindex is required for all users migraging from v1.0.1.

How to Upgrade

  1. If you are running an older version, first shut it down.
  2. Download the updated code changes with the cmd: git pull
  3. Review the changes to the settings.json.template file and consider adding and configuring the newly added settings. NOTE: An effort has been made to allow v1.0.1 settings.json files to still be compatible with v1.99.0, but you will receive many depreciation warning messages when you start the explorer and you may still need to manually fix image paths and change default settings where applicable.

Notable Changes

Read more
Assets 2
Loading

v1.0.1

08 Jun 02:06
@joeuhren joeuhren
v1.0.1
a175e03
Compare
Choose a tag to compare
v1.0.1 
v1.0.1
Assets 2
Loading

v1.0.0

27 May 17:34
@joeuhren joeuhren
v1.0.0
60fb8e2
Compare
Choose a tag to compare
v1.0.0

Initial release

Assets 2
Loading