Skip to main content
POST
Returns the unsigned contract creation that deploys an ONCHAINID for a customer’s wallet. An ERC-3643 register looks up an identity contract per wallet, so a wallet needs one before it can be registered. Build Pending Registration asks for the same deployment in its DEPLOY_IDENTITY phase, and this endpoint lets you deploy ahead of time. Only an instance bound to an ERC-3643 register can use it. A Trusset register needs no ONCHAINID, and the call answers REGISTER_OPERATION_UNSUPPORTED. Customer registration supports ERC-3643 T-REX 4 registers with ONCHAINID 2 identities and T-REX 5 registers with ONCHAINID 3 identities. On a T-REX 5 register this call returns a creation through the register’s identity factory instead of a contract creation: see On a T-REX 5 register and Which register you write to.
This call asks only the register whether the wallet has an ONCHAINID. It does not see one you deployed and confirmed for a wallet that is not registered yet, and plans a second deployment. Confirming that one as well replaces the recorded identity with the newer one.The deployment names no customer wallet, so Confirm ONCHAINID cannot tell which wallet it was built for. Confirm each deployment with the walletAddress you requested it for.
The ONCHAINID is created with managementKey as its management key. That is an issuer wallet, not the customer’s. Confirm ONCHAINID refuses a management key that is not a wallet registered to your instance.

Body Parameters

string
required
The customer’s wallet.
string
The wallet to name as the management key. Omit it to use your instance’s primary registered wallet, or the most recently registered one when none is primary. Name a wallet registered to your instance, because the confirm refuses any other with MANAGEMENT_KEY_NOT_INSTANCE. A malformed address is ignored.On a T-REX 5 register it names the wallet that will send the creation instead, and is never a management key. It must hold the IDENTITY_ISSUER role of the identity factory’s authority, or the call answers 403 SIGNER_ROLE_MISSING.

Broadcast the deployment

Send transaction.data as a contract creation, with no to. transaction.create marks it as one and is not a field to pass to your wallet library. Any wallet can send it. The confirm checks the management key the deployment names, not the sender. Then record it with Confirm ONCHAINID, using the same walletAddress. Until then, Build Pending Registration does not know the identity exists.

On a T-REX 5 register

The answer carries trexVersion: 5. When the identity factory already links an active identity to the wallet, the call returns it with exists: true and builds nothing. Otherwise it returns one transaction, stepType: createIdentity, that calls createIdentityFor on the identity factory, so transaction.to is the factory. identityType is CORPORATE for a company customer and INDIVIDUAL otherwise, and the salt is trusset-<chainId>-<wallet>, which carries no personal data. The investor wallet becomes the only MANAGEMENT key of its ONCHAINID. Your issuer wallets hold no key on it, so the answer carries no managementKey or implementationAuthority. The warning above does not apply either: the factory answers for the wallet, so no second identity is planned. Send the transaction from the wallet the answer names in signer, which holds the IDENTITY_ISSUER role of the factory’s authority. The factory links the identity to the wallet as the transaction mines, so the identity writes find it without a confirm. Confirm ONCHAINID still records it on the customer record. The call refuses with IDENTITY_ISSUER_MISSING when none of your instance’s wallets holds the IDENTITY_ISSUER role, IDENTITY_TYPE_NOT_ENABLED when the factory has no policy for the identity type, and IDENTITY_BINDING_REVOKED when the wallet’s binding on the factory is revoked. Use another wallet for the customer then.

Response Fields

object

Error Codes