Vivian Plasencia

## Description Update a `generateProof` function parameters in the docs. It should be `const proof = await generateProof(identity, group, message, scope)` here: https://github.com/semaphore-protocol/semaphore/blob/main/apps/docs/versioned_docs/version-V4-beta/guides/proofs.mdx#L95

**Description**: There were two extension contracts in Semaphore v3: https://github.com/semaphore-protocol/semaphore/tree/v3.15.2/packages/contracts/contracts/extensions The idea is to use the latest Semaphore v4 to update those contracts and add them to the `Semaphore Extensions`...

It would be very helpful to add to the documentation, that the Semaphore protocol works not only on Ethereum but on any other EVM-compatible chain, and works in the web2...

Use the same type for the group id in the `@semaphore-protocol/group` and `@semaphore-protocol/data` packages.

1

Right now, to create a group, the id could be a `BigNumberish` but to use the group id in any of the functions in the `SemaphoreSubgraph ` or `SemaphoreEthers `...

Make the contract tests more atomic and use `loadFixture`

5

### Description It would be nice to make the tests as atomic as possible and use `loadFixture`. This can help: https://github.com/semaphore-protocol/semaphore/blob/main/packages/cli-template-contracts-hardhat/test/Feedback.ts

Increase timeout for tests generating Semaphore proofs

1

## Description There is an error when running the test workflow: ```bash Proof › # generateProof › Should generate a Semaphore proof thrown: "Exceeded timeout of 20000 ms for a...