에이치쉐어

탈중앙화된 오픈소스 크로스 플랫폼 통화

홈페이지 https://h.cash/

참고자료 Whitepaper.pdf

커뮤니티

시세
1,483.89 KRW
상장된 거래소
9
심볼
HC
출시 예정
프로젝트 소개

"Hcash는 탈중앙화된 오픈소스 크로스 플랫폼 통화입니다.Hcash는 블록체인과 블록체인이 아닌 데이터의 교환이 가능하도록 설계되었습니다."

경영진 및 파트너사

Adam Geri

CEO

Andrew wasylewicz

COO

Joesph LIU

Chief Scientist

Shanghai jiao tong uni.

Hong kong Polytechnic Uni.

최신뉴스

등록된 뉴스가 없습니다.
해당 팀에게 응원 메세지를 남겨주세요!

메세지 남기러가기

미디움

Weekly Development Update

15–21 March 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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 workHyperCash/HCHcdCompleted development for block speed increaseOptimised block production algorithmAdded Best Hash featureOptimised codeHcwalletOptimised codeHyperExchange/HXHX coreModified storage format of native contractAdded off-chain matchmaking scheme for on-chain tradingHX IndicatorIncreased startup speed for some casesOptimised block height displayHX IDEAdded support for data transmission between IDE and debugger via network interfaceFixed lag bugs under debugging status on IDEFixed crash bug that occurred when shutting down debuggerHX ToolsFixed bugs on HX Decentralised Exchange (HDEX) HTML5 K lineAdjusted HDEX HTML5 home page and Markets page displayImplemented user configurationOngoing work:HyperCash/HCHcdDevelop ASIC-resistant mining algorithmConduct tests for Linkable RingCT codeHcwalletDevelopment on block validation on ASIC resistant mining algorithmhcGUIFix block non-synchronisation bug that appears when hcGUI has not been started for a long timeHcOMNIPrepare for CNYT issuingHcAutonomyPrepare for mainnet parameter adjustment proposalHyperExchange/HXHX coreDevelop BTM cross-chain codeAllow programme to launch in non-block replay mode when hx-node is abortedHX IndicatorRun tests for K line featureOptimise trading history query featureOptimise trading storage methodHX IDECompile debugger on macOS systemsHX ToolsRun tests on HDEX HTML5Run tests on back-end service and fix bugsAdd compatibility to Indicator private key filesWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 03. 22

Weekly Development Update

08–14 March 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdOptimised codeHcwalletOptimised codeTechnical supportConducted DApp researchHcAutonomyDrafted a new proposalHyperExchange/HXHX coreOptimised default log print informationFixed the bug that appears on Linux systems; starting after the software shuts down normally will trigger blockchain replaySolved core dump problem that occasionally occurs when Windows restartsIncreased token contract performanceHX IndicatorAdded K line featureFixed Config filesHX IDERemoved old code from console commandModified debugging status enumeration, centrally forwarding debug control commandsHX ToolsAdded balance query feature to HX Decentralised ExchangeAdded personal settings to HX Decentralised ExchangeAdded announcement query feature to HX Decentralised ExchangeOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop ASIC-resistant mining algorithmConduct tests for Linkable RingCT codeHcwalletDevelopment on block validation on ASIC resistant mining algorithmHcOMNIPrepare for CNYT issuingHyperExchange/HXHX coreModify the storage format of native contractDevelop BTM cross-chain codeFix several new bugsHX IndicatorRun tests for K line featureOptimise trading history query featureOptimise trading storage methodHX IDERun IDE and debugger integration test with RPC interfaceCompile debugger on macOS systemsHX ToolsDesign offline-chain matchmaking trade schemeAdd user asset deposit and withdrawal history query feature and integrate HX JS pluginIntegrate Announcement page with back-endIntegrate Markets page with back-endWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 03. 15

Weekly Development Update

08–14 March 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdOptimised codeHcwalletOptimised codeTechnical supportConducted DApp researchHcAutonomyDrafted a new proposalHyperExchange/HXHX coreOptimised default log print informationFixed the bug that appears on Linux systems; starting after the software shuts down normally will trigger blockchain replaySolved core dump problem that occasionally occurs when Windows restartsIncreased token contract performanceHX IndicatorAdded K line featureFixed Config filesHX IDERemoved old code from console commandModified debugging status enumeration, centrally forwarding debug control commandsHX ToolsAdded balance query feature to HX Decentralised ExchangeAdded personal settings to HX Decentralised ExchangeAdded announcement query feature to HX Decentralised ExchangeOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop ASIC-resistant mining algorithmConduct tests for Linkable RingCT codeHcwalletDevelopment on block validation on ASIC resistant mining algorithmHcOMNIPrepare for CNYT issuingHyperExchange/HXHX coreModify the storage format of native contractDevelop BTM cross-chain codeFix several new bugsHX IndicatorRun tests for K line featureOptimise trading history query featureOptimise trading storage methodHX IDERun IDE and debugger integration test with RPC interfaceCompile debugger on macOS systemsHX ToolsDesign offline-chain matchmaking trade schemeAdd user asset deposit and withdrawal history query feature and integrate HX JS pluginIntegrate Announcement page with back-endIntegrate Markets page with back-endWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 03. 15

Weekly Development Update

01 — 07 March 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/hcashorgPlease 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/HCHcdOptimised codeFixed several bugsReleased V2.1.0HcwalletOptimised codeFixed several bugsReleased V2.1.0HyperExchange/HXHX coreConducted research for BTM integrationOptimised several APIsReleased a new versionOptimised HX contract storage performanceCompleted BTM public and private key generation algorithm transplantationAdded a new API for native multi-signal address withdrawalHX IndicatorSet a timeout alert for middleware query before startupFixed contract asset large number compatibility bugHX IDEAdded function entry feature to IDE debug statusFixed ‘contract calculation uncompleted’ bug that appears when modifying contract call interface on IDEHX ToolsAdded market query API to HX Decentralised ExchangeOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop ASIC-resistant mining algorithmConduct tests for Linkable RingCT codeHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreModify the storage format of native contractDevelop BTM cross-chain codeFix the bug that appears on Linux systems; starting after the software shuts down normally will trigger blockchain replayHX IndicatorAdd K line featureOptimise pending order history displayHX IDECompile debugger on macOS systemsUse libevent to transfer debug dataHX ToolsDevelop HX Decentralised Exchange HTML5 pending order featureDevelop HX Decentralised Exchange HTML5 Assets pageConduct tests on HX peripheral tools and fix bugsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 03. 08

Weekly Development Update

01 — 07 March 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/hcashorgPlease 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/HCHcdOptimised codeFixed several bugsReleased V2.1.0HcwalletOptimised codeFixed several bugsReleased V2.1.0HyperExchange/HXHX coreConducted research for BTM integrationOptimised several APIsReleased a new versionOptimised HX contract storage performanceCompleted BTM public and private key generation algorithm transplantationAdded a new API for native multi-signal address withdrawalHX IndicatorSet a timeout alert for middleware query before startupFixed contract asset large number compatibility bugHX IDEAdded function entry feature to IDE debug statusFixed ‘contract calculation uncompleted’ bug that appears when modifying contract call interface on IDEHX ToolsAdded market query API to HX Decentralised ExchangeOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop ASIC-resistant mining algorithmConduct tests for Linkable RingCT codeHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreModify the storage format of native contractDevelop BTM cross-chain codeFix the bug that appears on Linux systems; starting after the software shuts down normally will trigger blockchain replayHX IndicatorAdd K line featureOptimise pending order history displayHX IDECompile debugger on macOS systemsUse libevent to transfer debug dataHX ToolsDevelop HX Decentralised Exchange HTML5 pending order featureDevelop HX Decentralised Exchange HTML5 Assets pageConduct tests on HX peripheral tools and fix bugsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 03. 08

Weekly Development Update

01 — 07 March 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/hcashorgPlease 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/HCHcdOptimised codeFixed several bugsReleased V2.1.0HcwalletOptimised codeFixed several bugsReleased V2.1.0HyperExchange/HXHX coreConducted research for BTM integrationOptimised several APIsReleased a new versionOptimised HX contract storage performanceCompleted BTM public and private key generation algorithm transplantationAdded a new API for native multi-signal address withdrawalHX IndicatorSet a timeout alert for middleware query before startupFixed contract asset large number compatibility bugHX IDEAdded function entry feature to IDE debug statusFixed ‘contract calculation uncompleted’ bug that appears when modifying contract call interface on IDEHX ToolsAdded market query API to HX Decentralised ExchangeOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop ASIC-resistant mining algorithmConduct tests for Linkable RingCT codeHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreModify the storage format of native contractDevelop BTM cross-chain codeFix the bug that appears on Linux systems; starting after the software shuts down normally will trigger blockchain replayHX IndicatorAdd K line featureOptimise pending order history displayHX IDECompile debugger on macOS systemsUse libevent to transfer debug dataHX ToolsDevelop HX Decentralised Exchange HTML5 pending order featureDevelop HX Decentralised Exchange HTML5 Assets pageConduct tests on HX peripheral tools and fix bugsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 03. 08

Weekly Development Update

22–28 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdFixed several bugsOptimised codehcGUIIncreased block rescanning speedHyperExchange/HXHX coreImplemented special account for deposits and transactionsOptimised connectionHX IndicatorFixed bug that appears when Senators collect rewardsFixed bug that appears on contract tokensAdded language option for first-time installationHX IDEFixed issues that appear when incorporating Java smart contract with blockchainUpgrade Kotlin contract templateFixed memory free issues on editorHX ToolsFixed bugs that appear on HX Decentralised Exchange query functionOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop ASIC-resistant mining algorithmConduct tests for Linkable RingCT codeContinue to locate and fix bugsContinue to optimise codeHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageOptimise HX contract storage performanceOptimise several APIsConduct research for BTM integrationHX IndicatorAdd K line featureHX IDEAdd Network communication module to debuggerCompile debugger on macOS systemsOptimise IDE codeHX ToolsDevelop HX Decentralised Exchange HTML5 home pageDevelop HX Decentralised Exchange HTML5 trading order featureConduct tests on HX peripheral tools and fix bugsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 03. 01

Weekly Development Update

22–28 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdFixed several bugsOptimised codehcGUIIncreased block rescanning speedHyperExchange/HXHX coreImplemented special account for deposits and transactionsOptimised connectionHX IndicatorFixed bug that appears when Senators collect rewardsFixed bug that appears on contract tokensAdded language option for first-time installationHX IDEFixed issues that appear when incorporating Java smart contract with blockchainUpgrade Kotlin contract templateFixed memory free issues on editorHX ToolsFixed bugs that appear on HX Decentralised Exchange query functionOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop ASIC-resistant mining algorithmConduct tests for Linkable RingCT codeContinue to locate and fix bugsContinue to optimise codeHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageOptimise HX contract storage performanceOptimise several APIsConduct research for BTM integrationHX IndicatorAdd K line featureHX IDEAdd Network communication module to debuggerCompile debugger on macOS systemsOptimise IDE codeHX ToolsDevelop HX Decentralised Exchange HTML5 home pageDevelop HX Decentralised Exchange HTML5 trading order featureConduct tests on HX peripheral tools and fix bugsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 03. 01

Weekly Development Update

22–28 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdFixed several bugsOptimised codehcGUIIncreased block rescanning speedHyperExchange/HXHX coreImplemented special account for deposits and transactionsOptimised connectionHX IndicatorFixed bug that appears when Senators collect rewardsFixed bug that appears on contract tokensAdded language option for first-time installationHX IDEFixed issues that appear when incorporating Java smart contract with blockchainUpgrade Kotlin contract templateFixed memory free issues on editorHX ToolsFixed bugs that appear on HX Decentralised Exchange query functionOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop ASIC-resistant mining algorithmConduct tests for Linkable RingCT codeContinue to locate and fix bugsContinue to optimise codeHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageOptimise HX contract storage performanceOptimise several APIsConduct research for BTM integrationHX IndicatorAdd K line featureHX IDEAdd Network communication module to debuggerCompile debugger on macOS systemsOptimise IDE codeHX ToolsDevelop HX Decentralised Exchange HTML5 home pageDevelop HX Decentralised Exchange HTML5 trading order featureConduct tests on HX peripheral tools and fix bugsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 03. 01

Weekly Development Update

