Getting Started
Last updated
Last updated
If you're a dApp, and you want to publish attestations, here are the steps to get up and running:
Decide on your , which is a description of what your attestations will look like.
Deploy your , which is a contract through which you push attestations into the registry (note: you can also call a smart contract function to do this for you — simple!).
Send your to your portal contract, which will push them to the registry.
All done!
You can call a function on the registry to deploy a portal contract for you, or you can deploy your own portal contract, over which you have full control to customize the way you wish.
You can decide to keep your portal simple, and you can also use one or more , which are small smart contracts that run extra verification logic over the attestations before they are registered. We have some that you can use, and more are being added all the time.
Please feel free to contact the developers in the community for support! They are always eager to help teams to get up and running quickly! You can find advice on our .
Note: the Verax registry is now permissionless on testnets, but still permissioned on mainnets, so you'll need to get on the allowlist to register Schemas or Portals. Fortunately this is fairly easy, !