Skip to main content
POST
Returns the unsigned transaction that registers waiting admissions of one profile on its eligibility register. A wallet of your instance that is an agent of the register signs and broadcasts it, then Confirm Admission records the result. Trusset holds no key and sends nothing. Only a register in the REGISTER or CLAIM mode can be built for. A profile bound to your instance register, or to a register managed outside Trusset, is refused. See Which registers can be signed here. Admissions are built for ERC-3643 T-REX 4 registers with ONCHAINID 2 identities in the REGISTER mode, as described first below. A T-REX 5 register (ONCHAINID 3 identities) on the same identity factory as your instance’s own T-REX 5 register is in the CLAIM mode, where an admission is a profile claim your wallet signs: see Admit by profile claim. A T-REX 5 register bound while your instance register is not T-REX 5 stays a read-only gate here: the build answers 409 ELIGIBILITY_ADMISSION_EXTERNAL with a message saying why, and wallets are admitted to it with the holder’s own T-REX 5 tooling.

Body Parameters

string
The profile, by key. Matched exactly, then in upper and lower case. Send this or profileId.
string
The profile, by id. Used instead of profileKey when both are sent.
string
required
The wallet that will sign. It must be a verified Ethereum wallet of your instance and an agent of the register. The transaction is simulated from it before anything is returned.In the CLAIM mode it needs no agent role. It must hold a CLAIM_SIGNER key on the claim issuer to receive the messages, and a MANAGEMENT key on it to receive the transactions.
array
CLAIM mode only. The signed messages of the first answer, as [{ walletAddress, signature, issuedAt }], with issuedAt exactly as each message gave it. At most 50 are read. An entry without issuedAt is not used, and the call answers its message again.
string[]
Only these admissions, by id. Up to 200 are read, and an id that is not a PENDING admission of this profile is ignored.
string[]
Only the admissions of these wallets. Up to 200 are read, and malformed addresses are dropped. Sent together with ids, an admission must match both.
Without ids or wallets, the oldest waiting admissions of the profile are used. One call builds at most 50. Build again after confirming for the rest.

What is checked

The checks run in this order, and the first that fails refuses the call:
  1. signerAddress is a verified wallet of your instance (SIGNER_NOT_INSTANCE_WALLET).
  2. The profile has a register, the register answers isVerified(address) with a single bool, and its mode is REGISTER (ELIGIBILITY_ADMISSION_INSTANCE_REGISTER, ELIGIBILITY_ADMISSION_EXTERNAL).
  3. signerAddress is an agent of the register (ELIGIBILITY_AGENT_REQUIRED). The message names the wallets that are. In the CLAIM mode the key checks under Admit by profile claim take its place.
  4. At least one admission is waiting among the ones selected (NOTHING_TO_ADMIT).
Then each admission is checked against your instance register and the eligibility register. An admission that fails is left out of the transaction and reported in skipped: Every remaining wallet is registered with the ONCHAINID and the country your instance register holds for it, so the eligibility register reads the same identity and claims. Last, the transaction is simulated from signerAddress. When it would revert, the call is refused with ELIGIBILITY_TX_WOULD_REVERT and nothing is returned to sign.

Admit by profile claim

In the CLAIM mode the profile register is a T-REX 5 identity registry on your instance register’s identity factory. It requires one claim topic beyond your instance register’s, profileTopic, and a wallet is admitted when its ONCHAINID carries a valid claim for that topic from claimIssuer. The build takes two calls with the same selection.
1

Sign the profile claims

The first call answers action: SIGN_MESSAGES, phase: SIGN_CLAIMS, with one entry in messages per wallet. Each has scheme: eip712, typedData, issuedAt, messageHash (the EIP-712 digest) and claimType: PROFILE, and its payload is the profile’s requirementsHash. signerAddress must hold a CLAIM_SIGNER key on claimIssuer (ELIGIBILITY_CLAIM_SIGNER_REQUIRED otherwise). Sign each typedData as EIP-712 typed data with it.
2

Write the claims

Call again with claimSignatures: [{ walletAddress, signature, issuedAt }]. signerAddress must now hold a MANAGEMENT key on claimIssuer (ELIGIBILITY_CLAIM_MANAGER_REQUIRED otherwise). Each signature is checked and refused with INVALID_CLAIM_SIGNATURE, CLAIM_SIGNER_NOT_TRUSTED or CLAIM_NOT_VALID, the message naming the wallet. The answer is action: SIGN_TRANSACTIONS with one addClaimTo step per wallet, stepType: admit, addressed to claimIssuer. The first step is simulated from signerAddress (ELIGIBILITY_TX_WOULD_REVERT).
3

Confirm

Broadcast each step and confirm each hash on its own with Confirm Admission.
The wallets are checked as above, with two differences. ALREADY_ADMITTED means the wallet already reads as verified on the eligibility register. COUNTRY_BLOCKED reads the country on the customer record, since a T-REX 5 register records none. Both answers add admission: CLAIM, claimIssuer, profileTopic and waiting, the number of admissions waiting among the ones selected. They carry no top-level transaction or functionName. Each step adds signer, the wallet that sends it, and subject, the wallet admitted, and its walletAddress is the wallet admitted rather than the signer. confirmWith adds perStep: true.

Response Fields

object

Error Codes