22–28 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdFixed several bugsOptimised codehcGUIIncreased block rescanning speedHyperExchange/HXHX coreImplemented special account for deposits and transactionsOptimised connectionHX IndicatorFixed bug that appears when Senators collect rewardsFixed bug that appears on contract tokensAdded language option for first-time installationHX IDEFixed issues that appear when incorporating Java smart contract with blockchainUpgrade Kotlin contract templateFixed memory free issues on editorHX ToolsFixed bugs that appear on HX Decentralised Exchange query functionOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop ASIC-resistant mining algorithmConduct tests for Linkable RingCT codeContinue to locate and fix bugsContinue to optimise codeHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageOptimise HX contract storage performanceOptimise several APIsConduct research for BTM integrationHX IndicatorAdd K line featureHX IDEAdd Network communication module to debuggerCompile debugger on macOS systemsOptimise IDE codeHX ToolsDevelop HX Decentralised Exchange HTML5 home pageDevelop HX Decentralised Exchange HTML5 trading order featureConduct tests on HX peripheral tools and fix bugsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 03. 01

Ring Signatures, Blockchai ...

The HyperCash development team has completed and released code for the implementation of Post-Quantum Linkable Ring Signatures in HC, and is now entering the deployment testing phase. This algorithm is based on a publication written by HCASH Chief Scientist, Dr Joseph Liu and his colleagues “Post-Quantum One-Time Linkable Ring Signature and Application to Ring Confidential Transactions in Blockchain”, which was published by the International Association for Cryptologic Research.Last November, Dr Joseph was announced as the Australian Computer Society’s ICT Researcher of the Year, at the 2018 Digital Disruptor Awards, recognising his ground-breaking research in advancing blockchain technology as a legitimate way to create new economic and social systems. These new developments, based on research conducted by some of the brightest minds in the industry, brings users of HC benefits from its high level of privacy and security.About ring signaturesIn cryptography, a ring signature is a type of digital signature that can be performed by any member of a group of users with cryptographic keys. A transaction message signed with a ring signature is verified by someone in a particular group of people, without revealing the public key (or identity) of the sender, receiver, the signatory or any of the other members of the group, while also withholding the transaction amount.The first cryptocurrency which successfully implemented an algorithm using ring signatures was Monero. In 2015, Dr Shen Noether published an article entitled “Ring Confidential Transactions”, which laid the foundation for the ring signature algorithm implemented in Monero.Much like Bitcoin, this implementation of the signature algorithm uses a “hash-based public key + private key” approach. The difference is, that the addition of the ring signature technology mixes the transaction sender’s public key with other public keys, and only then does it sign the information. When the receiver receives the transaction, they use their own private key to verify the signature. As such, other people (including potential malicious parties) are not able to tell which one of the public keys belongs to the sender. This gives Monero the capability of hiding the sender’s address information, making it impossible for external attackers to target the sender.In September 2017, Monero implemented a hard fork, and integrated RCT (Ring Signature Technology) to encrypt the transaction amount when making transactions, meaning that no one, except the sender and receiver can track any transaction details (including sender’s address and value of the inputs). After this, the new RCT address became the only address format for Monero.Blockchain security and privacy protectionAt the beginning of this year, blockchain analysis firm Chainalysis announced that it had received $30 million in Round B financing, led by Silicon Valley VC firm, Accel. In April last year, Chainalysis completed $16 million of Round A financing.Accel has invested in well-known companies such as Facebook, Dropbox, and Spotify, and has also shown interest blockchain technology. They believe that cryptocurrencies will achieve growth and will be subject to stricter supervision, leading them to their investment in Chainalysis.However, there are also concerns in the industry that blockchain data analysis companies such as Chainalysis, have played a role in promoting the compliance of blockchain companies, at the risk of user privacy. Foregoing user privacy systems can allow third parties to see balances in other users’ hot and cold wallets by simply transferring small amounts of funds to their target’s wallet address and observing the transaction’s UTXO dynamics.This type of analysis is generally based on probabilistic guessing, and associated wallets can be flagged as a risk — this is problematic when unwitting and legitimate users are considered a risk by compliance agencies. Given that regulation in the blockchain industry is not yet mature, users mistakenly deemed as a risk have no way to combat their classification. Because of this, privacy protection and blockchain security have become important considerations for the design of many new blockchain projects. More and more projects are improving the privacy and security of transactions through various methods to help users “blur” their wallet balance and transaction records, preventing their normal wallet activities from being tracked.A brief comparison of privacy protection technologiesWhen blockchain technology was first introduced, privacy was one of its core characteristics. For example, when Bitcoin is used as a payment method, all that is needed is an electronic address consisting of a string of alphanumeric characters, rather than a bank account that is connected to a personal identity, and is therefore at risk of privacy breaches. However, this level of privacy is called “pseudo-privacy”, which is similar to using a pseudonym to hide a real identity when writing a letter. Once an electronic address is obtained (or our analog “pseudonym”) and is associated with any real identity, privacy is breached. In the current information age, the cost of obtaining this information is not high. Therefore, some blockchain technology researchers have been focusing on exploring higher levels of privacy and security protection technologies.There are two main metrics used in privacy protection to evaluate a technology; relevance and traceability. For example, although Bitcoin replaces the identity information with an electronic address, we can still trace back to a certain transaction, and then find out the owner’s identity by analysing relevant information. In order to achieve a higher level of privacy and security, this relevance and traceability must be removed. Currently, the most widely used technologies to achieve this goal are ring signatures and zero-knowledge proof.Some examples of privacy protection technologies in well-known blockchains:When you spend Monero, the value of the inputs and outputs you are sending are encrypted and disguised to everyone except the receiver of each of those outputs. Pedersen commitments allow you to send Monero without revealing the value of the transactions. They also use RingCT, which allows for hidden amounts, origins and destinations of transactions with reasonable efficiency, and verifiable, trustless coin generation. In this case, people can prove that the signer (who is also the token sender) belongs to a certain “signature ring”, but cannot correspond the sender’s address and signature to any one of them.We take ZCASH as an example to explain zero-knowledge proof. Zcash addresses are either private (z-addresses) or transparent (t-addresses). Z-addresses start with a “z,” and t-addresses start with a “t.” A Z-to-Z transaction appears on the public blockchain, so it is known to have occurred and that the fee was paid. However, addresses, transaction amounts, and the memo field are all encrypted and not publicly visible. Third parties who are neither the sender nor the receiver of a transaction will not be able to obtain any information about the encrypted transaction — even the miner responsible for recording the transaction is not be able to obtain the encrypted address and the transaction amount. When an encrypted transaction is recorded, the miner is only allowed to record that “there is an unspent balance, and a transaction is generated”, and not allowed to record the blocked address and the transaction amount itself.We can see that both RingCT and zero-knowledge proof are higher-level privacy protection technologies. Zero-knowledge proof is highly dependent on a blockchain’s initial parameters. In current implementations of zero-knowledge proof technology, it is difficult to implement mobile payment methods because the signature is very large and highly affected by the network. It is worth mentioning that the HCASH development team is working on improving zero-knowledge proof tehnology to enable mobile payment methods.HCASH community member Ryan Xu also wrote, that for privacy protection and blockchain security, ring signature technology is still the best choice in the present, and pereceivable future.HCASH post-quantum linkable ring signaturesThe HyperCash team has adapted and improved current RingCT technology. Dr Joseph Liu and his team present a lattice-based post-quantum secure Ring CT protocol, that supports multi-input-multi-output transactions. It is a comprehensive Ring CT protocol, such that it contains all necessary parts including a linkable ring signature (for user anonymity), commitment scheme (for hiding the transaction amount) and range proof (to ensure the hidden value is a positive amount). All parts are in a lattice-based setting, meaning that the overall protocol is post-quantum secure.The release of this code enables other projects and users to gain access to HCASH’s version of post-quantum signature application and privacy protection. In future, the HCASH development team will continue to conduct more in-depth research in the direction of post-quantum signatures and ring signatures. Dr Joseph Liu will post an improved version of the current linkable ring signature scheme paper based on the present Monero ring signature. The upcoming paper is proposing to allow higher number of signatures by an order of magnitude three to four times greater than that of the current version of Monero. According to the HyperCash technology yellow paper, HC will continue to implement lattice-based post-quantum signature code, and become an industry leader in the protection of privacy.See HCASH’s Post-Quantum Linkable Ring Signature code at:https://github.com/chainchip/Lattice-RingCT-v2.0To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 28

Ring Signatures, Blockchai ...

The HyperCash development team has completed and released code for the implementation of Post-Quantum Linkable Ring Signatures in HC, and is now entering the deployment testing phase. This algorithm is based on a publication written by HCASH Chief Scientist, Dr Joseph Liu and his colleagues “Post-Quantum One-Time Linkable Ring Signature and Application to Ring Confidential Transactions in Blockchain”, which was published by the International Association for Cryptologic Research.Last November, Dr Joseph was announced as the Australian Computer Society’s ICT Researcher of the Year, at the 2018 Digital Disruptor Awards, recognising his ground-breaking research in advancing blockchain technology as a legitimate way to create new economic and social systems. These new developments, based on research conducted by some of the brightest minds in the industry, brings users of HC benefits from its high level of privacy and security.About ring signaturesIn cryptography, a ring signature is a type of digital signature that can be performed by any member of a group of users with cryptographic keys. A transaction message signed with a ring signature is verified by someone in a particular group of people, without revealing the public key (or identity) of the sender, receiver, the signatory or any of the other members of the group, while also withholding the transaction amount.The first cryptocurrency which successfully implemented an algorithm using ring signatures was Monero. In 2015, Dr Shen Noether published an article entitled “Ring Confidential Transactions”, which laid the foundation for the ring signature algorithm implemented in Monero.Much like Bitcoin, this implementation of the signature algorithm uses a “hash-based public key + private key” approach. The difference is, that the addition of the ring signature technology mixes the transaction sender’s public key with other public keys, and only then does it sign the information. When the receiver receives the transaction, they use their own private key to verify the signature. As such, other people (including potential malicious parties) are not able to tell which one of the public keys belongs to the sender. This gives Monero the capability of hiding the sender’s address information, making it impossible for external attackers to target the sender.In September 2017, Monero implemented a hard fork, and integrated RCT (Ring Signature Technology) to encrypt the transaction amount when making transactions, meaning that no one, except the sender and receiver can track any transaction details (including sender’s address and value of the inputs). After this, the new RCT address became the only address format for Monero.Blockchain security and privacy protectionAt the beginning of this year, blockchain analysis firm Chainalysis announced that it had received $30 million in Round B financing, led by Silicon Valley VC firm, Accel. In April last year, Chainalysis completed $16 million of Round A financing.Accel has invested in well-known companies such as Facebook, Dropbox, and Spotify, and has also shown interest blockchain technology. They believe that cryptocurrencies will achieve growth and will be subject to stricter supervision, leading them to their investment in Chainalysis.However, there are also concerns in the industry that blockchain data analysis companies such as Chainalysis, have played a role in promoting the compliance of blockchain companies, at the risk of user privacy. Foregoing user privacy systems can allow third parties to see balances in other users’ hot and cold wallets by simply transferring small amounts of funds to their target’s wallet address and observing the transaction’s UTXO dynamics.This type of analysis is generally based on probabilistic guessing, and associated wallets can be flagged as a risk — this is problematic when unwitting and legitimate users are considered a risk by compliance agencies. Given that regulation in the blockchain industry is not yet mature, users mistakenly deemed as a risk have no way to combat their classification. Because of this, privacy protection and blockchain security have become important considerations for the design of many new blockchain projects. More and more projects are improving the privacy and security of transactions through various methods to help users “blur” their wallet balance and transaction records, preventing their normal wallet activities from being tracked.A brief comparison of privacy protection technologiesWhen blockchain technology was first introduced, privacy was one of its core characteristics. For example, when Bitcoin is used as a payment method, all that is needed is an electronic address consisting of a string of alphanumeric characters, rather than a bank account that is connected to a personal identity, and is therefore at risk of privacy breaches. However, this level of privacy is called “pseudo-privacy”, which is similar to using a pseudonym to hide a real identity when writing a letter. Once an electronic address is obtained (or our analog “pseudonym”) and is associated with any real identity, privacy is breached. In the current information age, the cost of obtaining this information is not high. Therefore, some blockchain technology researchers have been focusing on exploring higher levels of privacy and security protection technologies.There are two main metrics used in privacy protection to evaluate a technology; relevance and traceability. For example, although Bitcoin replaces the identity information with an electronic address, we can still trace back to a certain transaction, and then find out the owner’s identity by analysing relevant information. In order to achieve a higher level of privacy and security, this relevance and traceability must be removed. Currently, the most widely used technologies to achieve this goal are ring signatures and zero-knowledge proof.Some examples of privacy protection technologies in well-known blockchains:When you spend Monero, the value of the inputs and outputs you are sending are encrypted and disguised to everyone except the receiver of each of those outputs. Pedersen commitments allow you to send Monero without revealing the value of the transactions. They also use RingCT, which allows for hidden amounts, origins and destinations of transactions with reasonable efficiency, and verifiable, trustless coin generation. In this case, people can prove that the signer (who is also the token sender) belongs to a certain “signature ring”, but cannot correspond the sender’s address and signature to any one of them.We take ZCASH as an example to explain zero-knowledge proof. Zcash addresses are either private (z-addresses) or transparent (t-addresses). Z-addresses start with a “z,” and t-addresses start with a “t.” A Z-to-Z transaction appears on the public blockchain, so it is known to have occurred and that the fee was paid. However, addresses, transaction amounts, and the memo field are all encrypted and not publicly visible. Third parties who are neither the sender nor the receiver of a transaction will not be able to obtain any information about the encrypted transaction — even the miner responsible for recording the transaction is not be able to obtain the encrypted address and the transaction amount. When an encrypted transaction is recorded, the miner is only allowed to record that “there is an unspent balance, and a transaction is generated”, and not allowed to record the blocked address and the transaction amount itself.We can see that both RingCT and zero-knowledge proof are higher-level privacy protection technologies. Zero-knowledge proof is highly dependent on a blockchain’s initial parameters. In current implementations of zero-knowledge proof technology, it is difficult to implement mobile payment methods because the signature is very large and highly affected by the network. It is worth mentioning that the HCASH development team is working on improving zero-knowledge proof tehnology to enable mobile payment methods.HCASH community member Ryan Xu also wrote, that for privacy protection and blockchain security, ring signature technology is still the best choice in the present, and pereceivable future.HCASH post-quantum linkable ring signaturesThe HyperCash team has adapted and improved current RingCT technology. Dr Joseph Liu and his team present a lattice-based post-quantum secure Ring CT protocol, that supports multi-input-multi-output transactions. It is a comprehensive Ring CT protocol, such that it contains all necessary parts including a linkable ring signature (for user anonymity), commitment scheme (for hiding the transaction amount) and range proof (to ensure the hidden value is a positive amount). All parts are in a lattice-based setting, meaning that the overall protocol is post-quantum secure.The release of this code enables other projects and users to gain access to HCASH’s version of post-quantum signature application and privacy protection. In future, the HCASH development team will continue to conduct more in-depth research in the direction of post-quantum signatures and ring signatures. Dr Joseph Liu will post an improved version of the current linkable ring signature scheme paper based on the present Monero ring signature. The upcoming paper is proposing to allow higher number of signatures by an order of magnitude three to four times greater than that of the current version of Monero. According to the HyperCash technology yellow paper, HC will continue to implement lattice-based post-quantum signature code, and become an industry leader in the protection of privacy.See HCASH’s Post-Quantum Linkable Ring Signature code at:https://github.com/chainchip/Lattice-RingCT-v2.0To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 28

