liabtc-mint-endpoint

• Location: xlink-dao/contracts/liabtc/liabtc-mint-endpoint.clar

• Deployed contract

Façade for xlink-staking contract designed to handle the lifecycle of the LiaBTC rebasing token (mint, burn and rebase operations).

The liabtc-mint-endpoint contract acts as single aBTC staker within the xlink-staking contract. It serves as an abstraction layer, simplifying interactions between LiaBTC users and the liquid staking pool management provided by the xlink-staking contract, also known as XLink Staking Manager.

Mint

The mint operation consists of two main actions:

• User transfers aBTC to be staked in the liquid staking pool.

• User receives LiaBTC tokens in exchange at a 1:1 ratio (1 aBTC = 1 LiaBTC).

When a user mints LiaBTC, the underlying aBTC is transferred to the Staking Manager, which stores the funds, tracks the liquid staking status (including shares and stake balances) and emits an event.

Burn

The burn operation (or unstake) allows users to withdraw their aBTC from the liquid staking pool in exchange for burning LiaBTC tokens at a 1:1 ratio. These operations are managed by the liabtc-mint-registry and involve a waiting period between the burn request and the final withdrawal of aBTC.

Request

User initiates the request to unstake a specific amount of aBTC. During this step:

• That same amount of LiaBTC tokens are burned from the user wallet.

• A burn request is created in the registry with a unique request-id and a PENDING status.

• The aBTC are sent from the Staking Manager to the registry, which will hold the funds until the request is either finalized or revoked.

Finalize

Once the burn-delay period (typically 1,000 Bitcoin blocks) has passed, the user or any other principal can finalize the request. On finalization:

• The corresponding aBTC is transferred from the registry to the requester, completing the unstaking process.

• The request status is updated to FINALIZED.

Revoke

Burn requests can be revoked by the requester at any time before it is finalized. When revoke:

• The corresponding aBTC is returned to the user.

• A mint operation is executed in the same transaction, restoring the user's original amount of LiaBTC.
• The request status is updated to REVOKED.

Rebase

This contract manages the LiaBTC token reserve through the rebase public function. Mint and burn operations perfom a rebase every time they are executed. However, rebase can be called permissionlessly by any principal.

The rebasing mechanism is implemented via the "shares" concept. The LiaBTC reserve reperesents the value in aBTC of the staking shares held by the liabtc-mint-endpoint, as tracked by the XLink Staking Manager contract.

The staking shares held by the liabtc-mint-endpoint are adjusted whenever users mint or burn LiaBTC. Over time, the value of these shares in aBTC grows as accrued staking rewards are reinvested, increasing the reserve.

For a detailed overview of the LiaBTC liquid token, refer to the token-liabtc contract documentation.

Features

Public

rebase

Updates the LiaBTC token reserve by recalculating its value in aBTC based on the staking shares held by the liabtc-mint-endpoint contract.

mint

Mints LiaBTC to the caller (defined as sender within the contract) in exchange for aBTC at a 1:1 ratio. The provided aBTC is staked in the XLink Staking Manager by the liabtc-mint-endpoint on behalf of the user.

The message and signature-packs parameters serve as inputs to the xlink-staking::stake function. They are part of the XLink liquid staking pool's reward accrual mechanism, which operates permissionlessly and relies on validators.

Parameters

Name	Type
amount	uint
message	{ token: principal, accrued-rewards: uint, update-block: uint }
signature-packs	list 100 { signer: principal, message-hash: (buff 32), signature: (buff 65) }

request-burn

Initiates the burn procedure for a certain amount of LiaBTC. Several actions are performed:

• LiaBTC amount is burned from the user wallet.

• The same amount of aBTC is unstaked from the xlink-staking contract and transferred to the liabtc-mint-endpoint, which then transfers it to the liabtc-mint-registry, where it is held until finalization or revocation.
• A request with PENDING status is created on the registry.

As with mint, the message and signature-packs parameters serve as inputs to the xlink-staking::unstake function.

Parameters

Name	Type
amount	uint
message	{ token: principal, accrued-rewards: uint, update-block: uint }
signature-packs	list 100 { signer: principal, message-hash: (buff 32), signature: (buff 65) }

revoke-burn

Revokes a burn request. Only the requester (requested-by field of the request) can call this function. The registry returns the funds back to user as in finalize-request, with the key difference that the mint function is invoked (with the user as sender) to restake the aBTC and mint the LiaBTC back to the user. Request status is updated to REVOKED.

Parameters

Name	Type
request-id	uint
message	{ token: principal, accrued-rewards: uint, update-block: uint }
signature-packs	list 100 { signer: principal, message-hash: (buff 32), signature: (buff 65) }

finalize-burn

Finalizes a burn request by transferring the aBTC from the registry to the user (requested-by field of the request). Request is set as FINALIZED. This function is permissionless and can be called by any user, even those who did not initiate the burn request.

Parameters

Name	Type
request-id	uint

finalize-burn-many

Finalizes requests in bulk.

Parameters

Name	Type
request-ids	list 1000 uint

Governance

The following functions are guarded by the is-dao-or-extension function. This implies that only the LISA DAO or an enabled extension can use these features.

set-use-whitelist

