v0.5.2

This release contains bug fixes and new command line option.

0.5.2 change log

Federation management

Tapyrus Core version v0.5.2 contains critical bug fixes to make federation management reliable:

1. Adding a new node to the tapyrus core network after an aggregate public key update(using xField in the block header) is now supported.
2. A node restarted after aggregate pubkey update can now use the block tree db key to persist and retrieve the list of aggpubkeys instead of using -reindex.
3. A new command line argument -reloadxfield is added to create the block tree db entry in older nodes while upgrading.

Token issue fee

Fee required to issue new tokens/colored coins is made to match the network fee rate. It was one tapyrus more than the network fee rate until now.

v0.5.2.rc1

Tapyrus Core 0.5.2 release candidate 1.

v0.5.1

This release contains minor bug fixes and support for arm64 architecture binaries and containers.

0.5.1 change log

ARM64 container

With version v0.5.1 Tapyrus is supported on ARM64 hosts. Tapyrus containers are also a vailable for ARM64 architecture

secp256k1

secp256k1 library is moved to its own repository and added to tapyrus repository as a sub module to allow independent development.

RPC

• getrawtransaction - version is renamed to features.
• decoderawtransaction - version is renamed to features..

v0.5.1rc1

Release with aarch64 support

v0.5.0 release

Tapyrus Core version 0.5.0 is now available containing some major improvements and bug fixes. Please refer to the release notes for details.

Tapyrus version 0.5.0 is now available for download at:

https://github.com/chaintope/tapyrus-core/releases/tag/v0.5.0

Please report bugs using the issue tracker at Github:

https://github.com/chaintope/tapyrus-core/issues

How to Upgrade

If you are running a node on older version(v0.3.0, v0.4.0, v0.4.1) testnet, shut it down. Wait until it has completelyshut down. Follow the instruction in Getting Started to start a new Tapyrus v0.5.0 node.

If you want to running a private tapyrus network, shut down all nodes. Follow the instruction in Getting Started to start a new Tapyrus v0.5.0 network. As v0.5.0 makes significant changes to consensus rules, when a running network is stopped all nodes should be upgraded before restarting the network again. Please note that tapyrus-signer network should also be upgraded to v0.5.0 following tapyrus signer network setup.

Downgrading warning

Tapyrus blockchain created by older versions(v0.3.0, v0.4.0 and v0.4.1) is not compatible with v0.5.0 and vice-versa. The testnet is reset with the release of v0.5.0.

Compatibility

Tapyrus v0.5.0 is supported on three platforms : Linux, MacOS and Windows(WSL)

Notable changes

Native Colored Coins scheme

With version v0.5.0 Tapyrus blockchain supports colored coins. Tapyrus consensus, script and wallet layers have been enhanced to support the ti. Apart from TPC, the default tapyrus coin, other tokens like NFTs, single issue tokens and reissuable tokens are now supported. Tokens may be issued, sent or received and burnt on Tapyrus blockchain. Complete specification of colored coins in Tapyrus can be found in here (日本語).

Script

• OP_COLOR opcode has been added to identify and process token/colorid in a transaction script.

Colored coin wallet

Tapyrus core wallet now supports colored coins. Coin issue, transfer and burn can be performed using tapyrus core wallet. New RPCs have been added to support these operations.

• getcolor
• issuetoken
• transfertoken
• burntoken
• reissuetoken

RPC overhaul

Tapyrus RPCs has been modified to remove old deprecated features and parameters. Account API support has been removed. Colored coin support has been added to other RPCs as follows. All the RPCs that get private key has been changed to accept WIF private key.

• getnewaddress - addresstype parameter has been removed and color parameter has been added.
• getrawchangeaddress - address type parameter has been removed and color parameter has been added.
• addmultisigaddress - address type parameter has been removed.
• getreceivedbyaddress - minconf parameter has been removed.
• getreceivedbylabel - minconf parameter has been removed.
• getbalance - account parameter has been removed and color parameter has been added.
• sendmany - account and minconf parameters have been removed and color parameter has been added.
• listreceivedbyaddress - minconf parameter has been removed.
• listreceivedbylabel - minconf parameter has been removed.
• listtransactions - dummy parameter has been removed.
• listunspent - account has been removed from the result.
• fundrawtransaction - iswitness flag has been removed.
• generate - private key parameter has been changed to accept WIF private key.
• generatetoaddress - private key parameter has been changed to accept WIF private key.

Removed RPCs

• getaccountaddress
• getaccount
• getaddressesbyaccount
• movecmd
• sendfrom
• addwitnessaddress
• listaccounts

Tapyrus Core v0.5.0rc4

Tapyrus Core 0.5.0 release candidate 4.

Tapyrus Core v0.5.0rc3

Tapyrus Core 0.5.0 release candidate 3.

Tapyrus Core v0.5.0rc2

Tapyrus Core version 0.5.0 release candidate 2.

Tapyrus Core v0.5.0rc1

Tapyrus Core version 0.5.0 release candidate 1.

Tapyrus Core v0.4.1

Tapyrus Core version 0.4.1 is now available containing a single new feature from upstream Bitcoin Core.

JSON-RPC whitelist feature

This can be used to control that access when exposing RPCs for Tapyrus Core that you manage to others. See the help documentation for more details.