Ring Signatures, Blockchai ...

The HyperCash development team has completed and released code for the implementation of Post-Quantum Linkable Ring Signatures in HC, and is now entering the deployment testing phase. This algorithm is based on a publication written by HCASH Chief Scientist, Dr Joseph Liu and his colleagues “Post-Quantum One-Time Linkable Ring Signature and Application to Ring Confidential Transactions in Blockchain”, which was published by the International Association for Cryptologic Research.Last November, Dr Joseph was announced as the Australian Computer Society’s ICT Researcher of the Year, at the 2018 Digital Disruptor Awards, recognising his ground-breaking research in advancing blockchain technology as a legitimate way to create new economic and social systems. These new developments, based on research conducted by some of the brightest minds in the industry, brings users of HC benefits from its high level of privacy and security.About ring signaturesIn cryptography, a ring signature is a type of digital signature that can be performed by any member of a group of users with cryptographic keys. A transaction message signed with a ring signature is verified by someone in a particular group of people, without revealing the public key (or identity) of the sender, receiver, the signatory or any of the other members of the group, while also withholding the transaction amount.The first cryptocurrency which successfully implemented an algorithm using ring signatures was Monero. In 2015, Dr Shen Noether published an article entitled “Ring Confidential Transactions”, which laid the foundation for the ring signature algorithm implemented in Monero.Much like Bitcoin, this implementation of the signature algorithm uses a “hash-based public key + private key” approach. The difference is, that the addition of the ring signature technology mixes the transaction sender’s public key with other public keys, and only then does it sign the information. When the receiver receives the transaction, they use their own private key to verify the signature. As such, other people (including potential malicious parties) are not able to tell which one of the public keys belongs to the sender. This gives Monero the capability of hiding the sender’s address information, making it impossible for external attackers to target the sender.In September 2017, Monero implemented a hard fork, and integrated RCT (Ring Signature Technology) to encrypt the transaction amount when making transactions, meaning that no one, except the sender and receiver can track any transaction details (including sender’s address and value of the inputs). After this, the new RCT address became the only address format for Monero.Blockchain security and privacy protectionAt the beginning of this year, blockchain analysis firm Chainalysis announced that it had received $30 million in Round B financing, led by Silicon Valley VC firm, Accel. In April last year, Chainalysis completed $16 million of Round A financing.Accel has invested in well-known companies such as Facebook, Dropbox, and Spotify, and has also shown interest blockchain technology. They believe that cryptocurrencies will achieve growth and will be subject to stricter supervision, leading them to their investment in Chainalysis.However, there are also concerns in the industry that blockchain data analysis companies such as Chainalysis, have played a role in promoting the compliance of blockchain companies, at the risk of user privacy. Foregoing user privacy systems can allow third parties to see balances in other users’ hot and cold wallets by simply transferring small amounts of funds to their target’s wallet address and observing the transaction’s UTXO dynamics.This type of analysis is generally based on probabilistic guessing, and associated wallets can be flagged as a risk — this is problematic when unwitting and legitimate users are considered a risk by compliance agencies. Given that regulation in the blockchain industry is not yet mature, users mistakenly deemed as a risk have no way to combat their classification. Because of this, privacy protection and blockchain security have become important considerations for the design of many new blockchain projects. More and more projects are improving the privacy and security of transactions through various methods to help users “blur” their wallet balance and transaction records, preventing their normal wallet activities from being tracked.A brief comparison of privacy protection technologiesWhen blockchain technology was first introduced, privacy was one of its core characteristics. For example, when Bitcoin is used as a payment method, all that is needed is an electronic address consisting of a string of alphanumeric characters, rather than a bank account that is connected to a personal identity, and is therefore at risk of privacy breaches. However, this level of privacy is called “pseudo-privacy”, which is similar to using a pseudonym to hide a real identity when writing a letter. Once an electronic address is obtained (or our analog “pseudonym”) and is associated with any real identity, privacy is breached. In the current information age, the cost of obtaining this information is not high. Therefore, some blockchain technology researchers have been focusing on exploring higher levels of privacy and security protection technologies.There are two main metrics used in privacy protection to evaluate a technology; relevance and traceability. For example, although Bitcoin replaces the identity information with an electronic address, we can still trace back to a certain transaction, and then find out the owner’s identity by analysing relevant information. In order to achieve a higher level of privacy and security, this relevance and traceability must be removed. Currently, the most widely used technologies to achieve this goal are ring signatures and zero-knowledge proof.Some examples of privacy protection technologies in well-known blockchains:When you spend Monero, the value of the inputs and outputs you are sending are encrypted and disguised to everyone except the receiver of each of those outputs. Pedersen commitments allow you to send Monero without revealing the value of the transactions. They also use RingCT, which allows for hidden amounts, origins and destinations of transactions with reasonable efficiency, and verifiable, trustless coin generation. In this case, people can prove that the signer (who is also the token sender) belongs to a certain “signature ring”, but cannot correspond the sender’s address and signature to any one of them.We take ZCASH as an example to explain zero-knowledge proof. Zcash addresses are either private (z-addresses) or transparent (t-addresses). Z-addresses start with a “z,” and t-addresses start with a “t.” A Z-to-Z transaction appears on the public blockchain, so it is known to have occurred and that the fee was paid. However, addresses, transaction amounts, and the memo field are all encrypted and not publicly visible. Third parties who are neither the sender nor the receiver of a transaction will not be able to obtain any information about the encrypted transaction — even the miner responsible for recording the transaction is not be able to obtain the encrypted address and the transaction amount. When an encrypted transaction is recorded, the miner is only allowed to record that “there is an unspent balance, and a transaction is generated”, and not allowed to record the blocked address and the transaction amount itself.We can see that both RingCT and zero-knowledge proof are higher-level privacy protection technologies. Zero-knowledge proof is highly dependent on a blockchain’s initial parameters. In current implementations of zero-knowledge proof technology, it is difficult to implement mobile payment methods because the signature is very large and highly affected by the network. It is worth mentioning that the HCASH development team is working on improving zero-knowledge proof tehnology to enable mobile payment methods.HCASH community member Ryan Xu also wrote, that for privacy protection and blockchain security, ring signature technology is still the best choice in the present, and pereceivable future.HCASH post-quantum linkable ring signaturesThe HyperCash team has adapted and improved current RingCT technology. Dr Joseph Liu and his team present a lattice-based post-quantum secure Ring CT protocol, that supports multi-input-multi-output transactions. It is a comprehensive Ring CT protocol, such that it contains all necessary parts including a linkable ring signature (for user anonymity), commitment scheme (for hiding the transaction amount) and range proof (to ensure the hidden value is a positive amount). All parts are in a lattice-based setting, meaning that the overall protocol is post-quantum secure.The release of this code enables other projects and users to gain access to HCASH’s version of post-quantum signature application and privacy protection. In future, the HCASH development team will continue to conduct more in-depth research in the direction of post-quantum signatures and ring signatures. Dr Joseph Liu will post an improved version of the current linkable ring signature scheme paper based on the present Monero ring signature. The upcoming paper is proposing to allow higher number of signatures by an order of magnitude three to four times greater than that of the current version of Monero. According to the HyperCash technology yellow paper, HC will continue to implement lattice-based post-quantum signature code, and become an industry leader in the protection of privacy.See HCASH’s Post-Quantum Linkable Ring Signature code at:https://github.com/chainchip/Lattice-RingCT-v2.0To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 28

Ring Signatures, Blockchai ...

