Updated details [ZEC] ZCASH + Announcing Zcash Cloud Mining

  • ZCASH [ZEC] Release Wallet v1.0.13-rc1

    Zcash v1.0.13-rc1 release



  • ZCASH [ZEC] Dev Update - Release, UX & Integration,Powers of Tau Ceremony, Next AMA


    This week we started testing the RC for 1.0.13. We intend to keep a Monday release date but in the end we decided to drop payment offloading8 being introduced as an experimental feature due to lack of necessary review time before the RC deadline. That said, it’s in really great shape for the following 1.0.14 release.

    Everything that’s been merged in and is undergoing testing can be seen in the release planning Github project6. This includes the introduction of payment disclosure6 as an experimental feature. We’ll also be putting together relevant documentation and tutorials for getting started with the new feature.

    UX and Integration 

    We released an evaluation2 of the new OpenBazaar v2.0 interface and user experience. We’re going to be continuing to look at other user experiences in the Zcash ecosystem (and other more mature ecosystems like Bitcoin) as we simultaneously begin to work through a set of guidelines for developers creating Zcash services. This will be an ongoing project which could also benefit from community feedback so look out for any UX-related surveys we might put out.

    We’re also updating our Integration Guide3 for third party developers to include some examples and clean up outdated information. If there are any examples you’d like to see included, let us know!

    Powers of Tau Ceremony 

    This week, the Zcash Foundation started organizing the new MPC Ceremony and it’s well underway. For details on the Foundation’s role in the ceremony and how you can be a participant, check out the blog: https://z.cash.foundation//blog/powers-of-tau/9

    Next AMA 

    We’re planning our next technical AMA for 2 weeks from today: Dec 1 at noon PST. Keep an eye out for the thread on this forum that will host the AMA. As always, we look forward to answering your questions and engaging with the community more!

  • ZCASH [ZEC] - Release wallet v1.0.13

    This release introduces new features, performance improvements and bug fixes. Our new low memory prover reduces memory usage by 43% when generating a shielded transaction, from 3 GB to 1.7 GB. An experimental feature, payment disclosure, can help services better manage their shielded payments. We also now fully support the z_shieldcoinbase RPC call to help miners sweep up and shield their coinbase rewards.

    Summary of the changes included in this release:

    1. Auto-senescence cycle has been reduced from 18 to 16 weeks. (#2733)
    2. Low-memory prover reduces JoinSplit creation memory usage from 3 GB to 1.7GB. (#2670, stats)
    3. Payment disclosure has been added as an experimental feature with new RPC calls z_getpaymentdisclosure and z_validatepaymentdisclosure (#2519). This feature enables a sender to prove that a payment was made to a recipient, which can help services better manage their shielded payments. See the documentation#2692). See an explanation of this command here#2652)
    4. Fixed potential shutdown errors have been fixed. (#2555)
    5. User interface messages have been cleaned up. (#2548, #2150, #2649)
    6. The extended QA tests have been migrated to Zcash. (#2533)
    7. A workaround has been implemented in the test wallet_protectcoinbase, which was previously failing on some platforms. (#2698)
    8. Benchmarking has been updated with new performance measurements and fixes. (#2645, #2659, #2377, #2687, #2665)

    For a more complete list of changes, see our 1.0.13 milestone.



  • ZCASH [ZEC]  Dev update - Releases, Network upgrade 0 (NU0) & More

    Thanks for your patience while most of us took a couple of days off last week to spend time with family for Thanksgiving.


    Last Monday, we announced our v1.0.13 release 

    This versions includes a lot of great improvements such as streamed
    proving for reducing the memory load in transactions involving shielded
    addresses and an experimental feature to test selective disclosure.

    We’ve already been putting a good amount of work into 1.0.14 which is currently slated to be released on the first day of 2018 but that’s likely to be adjusted due to conflicting holidays. The experimental feature for payment offloading, for example, was pushed out of 1.0.13 so it’s already well on it’s way to acceptance in the next release.

    Network upgrade 0 (NU0) Since the last update, we’ve had two engineering meetings focused on NU0 (formerly known as HF0) and will be releasing a concrete roadmap in the very near future. For those who’ve been reading these updates all year, you may remember that our goal for NU0 is to make future network upgrades (such as Sapling) simpler and safer like replay protection, activation logic user experience and transaction expiry. We are keeping track of these issues in the associated project

    Part of NU0 decisions were focused on whether we include non-malleability fixes but decided to leave those for a future upgrade since it is not within the scope of making future upgrades simpler and safer.

    UX We’re improving on a draft of UX guidelines for wallet creators which is more general to cryptocurrencies. Our goal is to release more specific documentation of UX standards for specific aspects of Zcash such as handling network upgrades and distinguishing between transactions with shielded or transparent addresses.


    We announced both our recent hires and new engineering openings 

    We’re also hosting our end of the yearAMA next Friday. So bring your questions about payment disclosure, Sapling, NU0 or whatever else you may be wondering about.

  • Zcash (ZEC) Dev Update -  New Release, Network upgrade, Research, auditing, AMA & hiring

    Release We progressed more on issues targeted for the 1.0.143 release including testing and review. There’s a bunch of candidates to go into the release including experimental features like payment offloading and viewing keys1 but as with previous releases, we tend to load up on tickets then narrow the scope as the time to review and edit permits.

    Network upgrades Today we released an overview roadmap of the upcoming network upgrades in 2018 and our intentions to make Zcash For Everyone21. The work for the first network upgrade (NU0 AKA Overwinter) is currently in progress some of which will be introduced in the releases prior including 1.0.14. This has the explicit goal of making future network upgrades safer and simpler. The second network upgrade (NU1 AKA Sapling) is a major version release and will introduce all of the great security and efficiency improvements we’ve been talking about over the last few months since the new faster zk-SNARK research was announced.

    We intend to post a more specific roadmap and visual accompaniment to the website in the coming weeks and will be communicating what the user experience will look like during these upgrades.

    UX In addition to researching methods for the best user experience during network upgrades, we’re working on finishing up a general UX guide for wallet creators based on our prior surveys of cryptocurrency wallets and service evaluations. This will be a general guide and should support the greater cryptocurrency ecosystem but as we approach the Sapling upgrade and better support for shielded addresses in the ecosystem, we’ll focus on guides which target the unique properties of shielded addresses such as payment disclosure and viewing keys.

    Research, auditing, AMA & hiring We’re progressing on consulting for the next round of audits we intend to have for Zcash and the upcoming upgrades.

    We also got to see a great empirical analysis of the Zcash transaction graph which we responded to in a blog post8.

    We just finished our end of the year AMA17, thanks everyone for joining us!

    And finally, we posted new engineering jobs27 to our website.

  • Zcash (ZEC) - URGENT zcash4win (zcash wallet & full node for Windows) update 1.0.12

    I meant to have a new release of zcash4win out a while ago, and was (and still am going to) change the name, but have been delayed by illness!

    Version 1.0.11 is entering auto-deprecation some time tomorrow when the block height for it gets hit, and I released version 1.0.12 of zcash4win earlier today on https://zcash4win.com

    Just go into Add/Remove Programs, uninstall zcash4win, then double click the msi file for 1.0.12 to install the new release

    In addition to bumping the zcash version to 1.0.12, it also flips the block explorer it uses to be https://zcashnetwork.info which shows unconfirmed transactions

    Also for command line only Windows users, the zipfile for stand alone command line zcash for windows version 1.0.12 is now at https://zcash.dl.mercerweiss.com/zcash-win-v1.0.12.zip

    Cheers and sorry again for the delay!

    -David Mercer Tucson, AZ

  • Zcash (ZEC) Dev Update - Release Planning, incoming viewing keys & More

    This week we continued many of the projects highlighted in the past couple of updates (1,2) so I won’t reiterate the details and keep this a short one. These projects include Overwinter specification, 1.0.14 code review and testing, Sapling specification and implementation, website scaling improvements and the UX dev guideline.

    We successfully merged support for incoming viewing keys into the release candidate and are hurrying to get remote proving1 in there as well.

    You can check out all the remaining goodies already in 1.0.14 RC via the release planning tracking we keep.

    Next week will be RC testing and the first week of the new year should be the full release.

    If anyone in the community is in Berlin for the beginning of the new year, definitely join us at an event we’re co-hosting on the 3rd called Privacy for Everyone.

    Happy Holidays!

  • ZCASH [ZEC] - Release Wallet v1.0.14



  • ZCASH [ZEC] Dev update - Release, Overwinter & Sapling Network Upgrades, UX + website + documentation

    Hard to believe it’s been a year since we started these updates! So much has happened since our first official dev update on January 13th3 last year. Feel free to poke around all of the dev updates1 we’ve published so far if you’d like.

    So the past couple weeks have been particularly slow due to holidays and events folks from our team attended like 34c3 in Leipzig, Germany where Zooko gave a great talk at4 about what he’s learned the past years in the cryptocurrency world and our co-sponsored event with Least Authority and Dekrypt Capital called “Privacy For Everyone” in Berlin, Germany. You can check out the livestream recordings of the various presentations from Privacy For Everyone here1. Better quality recordings of the talks should be uploaded in the coming weeks. Linda our UX researcher, myself and Zooko all participated in the event as presenters & panelists.


    This Thursday we got 1.0.14 released10 which includes a few key features like viewing keys6 and client-side shielded value tracking7.

    Viewing keys are something we’ve been thinking about for a while and hoping to implement to improve functionality for shielded addresses. In short, viewing keys are private keys distinct from their correlated spending keys which allow viewing capabilities on a per address basis. This opens up a lot of possibilities such as watch-only addresses and…

    And just to keep y’all updated, payment offloading5 experimental feature has been pushed back to 1.0.15 due to lack of review. The conflicting holiday schedules when the release candidate needed to be ready is the main reason and we anticipate plenty of time to get the reviews in for a 1.0.15 release. Thanks for your patience!

    Overwinter & Sapling Network Upgrades

    The end of the new year was the deadline for Overwinter specification for which we are very much on track with. The coming weeks will see final reviews of this specification followed by final implementation. As previously announced4, the date for Overwinter activation is set for June 2018. We’ve made good progress on user documentation for this upgrade and are planning a guide for third party developers as well. The goal is to make this first network upgrade as smooth as possible while also preparing to learn from the experience for subsequent upgrades (like Sapling which will follow suit with activation planned for September 2018).

    Sapling specification is also coming along nicely and will only ramp up now that the holidays are complete especially once engineers are on-boarded to alleviate overall workload of our spec design team.

    UX + website + documentation

    In addition to the Network Upgrade FAQ for users that we’ve been putting together and Network Upgrade guide for developers, we’re hoping to publish our UX checklist for developers to the website as part of the integration guide. We have also started preliminary discussions on redoing much of the website flow and content. This will come after we finish up our migration of the blog to wordpress which is very close to being complete.

    We’re also getting back on track with consolidating documentation such that guides can be easier to locate for users and developers.

    Thanks for everyone’s patience the past couple weeks for a developer update. You can blame me for the delay which should have come out last Friday.

    Happy New Year, Zcashers!

  • Statement from ZcashCo on Poloniex order error (January 2018)

    On 17 January, 2018 a peculiar sell order on Poloniex for the ZEC<->BTC trading pair was noted on Twitter:


    Source: https://twitter.com/anondran/status/95370397964017664029

    Also that day, a similarly peculiar sell order was created for the LTC<->BTC trading pair and noted by the same Twitter account:

    poloniex-error-order-ltcpoloniex-error-order-ltc.jpeg1475x713 168 KB

    Source: https://twitter.com/anondran/status/95370461602519040010

    At the time of this post, the total ZEC in circulation is 3,084,994 so therefore the 3.9M+ sell order is inaccurate.

    Screenshot_2018-01-18_13-45-50Screenshot_2018-01-18_13-45-50.png969x267 26 KB

    Source: https://coinmarketcap.com/currencies/zcash/4

    This issue appears to be limited to Poloniex and we’ve detected no problems on the Zcash blockchain. That said, we’re monitoring the situation and we’ve reached out to Poloniex to see if we can help.

    We’ll update this post with a link to Poloniex’s statement when they make one.

  • Zcash (ZEC) Release Wallet v 1.0.15-rc1



  • Zcash (ZEC) Release Wallet v1.0.15 release

    This release contains the Overwinter consensus rules with a testnet activation height. It also includes various bug fixes, and adds an experimental RPC method for merging UTXOs and notes. For complete changes, see doc/release-notes/release-notes-1.0.15.md



  • Zcash (ZEC) Weekly update - Releases & Upgrades, Documentation & Website/branding revamp

    Releases & Upgrades

    This week several of our engineers worked together on setting up a pre-testnet Overwinter activation test network. The idea here is to have a better idea of the tests we’ll need and any tweaks or updates necessary to properly evaluate the actual testnet activation which targets March 19th (testnet block height 207500).

    We also have been organizing issues3 to address for the next release, 1.1.0. As a reminder, if all goes smoothly with the Overwinter activation on testnet, 1.1.0 will include the main net activation height which targets June 25th and as a result, will be the first release that is Overwinter compatible. One week before the 1.1.0 release is set as a go/no-go target for confirming if we’re ready for adding the Overwinter activation height on the main network.

    Specification for the Sapling upgrade is undergoing final touchups which are needed before audits of the design can begin. We’ve also begun planning Sapling integration tasks. Our current roadmap sets the 1.1.1 release to have Sapling implemented and a testnet activation height (in the same way 1.0.15 set Overwinter testnet activation) and if all goes well with testing, the next release to be 2.0.0 with a main network activation block height.

    If keeping track of these releases and projected dates is confusing, have no fear! Another project we’ve been working on this week is setting up the internal visual roadmap for upcoming releases and network upgrades we’ve been using to be accessible publicly. This will make communicating our roadmap to the community much clearer as we can adjust projections where necessary and include details of contingency plans in case either network upgrade needs to be delayed. While we’re hopeful to get the network upgrades out as planned, our number one priority is security and stability of the network (as it always has been) and will not hesitate to delay if it makes sense.

    Documentation & Website/branding revamp

    The onboarding of new engineers is allowing for faster progress on some tasks which have been neglected or put to the side based on priorities. One of these is documentation! We’re really excited about archiving a lot of old documentation and moving the important stuff into one central place. In addition to consolidating our current documentation (i.e. from the wikis on the Zcash repo Github and the docs in the zcash source) we’re planning for a unified documentation of the API which include all the Zcash specifc RPC calls (i.e. z_* calls) and the calls inherited from bitcoin.

    We’re simultaneously making our first steps towards revamping the website and providing better channels for folks who visit the Zcash website for different reasons (new users, academics, developers, etc.) This is going to be a several month task but we think it’s well worth the wait for something we and the community can be proud of.


    This weekend we’re participating in a conference focused on promoting accessibility to blockchain technologies called moinBlockchain and will be presenting on cryptocurrency usability and while we’re there doing some informal surveying on folks use of different wallets.

    We’re also planning on a new usability spotlight program to give the opportunity for the Zcash community to engage in some of the UX research we’ve been pursuing. Stay tuned and let us know if there is a particular wallet or UX you’d like to see highlighted for community review.

    Latin America - Zcash users in Latin American countries might have heard of the service called AirTM. Their support for Zcash was announced this week. We’re asking for Latin American Zcashers to check out their services which pair someone looking to exchange a currency with a cashier who facilitates the trade. Cashiers who facilitate Zcash trades are important to boost liquidity of ZEC in their market and have the opportunity to help someone in need of exchanging to or from another currency while making a commission. And let us know what you think of the experience!

    Zcon0 - reminder to checkout the application for the first Zcash conference, Zcon0 being organized by the Zcash Foundation.

    Powers Of Tau - it was announced this week that the Powers of Tau ceremony being hosted by the Zcash Foundation is planned to conclude by March 15th. The next phase of the parameter generation is a circuit specific MPC for the upcoming Sapling and will begin soon with more details to come.

    Learn how to solve a Rubix Cube with the beginner method, using only six algorithms.

  • Zcash Team Grows with New Hires in Q1 2018

    Zerocoin Electric Coin Company

    The first round of hiring in 2018 has brought many skilled individuals to the Zcash team.
    We are excited to announce this group of passionate new hires who share
    the Zcash philosophy and possess the integrity and character that
    inspire us.

    The first round of hiring in 2018 has brought many skilled individuals to the Zcash team. We are excited to announce this group of passionate new hires who share the Zcash philosophy and possess the integrity and character that inspire us.

    Brad Miller


    Brad is a generalist engineer with a background in software engineering, mechanical design, and engineering physics. He is excited about the abundance of opportunities in the cryptocurrency space and their potential for massive impact. Brad is most passionate about bringing cryptocurrency to the masses by solving the challenges around usability and user experience. He holds a B.S. in Engineering Science and Mechanics from Virginia Tech and is currently working on an M.S. in Computer Science from Georgia Tech focusing on Machine Learning. He lives in Fort Collins, Colorado.

    Marshall Gaucher


    As a Software Engineer, Marshall has primarily worked with RF4CE technologies to develop some of the first voice recognition products in the broadband industry. He also brings a strong academic foundation with studies ranging from Mobile Computing to Robotics. Now, he is eager to pioneer new frontiers in the “Wild West” of Cryptocurrency.

    Ian Munoz


    Ian is an economist & developer with a background in high performance research computing, infrastructure, and reproducible software. He is passionate about encryption, privacy & decentralization. In his free time he dabbles in the linux kernel, works on containerization, and plays in the outdoors!

    Charlie O’Keefe


    Charlie has been programming since fourth grade, majored in math and computer science at the Colorado School of Mines, and has worked in the defense, education, health care, and energy industries. Throughout all of that, his interests gravitated to decentralization and privacy technologies, and he is very excited by the opportunity to contribute in those areas at Zcash!

    Eirik Ogilvie-Wigley


    Eirik graduated from CU Boulder in 2012 with a degree in mathematics. He has several years experience developing software in a professional setting, and has been a hobbyist programmer since he was a child. In his spare time Eirik enjoys doing abstract algebra, and is excited to bring his skills, experience, and enthusiasm to the Zcash team.

    Josh Swihart

    Marketing Director

    Josh does technology and marketing, mostly. Prior to Zcash, he served as the SVP of Global Marketing for K2, a high-growth tech company. He has also served as a global practice principal for EMC, the CEO of Aspenware, and was the co-founder of a couple other companies with exits to Accenture and EMC. He began his career as a software developer, data recovery specialist and BBS sysop while in high school. Josh has received numerous global and national awards for leadership, marketing and solution delivery.

    George Tankersley


    George is a cryptography engineer at Zcash, where he now works on turning math into magic Internet money. He’s spent the last few years deploying cryptography at Internet scale, contributing to the design of new protocols and to open source ecosystem projects like Certificate Transparency and Kubernetes. Prior to that he worked on a Linux distro, ran a small startup, worked as a pentester, and briefly took up blacksmithing.

    Zcash continues to value our contributors and the positive, enthusiastic community of fans. Keep an eye on the Zcash Jobs page for open positions on the team. Please join the Zcash community by contributing to our Slack or Forum conversations.

    Never forget to use the Div - Table style generator and the online HTML editor to compose perfect articles for your website!

  • Zcash (ZEC) Release Wallet v1. 1.0-rc1



  • Zcash (ZEC)  Weekly update  - April 6, 2018

    Just a quick dev update on Overwinter and Sapling this week. I’ll elaborate on more community related updates next week but as a reminder: Zcon0 & Consensus Scholar program applications are open!

    Overwinter Release This week we made the go decision for moving forward with the Overwinter release without inserting a buffer release. We received reports back from auditors of Overwinter changes and while some issues were found, they were not consensus related and therefore addressable in subsequent releases. This go decision essentially means that we plan to release 1.1.0 next week which will have include the target block height for activation on the main network. As always, you can keep track of the countdown to Overwinter activation on the information portal. We haven’t made the decision for the exact block height, yet but as mentioned previously, we’ll be targeting June 25th of this year and will obviously share that height when we decide.

    We’ve packaged a 1.1.0 release candidate and will do some testing before cutting the main release which is scheduled for Monday but could be pushed back a day or two to make sure we have the RC testing fully covered.

    Results from the Overwinter audit review will be published in the near future.

    Sapling This week we packaged up and tested the parameters generated from phase 1 of the MPC (aka Powers of Tau) and will be announcing them along with a coordinator report in the coming days. We also finished the verification tool for those parameters and released the code for phase 2 of the MPC for the Sapling circuit which we’ll probably start this weekend.

    Audits of the Sapling libraries are also underway and we’ve decided to move forward with a shielded ZEC accounting turnstyle. This means that when users migrate their ZEC from version 1 (Sprout/Overwinter) to version 2 (Sapling) shielded addresses, the value within that transfer is temporarily revealed. We’re discussing how to do this so that users maintain the most optimal privacy but the goal here is to address the lack of accounting ability for the shielded ZEC pool that so many people are concerned about. We have time to consider the best approach to do this accounting while maintaining the most optimal privacy for users and of course, always welcome community input.

  • ZCASH New Exchnage Update

    Hello everyone,

    We wanted to let you know that Zcash is now listed on Coinsranks

    Coinsranks aggregates price and volume information from 27 exchanges (offering more than 1200 cryptocurrencies).

    If any member of the Zcash team reads this message, we would be pleased to be mentioned on your website, so that visitors and potential investors can easily find a place where they can monitor your cryptocurrency price.

    If needed, please find here our website logos1.

    If you need any additional information, please let us know.

    Thanks. Have a nice day,

  • Updated Zcash UX Guidelines for Wallet Developers

    We have updated our checklist of good UX practices
    with specific advice on handling Zcash features. Our intent is to
    provide Zcash wallet developers with guidance on making design decisions
    and catch common usability problems.

    UX Checklist

    UX Checklist for Wallet Developers

    The updated content addresses how to:

    • Support transparent and shielded addresses
    • Set various transaction parameters
    • Use viewing keys for selective disclosure
    • Use memo fields for bookkeeping

    We believe that improving the user experience for wallets will be a huge step in making cryptocurrencies accessible. Zcash provides a Linux client but has not released an official wallet. A community maintained list of Zcash wallets is here.

  • Zcash (ZEC) Release Wallet 1.1.0

    This release contains the Overwinter mainnet activation height. It also includes various bug fixes, improvements for the z_mergetoaddress RPC method, and the NODE_BLOOM service bit. For complete changes, see doc/release-notes/release-notes-1.1.0.md



  • ZCASH Weekly update -  April 28, 2018

    Sorry for the day delay in this week’s update, but hopefully there’s a lot for you to take from this one!

    This week’s update will be based on the various engineering teams first sprint. We’re tracking each team’s progress in Github projects so you can see a more detailed view of what they’re tackling each two-week sprint and what they have in their longer-term backlogs.

    Zcashd Team This team focus on development of the zcashd client but stands distinct from consensus protocol (which is a separate team).

    The complete and released columns show 5 pull requests being merged as a result of this sprint and several issues being addressed such as MacOS build support and various researching and development work for support on Windows and what needs to be done to make sure Overwinter is supported on WinZEC. We also fixed a minor bug that was discovered in one of the audits which involved pulling in a change already made in bitcoin.

    We also established a more succinct process for user support tickets and how they should be properly passed to the suitable engineering teams for addressing. User support tickets are a high priority for us so streamlining their fixes this way is important and most of the issues are related to the zcashd client, making this especially relevant for this team. Once a fix is implemented, the user support team will resume communication with the user and do follow-up on whether their problem was resolved.

    Consensus Protocol Team This team focuses on the Zcash consensus protocol current and future upgrades which include R&D, specification and interfacing with the ZIP process .

    This team is heavily focused on consensus implementations necessary to get Sapling ready for activation on testnet. As a reminder: the testnet activation block height is planned to be included in 1.1.1 (as happened with Overwinter in 1.0.15). A lot was completed this sprint including initial support for the Sapling transaction format and pulling in the Sapling libraries which have been in heavy development and auditing over the last several months. While the new MPC generation ceremony for Sapling circuit parameters is not complete, separate parameters were generated to be ready for testnet activation and implemented into the consensus code this sprint.

    Development Infrastructure team This team works on making sure developers have the tools and infrastructure they need to efficiently collaborate, design, implement, review, test, and ship high quality projects.

    Much of the work done in this last sprint focused on improving the zcash deterministic build environment  and moving towards finishing the Sapling circuit MPC.

    Ecosystem team This team is the interface to everything not directly related to zcashd or the protocol and include support for third-party tools and services. Ecosystem projects developed by Zcash Co. also get handled in this team. Tracking for this team is kept private to prevent information leakage about third-parties.

    We’ve been concreting a plan for making sure third-party services are ready for Overwinter andstarted a list of those services which have made statements of readiness for the upgrade in the information portal . We’ll be adding to this list as others follow suit. You’re encouraged to ask services you use to make such a statement and contact us to be added (or if you find statements which aren’t listed, let us know about them by posting in this thread or sending an email).

    Some other things this team is working on include upgrading the zcash-bitcore library for Overwinter and a framework for collecting privacy metrics responsibly and reliably for improving Zcash and providing accountability.

    Documentation team This team works on improving the accessibility of zcashd and Zcash overall.

    The main project in this team is to transition most of our documentation into a Readthedocs instance. The last month has been focused on gathering all the documentation from various places and staging them into Readthedocs. After we’ve improved the organization a bit, we’ll be ready to release the first iteration for community feedback.

    We’re also looking to provide a tutorial for developers which parse Zcash transactions so they know how to update their code for Overwinter.

    Finally, one thing we’re interested in doing is making the ZIPs more accessible by pulling them into Readthedocs as well.

    Communication & Community This area is comprised of a few sub-teams including communications (marketing, PR, website), community (events, Zcash Foundation liaisoning, online forums) and business development. These teams are the smallest and have a lot of overlap of individuals, but we’re incredibly keen on expanding our global community team in particular. If you or someone you know (being Zcash enthusiasts) lives in Latin America, India, Asia, Africa and might want to help us engage with developers and users in those regions, be in touch!

    Check out the recap of Zooko’s trip to India  and our first community spotlight announcement from our blog.

    We’re prepping for our participation at Consensus 2018 where we’re hosting some students who were accepted to receive scholarships to attend the event and Zooko being on stage for a discussion with Whit Diffie!

    We participated in a panel about Privacy and Identity as part of this week’s Boston Blockchain Week and spoke and had a booth at SHE256  earlier this week.

    Finally, Zcon0 planning is coming along well. Folks at the foundation are starting to reach out to folks who applied encouraging them to secure their registration for the event. Those being provided with financial aid will be contacted soon after.

    Oh, and definitely check out the latest Foundation blog announcing the newest iteration of their grant program  and if you missed it, their announcement of a community governance panel.

Log in to reply

Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.