For further questions, please use the chat widget in the bottom right corner.
Note: Please include your BTC and Ordinals addresses, a screenshot of the bug/error, and a link to the transaction in the mempool (if applicable).
Error Messages
"The lender/borrower/ in this loan does not have enough BTC balance to fullfill request or has unconfirmed transactions pending. Please try again later".
Lender doesn't have enough BTC to provide for the loan.
Action Item: Borrower needs to wait for 10-15 minutes (the best offer(s) will be deleted), and borrow again.
Borrower doesn't have enough BTC to cover transaction fee.
Action Item: Load up BTC to cover transaction fees
"Repayer does not have sufficient BTC balance for fees or has unconfirmed transactions. Please try again later".
Action Item: Borrower needs to load up BTC to cover transaction fees or the borrower needs to make sure that his BTC for the repayment is confirmed.
Note: Right now, only unconfirmed BTC transactions that originated on Liquidium can be used to repay loans. All other BTC must be confirmed.
"Unlocker does not have sufficient BTC balance for fees or has unconfirmed transactions. Please try again later".
Action Item: Borrower or lender needs to load up BTC to cover transaction fees or the borrower or lender needs to make sure that his BTC for the unlock is confirmed.
Note: Right now, only confirmed BTC can be used to repay loans.
'Low Rune Balance'
Action Item: This means the borrower has an insufficient Rune balance for the collateral in this loan. The Rune balance must also be confirmed. Rune's in unconfirmed transactions are not used.
For Lenders, this means the loan CAN NOT be activated since the collateral amount is insufficient.
The loan was repaid successfully but i can't unlock my ordinal.
Action Item: Unfortunately this is due to a long outstanding bug that is affecting several other users as well. We are working hard to get this resolved.
For some more context, the issue stems from this being a loan on our version 1 DLC system. This was created with a partner of ours. The partner is still working to get the issue resolved, so unfortunately, we are not sure when the timeline is to have this resolved.
It remains a top priority for us as it is affecting several users. Keep your notifications turned on for any updates on this topic.