The HyperCash development team has completed and released code for the implementation of Post-Quantum Linkable Ring Signatures in HC, and is now entering the deployment testing phase. This algorithm is based on a publication written by HCASH Chief Scientist, Dr Joseph Liu and his colleagues “Post-Quantum One-Time Linkable Ring Signature and Application to Ring Confidential Transactions in Blockchain”, which was published by the International Association for Cryptologic Research.Last November, Dr Joseph was announced as the Australian Computer Society’s ICT Researcher of the Year, at the 2018 Digital Disruptor Awards, recognising his ground-breaking research in advancing blockchain technology as a legitimate way to create new economic and social systems. These new developments, based on research conducted by some of the brightest minds in the industry, brings users of HC benefits from its high level of privacy and security.About ring signaturesIn cryptography, a ring signature is a type of digital signature that can be performed by any member of a group of users with cryptographic keys. A transaction message signed with a ring signature is verified by someone in a particular group of people, without revealing the public key (or identity) of the sender, receiver, the signatory or any of the other members of the group, while also withholding the transaction amount.The first cryptocurrency which successfully implemented an algorithm using ring signatures was Monero. In 2015, Dr Shen Noether published an article entitled “Ring Confidential Transactions”, which laid the foundation for the ring signature algorithm implemented in Monero.Much like Bitcoin, this implementation of the signature algorithm uses a “hash-based public key + private key” approach. The difference is, that the addition of the ring signature technology mixes the transaction sender’s public key with other public keys, and only then does it sign the information. When the receiver receives the transaction, they use their own private key to verify the signature. As such, other people (including potential malicious parties) are not able to tell which one of the public keys belongs to the sender. This gives Monero the capability of hiding the sender’s address information, making it impossible for external attackers to target the sender.In September 2017, Monero implemented a hard fork, and integrated RCT (Ring Signature Technology) to encrypt the transaction amount when making transactions, meaning that no one, except the sender and receiver can track any transaction details (including sender’s address and value of the inputs). After this, the new RCT address became the only address format for Monero.Blockchain security and privacy protectionAt the beginning of this year, blockchain analysis firm Chainalysis announced that it had received $30 million in Round B financing, led by Silicon Valley VC firm, Accel. In April last year, Chainalysis completed $16 million of Round A financing.Accel has invested in well-known companies such as Facebook, Dropbox, and Spotify, and has also shown interest blockchain technology. They believe that cryptocurrencies will achieve growth and will be subject to stricter supervision, leading them to their investment in Chainalysis.However, there are also concerns in the industry that blockchain data analysis companies such as Chainalysis, have played a role in promoting the compliance of blockchain companies, at the risk of user privacy. Foregoing user privacy systems can allow third parties to see balances in other users’ hot and cold wallets by simply transferring small amounts of funds to their target’s wallet address and observing the transaction’s UTXO dynamics.This type of analysis is generally based on probabilistic guessing, and associated wallets can be flagged as a risk — this is problematic when unwitting and legitimate users are considered a risk by compliance agencies. Given that regulation in the blockchain industry is not yet mature, users mistakenly deemed as a risk have no way to combat their classification. Because of this, privacy protection and blockchain security have become important considerations for the design of many new blockchain projects. More and more projects are improving the privacy and security of transactions through various methods to help users “blur” their wallet balance and transaction records, preventing their normal wallet activities from being tracked.A brief comparison of privacy protection technologiesWhen blockchain technology was first introduced, privacy was one of its core characteristics. For example, when Bitcoin is used as a payment method, all that is needed is an electronic address consisting of a string of alphanumeric characters, rather than a bank account that is connected to a personal identity, and is therefore at risk of privacy breaches. However, this level of privacy is called “pseudo-privacy”, which is similar to using a pseudonym to hide a real identity when writing a letter. Once an electronic address is obtained (or our analog “pseudonym”) and is associated with any real identity, privacy is breached. In the current information age, the cost of obtaining this information is not high. Therefore, some blockchain technology researchers have been focusing on exploring higher levels of privacy and security protection technologies.There are two main metrics used in privacy protection to evaluate a technology; relevance and traceability. For example, although Bitcoin replaces the identity information with an electronic address, we can still trace back to a certain transaction, and then find out the owner’s identity by analysing relevant information. In order to achieve a higher level of privacy and security, this relevance and traceability must be removed. Currently, the most widely used technologies to achieve this goal are ring signatures and zero-knowledge proof.Some examples of privacy protection technologies in well-known blockchains:When you spend Monero, the value of the inputs and outputs you are sending are encrypted and disguised to everyone except the receiver of each of those outputs. Pedersen commitments allow you to send Monero without revealing the value of the transactions. They also use RingCT, which allows for hidden amounts, origins and destinations of transactions with reasonable efficiency, and verifiable, trustless coin generation. In this case, people can prove that the signer (who is also the token sender) belongs to a certain “signature ring”, but cannot correspond the sender’s address and signature to any one of them.We take ZCASH as an example to explain zero-knowledge proof. Zcash addresses are either private (z-addresses) or transparent (t-addresses). Z-addresses start with a “z,” and t-addresses start with a “t.” A Z-to-Z transaction appears on the public blockchain, so it is known to have occurred and that the fee was paid. However, addresses, transaction amounts, and the memo field are all encrypted and not publicly visible. Third parties who are neither the sender nor the receiver of a transaction will not be able to obtain any information about the encrypted transaction — even the miner responsible for recording the transaction is not be able to obtain the encrypted address and the transaction amount. When an encrypted transaction is recorded, the miner is only allowed to record that “there is an unspent balance, and a transaction is generated”, and not allowed to record the blocked address and the transaction amount itself.We can see that both RingCT and zero-knowledge proof are higher-level privacy protection technologies. Zero-knowledge proof is highly dependent on a blockchain’s initial parameters. In current implementations of zero-knowledge proof technology, it is difficult to implement mobile payment methods because the signature is very large and highly affected by the network. It is worth mentioning that the HCASH development team is working on improving zero-knowledge proof tehnology to enable mobile payment methods.HCASH community member Ryan Xu also wrote, that for privacy protection and blockchain security, ring signature technology is still the best choice in the present, and pereceivable future.HCASH post-quantum linkable ring signaturesThe HyperCash team has adapted and improved current RingCT technology. Dr Joseph Liu and his team present a lattice-based post-quantum secure Ring CT protocol, that supports multi-input-multi-output transactions. It is a comprehensive Ring CT protocol, such that it contains all necessary parts including a linkable ring signature (for user anonymity), commitment scheme (for hiding the transaction amount) and range proof (to ensure the hidden value is a positive amount). All parts are in a lattice-based setting, meaning that the overall protocol is post-quantum secure.The release of this code enables other projects and users to gain access to HCASH’s version of post-quantum signature application and privacy protection. In future, the HCASH development team will continue to conduct more in-depth research in the direction of post-quantum signatures and ring signatures. Dr Joseph Liu will post an improved version of the current linkable ring signature scheme paper based on the present Monero ring signature. The upcoming paper is proposing to allow higher number of signatures by an order of magnitude three to four times greater than that of the current version of Monero. According to the HyperCash technology yellow paper, HC will continue to implement lattice-based post-quantum signature code, and become an industry leader in the protection of privacy.See HCASH’s Post-Quantum Linkable Ring Signature code at:https://github.com/chainchip/Lattice-RingCT-v2.0To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 28

Why go ASIC Resistant?

Since HCASH released its yellow paper in July 2018, the Foundation have been continually reviewing methods of preventing ASIC mining hardware from being deployed, as wide-spread ASIC mining use could effectively create computing power monopolies; a system whereby one or a small number of powerful miners dominate a blockchain network.Today, after half a year of research and development, the HyperCash team are ready to deploy their new ASIC-resistant algorithm.The origins of ASIC mining (and its resistance), and the threat of computing power monopoliesHyperCash is not the only project that has realised the potential harm that could be caused by ASIC mining to communities and network stability.More and more projects are now developing ASIC resistant mining machines.Take Monero for example. When Bitmain released an ASIC mining machine capable of mining Monero and other CryptoNight algorithm tokens, the Monero community became deeply concerned as it quickly became apparent that the computing power of these mining machines would be way higher than any other mining machine currently in use, thus enabling a monopoly to be formed. To counteract this, the Monero community swiftly decided to change their mining algorithm via a hard fork, to one that incorporates ASIC resistance. The hard fork outcome was widely welcomed by Monero miners and community members. Since the fork, the price of the Monero token has risen sharply (indicating its perceived value) and is widely known as a cryptocurrency whereby GPU mining is still attainable and profitable; something that is considered important to those still viewing cryptocurrencies as a ‘tool for the everyman’, and not another outlet for faceless companies to earn profits from. Further efforts to keep this status-quo have been implemented by Monero’s team. The project announced through social media channels that they will revise their current mining algorithm every 6 months to prevent against new ASIC hardware being developed and implemented, and ultimately, threatening the network.Another example is Zcash. Zcash, another cryptocurrency that is resistant to ASIC mining machines have gone so far as to set up a technical advisory committee in charge of providing scientific advice on how to remain ASIC-resistant.Lastly, Ethereum. Just earlier this year, Ethereum’s (ETH) core developers reached a preliminary consensus agreement to implement a new Proof-of-Work (PoW) algorithm that will improve GPU-based efficiency — instead of relying on ASIC-based network mining. It is believed that this approach will not only make ASIC mining more “difficult”, but will also stabilize the networks hash value.From here, the question must be asked: why do so many blockchain projects have the desire to resist ASIC mining hardware? To understand this, we must understand exactly what an ASIC mining machine is.When Satoshi Nakamoto was first developing Bitcoin, in his original vision he hoped that people could use home computers to mine tokens. Specifically, he believed that people would rely merely on their CPUs to validate transactions. However, with the increasing value of Bitcoin and other cryptocurrencies, mining has become an industry, leading to increase competitiveness and ultimately, difficulty. Therefore, miners started to purchase and use more advanced hardware, and soon after, companies began appearing with the sole intent of researching, developing and updating specialised hardware to mine tokens that utilise specific algorithms, thus the term ‘application-specific integrated circuit’ miner or ASIC miner slowly grew into the widespread phenomenon it is today.The reason for this was that CPUs overall act as general-purpose processers. This means that while they are great at processing a multitude of different functions, they’re not effective at completing specific individual tasks. An example of this can be seen in graphics computing. In terms of graphics processing and 3D computing, it’s clear that CPUs aren’t as good at doing this as GPUs are, hence the creation and widespread adoption of GPUs.An extension of this are ASIC miners. To mine Bitcoin all a computer needs to do is calculate SHA256 hash values; a singular function. And again, even though a general-purpose CPU can calculate these values, they’re not very effective when considering cost and efficiency. Therefore, mining companies have designed application-specific chips whose primary function is for SHA256 (and other algorithms, depending on the token) calculations. Because it is designed to process a specific algorithm, the design of the ASIC chip is much more simple and less expensive than a CPU; and most importantly, in terms of computing power, they are (generally) tens of thousands or more times higher than currently used CPUs and GPUs.This makes it difficult to mine with normal CPUs and limits the market to those with large amounts of resources to spend on specialised hardware with a singular purpose, and access to cheap power.This usually limited the participation pool to professional mining organizations. This phenomenon has led to the emergence of ‘mining tyrants’, leading to a higher and higher entry barrier for those looking to become a miner, which effectively blocks ordinary users from being involved. This, we believe, is not in line with what blockchain networks were meant to be, and thus, we’ve decided to take a stance against it.The threat of centralization caused by a mining monopolyLast year, the Bitcoin Cash (BCH) Hard Fork battle led to the price of Bitcoin falling to below $6,000 USD overnight, and once to nearly $3,000. This unpredictable price drop added to the cryptocurrency markets instability and volatility.The reason that these fluctuations occurred was that during the hard fork, a battle was being waged by two major miners. In this battle, the computing power that was used to maintain normal operations of the BCH blockchain (via mining pools) were being used for other purposes, thus partially compromising the security of the chain, backlogging the validation and processing of transactions due to the now lack of computational power, and, ultimately sowing the seeds of doubt into users minds regarding the stability, longevity and independence of the network.The most questionable thing that has occurred during this phenomenon is the behaviour of the so called “mining tyrants”, whose actions negatively affect the common interests of all blockchain users. Unless dealt with, blockchain will be no different than any other centralised mechanism.Blockchain has always been viewed as a ‘decentralised’ technology. It’s a technology that was marketed as being more independent, fair and democratic. This technology has a large potential to change the world, especially considering its advancements in ledger technology and widespread appeal. However, if computing power becomes monopolised and ordinary users lose their ability to participate, then it begs the question: Is this new system any better than the last centralised system we moved from? Obviously, the potential of mining monopolies casts a shadow on the entire blockchain industry, and it will inevitably chip away at fundamentalist beliefs of the technology, thus, it must be addressed.The rise of Blockchain monopolies heavily affect network securityMonopolies that may form within a network such as BTC, ETH and others not only have the effect of causing centralisation, but also damage the stability and security of the network.These monopolies, that often take the form of mining pools sometimes employ dubious methods to increase their block rate higher than their computing power ratio. These methods include using ASIC boost, selfish mining, eclipse attacks and other means that enable these pools to conduct a 51% attack without needing to own 51% of the computational power on the network. An example can be seen on the XVG blockchain, where a mining tyrant achieved a 51% attack while only owning 10% of the total computational power on the network.ASIC-resistant mining machines and technological progressionWith what’s already been said above it seems fairly clear that ASIC-resistance should be something that all networks should strive to implement, however, there are some objections to these resistant technologies.Some people consider ASIC machines as part of the natural course of progression relating to advancements in science and technology. Others believe that the advent of ASIC mining machines, which can mine faster and cheaper serve a vital purpose of reducing network costs. The fear within some communities is that as networks move away from mining machines and those machines spawn from technological progression, that means that the networks themselves are shying away from that same technological progression; they’re trying to live against technology.In this regard, we must clarify that ASIC hardware is not technically considered to be a natural step in scientific and/or technological progression. Technological progression would imply that things on a network level are becoming more efficient, but they aren’t. If that were true then the network would be using less electricity, which isn’t the case when it comes to bitcoin for example. When Bitcoin first came out in 2009, Nakamoto used his own home computer to mine 7,200 BTC while using only several kWh’s of electricity per day. Now, tens of thousands of high-performance machines (including ASIC machines) around the world mine around 1,800 BTC while consuming millions of kWh’s of electricity per day. This hardware competition that is ultimately fuelled by ASIC mining machines has led to us consuming more energy than necessary. What’s more is that Bitcoin’s block rate is constant, and the blockchain network throughput is more dependent on the speed of the network, rather than the hardware. Thus, we don’t believe that implementing ASIC resistance means to rally against progression, rather, the opposite.ASIC mining machines have increased barriers to entry, which is not conducive to the popularisation and development of blockchain technologyPreviously, ordinary, household individuals were able to participate in the blockchain industry via mining if they had a computer to mine with, even if they didn’t know much about cryptocurrency or couldn’t afford an ASIC mining machine. What’s more, ASIC mining machines, whose target clients are large mining pools and large net worth individuals, are currently monopolised by a limited number of manufacturers.The value of blockchain itself comes from consensus, and consensus comes from the participation of more and more people. The higher the participation rate, the more popular blockchain will be, and the more popular that blockchain is, the more stable and healthy the price of the cryptocurrency. In other words, the more decentralised the environment, the more fair and secure the industry.It can then be derived that the advantages of high speed mining machines do not in-fact aid the network, but merely line the pockets of their owners with more tokens, as the block rate is unaffected. So, ASIC mining machines do not actually promote the development of a network from a technical point of view; on the contrary, it hinders the participation of ordinary people.Thus, in order to prevent against problems caused by monopolies, many new blockchain projects have abandoned the PoW algorithm and have turned to PoW and DPoS algorithms, such as seen in EOS. However, the governance of EOS super nodes have also been questioned. For example, many people think that their super nodes and cloud servers makes it almost impossible for most ordinary users to participate. If blockchains can be centralised, are they still considered as blockchains in the most fundamental sense?The HC team proposed in our yellow paper that the PoW algorithm has been recognised as the safest and most fair consensus algorithm after ten years of community testing, and as such, it should not be abandoned fully due to the potential of monopolies appearing. Thus, as a compromise, the HC team adopted a PoW+PoS hybrid consensus in its mainchain to maintain security, with the additional features and benefits of the PoS consensus mechanism.The combination of the two creates an excellent consensus algorithm for fostering strengths and avoiding shortcomings. The HC team has been preparing solutions for hidden dangers such as mining tyrants and centralised problems by developing and deploying ASIC-resistant algorithms.In conclusion, ASIC-resistant algorithms are necessary to increase community participation and secure network security. The ultimate goal of ASIC-resistant algorithms for each blockchain project, including HC, is not to resist ASIC mining machines, but to reduce barriers to entry, and to create a distributed PoW ecosystem that is as fair as accessible.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 27

