0.4.4.6 update

It was decided to update some libraries, which are used for Windows builds

libminiupnpc 1.6 -> 1.8
openssl 1.0.1c -> 1.0.1f
libdb 4.8.30 -> 5.3.21

New builds are backward-compatible, but wallet.dat becomes unreadable for old builds once it was opened by new client.

Testing builds for compatibility checking: [AMD64  | i686]

Balthazar

As far we know, some payment processors and users accepts 0/unconfirmed transactions. But this solution is not secure, because it’s possible to create two transactions with the same inputs, but different outputs.

http://eprint.iacr.org/2012/248.pdf

Attacker is able to send a first transaction directly to victim, and then broadcast a second transaction over the network. This couldn’t be prevented using the proof-of-work design, but it’s possible to fight with such manipulations through using an extension for our proof-of-stake system, and we even don’t need a chain fork to implement this.

Continue reading →

Balthazar

Just a little piece of info…

As far we know, some payment processors and users accepts 0/unconfirmed transactions. But this solution is not secure, because it’s possible to create two transactions with the same inputs, but different outputs.

http://eprint.iacr.org/2012/248.pdf

Attacker is able to send a first transaction directly to victim, and then broadcast a second transaction over the network. This couldn’t be prevented using the proof-of-work design, but it’s possible to fight with such manipulations through using an extension for our proof-of-stake system, and we even don’t need a chain fork to implement this.

Continue reading →

Анонс изменений 0.4.4.8

Changes planned for 0.4.4.8:

  • Separate databases for private keys and transactions, instead of wallet.dat;
  • Moving the public data to separate folder (e.g. move blockchain database to AppData\Local\Novacoin on Windows);
  • Switching to UTXO storage (similar to used in the Bitcoin, but with extended metadata) instead of the current full transaction logs approach;
  • Switching to deterministic keys, and possibly withdrawal of the keypool approach;
  • Withdrawal of the Berkeley DB support (LevelDB is used by default for a long time).

This changes will be implemented in the 0.4.4.7 testing branch, the 0.4.4.7 binaries will be rebuilt and published sometimes, just for testing purposes.

Parts of this functionality are already available for testing.

Changes planned for 0.4.4.8

Changes planned for 0.4.4.8:

  • Separate databases for private keys and transactions, instead of wallet.dat;
  • Moving the public data to separate folder (e.g. move blockchain database to AppData\Local\Novacoin on Windows);
  • Switching to UTXO storage (similar to used in the Bitcoin, but with extended metadata) instead of the current full transaction logs approach;
  • Switching to deterministic keys, and possibly withdrawal of the keypool approach;
  • Withdrawal of the Berkeley DB support (LevelDB is used by default for a long time).

This changes will be implemented in the 0.4.4.7 testing branch, the 0.4.4.7 binaries will be rebuilt and published sometimes, just for testing purposes.

Parts of this functionality are already available for testing.

Проблема

Клиенты версий ниже 0.4.4.5 содержали ошибку, которая в дальнейшем была исправлена. Как результат, вот этот блок:

http://explorer.novaco.in/block/aab5ad74039e711b3afb52127c0ea6eaac5bc756c41d76ca0460ea29d0ec85f2

был отклонен клиентами с версией до 0.4.4.5, а 0.4.4.5 и более новые его приняли без проблем. Если у вас клиент с версией ниже 0.4.4.5, то следует обновить его до 0.4.4.5 или более новой.

P.S. Подтверждено, что btc-e, coinpool и khore находятся на правильной ветке.

Attention

Attention to all users of novacoin.

Chain fork happened due to fee calculation issue with block #65873. The following short FAQ should be helpful in order to resolve this problem.

Q: I’ve got an alert message from my Novacoin client. Is this right thread
A: Yes, that’s right thread.

Q: What’s happened?
A: Some clients has this block rejected while the most part of nodes accepted that without any problem. That’s caused a chain fork which couldn’t be resolved automatically.

Q: What should I do?
A: You need to install 0.4.4.5 or 0.4.4.6 update, these versions are not affected by this issue. Continue reading →

Инсталлятор поврежден

Инсталлятор поврежден и на некоторых системах ведет себя странно, сейчас заменим. Неприятная нестыковка.

64-бит инсталлятор перезалит, sha1 хэш правильного файла 

8a8eac4c2abd70e94520014dfe67faa63945e2c3

32-бит инсталлятор перезалит, sha1 хэш правильного файла 

ae600c0df9f5367787ff1ba9a401e3858005ee70

Continue reading →

Release 0.4.4.6

NovaCoin 0.4.4.6 client update builds, some testing wold be helpful.

Linux x86_64 static:
http://sourceforge.net/projects/novacoin/files/novacoin-0.4.4.6.ubuntu-lts-x86_64.tar.bz2/download

Win32 static:
http://sourceforge.net/projects/novacoin/files/novacoin-0.4.4.6-nosetup-win32.zip/download

Windows 64 bit installer:
http://sourceforge.net/projects/novacoin/files/novacoin-setup-win32-amd64-0.4.4.6.exe/download

Windows 32 bit installer:
http://sourceforge.net/projects/novacoin/files/novacoin-setup-win32-0.4.4.6.exe/download

Please check README file before running.

  Valid XHTML 1.0 Transitional Valid XHTML 1.0 Transitional   Valid CSS Valid CSS      I find a bug/typo or I have a suggestion
Adapted for Lynx-like browsers
2013-2017 © Zloy & Co
For donations: 4ZLoY6T8wXKgrbZM9gL8fQt48NUzGo2yAg