Hush can confirm that we are vulnerable to the Zcash inflation bug (CVE-2019-7167) and we are working on an upgrade to Sapling. More details and recommendations for those with shielded funds can be found at https://myhush.org/sapling/

March 7th, 2018

Gears are turning, commits are being made, and Hush is in "heads down" mode taking care of business.

Here's what the team has been up to and what is creeping up our "to-do" list.

• Hush has a new roadmap. It is chronological. For updates on how specific projects are progressing, tune in to our official Twitter feed or take a peek at our #github channel on http://myhush.org/discord. This is going to be an extremely productive year!
• The dev team released Hush 1.0.14 this week. This release unlocks some important features of HushList. HushNG will utilize these updates in its private messaging functionality. It includes RPC methods z_importviewingkey and z_exportviewingkey. Here's the GitHub PR with the technical details.
• We've updated our Dashboard to increase transparency regarding completed projects, where money is coming and going, and team member donation addresses.
• We have a very solid dev team now and are turning our focus heavily to fleshing out our marketing team. Hush is actively recruiting front end web developers, marketing professionals, videographers, animators, and social media enthusiasts. Want to contribute but didn't see your specialty here? Drop us a line anyway! Looking for a bounty to work on? We have those. Send work samples and your specific skill set. Contact a core team member on our Discord and we'll put you in touch with the right team/person.

As a friendly reminder, if you have a support question please reach out on myhush.org/discord. You can also engage with the rest of the Hush community at myhush.org/twitter, myhush.org/telegram, myhush.org/bitcointalk, and myhush.org/reddit.

February 20, 2018

Updates for this week.

- The numbers are complete for BTCH airdrop! Hush, Unity, and DEX holders have already been paid. Bitcoin holders are in the process of being paid right now. Instructions to receive your BTCH can be found on btchush.org/airdrop.

- The HushList command-line has been added to CPAN and can be installed via CPAN Hush : https://metacpan.org/release/Hush