Why go ASIC Resistant?

Since HCASH released its yellow paper in July 2018, the Foundation have been continually reviewing methods of preventing ASIC mining hardware from being deployed, as wide-spread ASIC mining use could effectively create computing power monopolies; a system whereby one or a small number of powerful miners dominate a blockchain network.Today, after half a year of research and development, the HyperCash team are ready to deploy their new ASIC-resistant algorithm.The origins of ASIC mining (and its resistance), and the threat of computing power monopoliesHyperCash is not the only project that has realised the potential harm that could be caused by ASIC mining to communities and network stability.More and more projects are now developing ASIC resistant mining machines.Take Monero for example. When Bitmain released an ASIC mining machine capable of mining Monero and other CryptoNight algorithm tokens, the Monero community became deeply concerned as it quickly became apparent that the computing power of these mining machines would be way higher than any other mining machine currently in use, thus enabling a monopoly to be formed. To counteract this, the Monero community swiftly decided to change their mining algorithm via a hard fork, to one that incorporates ASIC resistance. The hard fork outcome was widely welcomed by Monero miners and community members. Since the fork, the price of the Monero token has risen sharply (indicating its perceived value) and is widely known as a cryptocurrency whereby GPU mining is still attainable and profitable; something that is considered important to those still viewing cryptocurrencies as a ‘tool for the everyman’, and not another outlet for faceless companies to earn profits from. Further efforts to keep this status-quo have been implemented by Monero’s team. The project announced through social media channels that they will revise their current mining algorithm every 6 months to prevent against new ASIC hardware being developed and implemented, and ultimately, threatening the network.Another example is Zcash. Zcash, another cryptocurrency that is resistant to ASIC mining machines have gone so far as to set up a technical advisory committee in charge of providing scientific advice on how to remain ASIC-resistant.Lastly, Ethereum. Just earlier this year, Ethereum’s (ETH) core developers reached a preliminary consensus agreement to implement a new Proof-of-Work (PoW) algorithm that will improve GPU-based efficiency — instead of relying on ASIC-based network mining. It is believed that this approach will not only make ASIC mining more “difficult”, but will also stabilize the networks hash value.From here, the question must be asked: why do so many blockchain projects have the desire to resist ASIC mining hardware? To understand this, we must understand exactly what an ASIC mining machine is.When Satoshi Nakamoto was first developing Bitcoin, in his original vision he hoped that people could use home computers to mine tokens. Specifically, he believed that people would rely merely on their CPUs to validate transactions. However, with the increasing value of Bitcoin and other cryptocurrencies, mining has become an industry, leading to increase competitiveness and ultimately, difficulty. Therefore, miners started to purchase and use more advanced hardware, and soon after, companies began appearing with the sole intent of researching, developing and updating specialised hardware to mine tokens that utilise specific algorithms, thus the term ‘application-specific integrated circuit’ miner or ASIC miner slowly grew into the widespread phenomenon it is today.The reason for this was that CPUs overall act as general-purpose processers. This means that while they are great at processing a multitude of different functions, they’re not effective at completing specific individual tasks. An example of this can be seen in graphics computing. In terms of graphics processing and 3D computing, it’s clear that CPUs aren’t as good at doing this as GPUs are, hence the creation and widespread adoption of GPUs.An extension of this are ASIC miners. To mine Bitcoin all a computer needs to do is calculate SHA256 hash values; a singular function. And again, even though a general-purpose CPU can calculate these values, they’re not very effective when considering cost and efficiency. Therefore, mining companies have designed application-specific chips whose primary function is for SHA256 (and other algorithms, depending on the token) calculations. Because it is designed to process a specific algorithm, the design of the ASIC chip is much more simple and less expensive than a CPU; and most importantly, in terms of computing power, they are (generally) tens of thousands or more times higher than currently used CPUs and GPUs.This makes it difficult to mine with normal CPUs and limits the market to those with large amounts of resources to spend on specialised hardware with a singular purpose, and access to cheap power.This usually limited the participation pool to professional mining organizations. This phenomenon has led to the emergence of ‘mining tyrants’, leading to a higher and higher entry barrier for those looking to become a miner, which effectively blocks ordinary users from being involved. This, we believe, is not in line with what blockchain networks were meant to be, and thus, we’ve decided to take a stance against it.The threat of centralization caused by a mining monopolyLast year, the Bitcoin Cash (BCH) Hard Fork battle led to the price of Bitcoin falling to below $6,000 USD overnight, and once to nearly $3,000. This unpredictable price drop added to the cryptocurrency markets instability and volatility.The reason that these fluctuations occurred was that during the hard fork, a battle was being waged by two major miners. In this battle, the computing power that was used to maintain normal operations of the BCH blockchain (via mining pools) were being used for other purposes, thus partially compromising the security of the chain, backlogging the validation and processing of transactions due to the now lack of computational power, and, ultimately sowing the seeds of doubt into users minds regarding the stability, longevity and independence of the network.The most questionable thing that has occurred during this phenomenon is the behaviour of the so called “mining tyrants”, whose actions negatively affect the common interests of all blockchain users. Unless dealt with, blockchain will be no different than any other centralised mechanism.Blockchain has always been viewed as a ‘decentralised’ technology. It’s a technology that was marketed as being more independent, fair and democratic. This technology has a large potential to change the world, especially considering its advancements in ledger technology and widespread appeal. However, if computing power becomes monopolised and ordinary users lose their ability to participate, then it begs the question: Is this new system any better than the last centralised system we moved from? Obviously, the potential of mining monopolies casts a shadow on the entire blockchain industry, and it will inevitably chip away at fundamentalist beliefs of the technology, thus, it must be addressed.The rise of Blockchain monopolies heavily affect network securityMonopolies that may form within a network such as BTC, ETH and others not only have the effect of causing centralisation, but also damage the stability and security of the network.These monopolies, that often take the form of mining pools sometimes employ dubious methods to increase their block rate higher than their computing power ratio. These methods include using ASIC boost, selfish mining, eclipse attacks and other means that enable these pools to conduct a 51% attack without needing to own 51% of the computational power on the network. An example can be seen on the XVG blockchain, where a mining tyrant achieved a 51% attack while only owning 10% of the total computational power on the network.ASIC-resistant mining machines and technological progressionWith what’s already been said above it seems fairly clear that ASIC-resistance should be something that all networks should strive to implement, however, there are some objections to these resistant technologies.Some people consider ASIC machines as part of the natural course of progression relating to advancements in science and technology. Others believe that the advent of ASIC mining machines, which can mine faster and cheaper serve a vital purpose of reducing network costs. The fear within some communities is that as networks move away from mining machines and those machines spawn from technological progression, that means that the networks themselves are shying away from that same technological progression; they’re trying to live against technology.In this regard, we must clarify that ASIC hardware is not technically considered to be a natural step in scientific and/or technological progression. Technological progression would imply that things on a network level are becoming more efficient, but they aren’t. If that were true then the network would be using less electricity, which isn’t the case when it comes to bitcoin for example. When Bitcoin first came out in 2009, Nakamoto used his own home computer to mine 7,200 BTC while using only several kWh’s of electricity per day. Now, tens of thousands of high-performance machines (including ASIC machines) around the world mine around 1,800 BTC while consuming millions of kWh’s of electricity per day. This hardware competition that is ultimately fuelled by ASIC mining machines has led to us consuming more energy than necessary. What’s more is that Bitcoin’s block rate is constant, and the blockchain network throughput is more dependent on the speed of the network, rather than the hardware. Thus, we don’t believe that implementing ASIC resistance means to rally against progression, rather, the opposite.ASIC mining machines have increased barriers to entry, which is not conducive to the popularisation and development of blockchain technologyPreviously, ordinary, household individuals were able to participate in the blockchain industry via mining if they had a computer to mine with, even if they didn’t know much about cryptocurrency or couldn’t afford an ASIC mining machine. What’s more, ASIC mining machines, whose target clients are large mining pools and large net worth individuals, are currently monopolised by a limited number of manufacturers.The value of blockchain itself comes from consensus, and consensus comes from the participation of more and more people. The higher the participation rate, the more popular blockchain will be, and the more popular that blockchain is, the more stable and healthy the price of the cryptocurrency. In other words, the more decentralised the environment, the more fair and secure the industry.It can then be derived that the advantages of high speed mining machines do not in-fact aid the network, but merely line the pockets of their owners with more tokens, as the block rate is unaffected. So, ASIC mining machines do not actually promote the development of a network from a technical point of view; on the contrary, it hinders the participation of ordinary people.Thus, in order to prevent against problems caused by monopolies, many new blockchain projects have abandoned the PoW algorithm and have turned to PoW and DPoS algorithms, such as seen in EOS. However, the governance of EOS super nodes have also been questioned. For example, many people think that their super nodes and cloud servers makes it almost impossible for most ordinary users to participate. If blockchains can be centralised, are they still considered as blockchains in the most fundamental sense?The HC team proposed in our yellow paper that the PoW algorithm has been recognised as the safest and most fair consensus algorithm after ten years of community testing, and as such, it should not be abandoned fully due to the potential of monopolies appearing. Thus, as a compromise, the HC team adopted a PoW+PoS hybrid consensus in its mainchain to maintain security, with the additional features and benefits of the PoS consensus mechanism.The combination of the two creates an excellent consensus algorithm for fostering strengths and avoiding shortcomings. The HC team has been preparing solutions for hidden dangers such as mining tyrants and centralised problems by developing and deploying ASIC-resistant algorithms.In conclusion, ASIC-resistant algorithms are necessary to increase community participation and secure network security. The ultimate goal of ASIC-resistant algorithms for each blockchain project, including HC, is not to resist ASIC mining machines, but to reduce barriers to entry, and to create a distributed PoW ecosystem that is as fair as accessible.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 27

