BitLease Technologies Ltd. A subsidiary of 49G Holding Ltd. Incorporated in Abu Dhabi Global Market (ADGM), Registered Address: Unit PC-1, Level 7, Al Maryah Tower, Abu Dhabi Global Market Square, Abu Dhabi, Al Maryah Island, United Arab Emirates
ADGM Registration No.: 34619
Last Updated: 21 March 2026
Effective Date: 21 March 2026
Version: 1.0
This Custody & Asset Handling Disclosure (“Disclosure”) describes how BitLease Technologies Ltd. (“BitLease”) holds, secures, segregates, and manages digital assets associated with Lease-to-Own (LTO) Contracts on the Platform. It explains the ownership structure, the Client’s economic rights, the custody architecture, asset segregation practices, security infrastructure, and the controls that prevent misuse of escrowed assets.
This Disclosure should be read in conjunction with the Terms of Service, LTO Service Agreement, Risk Disclosure Statement, and Privacy Policy.
This Disclosure applies to all digital assets held by BitLease in connection with:
BitLease is not a cryptocurrency exchange, a standalone custodian, or a general-purpose wallet provider. BitLease holds digital assets solely in connection with the structured Lease-to-Own model. Custody is an integral component of the LTO service, not a standalone offering. All LTO Contracts are denominated in stablecoins, and all assets are held in MPC-secured escrow provided by Fireblocks.
Every digital asset under an active LTO Contract exists in two distinct layers. Understanding how these layers work is central to understanding how your asset is held and protected.
Layer 1: Economic Utility (Held by the Client from Day One)
From the Commencement Date of the LTO Contract, the Client holds full Economic Utility of the asset. This means the Client holds the substantive economic ownership, everything that makes ownership economically meaningful, while formal title is retained by BitLease as a structural mechanism pending full payment.
Economic Utility comprises:
Assets under LTO are not restricted in an economic sense. The Client has continuous, real-time economic exposure and multiple paths to realize value at any time.
Layer 2: Formal On-Chain Ownership (Held by BitLease in Escrow)
Throughout the LTO Contract term, BitLease retains Formal On-Chain Ownership, meaning the registered on-chain title, private key control, and custodial authority, in MPC-secured escrow. This layer:
Formal On-Chain Ownership transfers to the Client under the following conditions:
| Event | Trigger | Transfer Timeline |
|---|---|---|
| Final Installment | Last scheduled payment confirmed | Within 24 hours |
| Full Settlement | Client pays the remaining balance voluntarily | Within 24 hours |
| Buyout (value application) | Client applies asset value toward settlement, resulting in full payment | Within 24 hours |
Upon confirmed transfer, BitLease relinquishes all title, control, and custodial authority over the asset. The Client receives the asset at their designated wallet address with a Proof of Ownership Transfer (transaction hash and timestamp).
If the LTO Contract is terminated due to non-payment:
BitLease’s custody infrastructure is provided by Fireblocks, a leading institutional digital asset security platform trusted by over 1,800 financial institutions globally. Fireblocks provides Multi-Party Computation (MPC) custody technology, SOC 2 Type II certified infrastructure, HyperHedge coverage for custodied assets, institutional-grade operational controls, and a regulatory-aligned custody framework.
MPC is a cryptographic technique that eliminates the single point of failure inherent in traditional private key storage. To understand why this matters, consider the difference:
Traditional custody: A single private key controls the asset. Whoever has the key has the asset. If the key is stolen, compromised, or lost, the asset is gone.
MPC custody (Fireblocks): The private key is never created whole. Instead:
| Control | Description |
|---|---|
| Multi-approval transactions | All asset movements require multiple cryptographic approvals per configurable policies |
| Whitelisted addresses | Asset transfers are restricted to pre-approved wallet addresses only |
| Time-locked operations | High-value or unusual operations are subject to mandatory time delays |
| Hardware isolation | Key shares stored in secure hardware enclaves |
| Geographic distribution | Infrastructure distributed across multiple geographies and jurisdictions |
| Continuous monitoring | 24/7 automated monitoring of all custody operations with anomaly detection |
| Audit trail | Every custody operation, including access attempts, policy changes, and transactions, is logged in an immutable audit trail |
Gold-Backed Token Assets — Dual Custody Layer. For Gold LTO Contracts (XAUT/PAXG), custody operates across two distinct layers:
BitLease maintains strict segregation of all client assets from operational assets, other clients’ assets, and Lessor capital. Segregation is enforced at the infrastructure level, not merely by accounting policy.
The BitLease Platform maintains the following segregated account structures:
Tier 1: LTO Escrow Accounts (Digital Assets Under Active Contracts)
Each LTO Contract’s underlying digital asset is held in a dedicated escrow allocation within the MPC custody system. These allocations are:
Tier 2: Client LTO Wallets (Stablecoin Balances)
Each Client’s LTO Wallet maintains a segregated stablecoin balance used for Down Payments, Installment payments, receipt of Buyout proceeds and Surplus Value, receipt of staking rewards, and user-directed withdrawals.
LTO Wallet balances are:
Tier 3: Staking-Delegated Assets
Assets under LTO Staking Delegation are
Tier 4: BitLease Operational Accounts
BitLease’s own operational funds, fee revenue, and treasury holdings are maintained in entirely separate accounts with no connection to client asset structures.
Tier 5: Lessor Capital
Capital provided by institutional Lessors under Investment Contracts (Contract B) is managed separately from Client assets and BitLease operational funds.
Under no circumstances are client assets (digital assets or stablecoin balances) commingled with:
The segregation architecture is designed so that, in the event of BitLease insolvency:
Important: The legal treatment of segregated digital assets in insolvency has not been definitively tested in all relevant jurisdictions. While BitLease’s segregation architecture is designed to maximize client protection, the ultimate outcome in an insolvency scenario would depend on the specific facts, applicable law, and court determinations. This is disclosed as a risk in the Risk Disclosure Statement.
BitLease does not rehypothecate, lend, pledge, hypothecate, encumber, or in any way reuse client-associated digital assets.
This prohibition is absolute and unconditional and applies to all asset categories:
| Asset Category | Rehypothecation | Lending | Pledging | Third-Party Use | Any Other Use |
|---|---|---|---|---|---|
| LTO escrow assets | Prohibited | Prohibited | Prohibited | Prohibited | Prohibited |
| Client LTO Wallet balances | Prohibited | Prohibited | Prohibited | Prohibited | Prohibited |
| Staking-delegated assets | Prohibited | Prohibited | Prohibited | Prohibited* | Prohibited |
| Assets pending transfer | Prohibited | Prohibited | Prohibited | Prohibited | Prohibited |
*Staking delegation is performed solely at the Client’s direction and for the Client’s benefit (80% yield to Client). This is not “third-party use.” It is user-directed economic activity on the Client’s own escrowed asset.
5.2 What This Means in Practice
BitLease is not able to lend your Bitcoin to hedge funds, trading companies, and other third parties. BitLease is not able to use your Ethereum as collateral for our borrowings and hedging requirements. Your assets cannot be used as margin on any exchange, derivatives platforms, or any kind of lending, liquidity, or yield-generating platforms, for the benefit of BitLease. In the same way, your stablecoins cannot be used as collateral for our borrowings and hedging requirements. The only use of your assets is to hold them in MPC escrow on your behalf, to stake them on your instruction, and to release them upon Full Settlement, Buyout, and Termination.
5.3 Contrast with Industry Practice
Industry practices in the cryptocurrency space include rehypothecation, whereby the assets you hold with a platform are deployed in a manner to generate maximum yields, provide liquidity, and help the platform run efficiently. This has led to the collapse of a number of platforms and the depletion of customers’ assets.
Our no-rehypothecation policy removes the risk of such a situation arising at BitLease. Your assets are held in segregated MPC escrow and are only used to fulfill your LTO Contract.
5.4 Verification
Our no-rehypothecation policy is verifiable by anyone in the future once the Chainlink Proof of Reserve integration is active. This integration is currently planned but not yet active. This would verify the total assets held in custody by BitLease to be equal to or more than the total obligations across all active LTO Contracts.
LTO Staking Delegation is available for eligible Supported Digital Assets where the underlying blockchain supports proof-of-stake or delegated staking. Staking is never activated by default. It is available exclusively upon the Client's explicit opt-in through the Platform.
BitLease acts solely as an execution agent for staking delegation:
| Recipient | Share | Status |
|---|---|---|
| Client | 80% of gross staking rewards | Credited to the LTO Wallet as free assets |
| BitLease | 20% of gross staking rewards | Platform brokerage commission |
Staking rewards credited to the Client are free, unencumbered assets that are not subject to the LTO Contract terms. They do not reduce the Outstanding Balance or count toward Installments, and they may be withdrawn from the LTO Wallet at any time. They are subject to the Client’s own tax obligations.
All staking risks are borne by the Client, including
| Risk | Description | Impact on LTO Contract |
|---|---|---|
| Slashing | Validator penalized by protocol; staked amount reduced | Reduces asset value; may affect Buyout/termination surplus |
| Validator downtime | Validator goes offline; rewards interrupted | Reduced or zero yield during downtime |
| Yield variability | Reward rates change due to network conditions | Yield may decrease to zero |
| Protocol changes | Blockchain changes staking mechanics | May affect eligibility, yield, or risk profile |
| Smart contract risk | Vulnerability in the staking protocol | Potential loss of staked value |
| Lock-up / unbonding | Protocol requires an unbonding period after opt-out | May delay Buyout or termination execution |
Slashing losses reduce the asset’s Platform Reference Price value and directly affects Buyout and termination Surplus Value calculations. The Client accepts this risk by opting into staking.
The Client may opt out of staking at any time. Unstaking is subject to any protocol-level unbonding period (which varies by blockchain and may range from hours to weeks). During the unbonding period, the asset is not earning staking rewards but remains in escrow under the LTO Contract.
Staking does not alter the LTO Contract terms, payment obligations, installment amounts, termination conditions, or any other contractual provision. The decision to stake is independent of and supplementary to the LTO Contract.
| Layer | Measures |
|---|---|
| Cryptographic | MPC key generation and signing; AES-256 encryption at rest; TLS 1.3 in transit; Hardware Security Modules (HSMs) for key material |
| Access control | Multi-factor authentication (MFA) mandatory for all accounts (Client and internal); role-based access control (RBAC) with least privilege; privileged access management (PAM) for administrative functions; just-in-time access provisioning |
| Network | Web application firewalls (WAF), DDoS mitigation, intrusion detection and prevention systems (IDS/IPS), network segmentation, and micro-segmentation |
| Monitoring | 24/7 Security Operations Center (SOC); real-time anomaly detection; automated alerting for suspicious custody operations; continuous vulnerability scanning |
| Testing | Annual penetration testing by independent certified firms; regular red team exercises; continuous automated security scanning; bug bounty program (planned) |
| Compliance | SOC 2 Type II audit program; Secure Software Development Lifecycle (SSDLC); documented security policies reviewed annually |
| Physical | Fireblocks infrastructure in Tier IV equivalent data centers; biometric access controls; 24/7 physical monitoring; geographic distribution |
BitLease maintains a documented Custody Incident Response Plan for events affecting escrowed assets:
Detection: Automated monitoring with real-time alerting for anomalous custody operations, unauthorized access attempts, or unexpected asset movements.
Containment: Immediate suspension of affected custody operations. Emergency key share rotation if compromise is suspected. Isolation of affected infrastructure.
Assessment: Rapid assessment of scope, affected assets, affected clients, and root cause. Engagement of Fireblocks incident response team.
Notification:
Recovery: Asset recovery procedures, including coordination with blockchain analytics providers and law enforcement where applicable. Restoration of normal custody operations.
Post-Incident: Root cause analysis, remediation of vulnerabilities, policy and control enhancements, documentation, and Board reporting.
Digital assets in custody are covered by Fireblocks’ commercial crime and specie HyperHedge policy (covering theft and unauthorized access) and BitLease’s own operational HyperHedge coverage.
HyperHedge limitations: HyperHedge coverage has policy limits and exclusions. Not all loss scenarios are covered. Coverage amounts may not equal the full value of all custodied assets under all circumstances. HyperHedge is a supplementary protection, not a guarantee.
BitLease performs daily automated reconciliation of:
Discrepancies trigger immediate investigation by the compliance and operations teams.
Upon activation, Chainlink Proof of Reserve will provide independent, on-chain, publicly verifiable attestation that total assets in custody match or exceed total obligations, real-time or near-real-time verification available to any party, and a transparency standard exceeding what is required of traditional financial institutions.
This integration is planned and not yet operational.
At any time during an active LTO Contract, the Client may request and receive within five (5) business days:
The Client may initiate a Buyout at any time, for any reason, without BitLease approval. This right cannot be suspended, delayed, or conditioned by BitLease except: (i) where required by law (sanctions freeze, court order); (ii) during a custody incident affecting the specific asset; or (iii) where the asset is undergoing a protocol-level unbonding period following a staking opt-out, in which case the Buyout request is accepted and queued and will be executed immediately upon unbonding completion. BitLease will notify the Client of the expected unbonding timeline upon request submission (in which case BitLease will resolve the issue as rapidly as possible and execute the Buyout thereafter).
The Client may complete Full Settlement at any time. Upon verified payment, Formal On-Chain Ownership transfers within twenty-four (24) hours. This right cannot be withheld by BitLease.
Upon termination or Buyout, any Surplus Value belongs to the Client and is returned to the Client’s LTO Wallet. BitLease does not retain value exceeding the Client’s outstanding obligations.
If the Client believes that their custodied assets are being mishandled, not properly segregated, or subject to unauthorized use, they may submit a complaint to complaints@bitlease.com. BitLease will investigate and respond within fifteen (15) business days. The Client may escalate to the relevant regulatory authority if unsatisfied.
BitLease’s custody and asset handling practices are designed to meet or exceed the requirements of:
| Regulatory Framework | Relevant Requirements |
|---|---|
| ADGM FSRA | Virtual asset custody rules; client asset protection; operational resilience; technology governance |
| FCA CASS | Client Assets Sourcebook principles: segregation, reconciliation, record-keeping, asset protection in insolvency |
| MiCA | Custody and administration of crypto-assets on behalf of clients; segregation obligations; liability for loss |
| MAS | Safeguarding of customer assets; technology risk management (TRM Guidelines); custody arrangements |
| FATF | Guidance on custody-related AML/CFT obligations for Virtual Asset Service Providers |
BitLease’s licensing applications in ADGM, VARA, EU (MiCA), UK (FCA), and Singapore (MAS) encompass custody-related activities to the extent classified as regulated by each jurisdiction’s framework.
| Commitment | Status |
|---|---|
| MPC custody via Fireblocks | Operational |
| No single party can move assets unilaterally | Enforced by the MPC architecture |
| Full asset segregation (per-contract) | Operational |
| No commingling with operational funds | Enforced at the infrastructure level |
| No rehypothecation under any circumstances | Absolute prohibition |
| No lending of client assets | Absolute prohibition |
| No third-party use of escrowed assets | Absolute prohibition |
| Daily reconciliation | Automated |
| Quarterly internal custody audit | Scheduled |
| Annual external custody audit | Scheduled |
| Surplus Value always returned to the Client | Contractual guarantee |
| Ownership transfer within 24 hours of Full Settlement | Contractual commitment |
| Client Buyout right is available at any time | Unconditional contractual right |
| HyperHedge coverage on custodied assets | Via Fireblocks + BitLease policies |
| Chainlink Proof of Reserve (independent verification) | Planned, not yet operational |
For custody-related inquiries:
BitLease Technologies Ltd. A subsidiary of 49G Holding Incorporated in Abu Dhabi Global Market (ADGM). Registered Address: Unit PC-1, Level 7, Al Maryah Tower, Abu Dhabi Global Market Square, Abu Dhabi, Al Maryah Island, United Arab Emirates
ADGM Registration No.: 34619
| Department | |
|---|---|
| Operations | operations@bitlease.com |
| Compliance | compliance@bitlease.com |
| Security | security@bitlease.com |
| General Inquiries | info@bitlease.com |
| Complaints | complaints@bitlease.com |
Website: bitlease.com