- The hashReserve bug, or, 'why won't my wallet sync?'
   This has been a fairly difficult bug to get to the heart of. Bitcoin Gold (BTG) was released late last year. It borrowed the Zcash (ZEC) Proof of Work (Equihash) but BTG decided to use a field in the block header that was previously unused - the hashReserve field. The hashReserve field defaults to zero. BTG decided to put the block height in this field. This made it incompatible with the Zcash block header. Since this field was previously unused, software wasn't reading the value in it. The value was assumed to be zero. So when BTG started adding the block height, hashes started coming up incorrect.

   Months later, someone started using BTG mining software to mine other Equihash coins, like Hush. This injected the problem into those chains. Because of the incorrect hashing, nodes started getting banned.

   To fix this, the Hush dev team created a fix that reads the hashReserve field (since it is no longer safe to assume it is zero.) This also fixes zcash upstream and every zcash fork that exists. Komodo and a few other Equihash coins have already applied the Hush fix. We expect this will also fix the ongoing problems with Cryptopia.

   The fix is included in the latest release of Hush, 1.0.13.

   Here are the version [https://github.com/MyHush/hush/blob/master/release_notes.md]release notes[/url].

- The new swing wallet, due out within the next week, will use the updated release so if you use the swing wallet be sure to upgrade sooner rather than later.

- We have created some new links, to make finding us online faster and easier. 
https://www.myhush.org/bitcointalk 
https://www.myhush.org/discord 
https://www.myhush.org/reddit 
https://www.myhush.org/twitter   

https://www.btchush.org/bitcointalk 
https://www.btchush.org/discord   
https://www.btchush.org/reddit 
https://www.btchush.org/twitter 


HushNG will utilize the latest release of Hush. Installing 1.0.13 will prep your system for installation of HushNG. If you are a dev interested in working on this project please let us know. We have a great core team and continue to seek new talent.

- We also continue our search to add professionals to our Marketing Team. If you have marketing experience we'd love to hear from you!

February 15, 2018

Happy Year of the Dog!

The Hush team is moving forward at a steady pace and wanted to send out a few updates.

Would you like a little more information about the project? Coincentral wrote up a very comprehensive article on Hush a few days ago.

Team updates
We have some new faces on the core team. Several community members and Hush enthusiasts really stepped up and have been very active in moving Hush forward the last few weeks. Please join us in welcoming Bruxis and FireMartZ to our dev team. We expect we will be adding a few more team members in coming days. You can expect to see bios and more information on the new team members on myhush.org soon.

Infrastructure updates
Thanks to the efforts of the new dev team, wallet.myhush.org is running again.

We want to also thank community member peletubi for running the servers hosting explorer.myhush.org.

In response to our DNS seed (sync) problem several people are working on setting up seeders. Once those are up and stable we will let you know so you can change your config file.

Upcoming
The new Hushd repo (1.0.13) will include new dns seeds (resolves sync issues). Your system will need to run certain processes in order for HushNG to function. This version release will prep your system so that these requirements are already in place when HushNG is released.

Following the version release there will be a new Hush swing wallet release.
 
We believe that more explorers are better and should be run by multiple people outside of the Hush team. We will be publishing instructions for setting one up. In the meantime we invite the community to reach out to us on Discord if you have any technical questions about setting one up.

February 8, 2018

Hi everyone,

Just wanted to send out a quick update on what the team has been working on for the last week or so.

Team updates
Right now we have 8 new names carrying the dev role that our core dev, Duke, is working directly with. Eventually some of those folks will be invited to the core team. Currently everyone is working together on various projects with HushNG and both websites at the top of the projects list. Most recently, the watch-only fix was merged from the Windows branch to the main branch, and the process of removing the need for a special platform-specific branch was started. You can see technical details of what else the new devs have been working on on our GitHub page.

Our marketing team is busily applying to exchanges. We've completed several applications last week and have organized a list of exchanges that we are interested in learning more about and/or applying to. We've received some great feedback from the community about which exchanges might be a good fit for Hush in regards to having reasonable fees as well as being the right size for a project like Hush. We're going through those recommendations as we speak. Thank you for those.

We are still actively recruiting for both groups.

Web Wallet
Although we don't have an ETA for bringing the web wallet back up right now, we do have two workarounds. The first is to use the Agama wallet to see your Hush balance. That requires you have your private key. If you have that, use the instructions on our airdrop page to see your balance. If you don't have your private key you can download the web wallet and run it locally to retrieve your private key then use your key in Agama. The advantage of this is that everything runs locally and doesn't require sending sensitive data to a server you don't know. Downloading and running the web wallet locally is more complicated than using the web wallet and we understand that frustration. We are working on a How To to make this easier and we have a very helpful community answering questions in the support channel on Discord in the meantime.

Hush services
One unexpected consequence of our servers being taken offline is important to those of you running full Hush nodes. It has impacted the ability of Hush nodes to discover each other. This is called the DNS seed. Normally, when someone makes a request for identification of a node they receive a response indicating the nearest node. Instead of responding with the neearest node, the DNS seed responds with a *list* of known nodes, which speeds up the whole process exponentially. Now instead of trying a single address and making another request if it can't reach that one, a node has a whole list it can use. Our DNS seed was on one of the servers that were taken down and this is one of the projects that have taken precedence in the background. When this is resolved folks running full nodes should see a vast improvement in functionality. Feel free to track technical progress in GitHub.

Airdrop updates
Hush, Supernet, and Dex have all received their BTCH. As you might expect, BTC is a larger, more complex process but should be finished soon. The exact numbers and details will be in the full release of the BTCH whitepaper, which will follow shortly thereafter. We still expect to be able to meet our goal of completing the airdrop and releasing the whitepaper this month.

Next up
In addition to the projects mentioned above we will also be releasing details on HushList, our private mailing list-style messenger which utilizes zkSNARKS. We are working on a How To article with screenshots to show exactly what it looks like and how you can use it. It is currently command-line only and we are also working to provide an easier way to use it in the near future.

If you have an article, whitepaper, or how-to you would like to see, please contact us on Discord.

The community member who designed the BTCHush logo has graciously provided a design overhaul for btchush.org. We will be implementing that soon as well. We intend to provide redirect links on each website to our Discord to diminish link confusion. If links change, those pages can simply be updated to reflect the new location. A few of our new devs have also made some cosmetic changes to the Hush website. Expect to see minor changes here and there as our new group members come up to speed. There are a lot of good things going on right now. Please reach out to us on Discord if you are interested in jumping in.

Hey everyone,

Firstly, if you haven't seen instructions on how to receive your BTCH airdrop you can find them at: http://btchush.org/airdrop/.

Secondly, we have a very good start on rounding out our new marketing team and want to reach out to the community to continue to bring on the best and brightest. If you have professional marketing experience please send us examples of your work and a resume. At this time we are looking for verifiable work history (open source projects and cryptocurrency experience will, of course, send you to the top of the pile.) The marketing role is more than sending out tweets, we need people on the marketing team who can bring creative ideas on getting Hush's branding and development into the spotlight, where it belongs.

Likewise, we are already speaking to handful of developers who appear to have the drive and ability to take Hush to the next phase of our plan and want to hear from others as well. Send resumes, GitHub, and/or work examples.

Community outreach is important to us. After the recent reorganization, we are in need of Discord moderators who can ensure our forums are respectful and allow for diverging opinions without causing harm to Hush or the community itself. It is especially important in this role to be known by the community. If you are interested (or better yet, have a recommendation) please PM a moderator on Discord.

All invitations to join the above teams are considered trials to be added to the core team in the future. Our goal is to build the core team with the strongest, brightest, and most creative individuals possible. In the meantime, you will see members come and go on these teams until the right people find the right positions both for themselves and for Hush.

The instructions on how to claim BTCH and how to activate Hush in from the Agama wallet have been added to: http://btchush.org/airdrop/

As indicated in the most recent ANN, please direct Support questions to the Support channel on our Discord server.

Feel free to set that up and let the Hush team know!

January 31, 2018

We have some explaining to do.

On January 29th, two core Hush devs had a personal conflict that resulted in Hush's servers being taken offline. This action impacted the web wallet, our main explorer, and all of the BTCH code and research. It also created a huge level of Fear, Uncertainty, and Doubt within the Hush community. We'd like to lay out our plans as to how Hush will be moving forward to try and alleviate some of that unease.

As you might expect from this kind of event, the Hush Core Team has been shaken up. While we are not fond of "airing dirty laundry" so to speak (nor do we believe personal drama is interesting enough to discuss, usually) we do hold Radical Transparency as a Hush value. Therefore we wish to let the community know that the core Hush Team is now Duke Leto (Back End Dev), and Tamsin Thorn (Technical Writer). We would like to specify that no one was asked to leave the project. All team members who have decided to move on to other projects have done so on their own accord. The remaining Hush team would also like to move forward with restructuring and rebuilding. We are seeking new core members to round out our skill sets and create redundancy within the team.

We believe that the silver lining in this upheaval is the immediate and strong response by the community itself to step up. Almost immediately, a new Discord server was launched and community members started volunteering skills, donations, time, damage control, and infrastructure resources. Most excitedly, we now have a dedicated marketing team and will be focusing efforts on listing HUSH and BTCH on exchanges in upcoming days.

As far as projects go, we are concentrating on migration and recovering from recent events. HushNG is nearly complete, but launch will be delayed until the core team has enough bandwidth to finish it. Know that it is a priority for the team.

Let's talk about the BTCH merged airdrop.
The good news is that no changes will be made to the snapshot date. It remains on 1 Feb, noon UTC. We still get a lot of questions about how to receive the airdrop. We ask that you direct these questions to our #support channel in Discord so that community members can assist. The core team will be very hard pressed to answer Support questions for a while (although we are in the process of hiring a dedicated Support person.) Duke, in particular is primarily offline working on the BTCH code with jl777. Remember that this kind of merged airdrop has NEVER BEEN DONE BEFORE and the devs need to concentrate. Additionally, the server that carries BTCH data and code now needs to be recreated by hand. This is an involved process, as you can imagine.

Claiming your airdrop is also unchanged. As outlined on btchush.org, you should be able to claim your BTCH sometime in Feb. We are working hard to make sure that doesn't get pushed back too far. Having to recreate the server has thrown a wrench in that timeline. But rest assured, it will still happen. For now, Hold your HUSH until the snapshot and you'll be able to claim BTCH in the future.

From btchush.org:

What can you do to help?
We can always use more people in Discord fielding Support questions. If you are interested in getting involved with interactions with exchanges and pools let us know. And if you are a developer we definitely want to hear from you. Send us your resume and/or github info. Lastly, this incident has outlined a specific need to crowd-source new explorers. There should be multiple explorers, not just one. And those should be controlled by independent entities, not just the creators of Hush. It is in the everyone's interest to be able to independently verify transactions. If you create an explorer, please do let us know.

The party responsible for bringing down the servers did reinstate them temporarily to assist with transition. They have given us until tomorrow to migrate. All of our focus will be on this task today since this impacts the web wallet and the explorer. Thank you for your patience and understanding.

Edit: TheTrunk is no longer with the team.

If the entire supply is in circulation, what is there to mine? If your goal is mining, Hush is a better coin for you.

Bitcoin Hush (BTCH) is not something that has ever existed before. It is a Komodo (KMD) asset chain with imported Unspent Transaction Output (UTXO) datasets from four different blockchains (HUSH, SUPERNET, DEX, BTC). It dumps that value onto a fifth, brand-new chain. It does not fork from KMD, nor does it fork from BTC or HUSH. It is technically NOT A FORK, but a merged airdrop.

Why you want BTCH:
Besides getting the airdrop, as a KMD asset chain BTCH takes full advantage of the KMD ecosystem (utilizing tech like dPOW and dICO). The names involved in the creation of BTCH, jl777 (KMD) & Duke Leto (HUSH), are some of the best and brightest in the industry. BTCH is a new coin to try out new ideas that are simply impossible with any blockchain that currently exists. As a KMD asset chain, it will inherit future KMD technology and updates. It is the DaVinci's Workshop of blockchain technology and already has *lots* of eyes on it.

Why you *still* want HUSH:
HUSH is the mother chain to BTCH, and has it’s own network. It’s not going anywhere. HUSH is profitable to mine (with webmining coming back soon), but not BTCH since it's entire supply will be in circulation. HUSH still has a low circulating supply (less than 15%) and will have on-chain public HushLists before any other coin. HushNG (Hush's all-in-one high speed messaging, transaction, and asset platform) is also about to be released.  