Why go ASIC Resistant?

Since HCASH released its yellow paper in July 2018, the Foundation have been continually reviewing methods of preventing ASIC mining hardware from being deployed, as wide-spread ASIC mining use could effectively create computing power monopolies; a system whereby one or a small number of powerful miners dominate a blockchain network.Today, after half a year of research and development, the HyperCash team are ready to deploy their new ASIC-resistant algorithm.The origins of ASIC mining (and its resistance), and the threat of computing power monopoliesHyperCash is not the only project that has realised the potential harm that could be caused by ASIC mining to communities and network stability.More and more projects are now developing ASIC resistant mining machines.Take Monero for example. When Bitmain released an ASIC mining machine capable of mining Monero and other CryptoNight algorithm tokens, the Monero community became deeply concerned as it quickly became apparent that the computing power of these mining machines would be way higher than any other mining machine currently in use, thus enabling a monopoly to be formed. To counteract this, the Monero community swiftly decided to change their mining algorithm via a hard fork, to one that incorporates ASIC resistance. The hard fork outcome was widely welcomed by Monero miners and community members. Since the fork, the price of the Monero token has risen sharply (indicating its perceived value) and is widely known as a cryptocurrency whereby GPU mining is still attainable and profitable; something that is considered important to those still viewing cryptocurrencies as a ‘tool for the everyman’, and not another outlet for faceless companies to earn profits from. Further efforts to keep this status-quo have been implemented by Monero’s team. The project announced through social media channels that they will revise their current mining algorithm every 6 months to prevent against new ASIC hardware being developed and implemented, and ultimately, threatening the network.Another example is Zcash. Zcash, another cryptocurrency that is resistant to ASIC mining machines have gone so far as to set up a technical advisory committee in charge of providing scientific advice on how to remain ASIC-resistant.Lastly, Ethereum. Just earlier this year, Ethereum’s (ETH) core developers reached a preliminary consensus agreement to implement a new Proof-of-Work (PoW) algorithm that will improve GPU-based efficiency — instead of relying on ASIC-based network mining. It is believed that this approach will not only make ASIC mining more “difficult”, but will also stabilize the networks hash value.From here, the question must be asked: why do so many blockchain projects have the desire to resist ASIC mining hardware? To understand this, we must understand exactly what an ASIC mining machine is.When Satoshi Nakamoto was first developing Bitcoin, in his original vision he hoped that people could use home computers to mine tokens. Specifically, he believed that people would rely merely on their CPUs to validate transactions. However, with the increasing value of Bitcoin and other cryptocurrencies, mining has become an industry, leading to increase competitiveness and ultimately, difficulty. Therefore, miners started to purchase and use more advanced hardware, and soon after, companies began appearing with the sole intent of researching, developing and updating specialised hardware to mine tokens that utilise specific algorithms, thus the term ‘application-specific integrated circuit’ miner or ASIC miner slowly grew into the widespread phenomenon it is today.The reason for this was that CPUs overall act as general-purpose processers. This means that while they are great at processing a multitude of different functions, they’re not effective at completing specific individual tasks. An example of this can be seen in graphics computing. In terms of graphics processing and 3D computing, it’s clear that CPUs aren’t as good at doing this as GPUs are, hence the creation and widespread adoption of GPUs.An extension of this are ASIC miners. To mine Bitcoin all a computer needs to do is calculate SHA256 hash values; a singular function. And again, even though a general-purpose CPU can calculate these values, they’re not very effective when considering cost and efficiency. Therefore, mining companies have designed application-specific chips whose primary function is for SHA256 (and other algorithms, depending on the token) calculations. Because it is designed to process a specific algorithm, the design of the ASIC chip is much more simple and less expensive than a CPU; and most importantly, in terms of computing power, they are (generally) tens of thousands or more times higher than currently used CPUs and GPUs.This makes it difficult to mine with normal CPUs and limits the market to those with large amounts of resources to spend on specialised hardware with a singular purpose, and access to cheap power.This usually limited the participation pool to professional mining organizations. This phenomenon has led to the emergence of ‘mining tyrants’, leading to a higher and higher entry barrier for those looking to become a miner, which effectively blocks ordinary users from being involved. This, we believe, is not in line with what blockchain networks were meant to be, and thus, we’ve decided to take a stance against it.The threat of centralization caused by a mining monopolyLast year, the Bitcoin Cash (BCH) Hard Fork battle led to the price of Bitcoin falling to below $6,000 USD overnight, and once to nearly $3,000. This unpredictable price drop added to the cryptocurrency markets instability and volatility.The reason that these fluctuations occurred was that during the hard fork, a battle was being waged by two major miners. In this battle, the computing power that was used to maintain normal operations of the BCH blockchain (via mining pools) were being used for other purposes, thus partially compromising the security of the chain, backlogging the validation and processing of transactions due to the now lack of computational power, and, ultimately sowing the seeds of doubt into users minds regarding the stability, longevity and independence of the network.The most questionable thing that has occurred during this phenomenon is the behaviour of the so called “mining tyrants”, whose actions negatively affect the common interests of all blockchain users. Unless dealt with, blockchain will be no different than any other centralised mechanism.Blockchain has always been viewed as a ‘decentralised’ technology. It’s a technology that was marketed as being more independent, fair and democratic. This technology has a large potential to change the world, especially considering its advancements in ledger technology and widespread appeal. However, if computing power becomes monopolised and ordinary users lose their ability to participate, then it begs the question: Is this new system any better than the last centralised system we moved from? Obviously, the potential of mining monopolies casts a shadow on the entire blockchain industry, and it will inevitably chip away at fundamentalist beliefs of the technology, thus, it must be addressed.The rise of Blockchain monopolies heavily affect network securityMonopolies that may form within a network such as BTC, ETH and others not only have the effect of causing centralisation, but also damage the stability and security of the network.These monopolies, that often take the form of mining pools sometimes employ dubious methods to increase their block rate higher than their computing power ratio. These methods include using ASIC boost, selfish mining, eclipse attacks and other means that enable these pools to conduct a 51% attack without needing to own 51% of the computational power on the network. An example can be seen on the XVG blockchain, where a mining tyrant achieved a 51% attack while only owning 10% of the total computational power on the network.ASIC-resistant mining machines and technological progressionWith what’s already been said above it seems fairly clear that ASIC-resistance should be something that all networks should strive to implement, however, there are some objections to these resistant technologies.Some people consider ASIC machines as part of the natural course of progression relating to advancements in science and technology. Others believe that the advent of ASIC mining machines, which can mine faster and cheaper serve a vital purpose of reducing network costs. The fear within some communities is that as networks move away from mining machines and those machines spawn from technological progression, that means that the networks themselves are shying away from that same technological progression; they’re trying to live against technology.In this regard, we must clarify that ASIC hardware is not technically considered to be a natural step in scientific and/or technological progression. Technological progression would imply that things on a network level are becoming more efficient, but they aren’t. If that were true then the network would be using less electricity, which isn’t the case when it comes to bitcoin for example. When Bitcoin first came out in 2009, Nakamoto used his own home computer to mine 7,200 BTC while using only several kWh’s of electricity per day. Now, tens of thousands of high-performance machines (including ASIC machines) around the world mine around 1,800 BTC while consuming millions of kWh’s of electricity per day. This hardware competition that is ultimately fuelled by ASIC mining machines has led to us consuming more energy than necessary. What’s more is that Bitcoin’s block rate is constant, and the blockchain network throughput is more dependent on the speed of the network, rather than the hardware. Thus, we don’t believe that implementing ASIC resistance means to rally against progression, rather, the opposite.ASIC mining machines have increased barriers to entry, which is not conducive to the popularisation and development of blockchain technologyPreviously, ordinary, household individuals were able to participate in the blockchain industry via mining if they had a computer to mine with, even if they didn’t know much about cryptocurrency or couldn’t afford an ASIC mining machine. What’s more, ASIC mining machines, whose target clients are large mining pools and large net worth individuals, are currently monopolised by a limited number of manufacturers.The value of blockchain itself comes from consensus, and consensus comes from the participation of more and more people. The higher the participation rate, the more popular blockchain will be, and the more popular that blockchain is, the more stable and healthy the price of the cryptocurrency. In other words, the more decentralised the environment, the more fair and secure the industry.It can then be derived that the advantages of high speed mining machines do not in-fact aid the network, but merely line the pockets of their owners with more tokens, as the block rate is unaffected. So, ASIC mining machines do not actually promote the development of a network from a technical point of view; on the contrary, it hinders the participation of ordinary people.Thus, in order to prevent against problems caused by monopolies, many new blockchain projects have abandoned the PoW algorithm and have turned to PoW and DPoS algorithms, such as seen in EOS. However, the governance of EOS super nodes have also been questioned. For example, many people think that their super nodes and cloud servers makes it almost impossible for most ordinary users to participate. If blockchains can be centralised, are they still considered as blockchains in the most fundamental sense?The HC team proposed in our yellow paper that the PoW algorithm has been recognised as the safest and most fair consensus algorithm after ten years of community testing, and as such, it should not be abandoned fully due to the potential of monopolies appearing. Thus, as a compromise, the HC team adopted a PoW+PoS hybrid consensus in its mainchain to maintain security, with the additional features and benefits of the PoS consensus mechanism.The combination of the two creates an excellent consensus algorithm for fostering strengths and avoiding shortcomings. The HC team has been preparing solutions for hidden dangers such as mining tyrants and centralised problems by developing and deploying ASIC-resistant algorithms.In conclusion, ASIC-resistant algorithms are necessary to increase community participation and secure network security. The ultimate goal of ASIC-resistant algorithms for each blockchain project, including HC, is not to resist ASIC mining machines, but to reduce barriers to entry, and to create a distributed PoW ecosystem that is as fair as accessible.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 27

Why go ASIC Resistant?

