Environments
ISBE currently has two environments. Each utilizes the same technology stack (secp256k1 cryptography, smart contracts on the uc network) but with specific values. The onboarding process is identical; the only things that change are the URLs and the trust anchor.
Onboarding is currently only possible in the USE-CASE networks (uc, uc-pre), which use secp256k1 cryptography.
PRE — Pre-Production
Validation environment prior to production. Equivalent to production in terms of stability.
| Resource | Value |
|---|---|
| Portal | https://pre.portal.redisbe.com |
| Trust Anchor (TA) | did:isbe:uc-pre:z1N1q5h8vcuHaic1fZjpZiQaSDHt |
modelDeploy | uc-pre |
| DID Registry API | https://did-registry.pre.portal.redisbe.com |
| DID Registry Swagger UI | https://did-registry.pre.portal.redisbe.com/api |
| TIR API | https://tir.pre.portal.redisbe.com/trusted-issuers-registry/v1 |
| TIR Swagger UI | https://tir.pre.portal.redisbe.com/api-docs |
PRO — Production
Productive environment. Operations here are persistent and public.
| Resource | Value |
|---|---|
| Portal | https://portal.redisbe.com |
| Trust Anchor (TA) | did:isbe:uc:z12kVar5p6bD5WCjEJcQ18Zyt8XV |
modelDeploy | uc |
| DID Registry API | https://did-registry.portal.redisbe.com |
| DID Registry Swagger UI | https://did-registry.portal.redisbe.com/api/v1 |
| TIR API | https://tir.portal.redisbe.com/trusted-issuers-registry/v1 |
| TIR Swagger UI | https://tir.portal.redisbe.com/api-docs |
How to Point CLIs to the Correct Environment
isbe-identity-did-gen
When generating a DID, pass the -m parameter with the environment's modelDeploy:
# Pre-production
./did-gen did -m uc-pre -p 0x<PRIVATE_KEY>
# Production (default value if -m is omitted)
./did-gen did -m uc -p 0x<PRIVATE_KEY>
isbe-identity-accreditation-cli
Edit isbe-data/isbe-config.json to adjust tirUrl and trustAnchors to the corresponding environment. See Trust Chain for more details.
If the modelDeploy with which you generate the DID does not match the network the API points to, the registration transaction will fail with a validation error. Always verify the consistency among the three values: blockchain network, the DID's modelDeploy, and the API URL.