What exchanges support BTCH?
The first exchange to support BTCH will be BarterDEX. Atomic swaps have already been completed with KMD and BTCH. Others will follow later.

What is the total supply?
21,000,000 coins, like Satoshi intended.

Where can I read the technical specs?
Keep an eye on our website, btchush.org for our whitepaper. A pre-release will be out soon, followed by the full whitepaper after the snapshot date. (The full whitepaper will be out after the snapshot in order to include data from the snapshot itself.)

How do I get the airdrop?
You must have control of the private key (i.e. not on a centralized exchange!) for your transparent address (taddr). If you have HUSH in a shielded address (zaddr) you must migrate it to a taddr before the snapshot date in order to receive the airdrop. (Or you may simply choose to continue to enjoy the privacy zkSNARKs provides to your zaddr.) Soon after the snapshot date, BTCH will release our own wallet. Take your HUSH taddr private key and import it to that wallet to unlock your BTCH. You may also use your private key in BarterDEX or Agama to receive the airdrop.

A block height will be chosen closest to (but not later than) 12pm NOON UTC on Feb 1st 2018.

Unconfirmed transactions (in flight) WILL NOT BE COUNTED. The mempool will be ignored!!!!  

For each 1 HUSH, you will get 1 BTCH.  
For each 1 SUPERNET/Unity, you will get 1 BTCH.  
For each 1 DEX, you will get 1 BTCH.  
For each 1 BTC, you will get 1 BTCH.  