Since HCASH released its yellow paper in July 2018, the Foundation have been continually reviewing methods of preventing ASIC mining hardware from being deployed, as wide-spread ASIC mining use could effectively create computing power monopolies; a system whereby one or a small number of powerful miners dominate a blockchain network.Today, after half a year of research and development, the HyperCash team are ready to deploy their new ASIC-resistant algorithm.The origins of ASIC mining (and its resistance), and the threat of computing power monopoliesHyperCash is not the only project that has realised the potential harm that could be caused by ASIC mining to communities and network stability.More and more projects are now developing ASIC resistant mining machines.Take Monero for example. When Bitmain released an ASIC mining machine capable of mining Monero and other CryptoNight algorithm tokens, the Monero community became deeply concerned as it quickly became apparent that the computing power of these mining machines would be way higher than any other mining machine currently in use, thus enabling a monopoly to be formed. To counteract this, the Monero community swiftly decided to change their mining algorithm via a hard fork, to one that incorporates ASIC resistance. The hard fork outcome was widely welcomed by Monero miners and community members. Since the fork, the price of the Monero token has risen sharply (indicating its perceived value) and is widely known as a cryptocurrency whereby GPU mining is still attainable and profitable; something that is considered important to those still viewing cryptocurrencies as a ‘tool for the everyman’, and not another outlet for faceless companies to earn profits from. Further efforts to keep this status-quo have been implemented by Monero’s team. The project announced through social media channels that they will revise their current mining algorithm every 6 months to prevent against new ASIC hardware being developed and implemented, and ultimately, threatening the network.Another example is Zcash. Zcash, another cryptocurrency that is resistant to ASIC mining machines have gone so far as to set up a technical advisory committee in charge of providing scientific advice on how to remain ASIC-resistant.Lastly, Ethereum. Just earlier this year, Ethereum’s (ETH) core developers reached a preliminary consensus agreement to implement a new Proof-of-Work (PoW) algorithm that will improve GPU-based efficiency — instead of relying on ASIC-based network mining. It is believed that this approach will not only make ASIC mining more “difficult”, but will also stabilize the networks hash value.From here, the question must be asked: why do so many blockchain projects have the desire to resist ASIC mining hardware? To understand this, we must understand exactly what an ASIC mining machine is.When Satoshi Nakamoto was first developing Bitcoin, in his original vision he hoped that people could use home computers to mine tokens. Specifically, he believed that people would rely merely on their CPUs to validate transactions. However, with the increasing value of Bitcoin and other cryptocurrencies, mining has become an industry, leading to increase competitiveness and ultimately, difficulty. Therefore, miners started to purchase and use more advanced hardware, and soon after, companies began appearing with the sole intent of researching, developing and updating specialised hardware to mine tokens that utilise specific algorithms, thus the term ‘application-specific integrated circuit’ miner or ASIC miner slowly grew into the widespread phenomenon it is today.The reason for this was that CPUs overall act as general-purpose processers. This means that while they are great at processing a multitude of different functions, they’re not effective at completing specific individual tasks. An example of this can be seen in graphics computing. In terms of graphics processing and 3D computing, it’s clear that CPUs aren’t as good at doing this as GPUs are, hence the creation and widespread adoption of GPUs.An extension of this are ASIC miners. To mine Bitcoin all a computer needs to do is calculate SHA256 hash values; a singular function. And again, even though a general-purpose CPU can calculate these values, they’re not very effective when considering cost and efficiency. Therefore, mining companies have designed application-specific chips whose primary function is for SHA256 (and other algorithms, depending on the token) calculations. Because it is designed to process a specific algorithm, the design of the ASIC chip is much more simple and less expensive than a CPU; and most importantly, in terms of computing power, they are (generally) tens of thousands or more times higher than currently used CPUs and GPUs.This makes it difficult to mine with normal CPUs and limits the market to those with large amounts of resources to spend on specialised hardware with a singular purpose, and access to cheap power.This usually limited the participation pool to professional mining organizations. This phenomenon has led to the emergence of ‘mining tyrants’, leading to a higher and higher entry barrier for those looking to become a miner, which effectively blocks ordinary users from being involved. This, we believe, is not in line with what blockchain networks were meant to be, and thus, we’ve decided to take a stance against it.The threat of centralization caused by a mining monopolyLast year, the Bitcoin Cash (BCH) Hard Fork battle led to the price of Bitcoin falling to below $6,000 USD overnight, and once to nearly $3,000. This unpredictable price drop added to the cryptocurrency markets instability and volatility.The reason that these fluctuations occurred was that during the hard fork, a battle was being waged by two major miners. In this battle, the computing power that was used to maintain normal operations of the BCH blockchain (via mining pools) were being used for other purposes, thus partially compromising the security of the chain, backlogging the validation and processing of transactions due to the now lack of computational power, and, ultimately sowing the seeds of doubt into users minds regarding the stability, longevity and independence of the network.The most questionable thing that has occurred during this phenomenon is the behaviour of the so called “mining tyrants”, whose actions negatively affect the common interests of all blockchain users. Unless dealt with, blockchain will be no different than any other centralised mechanism.Blockchain has always been viewed as a ‘decentralised’ technology. It’s a technology that was marketed as being more independent, fair and democratic. This technology has a large potential to change the world, especially considering its advancements in ledger technology and widespread appeal. However, if computing power becomes monopolised and ordinary users lose their ability to participate, then it begs the question: Is this new system any better than the last centralised system we moved from? Obviously, the potential of mining monopolies casts a shadow on the entire blockchain industry, and it will inevitably chip away at fundamentalist beliefs of the technology, thus, it must be addressed.The rise of Blockchain monopolies heavily affect network securityMonopolies that may form within a network such as BTC, ETH and others not only have the effect of causing centralisation, but also damage the stability and security of the network.These monopolies, that often take the form of mining pools sometimes employ dubious methods to increase their block rate higher than their computing power ratio. These methods include using ASIC boost, selfish mining, eclipse attacks and other means that enable these pools to conduct a 51% attack without needing to own 51% of the computational power on the network. An example can be seen on the XVG blockchain, where a mining tyrant achieved a 51% attack while only owning 10% of the total computational power on the network.ASIC-resistant mining machines and technological progressionWith what’s already been said above it seems fairly clear that ASIC-resistance should be something that all networks should strive to implement, however, there are some objections to these resistant technologies.Some people consider ASIC machines as part of the natural course of progression relating to advancements in science and technology. Others believe that the advent of ASIC mining machines, which can mine faster and cheaper serve a vital purpose of reducing network costs. The fear within some communities is that as networks move away from mining machines and those machines spawn from technological progression, that means that the networks themselves are shying away from that same technological progression; they’re trying to live against technology.In this regard, we must clarify that ASIC hardware is not technically considered to be a natural step in scientific and/or technological progression. Technological progression would imply that things on a network level are becoming more efficient, but they aren’t. If that were true then the network would be using less electricity, which isn’t the case when it comes to bitcoin for example. When Bitcoin first came out in 2009, Nakamoto used his own home computer to mine 7,200 BTC while using only several kWh’s of electricity per day. Now, tens of thousands of high-performance machines (including ASIC machines) around the world mine around 1,800 BTC while consuming millions of kWh’s of electricity per day. This hardware competition that is ultimately fuelled by ASIC mining machines has led to us consuming more energy than necessary. What’s more is that Bitcoin’s block rate is constant, and the blockchain network throughput is more dependent on the speed of the network, rather than the hardware. Thus, we don’t believe that implementing ASIC resistance means to rally against progression, rather, the opposite.ASIC mining machines have increased barriers to entry, which is not conducive to the popularisation and development of blockchain technologyPreviously, ordinary, household individuals were able to participate in the blockchain industry via mining if they had a computer to mine with, even if they didn’t know much about cryptocurrency or couldn’t afford an ASIC mining machine. What’s more, ASIC mining machines, whose target clients are large mining pools and large net worth individuals, are currently monopolised by a limited number of manufacturers.The value of blockchain itself comes from consensus, and consensus comes from the participation of more and more people. The higher the participation rate, the more popular blockchain will be, and the more popular that blockchain is, the more stable and healthy the price of the cryptocurrency. In other words, the more decentralised the environment, the more fair and secure the industry.It can then be derived that the advantages of high speed mining machines do not in-fact aid the network, but merely line the pockets of their owners with more tokens, as the block rate is unaffected. So, ASIC mining machines do not actually promote the development of a network from a technical point of view; on the contrary, it hinders the participation of ordinary people.Thus, in order to prevent against problems caused by monopolies, many new blockchain projects have abandoned the PoW algorithm and have turned to PoW and DPoS algorithms, such as seen in EOS. However, the governance of EOS super nodes have also been questioned. For example, many people think that their super nodes and cloud servers makes it almost impossible for most ordinary users to participate. If blockchains can be centralised, are they still considered as blockchains in the most fundamental sense?The HC team proposed in our yellow paper that the PoW algorithm has been recognised as the safest and most fair consensus algorithm after ten years of community testing, and as such, it should not be abandoned fully due to the potential of monopolies appearing. Thus, as a compromise, the HC team adopted a PoW+PoS hybrid consensus in its mainchain to maintain security, with the additional features and benefits of the PoS consensus mechanism.The combination of the two creates an excellent consensus algorithm for fostering strengths and avoiding shortcomings. The HC team has been preparing solutions for hidden dangers such as mining tyrants and centralised problems by developing and deploying ASIC-resistant algorithms.In conclusion, ASIC-resistant algorithms are necessary to increase community participation and secure network security. The ultimate goal of ASIC-resistant algorithms for each blockchain project, including HC, is not to resist ASIC mining machines, but to reduce barriers to entry, and to create a distributed PoW ecosystem that is as fair as accessible.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 27

Weekly Development Update

15–21 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HChcGUIIncreased block rescanning speedHyperExchange/HXHX coreDeveloped customised multi-signature API for SenatorsAdded USDT assetHX IndicatorAdded order history to HX Exchange pageOptimised lock-in contractAdded USDT assetHX IDEAdapted new debugging return data formatHX ToolsConducted tests for HX Exchange market data collection and query interface code developmentOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop getinfo and getblock functionality on ASIC resistant mining algorithmHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageImplement special account for deposits and transactionsOptimise HX contract storage performanceHX IndicatorAdd K line featureHX IDEAdd TcpListener and data acquisition channel to UVM and debugger separationCompile debugger on macOS systemsHX ToolsDevelop HX Exchange commission inquiry HTML5 pageDevelop HX Exchange HTML5 home pageConduct tests on HX peripheral toolsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 22

Weekly Development Update

15–21 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HChcGUIIncreased block rescanning speedHyperExchange/HXHX coreDeveloped customised multi-signature API for SenatorsAdded USDT assetHX IndicatorAdded order history to HX Exchange pageOptimised lock-in contractAdded USDT assetHX IDEAdapted new debugging return data formatHX ToolsConducted tests for HX Exchange market data collection and query interface code developmentOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop getinfo and getblock functionality on ASIC resistant mining algorithmHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageImplement special account for deposits and transactionsOptimise HX contract storage performanceHX IndicatorAdd K line featureHX IDEAdd TcpListener and data acquisition channel to UVM and debugger separationCompile debugger on macOS systemsHX ToolsDevelop HX Exchange commission inquiry HTML5 pageDevelop HX Exchange HTML5 home pageConduct tests on HX peripheral toolsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 22

Weekly Development Update

15–21 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HChcGUIIncreased block rescanning speedHyperExchange/HXHX coreDeveloped customised multi-signature API for SenatorsAdded USDT assetHX IndicatorAdded order history to HX Exchange pageOptimised lock-in contractAdded USDT assetHX IDEAdapted new debugging return data formatHX ToolsConducted tests for HX Exchange market data collection and query interface code developmentOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop getinfo and getblock functionality on ASIC resistant mining algorithmHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageImplement special account for deposits and transactionsOptimise HX contract storage performanceHX IndicatorAdd K line featureHX IDEAdd TcpListener and data acquisition channel to UVM and debugger separationCompile debugger on macOS systemsHX ToolsDevelop HX Exchange commission inquiry HTML5 pageDevelop HX Exchange HTML5 home pageConduct tests on HX peripheral toolsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 22

Weekly Development Update

15–21 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HChcGUIIncreased block rescanning speedHyperExchange/HXHX coreDeveloped customised multi-signature API for SenatorsAdded USDT assetHX IndicatorAdded order history to HX Exchange pageOptimised lock-in contractAdded USDT assetHX IDEAdapted new debugging return data formatHX ToolsConducted tests for HX Exchange market data collection and query interface code developmentOngoing work:HyperCash/HCHcdAdjust and develop mainnet parametersDevelop getinfo and getblock functionality on ASIC resistant mining algorithmHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportConduct DApp researchHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageImplement special account for deposits and transactionsOptimise HX contract storage performanceHX IndicatorAdd K line featureHX IDEAdd TcpListener and data acquisition channel to UVM and debugger separationCompile debugger on macOS systemsHX ToolsDevelop HX Exchange commission inquiry HTML5 pageDevelop HX Exchange HTML5 home pageConduct tests on HX peripheral toolsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 22

Weekly Development Update

08 — 14 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdDevelopment on ASIC resistant mining algorithm:— Block processing logic— Difficulty level adjustment algorithmExchangesCompleted HSR to HC swap for BitpieTechnical supportSupported community members in completing HSR to HC swapHyperExchange/HXHX coreTested USDT integrationHX IndicatorCompleted MD5 check for node clientOptimised transaction status display of failed transactions to contract addressAdded Citizen proposer name to proposal displayHX IDEModified data format for debugger and IDE interactionsModified data sending API on debuggerHX ToolsHX Exchange market data collection and query interface code developmentData collection and query interface tests for HX Exchange K line developmentOngoing work:HyperCash/HCHcdDevelopment on ASIC resistant mining algorithm:— develop getinfo and getblock functionalityHcwalletDevelopment on block validation on ASIC resistant mining algorithmhcGUIIncrease rescan speedTechnical supportConduct research for DApp developmentHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageDevelop customised multi-signature API for SenatorsHX IndicatorAdd order history to HX Exchange pageFix several bugsHX IDEFix bugs that occur after debugger API is modifiedCompile debugger on macOS systemsHX ToolsConduct tests for HX Exchange market data collection and query interface code developmentConduct research for HX Exchange developmentConduct tests on HX peripheral toolsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 15

Weekly Development Update

