Skip to main content
This guide is for a tokenization platform or issuer whose clients hold a token they would rather borrow against than sell. By the end the token has a lending market, the market is authorized on the token, and a bank has taken it as lender of record. Your clients can then borrow through your app. Before you start, you need an instance with a registered wallet. That wallet signs the deployment and becomes the market’s deployer. Signing the token-side steps needs a wallet with the agent or identity registry role on the token, which is often your platform’s.

1. Import the token and describe it

Detect Token reads the contract and reports its standard before anything is written. Import Token creates the record your instance holds. Trusset does not deploy the token, hold it or become a party to it. Lenders decide from what you publish. Publish the profile with Update Profile, and the instrument record with its identifiers, legal terms and offering documents with Save Instrument. Only the token’s controller publishes the instrument record. Everything in both is your assertion, and it is marked that way wherever it surfaces. A token without a published profile cannot back a market: deployment refuses it with TOKEN_PROFILE_REQUIRED.

2. Choose the collateral mode

The mode decides where the client’s tokens sit during the loan. It is fixed at deployment. FREEZE is the default and keeps the client in custody of the asset. An ERC-7943 token that is not ERC-3643 cannot be frozen by the adapter, so it runs in CUSTODY. Collateral token standards lists every refusal.

3. Choose how it is priced

Get Deployment Options returns the ranges and the factory’s own limits before you choose.

4. Deploy and nominate a bank

Deploy Market deploys the market, its oracle, rate model, insurance fund, collateral adapter and liquidation router in one transaction. It also attests the asset data built from your profile and sets the opening rate and term offering. Name the banks that may take the market in candidates. Set openToAnyCurator to offer it to any approved lender as well. Such a claimant must be verified on the borrower register you installed, and its claim takes two transactions, announced and then completed after a delay. Add or withdraw a nomination later with Nominate Candidate and Withdraw Nomination. One instance runs one active market per collateral token, collateral mode and settlement token. A second deployment of the same combination answers MARKET_EXISTS.

5. Authorize the market on the token

A deployed market cannot take loans until the token accepts its contracts. Get Setup Steps lists what is outstanding and who must sign each step. Configure Market returns the calldata, the token’s agent or identity registry operator signs it, and Confirm Configuration records it. Where the token gates holders, every recipient of seized tokens must be admitted on it as well. That is the market’s liquidation router, its auction venue when auctions are on, and the sale recipient the bank names. Otherwise a liquidation cannot deliver the collateral.

6. Hand it to the bank

The nominated bank finds the market in its queue and reviews the asset data you attested. When it signs the adoption, it assigns every market role to its own wallets or its agents’. From then on its issuer sets the limits, its rate model owner the rates and its market admin the gates. You no longer change them. Get Nominations shows who may take the market. Get Configuration Status reports pendingCurator until a bank has.

7. Keep the register in step

The collateral lock on chain is not the register entry. Whoever keeps the token’s register makes that entry, from the facts List Pledges returns: who pledged, to whom, how much and in which transaction. In a FREEZE market the client stays the holder and the lock names a pledgee, which is what a pledge entry records. In a CUSTODY market the tokens move to the adapter, a transfer for security, and the change of holder is the event to record. If your platform is not the register provider, pass this step to the party that is. Name that party on the market, on the page of the market in the Issuer Portal, under Asset register, or with Set Market Register. The market then appears in the register provider’s queue. Once it imports the market, it reads the pledge record itself and receives each change as a pledge webhook. The assignment is a record beside the market. It gives the register provider no role on it.

Next

Your clients can now borrow. Embed earn and borrow adds the borrow button and the earning vault to your app. Launch a credit line shows the bank’s side of the adoption.