Social media
Twitter | Discord | Facebook

January 25th Hush team update


It may seem like it's been a fairly quiet week on the surface but that's because the Hush/BTCH team has been in "heads down" mode. Here's what we've finished and what we're working on.

Critical updates:

• The $BTCH snapshot was pushed back to Feb 1 due to community feedback on problems moving Hush to wallets. Although we don't support 3rd party products, we have a running dialogue in our #support-wallets channel on Discord.

Completed projects:

• SSL on btchush.org has been fixed.
• One of our community members put up a $BTCH explorer. Be sure to check out the built-in rich list.
• BTCH mainnet is online. Want to run your own $BTCH full node? We have instructions on how to do that.

Development updates:

• HushNG is progressing quickly. If you'd like to check it out, you can find the repo here. If you'd like to help, we need help on these items.
• There will be a BTCH Whitepaper pre-release soon. The full whitepaper will be released after the snapshot so that it can include data from the snapshot date.
• Our web wallet is expecting an update this week in regards to max characters, translations, and potentially style.
• We have a number of bounties that we can use a hand with. Please see the appropriate GitHub link for individual project status and point of contact and track us down in Discord.
• If you are interested in helping with translations please connect with our translation team via transifex or in our #translation-team channel on Discord.

News:

• BarterDEX was added to coinmarketcap.com.
• Zgold, a new airdrop for $HUSH holders has been announced. The snapshot date is Jan 3. If you held Hush in a wallet where you controlled the private keys before this date you will receive the airdrop. Zgold will initially trade on BarterDEX.
• $BTCH has a new logo and is working on the design for the website.

