docs: update Hats reference to clarify it's WIP

website/blog/2024-02-28-maci-v1.2.0.md

@@ -17,7 +17,7 @@ This is our first release since [MACI v1.1.1](/blog/maci-v1-1-1-release) just ov
 
 ## Background
 
-MACI - Minimal Anti-Collusion Infrastructure - is an Ethereum application that provides privacy and collusion resistance for on-chain voting. If you're new to MACI, we first recommend reading our [Introduction documentation](/docs/introduction) for background information and referring to our [Technical Introduction to MACI](/blog/maci-1-0-technical-introduction) for a deep dive of MACI's technical details.
+MACI - Minimal Anti-Collusion Infrastructure - is an Ethereum application that provides privacy and collusion resistance for on-chain voting. If you're new to MACI, we first recommend reading our [documentation](/docs/introduction) for background information and and technical details.
 
 ## Refactoring Work
 
@@ -37,7 +37,7 @@ Circomkit has become our go-to for circuit-related tasks, such as compiling circ
 
 We've moved reusable circuit logic, like our [Poseidon permutation](https://github.com/privacy-scaling-explorations/zk-kit/tree/main/packages/poseidon-cipher) encryption and decryption code, into zk-kit. This not only benefits MACI through more circuit usage and testing but also supports wider community adoption.
 
