REGISTER AUTHORIZER

If you wish to register any network authorizer then use this git-action

REGISTER AUTHORIZER GITHUB ACTION - https://github.com/0chain/zus-cicd/actions/workflows/register-authorizer.yaml

AUTHORIZER GITHUB REPOSITORY - https://github.com/0chain/token_bridge_authserver

INTRODUCTION

This GitHub Action verifies the absence of the authorizer to validate registration. It works even when the authorizer is not registered, guaranteeing a distinct registration. If the authorizer is already registered, it fails in contrast, keeping the registration's exclusivity.

For ActiveSet or Docker Based Deployment - Multiple Server with different URLs

Activeset networks are docker based deployments on multiple Hetzner dedicated servers. Here Miner & Sharder of different server connect and form a network .

example - As https://demo1.zus.network/sharder01/_diagnostics network is setup.

For K8s Based Deployment - Single Node

Kubernetes based deployments is single node where only one hetzner dedicated server form a network on one server.

example - As https://test2.zus.network/sharder01/_diagnostics network is setup.

why we register authorizer and why it's registered differently from other providers?

Manage authorizer with managing wallet, add/delete and so on, it should be extended for other providers as well. For miner and sharder it is not easy to do though, and later on it will be changed when view-change will be enabled