> For the complete documentation index, see [llms.txt](/llms.txt).

To verify the PowPeg protocol nodes, follow the HSM firmware attestation process using the steps below. See the [Attestation README](https://github.com/rsksmart/rsk-powhsm/blob/2.3.5/docs/attestation.md).

:::tip[Tip]

For a comprehensive list of attestations, see the [PowPeg HSM Firmware Attestation](https://rootstock.io/powpeg/) landing page.

:::

### PowPeg HSM Firmware Attestation — Sovryn

**Sovryn:**

Video: [/img/rsk/architecture/powpeg-hsm-attestation/sovryn.html](/img/rsk/architecture/powpeg-hsm-attestation/sovryn.html)

**pNetwork:**

Video: [/img/rsk/architecture/powpeg-hsm-attestation/pnetwork.html](/img/rsk/architecture/powpeg-hsm-attestation/pnetwork.html)

### Frequently Asked Questions

### What is the multisig scheme for the powHSM? It is a M of N multisig. What is M and what is N?

> - A: The best way to get this information is by querying the Bridge directly, since the number of members of the PowPeg may change after a PowPeg composition change.
> - You can use the following methods to query the bridge: `getFederationSize`, `getFederationThreshold`.
> - By consensus the required amount of signers (M) will always be half plus one the total amount of pegnatories  `M = N / 2 + 1`. See the signatories and attestation information in [PowPeg HSM Firmware Attestation](#powpeg-hsm-firmware-attestation---sovryn).
