Proofs

• Proof of payment
• Proof of funds

These features are courtesy of Monero.

• Fixed synchronization issues
• Added new startup flag --contact to set node admin contact information (e.g. e-mail)

Legacy Fusion

In this optional release fusion transactions are introduced for WalletLegacy which powers the simplewallet and Classic GUI.
Fusion transactions can be used to optimize lots of small outputs into larger ones to reduce transaction size when sending large amounts. Usage in simplewallet:
estimate_fusion <threshold>
optimize <threshold> <mixin>.
Json RPC methods are in SimpleWallet documentation.

They shall not pass

• Limit reorganization depth to mined money unlock window
• Do not reorganize to alternative chain if it lacks at least one transaction from the public chain (51%-attack protection)
• Disallow merged mining tag in the coinbase transaction
• LWMA difficulty algorithm fix

This update has a softfork update at height 300000.

Attention! This update requires nodes at version 1.6.0 to resync their blockchain! Mandatory.
You can use bootstrap from https://bootstrap.krbnodes.pp.ua/blockchain-2018-11-09.tar.gz or https://looongcat.pp.ua/blockchain-2018-11-09.tar.gz (mirror)

This is especially important for pool owners. Please, compare your next difficulty readings after the update and resync, this can be checked in node's /getinfo rpc endpoint or status command in console. Contact us in Pool operators channel to make sure you have correct difficulty, or at least check public nodes /getinfo and version. Alternatively, refer to node http://45.32.232.11:32348/getinfo or http://108.61.198.115:32348/getinfo for current difficulty. It is important for all nodes to have same difficulty.

Note: warning message WARNING An attempt of too deep reorganization: XXX, BLOCK REJECTED can be ignored, do not be scared 😃

v.1.6.0

DA tweaks

v.1.5.9

Fixed sync issues in previous version 1.5.8 due to fusion transactions

• Updated burning bug patch - now it will compare with all wallet transactions during check
• Fixed refresh of large wallets with burning check
• Fusion transactions backward compatibility
• Sync without checkpoints option in daemon
• Fixed case of '[O]pen wallet' command in simplewallet

Firefighter

• Fixed burning bug:
  • Doesn't process burning transactions in a wallet
  • Wallet throws an error if duplicate output key is found
  • Checks against outputs keys stored in memory while the wallet is on
  • Upon reset it will check all transactions against all output keys
  • Leave double-counting fix intact just in case (check for duplicate output key in the scope of one transaction)
• Fixed sending of large amounts in walletd, and WalletGreen based GUI wallets (Karbo wallet 2 and Lite wallet)
• Added new JSON RPC methods
• Fixed search by Payment ID in transactions memory pool etc.

Burning transaction report in logs looks like this:
ERROR Failed to process transaction: duplicate transaction output key is found, transaction hash 2319509d6d66158faf2f6d71fd9f5699b08f391994c7ea750a80634b99d0e41a
Such transactions are not added and credited to balance.

Sign/verify message

• Sign/verify message
• Json parsing fixed
• Tx fee verification updated to fix syncing issues
• Other misc bugfixes

Send and prove

• Fix sending error "SwappedVector::operator[]"
• Use transaction private key to prove sending

This is hotfix of minimal fee function not being able to check outgoing transaction or mempool transaction due to the invalid height. This requires a mandatory update of all nodes.

Transaction private key allows one to check the amount of KRB sent to a particular address in a particular transaction, given that transaction's secret tx_key.

LWMA-2 Update

This is release with the minor but important update of the LWMA-2 difficulty algorithm.

What's new:

• Use only symmetrical limits in LWMA-2
• Correct types conversion in Minimal Fee calculation
• RPC methods to check transaction with its private key or private view key
• Various small fixes

Please make sure you have version v1.5.5.802 (c60236c)

Fusion fix

This is hotfix release for the previous v. 1.5.3 with:

• Correction of creation and handling of Fusion transactions
• Fixed moving of the data folder to the correct location on Mac
• Correct umixable balance in simplewallet is added
• Revert optimizations that break compatibility with third-party GUI and Lite wallets.

In the v.1.5.3 release HARDFORK V4 IS SET AT HEIGHT 266000. What's new:

• Stopping offline timestamp attacks with Poisson check by RYO Currency Project (https://github.com/ryo-currency/ryo-writeups/blob/master/poisson-writeup.md)
• Adaptive minimal transaction fee
• LWMA-2 Difficulty Algorithm by Zawy (zawy12/difficulty-algorithms#3)
• New FTL and MTP limits
• Minimum mixin limit
• Changed dust threshold
• Changed block template
• Various fixes and improvements

Information for exchanges and other services how to work with new fees: https://github.com/seredat/karbowanec/wiki/Dynamic-transaction-minimum-fee

In this release minimum mixin limit is set to 2, it is still possible to send with zero mixin although this is undesirable and is not recommended. If you experience problems with sending transactions with errors like 'Mixin count is too big', please use fusion transactions to optimize your wallet inputs (described in wiki documentation: estimateFusion() and sendFusionTransaction()).

Pools operating 'cryptonote-forknote-pool' or compatible software should update Node-Cryptonote-Util to this version: https://github.com/aivve/node-cryptonote-util. The reference pool software is here: https://github.com/Karbovanets/karbo-pool.

Pools operating 'cryptonote-nodejs-pool' should change config on hardfork height. The changes in config are:

"daemonType": "default",
"cnAlgorithm": "cryptonight",
"cnVariant": 0,
"cnBlobType": 0,

The example of Karbo config is here: https://github.com/Karbovanets/cryptonote-nodejs-pool/blob/master/config_examples/karbo.json