@Fair-Exchange Fair-Exchange released this Apr 30, 2018 · 195 commits to master since this release

Assets 2

This is a working release as we approach stable version releases.

@Fair-Exchange Fair-Exchange released this Apr 20, 2018 · 205 commits to master since this release

Assets 2

This is a working release as we approach stable version releases.

"accept failure.2" is not a serious error and usually is due to an un-synced node.

It can usually be addressed with the "reindex" .bat tool.

@Fair-Exchange Fair-Exchange released this Apr 18, 2018 · 206 commits to master since this release

Assets 2

This is a working release as we approach stable version releases.

"accept failure.2" is not a serious error and usually is due to an un-synced node.

It can usually be addressed with the "reindex" .bat tool.

@Fair-Exchange Fair-Exchange released this Apr 16, 2018 · 209 commits to master since this release

Assets 2

This is a working release as we approach stable version releases.

"accept failure.2" is not a serious error and usually is due to an un-synced node.

It can usually be addressed with the "reindex" .bat tool.

@Fair-Exchange Fair-Exchange released this Apr 14, 2018 · 214 commits to master since this release

Assets 2

This is a working release as we approach stable version releases.

"accept failure.2" is not a serious error and usually is due to an un-synced node.

It can usually be addressed with the "reindex" .bat tool.

@Fair-Exchange Fair-Exchange released this Feb 24, 2018 · 236 commits to master since this release

Assets 2

Raw beta version, untested.

"accept failure.2" is not a serious error and usually is due to an un-synced node.

It can usually be addressed with the "reindex" .bat tool.

It is, however, a bit of an unnecessarily depressing message and has thus been changed to "never accept failure"

Pre-release

@Fair-Exchange Fair-Exchange released this Feb 24, 2018 · 236 commits to master since this release

Assets 2

Raw beta version, untested. Compiled in Ubuntu 16.04 LTS 64 bit

"accept failure.2" is not a serious error and usually is due to an un-synced node.

It can usually be addressed with the "reindex" .bat tool.

It is, however, a bit of an unnecessarily depressing message and has thus been changed to "never accept failure"