Release Details

1. Solve max transaction length in broadcast.
2. Refactor the code
3. Clean up the unused code
4. Switch to the latest Swagger
5. Update the known peers for Mainnet and Testnet configuration

Release Information

1. The max transaction length for broadcast expended from 1114 bytes to 4096 bytes, this will solve the issue that some long transactions(Register/Execute) can not be broadcasted.
2. Refactor the code and fix the issue of scala code style. Fixed some java style code or incorrect usage code.
3. Some used transaction types and elements are remove. e.g. Alias, Issue/Reissue/Transfer Transactions, Matcher. Related unit test are removed too.
4. Switched the Swagger version from 0.2.1 to 2.0.0
5. Update known peers
   i. Known Peers for Mainnet
   known-peers = ["13.55.174.115:9921","13.52.40.227:9921","13.113.98.91:9921","3.121.94.10:9921"]
   ii. Known Peers for Testnet
   known-peers = ["54.193.47.112:9923","13.56.200.72:9923","18.218.106.1:9923","3.17.78.253:9923","34.222.191.174:9923"]
6. Node users can reuse the previous block data without any re-download/re-sync. Users can restart the node with same blockchain data/state with same configuration.
7. This release for both V Systems Testnet and Mainnet users