---
Community Outreach:
Hush is an open-source, community-driven project. If you're interested in getting involved, let us know. We have a number of entry points to join the hush team. We're especially interested in talking with you if you have any of the following skills or experience: 
web design 
graphic design 
support 
bitcore 
node.js 
electron 
ipfs 
i2p 
accounting 
community managing 
zkSNARKs 

Announcement 6 January, 2018

Critical updates:

• We recently learned of the Swing GUI "watchonly" Bug (see our last announcement for details). We'd like to add that if you use BarterDEX, it does create watchonly addresses. If you then use the SWING wallet, BE CAREFUL! It will show you watchonly addresses but those addresses are not owned by you directly in your Hush wallet but rather in BarterDEX. Funds sent to those addresses can be accessed in BarterDEX only. Not in Hush.

Development Updates:

• We have updated our website, myhush.org. It is powered by our github repository. As everything in the cryptocurrency world goes, things move fast and furiously. Expect to see a slew of new bounties soon!
• HUSH is included in yesterday's ElectrumX 1.2.1 release. This introduces the ability for wallets to avoid downloading all transaction history.
• The wallet module of HushNG is nearing completion and will replace the GUI wallet as an OFFICIALLY SUPPORTED wallet by the Hush Core Team.
• Our web wallet is back online. https://wallet.myhush.org/
• Bitcore+TLS+1.0.13 is available here: https://github.com/MyHush/hush/tree/v1.0.13-bitcoreTLS