Sets the use-whitelist variable.

Parameters

Name	Type
new-use	bool

set-whitelisted

Assigns the whitelist status of a user. Modifies the whitelisted map.

Parameters

Name	Type
user	principal
new-whitelisted	bool

set-whitelisted-many

Assigns the whitelist status of users in bulk.

Parameters

Name	Type
users	list 1000 principal
new-whitelisted	list 1000 bool

set-mint-paused

Sets the mint-paused variable.

Parameters

Name	Type
new-paused	bool

set-burn-paused

Sets the burn-paused variable.

Parameters

Name	Type
new-paused	bool

set-burn-delay

Sets the burn-delay variable.

Parameters

Name	Type
new-delay	uint

Supporting features

is-dao-or-extension

Standard protocol function to check whether the contract-caller is an enabled extension within the DAO or the tx-sender is the DAO itself (proposal execution scenario). The enabled extension check is delegated to the LISA's executor-dao contract.

is-whitelisted-or-mint-for-all

Checks if a given principal is eligible for minting under the current whitelist settings. If the whitelist is active, returns false if the user is not whitelisted. Returns true in all other cases.

Parameters

Name	Type
user	principal

validate-mint

xlink-staking::validate-stake façade for handling aBTC staking. Within the contract, this function is solely called by the mint function. Throws if mint is paused or the sender is not whitelisted (when applicable).

Parameters

Name	Type
amount	uint

validate-request-burn

xlink-staking::validate-unstake façade for handling aBTC unstaking. Within the contract, this function is solely called by the request-burn function. Throws if burn is paused.

Parameters

Name	Type
amount	uint

validate-revoke-burn

Performs revoke burn validations and returns the corresponding request details. Within the contract, this function is solely called by the revoke-burn function. Validations encompass: burn is not paused, request exists, request has PENDING status and sender matches the requested-by field on the burn request (only the requester can revoke).

Parameters

Name	Type
request-id	uint

validate-finalize-burn

Performs finalize burn validations and returns the corresponding request details. Within the contract, this function is solely called by the finalize-burn function. Validations encompass: burn is not paused, request exists, request has PENDING status and the burn-delay period has been completed.

Parameters

Name	Type
request-id	uint

Getters

is-mint-paused

Returns the mint-paused variable.

is-burn-paused

Returns the burn-paused variable.

is-not-mint-paused-or-fail

Throws with err-paused if mint is paused, returns (ok true) otherwise.

is-not-burn-paused-or-fail

Throws with err-paused if burn is paused, returns (ok true) otherwise.

get-burn-request-or-fail

Returns a burn request stored in the liabtc-mint-registry's burn-request map. If entry doesn't exist, throws.

Parameters

Name	Type
request-id	uint

get-burn-request-or-fail-many

Returns a list of burn requests stored in the liabtc-mint-registry. If any of the entries doesn't exist, throws.

Parameters

Name	Type
request-ids	list 1000 uint

get-burn-delay

Returns the burn-delay variable.

get-current-bitcoin-block

Getter for testing purposes. If mainnet, returns the burn-block-height.

Storage

mint-paused

Data	Type
Variable	bool

Indicates the operational status for the mint (stake) operations.

burn-paused

Data	Type
Variable	bool

Indicates the operational status for the burn (unstake) operations.

burn-delay

Data	Type
Variable	uint

Indicates the waiting period for a burn request, measured in Bitcoin blocks (burn chain). It represents the time users must wait between initiating burn request and being able to finalize it.

use-whitelist

Data	Type
Variable	bool

Indicates whether the whitelist mechanism is currently active. The whitelist applies to mint (stake) operations but not to burn (unstake) ones.

whitelisted

Data	Type
Map	principal bool

Maintains a mapping of users (principal) to their whitelist status (bool).

Relevant constants

PENDING

Type	Value
buff 1	0x00

Burn request pending status. When created, burn requests start with this status.

FINALIZED

Type	Value
buff 1	0x01

Burn request finalize status.

REVOKED

Type	Value
buff 1	0x02

Burn request revoked status.

Contract calls

• xlink-staking: Interactions with the Staking Manager are present in the contract's core opertions. It is called during every mint or burn operation to handle the corresponding stake or unstake actions. Additionally, the Staking Manager is essential to perfom the LiaBTC rebase by retrieving the value of aBTC held by the liabtc-mint-endpoint as a staker within the protocol.
• liabtc-mint-registry: The registry is called to manage burn requests and handle funds during the burning/unstaking process.
• token-liabtc: This contract is called to perform three essential actions: rebase, mint and burn.
• 'SP2XD7417HGPRTREMKF748VNEQPDRR0RMANB7X1NK.token-abtc: As the underlying token that backs LiaBTC, this contract is called for transfers and to specify the token being staked in the Staking Manager.

• 'SM26NBC8SFHNW4P1Y4DFH27974P56WN86C92HPEHH.lisa-dao: This contract is exclusively called by the is-dao-or-extension function for authorizing governance operations.

Errors

Error Name	Value
err-unauthorised	(err u1000)
err-paused	(err u7001)
err-request-pending	(err u7006)
err-request-finalized-or-revoked	(err u7007)
err-not-whitelisted	(err u7008)