08 — 14 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdDevelopment on ASIC resistant mining algorithm:— Block processing logic— Difficulty level adjustment algorithmExchangesCompleted HSR to HC swap for BitpieTechnical supportSupported community members in completing HSR to HC swapHyperExchange/HXHX coreTested USDT integrationHX IndicatorCompleted MD5 check for node clientOptimised transaction status display of failed transactions to contract addressAdded Citizen proposer name to proposal displayHX IDEModified data format for debugger and IDE interactionsModified data sending API on debuggerHX ToolsHX Exchange market data collection and query interface code developmentData collection and query interface tests for HX Exchange K line developmentOngoing work:HyperCash/HCHcdDevelopment on ASIC resistant mining algorithm:— develop getinfo and getblock functionalityHcwalletDevelopment on block validation on ASIC resistant mining algorithmhcGUIIncrease rescan speedTechnical supportConduct research for DApp developmentHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageDevelop customised multi-signature API for SenatorsHX IndicatorAdd order history to HX Exchange pageFix several bugsHX IDEFix bugs that occur after debugger API is modifiedCompile debugger on macOS systemsHX ToolsConduct tests for HX Exchange market data collection and query interface code developmentConduct research for HX Exchange developmentConduct tests on HX peripheral toolsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 15

Weekly Development Update

08 — 14 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdDevelopment on ASIC resistant mining algorithm:— Block processing logic— Difficulty level adjustment algorithmExchangesCompleted HSR to HC swap for BitpieTechnical supportSupported community members in completing HSR to HC swapHyperExchange/HXHX coreTested USDT integrationHX IndicatorCompleted MD5 check for node clientOptimised transaction status display of failed transactions to contract addressAdded Citizen proposer name to proposal displayHX IDEModified data format for debugger and IDE interactionsModified data sending API on debuggerHX ToolsHX Exchange market data collection and query interface code developmentData collection and query interface tests for HX Exchange K line developmentOngoing work:HyperCash/HCHcdDevelopment on ASIC resistant mining algorithm:— develop getinfo and getblock functionalityHcwalletDevelopment on block validation on ASIC resistant mining algorithmhcGUIIncrease rescan speedTechnical supportConduct research for DApp developmentHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageDevelop customised multi-signature API for SenatorsHX IndicatorAdd order history to HX Exchange pageFix several bugsHX IDEFix bugs that occur after debugger API is modifiedCompile debugger on macOS systemsHX ToolsConduct tests for HX Exchange market data collection and query interface code developmentConduct research for HX Exchange developmentConduct tests on HX peripheral toolsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 15

Weekly Development Update

08 — 14 Feb 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdDevelopment on ASIC resistant mining algorithm:— Block processing logic— Difficulty level adjustment algorithmExchangesCompleted HSR to HC swap for BitpieTechnical supportSupported community members in completing HSR to HC swapHyperExchange/HXHX coreTested USDT integrationHX IndicatorCompleted MD5 check for node clientOptimised transaction status display of failed transactions to contract addressAdded Citizen proposer name to proposal displayHX IDEModified data format for debugger and IDE interactionsModified data sending API on debuggerHX ToolsHX Exchange market data collection and query interface code developmentData collection and query interface tests for HX Exchange K line developmentOngoing work:HyperCash/HCHcdDevelopment on ASIC resistant mining algorithm:— develop getinfo and getblock functionalityHcwalletDevelopment on block validation on ASIC resistant mining algorithmhcGUIIncrease rescan speedTechnical supportConduct research for DApp developmentHcAutonomyPrepare for new proposalsHyperExchange/HXHX coreAdd K line feature to HX Exchange pageDevelop customised multi-signature API for SenatorsHX IndicatorAdd order history to HX Exchange pageFix several bugsHX IDEFix bugs that occur after debugger API is modifiedCompile debugger on macOS systemsHX ToolsConduct tests for HX Exchange market data collection and query interface code developmentConduct research for HX Exchange developmentConduct tests on HX peripheral toolsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 15

HyperCash completed Post-Q ...

The HyperCash development team has completed the Post-Quantum Linkable Ring Signature code development and is entering the deployment testing phase. This algorism is based on the HCASH Chief Scientist Dr Joseph Liu ‘s publication “Post-Quantum One-Time Linkable Ring Signature and Application to Ring Confidential Transactions in Blockchain” published on IACR(International Association for Cryptologic Research).In this version, we present a lattice-based post-quantum secure Ring CT protocol, that supports multi-input-multi-output transactions. It is a comprehensive Ring CT protocol such that it contains all necessary parts including linkable ring signature (for user anonymity), commitment scheme (for hiding transaction amount) and range proof (to ensure the hidden value is a positive amount). All parts are in a lattice-based setting, meaning that the overall protocol is post-quantum secure.Now HyperCash will be the world’s first cryptocurrency to implement Post-quantum Ring Signature algorithms.Journal: https://eprint.iacr.org/2018/379.pdfPlease keep an eye on HCASH announcement channels for updates regarding the HyperCash Post-Quantum Linkable Ring Signature, and more. We hope you will enjoy the launch of our new function and we appreciate your support.We are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of HCASH.For more information regarding Hcash, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 08

HyperCash completed Post-Q ...

The HyperCash development team has completed the Post-Quantum Linkable Ring Signature code development and is entering the deployment testing phase. This algorism is based on the HCASH Chief Scientist Dr Joseph Liu ‘s publication “Post-Quantum One-Time Linkable Ring Signature and Application to Ring Confidential Transactions in Blockchain” published on IACR(International Association for Cryptologic Research).In this version, we present a lattice-based post-quantum secure Ring CT protocol, that supports multi-input-multi-output transactions. It is a comprehensive Ring CT protocol such that it contains all necessary parts including linkable ring signature (for user anonymity), commitment scheme (for hiding transaction amount) and range proof (to ensure the hidden value is a positive amount). All parts are in a lattice-based setting, meaning that the overall protocol is post-quantum secure.Now HyperCash will be the world’s first cryptocurrency to implement Post-quantum Ring Signature algorithms.Journal: https://eprint.iacr.org/2018/379.pdfPlease keep an eye on HCASH announcement channels for updates regarding the HyperCash Post-Quantum Linkable Ring Signature, and more. We hope you will enjoy the launch of our new function and we appreciate your support.We are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of HCASH.For more information regarding Hcash, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 08

HyperCash completed Post-Q ...

The HyperCash development team has completed the Post-Quantum Linkable Ring Signature code development and is entering the deployment testing phase. This algorism is based on the HCASH Chief Scientist Dr Joseph Liu ‘s publication “Post-Quantum One-Time Linkable Ring Signature and Application to Ring Confidential Transactions in Blockchain” published on IACR(International Association for Cryptologic Research).In this version, we present a lattice-based post-quantum secure Ring CT protocol, that supports multi-input-multi-output transactions. It is a comprehensive Ring CT protocol such that it contains all necessary parts including linkable ring signature (for user anonymity), commitment scheme (for hiding transaction amount) and range proof (to ensure the hidden value is a positive amount). All parts are in a lattice-based setting, meaning that the overall protocol is post-quantum secure.Now HyperCash will be the world’s first cryptocurrency to implement Post-quantum Ring Signature algorithms.Journal: https://eprint.iacr.org/2018/379.pdfPlease keep an eye on HCASH announcement channels for updates regarding the HyperCash Post-Quantum Linkable Ring Signature, and more. We hope you will enjoy the launch of our new function and we appreciate your support.We are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of HCASH.For more information regarding Hcash, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 08

Weekly Development Update

1–7 February 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdCompleted technical evaluation of ASIC resistant mining algorithmhcExplorerAdded block generation monitoring functionalityExchangesCompleted HSR to HC swap for BitpieTechnical supportSupported community members to complete HSR to HC swapHcAutonomyCompleted testing on mainnet proposalHyperExchange/HXHX coreHX middleware network optimizationHX IndicatorHX token lock contract functionExchange order book recordingHX IDEOptimized IDE contract templateHX ToolsWorkshop on hx order matching page displayOngoing work:Hypercash/HCHcdDevelopment on ASIC resistant mining algorithm: — Block processing logic — getinfo and getblock functionality — difficulty level adjustment algorithmHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportSupporting community members to complete HSR to HC swapHyperExchange/HXHX coreHX exchange K line data processingTesting on merging HC crosschain withdrawal requestsHX senator election processHX IndicatorFurther optimization on UI elementsTesting and bug fixingHX IDEModify IDE data interaction APICompile MAC version of the IDEHX ToolsTesting on auxiliary toolsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 08

Weekly Development Update

1–7 February 2019The following is a weekly progress report from the HCASH development team. This report is divided in two parts: completed and ongoing work.Our GitHub code can be found here: www.github.com/HcashOrgPlease 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/HCHcdCompleted technical evaluation of ASIC resistant mining algorithmhcExplorerAdded block generation monitoring functionalityExchangesCompleted HSR to HC swap for BitpieTechnical supportSupported community members to complete HSR to HC swapHcAutonomyCompleted testing on mainnet proposalHyperExchange/HXHX coreHX middleware network optimizationHX IndicatorHX token lock contract functionExchange order book recordingHX IDEOptimized IDE contract templateHX ToolsWorkshop on hx order matching page displayOngoing work:Hypercash/HCHcdDevelopment on ASIC resistant mining algorithm: — Block processing logic — getinfo and getblock functionality — difficulty level adjustment algorithmHcwalletDevelopment on block validation on ASIC resistant mining algorithmTechnical supportSupporting community members to complete HSR to HC swapHyperExchange/HXHX coreHX exchange K line data processingTesting on merging HC crosschain withdrawal requestsHX senator election processHX IndicatorFurther optimization on UI elementsTesting and bug fixingHX IDEModify IDE data interaction APICompile MAC version of the IDEHX ToolsTesting on auxiliary toolsWe are grateful for the immense effort made by all contributors. Each contributor and community member is vital to the technical development of the HCASH ecosystem.To stay up to date with information, or to join our community, check out the following channels:Twitter, Facebook, Reddit, English Telegram, Chinese Telegram, Korean Telegram, Korean Announcements, KakaoTalk, Naver Blog

HyperCash

19. 02. 08

거래소
거래소 마켓 시세 거래량 주소
Binance 추후 제공 추후 제공 추후 제공 바로 가기
BITHUMB 추후 제공 추후 제공 추후 제공 바로 가기
OKEx 추후 제공 추후 제공 추후 제공 바로 가기
Kucoin 추후 제공 추후 제공 추후 제공 바로 가기
ACX 추후 제공 추후 제공 추후 제공 바로 가기
CoinExchange 추후 제공 추후 제공 추후 제공 바로 가기
EXX 추후 제공 추후 제공 추후 제공 바로 가기
Hadax 추후 제공 추후 제공 추후 제공 바로 가기
ZB 추후 제공 추후 제공 추후 제공 바로 가기
취약성 검증

해당 팀의 취약성 검증 결과가 없습니다.
취약성 검증은 왜 필요할까요?

더 알아보기

코멘트 0

* 작성된 질문 내용은 수정 변경이 되지 않습니다.

* 질문에는 토큰팀 담당자가 직접 답변합니다.

Information
Platform ERC20
Accepting
Hard cap -
Audit -
Stage -
Location -
주요 코인 시세 *2019년 03월 26 기준

비트코인

BTC

4,481,084.37 KRW 1.77%

이더리움

ETH

152,568.52 KRW 1.74%

리플

XRP

341.66 KRW 2.23%

라이트코인

LTC

66,607.44 KRW 2.20%

이오스

EOS

4,136.43 KRW 0.40%

비트코인 캐시

BCH

178,819.04 KRW 4.47%

바이넨스 코인

BNB

18,189.25 KRW 4.74%

테더

USDT

1,142.48 KRW 0.22%

스텔라루멘

XLM

113.21 KRW 4.96%

카르다노

ADA

68.96 KRW 0.38%

트론

TRX

25.39 KRW 3.41%

비트코인 사토시 비전

BSV

72,712.08 KRW 1.60%

모네로

XMR

58,482.73 KRW 3.62%

대쉬

DASH

101,563.61 KRW 2.81%

메이커

MKR

811,602.26 KRW 1.56%

네오

NEO

10,064.66 KRW 4.07%

온톨로지

ONT

1,288.08 KRW 8.27%

이더리움 클래식

ETC

5,306.49 KRW 2.03%

XEM

56.22 KRW 2.49%

테조스

XTZ

761.40 KRW 6.67%