The following is a weekly progress report from the HCASH development team, and is divided in two parts: ongoing and completed work.
Our GitHub code can be found here: github.com/HcashOrg
Please note: code is being uploaded to GitHub progressively; if you find that something from this document is missing from a repository, please check back periodically.
Completed work:
HyperCash/HC
Hcd
We used a recursive formula to achieve a summation formula, then used this to calculate the supply of HC, thus eliminating accumulated errors, and ensuring the correct HC block amount and difficulty.
The CHECKMULTISIG instruction supports multi-signature functionality and new BLISS addresses.
Hcwallet
Quantum resistant addresses participate in multi-signature address formalisation, transaction signatures, and transaction initiation.
Quantum resistant addressed tickets support an address reuse function to avoid continuously generating a large numbers of addresses.
Repaired decoding error in Quantum resistant addresses.
Added Quantum resistant addresses into Script merge process.
HcGUI
Overviewed real-time changes of statistical data (balance/ticket/transaction).
Corrected incorrect translation
Repaired download failure in HcGui language settings.
HcExplorer
Completed new web page design
Trimmed page content
Hc Testnet PoS Mining Pool
Completed new web page design
Trimmed page content
Hc Testnet PoW Mining Pool
Completed test together with UUPool
HyperExchange/HX
HX Wallet
Increased bonus-related functions. (Users with more than 10,000 HX will automatically receive dividends regularly, which needs to be collected by the users themselves. Dividends are derived from withdrawal fees and fees from invoking smart contracts)
HX IDE
Optimised data access for chain switching and initialisation settings for wallet free state, repaired crash problem when releasing memory.
HyperExchange
Carried out basic cross chain testing between HX chain and HC public testnet.
Users need to pay transaction fees when withdrawing cross chain assets on the HX chain, these fees will be collected in a pool. Similarly, users will have to pay transaction fees when they withdraw assets from smart contracts.
In the HX chain, for every 100,000 blocks, users who hold more than 10,000 HX will be able to participate in fee allocation activities.
Some parameters in the HX chain are hard-coded, and need to be put into ‘global_property’, allowing HX to be modified through a proposal process.
Ongoing work:
HyperCash/HC
Hcd
Regression testing for functionalities such as block generation, transactions, and block & voting queries
Hcwallet
The ‘setaccount’ command to support switching between normal and quantum resistant accounts by ‘cli’ clients.
Regression testing for functionalities such as construction, signatures and transactions on normal and quantum resistant addresses.
Test the proposal initiation functionality, including how to count affirmative, negative, and abstention votes, and that of block version upgrades after voting.
HcGUI
New interface development
Change the application settings position. The settings are only clickable while synchronising, and need to be moved into the menu on the homepage for users’ convenience.
HcExplorer
New interface development
Pg Model: use ‘postgresl’ to support greater website traffic and faster access speeds
Hc testnet PoS Mining Pool
New interface development
Support purchasing of tickets by quantum resistant signatures
HSR to HC on cryptocurrency exchanges
Prepare technical documents
Provide technical support
HSR to HC wallet upgrade process
Prepare technical documents
Provide technical support
HyperExchange/HX
HX wallet
New interface design
HX IDE
Integrate single-step Debugger
Debug interface design
HyperExchange
Program the ETH private key generation module on the HX chain: In order to ensure security, private keys needs to be generated on the HX side, and signatures for empty transactions need to be completed on the C++side of the HX chain.
Deploy the testnet.
Bugs found on HX are being fixed.
We are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of HCASH.