Community Outreach: Hush is an open-source, community-driven project. If you're interested in getting involved, let us know. We have a number of entry points to join the hush team. We're especially interested in talking with you (https://discord.io/hush) if you have any of the following skills or experience:

• web design
• bitcore
• node.js
• electron
• ipfs
• i2p
• accounting
• community managing
• zkSNARKs

Critical announce: Swing GUI "watchonly" Bug

The HUSH team has learned of an upstream ZEC change which has caused a bug in the Swing wallet GUI. The "Own Addresses" tab shows the addresses a user owns and the addresses a user is watching. Watched addresses can be owned by someone else. This means it is possible to send a transaction to an address you don't own.

List of affected SWING wallets: Hush, ZenCash, Zero, ZCash, ZClassic

Workaround: The Hush team is not responsible for Swing software fixes. It would seem prudent that users create a new address so ownership is known absolutely rather than using a previously existing address that you aren't positive about.

Please direct inquires to:
https://github.com/vaklinov?tab=repositories
https://github.com/vaklinov/hush-swing-wallet-ui

A Busy Month

December has been an extremely busy month for HUSH.

We’ve published the white paper on HushList (https://github.com/leto/hushlist/blob/master/whitepaper/protocol.pdf), authored by David Mercer (radix42) and Duke Leto. It details the technical specifications for our zk-snarks communications layer and is portable to other ZEC forks.

Development on HushNG (lead by Matt Reichardt) remains an active project. This platform will serve as messenger, wallet, and miner platform all-in-one.

We've added fresh talent to our already well-established core team. We’ve removed the ‘Lead’ designation to allow more contributors to participate simultaneously. Progress has invigorated new initiatives in marketing, design, community, and core development.


Infrastructure updates

Madbuda is extending hushd compatibility with Bitcore. This allows HUSH to be used with services like BitPay, Copay, Streamium. The insight-api will provide a simple gateway for companies to accept HUSH as payment. One thing this extension will allow is a website chat box to use the HUSH blockchain via the HUSH Explorer API. We are working towards porting this functionality to other forks down the road.

We migrated myhush.org to CloudFlare for DDoS protection and will be releasing the redesign very soon. The new design will include our updated road map, the recently released Hushlist whitepaper, and discuss our inclusion on the BarterDex exchange and the Agama wallet.


HushNG and HushList

HUSH Next-Generation is our all-in-one platform that includes the Private Messenger, Wallet, GUI Miner, and Asset Issuance. HushNG is a high-speed messaging, transaction and asset platform for the blockchain.

Hushlist is a program which allows encrypted mailing-list style communications via Hush transactions. It takes advantage of zk-snarks, allowing you to send messages anonymously.



Core Team

Our established core dev team includes Duke Leto, Larry Ludlow and Matthew Reichardt.

David Mercer (radix42) is now contributing upstream of the core development team, working hard to improve Zcash GUI wallets which will be merged into Hush core when complete. David remains a wealth of knowledge to the project as his work on Zcash and other projects informs and guides Hush development. A heartfelt thanks from the Hush community for in getting Hush to where it is.

Kent Sommers has opted to remain a contributor of HUSH, albeit from outside the core title. His work on TLS, deterministic builds, and Zcash upstream integrations is invaluable to the project.

Iolar (Demartini) helps with our website.

TheTrunk is a new team member and is working with Infrastructure and Community. He created the original web wallet, managed some bitcore ports, and is working on a new explorer.

Luge is the website designer, working on HushNG, as well as various network and wallet properties.

Axel 'SparkIt' Karlsson continues to help us interact with our community.

clamoring (https://www.linkedin.com/in/tamsin-thorn-a5178383/) is another new team member and is heading up the technical writing for Hush. She has enterprise-level experience in encryption and network engineering as well as a healthy interest in cryptocurrency. Her experience translating dev jargon to management-speak allows her to explain very technical content to non-technical audiences.



Moving Forward

Our development is more active than ever and community interaction remains a top priority. The next few weeks we are concentrating on closing out some development tasks, re-launching myhush.org, and releasing v.1.0.13 (which will include: deterministic builds, secure nodes and updated default peers).

We are thoughtfully moving forward with applications to a number of high-profile exchanges. Our most recent application is with Binance Community Coin of the Month.

To stay caught up with the HUSH Team, please visit our new Community Dashboard (http://dashboard.myhush.org/), our Discord Channel (https://discordapp.com/invite/7bB78U4), or follow @myhushteam or @dukeleto on Twitter.

Thank you for your support as we steer HUSH through these exciting times!