-These efforts are part of a broader initiative at [Privacy and Scaling Explorations (PSE)](https://pse.dev/) to foster open-source development and contribute to public goods. By aligning MACI with these values, we aim to enhance its utility and encourage collaborative growth. In the coming months, we're committed to extracting more of our circuit logic for broader use and contributing to projects that align with our mission. These efforts will continue to be tracked [here](https://github.com/privacy-scaling-explorations/zk-kit/issues/131).
+These efforts are part of a broader initiative at [Privacy and Scaling Explorations (PSE)](https://pse.dev/) to foster open-source development and contribute to public goods. By aligning MACI with these values, we aim to enhance its utility and encourage collaborative growth. In the coming months, we're committed to extracting more of our circuit logic for broader use ([track progress here](https://github.com/privacy-scaling-explorations/zk-kit/issues/131)) and contributing to projects that align with [our mission](/roadmap#maci-mission--vision).
 
 ### Code Refactor
 
@@ -62,21 +62,21 @@ The new version of the Tally circuit (specific for non-QV), has reduced constrai
 
 We invite projects interested in leveraging this secure, on-chain voting mechanism to reach out for potential integrations. We hope to continue to expand support for additional voting methodologies, so please let us know your project's needs!
 
-### New Gatekeepers (EAS and Hats Protocol)
+### New Gatekeeper
 
-In our effort to fortify MACI against Sybil attacks, we've integrated two innovative gatekeeper mechanisms: [EAS](https://attest.sh/) and [Hats Protocol](https://www.hatsprotocol.xyz/).
+In our effort to fortify MACI against Sybil attacks, we've integrated an innovative gatekeeper mechanism: [EAS](https://attest.sh/) - you can [view the contract here](https://github.com/privacy-scaling-explorations/maci/blob/v1.2.0/contracts/contracts/gatekeepers/EASGatekeeper.sol).
 
 As part of configuring a MACI deployment, the coordinator sets a user signup gatekeeper contract. This contract dictates the criteria a user must pass in order to participate in a poll. For example, user might need to prove ownership of a certain NFT, or prove that they have passed some sort of proof-of-personhood verification.
 
-With the addition of these two new gatekeepers, EAS and Hats Protocol, MACI instances could be configured to e.g. only allow Ethereum accounts with a trusted EAS attestation or those designated with a specific role by the Hats Protocol. These modules open up new avenues for access control strategies.
+With the addition of this new gatekeeper, EAS (and soon™ [Hats Protocol](https://www.hatsprotocol.xyz/), MACI instances could be configured to e.g. only allow Ethereum accounts with a trusted EAS attestation or those designated with a specific role by the Hats Protocol. These modules open up new avenues for access control strategies.
 
-We expect to continue to expand our [gatekeeper capabilities](https://github.com/privacy-scaling-explorations/maci/tree/dev/contracts/contracts/gatekeepers) and welcome the community to come up with new and innovative ways to grant access to MACI's rounds, helping make MACI more customizable and sybil-resilient.
+We expect to continue to expand our [gatekeeper capabilities](https://github.com/privacy-scaling-explorations/maci/tree/dev/contracts/contracts/gatekeepers) and welcome the community to come up with new and innovative ways to grant access to MACI's rounds, helping make MACI more customizable and sybil-resilient. The Hats Protocol gatekeeper is [currently in progress](https://github.com/privacy-scaling-explorations/maci/pull/1191) and will be released soon™ (in v1.2.1).
 
 ### Documentation Website
 
 We're excited to announce that all MACI documentation has been unified on our new website, [maci.pse.dev](/)!
 
-This platform will serve as the definitive resource for all information related to MACI, including blog releases, documentation updates, and roadmap progress. Please report any inconsistencies you may find. As always, we welcome suggestions on how to make it better.
+This platform will serve as the definitive resource for all information related to MACI, including [blog](/blog) releases, [documentation](/docs/introduction) updates, and [roadmap](/roadmap) progress. Please report any inconsistencies you may find. As always, we welcome suggestions on how to make it better.
 
 ## Security Audit
 
@@ -96,13 +96,13 @@ We'll update this page after the ceremony completes to include the production-re
 
 ## Get Involved
 
-MACI is deeply committed to our community, through our open initiatives like [publishing public roadmaps](https://github.com/privacy-scaling-explorations/maci/discussions/859), transparent [repository management](https://github.com/privacy-scaling-explorations/maci/discussions/847), and a [public Discord channel](https://discord.com/invite/sF5CT5rzrR) for interaction with our team.
+MACI is deeply committed to our community, through our open initiatives like [public roadmaps](https://github.com/privacy-scaling-explorations/maci/discussions/859), transparent [repository management](https://github.com/privacy-scaling-explorations/maci/discussions/847), and a [public Discord channel](https://discord.com/invite/sF5CT5rzrR) for interaction with our team.
 
 With every issue, PR, feature and roadmap iteration, we welcome feedback to ensure that the continued development of MACI reflects your and the community's needs. Keep an eye out on our [documentation](/), [GitHub discussions](https://github.com/privacy-scaling-explorations/maci/discussions) and our official [Twitter/X account](https://twitter.com/zkMACI) for updates.
 
 For those looking to contribute directly, report bugs, or offer feedback, our [GitHub repository](https://github.com/privacy-scaling-explorations/maci) is open for issues and discussions. We're eager to assist with your projects or contributions.
 
-For practical implementation insights, review our docs as well as the [clr.fund](https://github.com/clrfund) and [QF](https://github.com/privacy-scaling-explorations/qf) repositories as reference implementations.
+For practical implementation insights, review our docs as well as the [clr.fund](https://github.com/clrfund/monorepo/) and [QF](https://github.com/privacy-scaling-explorations/qf) repositories as reference implementations. Both are quadratic funding implementations, a mechanism which otherwise is highly susceptible to collusion and bribery. Most notably, clr.fund is already working on integrating MACI v1.2.0, after having used v0.x until now. You can follow their development effort under this [GitHub branch](https://github.com/clrfund/monorepo/tree/feat/maci-v1).
 
 For any other questions or feedback, please reach out to us via [PSE's Discord](https://discord.com/invite/sF5CT5rzrR), in our [`#🗳️-maci` channel](https://https//discord.com/channels/943612659163602974/1164613809730748507). We're excited to connect and collaborate with you!
 
@@ -112,9 +112,7 @@ For any other questions or feedback, please reach out to us via [PSE's Discord](
 - [MACI documentation](/docs/introduction)
 - [A technical introduction to MACI 1.0 - Kyle Charbonnet](/blog/maci-1-0-technical-introduction)
 - [Minimal anti-collusion infrastructure - Vitalik](https://ethresear.ch/t/minimal-anti-collusion-infrastructure/5413)
-- [Discord server](https://discord.com/invite/sF5CT5rzrR)
-
-MACI's effectiveness can be seen in projects such as [clr.fund](https://github.com/clrfund) and [QF](https://github.com/privacy-scaling-explorations/qf) - both quadratic funding implementations, a mechanism which otherwise is highly susceptible to collusion and bribery. Most notably, clr.fund is already working on integrating MACI v1.2.0, after having used v0.x until now. You can follow their development effort under this [GitHub branch](https://github.com/clrfund/monorepo/tree/feat/maci-v1).
+- [PSE Discord server](https://discord.com/invite/sF5CT5rzrR)
 
 ## Release