# \[Archive\] Can't create a new verifier

**URL:** <https://builder.metamask.io/t/archive-cant-create-a-new-verifier/1940>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [June 8, 2023, 3:48pm UTC](https://builder.metamask.io/t/archive-cant-create-a-new-verifier/1940 "2023-06-08T15:48:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![oauth](https://avatars.discourse-cdn.com/v4/letter/o/8edcca/32.png) [@oauth](https://builder.metamask.io/u/oauth)\
**Post date:** [June 8, 2023, 3:48pm UTC](https://builder.metamask.io/t/archive-cant-create-a-new-verifier/1940/1 "2023-06-08T15:48:55Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **oauth** on 6/8/2023.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

I would like to create a verifier on Testnet with custom auth, I provide a valid endpoint for the JWKS (I’ve just tested it with curl) and it’s taking forever. The name of the verifier is brillion-verifier5. Is it because of the testnet migration that is mentionned in the banner?

---

<div class="post-metadata">

**Author:** ![zhen](https://avatars.discourse-cdn.com/v4/letter/z/a88e57/32.png) [@zhen](https://builder.metamask.io/u/zhen)\
**Post date:** [June 9, 2023, 2:39am UTC](https://builder.metamask.io/t/archive-cant-create-a-new-verifier/1940/2 "2023-06-09T02:39:21Z")

</div>

Yes, use sapphire\_devnet please

---

<div class="post-metadata">

**Author:** ![oauth](https://avatars.discourse-cdn.com/v4/letter/o/8edcca/32.png) [@oauth](https://builder.metamask.io/u/oauth)\
**Post date:** [June 9, 2023, 9:10am UTC](https://builder.metamask.io/t/archive-cant-create-a-new-verifier/1940/3 "2023-06-09T09:10:14Z")

</div>

I’ve also created one on Sapphire Testnet from two different accounts 12h ago, but none of them is deployed. They’re still “processing”.  
`brillion-verifier-test-personal1` and `brillion-test-sapphire-1`.

For the EVM testnet migration, do you know when it will be restored? Is it up/down at most times? I would like the banner to route me to a more detailed description/timeline of the situation.

Also I don’t find any guideline regarding what switching to Sapphire implies.

---

<div class="post-metadata">

**Author:** ![oauth](https://avatars.discourse-cdn.com/v4/letter/o/8edcca/32.png) [@oauth](https://builder.metamask.io/u/oauth)\
**Post date:** [June 12, 2023, 9:40am UTC](https://builder.metamask.io/t/archive-cant-create-a-new-verifier/1940/4 "2023-06-12T09:40:29Z")

</div>

Any information as to why I can’t create verifiers with custom auth on Sapphire either, from 2 different accounts? It’s been 3 days that I’ve tried to create them, they’re all still “Processing”.

Plus, if you could share any timeline about the Testnet migration I would really love it!

Thx

---

<div class="post-metadata">

**Author:** ![oauth](https://avatars.discourse-cdn.com/v4/letter/o/8edcca/32.png) [@oauth](https://builder.metamask.io/u/oauth)\
**Post date:** [June 14, 2023, 8:35am UTC](https://builder.metamask.io/t/archive-cant-create-a-new-verifier/1940/5 "2023-06-14T08:35:09Z")

</div>

I was able to get verifiers deployed on Sapphire, only when a project exists on Sapphire as well. Eventually even the Sapphire project/verifier didn’t work and I was able to have them work on Aqua.

Not a good developer experience though, no support, users can’t use their web3auth-generated account for days, etc.