Mint

Mint or Issue ENSC

POST /mint

This endpoint mints or issues ENSC tokens by generating an unsigned transaction. It requires that the asset symbol is "ENSC", verifies that the recipient is eligible to mint and confirms that the amount does not exceed the recipient’s mint allocation. Upon successful validation, it returns the unsigned transaction details.

Headers

Name	Value
Content-Type	application/json
Authorization	Bearer <api_key>

Body

Name	Type	Description
recipient	string	The wallet address that will receive the minted tokens.
amount	number	The amount to mint (in whole tokens).
assetSymbol	string	The asset symbol to mint (must be "ENSC").

Example

Mint Request

{
  "recipient": "0xRecipientAddressABC123",
  "amount": 500,
  "assetSymbol": "ENSC"
}

Response (200) Ok

{
  "status": 200,
  "message": "Transaction processed successfully",
  "data": {
    "to": "0xTokenContractAddressXYZ",
    "value": 0,
    "gasLimit": "0x186a0",
    "gasPrice": "20000000000",
    "nonce": "5",
    "data": "0x40c10f19000000000000000000000000xRecipientAddressABC12300000000000000000000000000000000000000000000000000000000001f4",
    "gasPrice": "20000000000",
    "nonce": "5"
  }
}

Error Responses

Invalid Recipient Address

{
  "status": 400,
  "error": "Invalid Request",
  "message": "Invalid recipient address",
  "data": null
}

Invalid Asset Symbol

// If the asset symbol is not "ENSC", the service returns an error:
{
  "status": 400,
  "error": "Invalid Request",
  "message": "Invalid asset symbol, only ENSC is supported",
  "data": null
}

Recipient Not Allowed to Mint

{
  "status": 403,
  "error": "Forbidden",
  "message": "Recipient is not allowed to mint",
  "data": null
}

Exceeded Mint Allocation

// If the requested amount exceeds the recipient’s mint allocation:
{
  "status": 400,
  "error": "Invalid Request",
  "message": "Recipient has reached their mint limit",
  "data": null
}