Executive Summary
- The South African supplier should operate nodes under a restricted signing arrangement controlled by the Irish custodian. Giving the supplier an unrestricted validator key leaves it able to sign exits and influence execution rewards. Custody classification depends on actual control over assets or their means of access. A contractual description cannot settle that test. (Regulation (EU) 2023/1114, art. 3(1)(17); Ethereum consensus specifications, Phase0 Honest Validator and Bellatrix Honest Validator, block proposal; Electra Beacon Chain, process_voluntary_exit.)
- The Irish custodian needs custody authorisation and explicit customer consent for its staking service. The European Commission treats intermediary staking involving custody as ancillary to custody under the Markets in Crypto-Assets Regulation (MiCA). Its interpretation is nonbinding. Any client transfers that meet the separate statutory definition require the relevant transfer permission. (Regulation (EU) 2023/1114, arts 59, 75 and 82; Commission answers published by ESMA, Q&As 2067 and 2071, 20 June 2024.)
- The South African node-operator exemption continues separately from the expired general licensing application timetable. It depends on the operative notice and its conditions, rather than the business's chosen description. The financial-intelligence test is separate and turns on the activities performed. (FSCA FAIS Notice 90 of 2022, paras 1–4; Financial Intelligence Centre Act 38 of 2001, Schedule 1, item 22.)
- An attributable slashing loss can expose the custodian to customer liability under MiCA. Slashing means a protocol penalty for specified conflicting signatures. The supplier's reimbursement obligation must follow a separate agreement identifying causation, covered losses and limits. Customer consent does not remove the statutory liability. (Regulation (EU) 2023/1114, arts 73(1) and 75(8); Commission answer, Q&A 2067.)
- Ethereum permits the custodian to initiate an exit through its withdrawal address without the supplier's validator key. Eligibility checks, queues and the withdrawal sweep still govern when ETH becomes available. Customer terms and supplier response times must reflect those separate stages. (EIP-7002, Specification; Ethereum consensus specifications, Electra Beacon Chain, process_withdrawal_request and initiate_validator_exit.)
- The custodian remains responsible for outsourced operations and compliance with the Digital Operational Resilience Act (DORA). Its contract needs enforceable access, incident assistance, continuity and exit rights, backed by evidence that the supplier cannot bypass the signing restrictions. A fiat service fee also requires South African tax and exchange-control treatment; it does not become exempt because the infrastructure supports cryptoassets. (Regulation (EU) 2023/1114, art. 73; Regulation (EU) 2022/2554, arts 28–30; Exchange Control Regulations, 1961, reg. 6; Income Tax Act 58 of 1962, s. 1, definition of gross income.)
The asset and signing sequence
Staking commits ether (ETH), Ethereum's native cryptoasset, to support the network's proof-of-stake process. Validators propose transaction blocks and attest to the chain. Protocol rules provide rewards for duties performed and penalties for specified failures. The selected service uses Ethereum mainnet validators with Type 1 withdrawal credentials, identified by the prefix 0x01. Each newly activated validator requires 32 ETH. That figure describes the protocol threshold, rather than the size of the proposed transaction. (Ethereum consensus specifications, Phase0 Honest Validator, validator duties; Electra Beacon Chain, MIN_ACTIVATION_BALANCE and is_eligible_for_activation_queue.)
The Irish CASP obtains customers' staking instructions, records their respective interests and controls the deposit transaction. The supplier receives no customer assets. Its initial payment is a separate fiat invoice paid through an ordinary banking channel. No South African retail customer or transfer of South African customer cryptoassets abroad forms part of this arrangement.
A validator has a public identity and a private signing key, called its BLS key. The key authenticates consensus duties: proposing blocks and attesting to the chain. A different credential records the execution address that receives withdrawals. Control of that address depends on its account key or, for a contract wallet, its code and administrative permissions. Keeping these roles distinct permits a custodian to outsource computing operations without giving the operator authority to spend withdrawn ETH. (Ethereum consensus specifications, Phase0 Honest Validator, validator duties; EIP-7002, Specification.)
Ethereum does not supply a native delegation arrangement that allocates contractual rights between these businesses. The B2B agreement assigns operational duties outside the protocol. Customer entitlements remain in the CASP's custody records, while the chain records validator balances and withdrawal credentials. The selected service excludes lending, restaking and the issue of a transferable receipt token. (Ethereum, Delegated staking, What is delegated staking? and The delegation spectrum; Regulation (EU) 2023/1114, art. 75(2).)
Two reward paths require separate controls. Consensus rewards increase the validator balance. During an automatic sweep, the network checks validators in turn and sends an eligible Type 1 validator's balance above 32 ETH to its withdrawal address. Execution transaction rewards use a fee-recipient address selected during block production. That address can differ from the withdrawal address. The CASP must control both destinations and reconcile received rewards with its customer ledger. (Ethereum consensus specifications, Electra Beacon Chain, get_validators_sweep_withdrawals; Bellatrix Honest Validator, prepare_execution_payload.)
The supplier's fee should remain a fiat contractual debt. Giving it a right to deduct ETH at source would introduce a new asset-control and payment arrangement. The customer agreement should state the gross reward calculation, the CASP's charge, any disclosed supplier charge and the resulting customer entitlement. The CASP cannot use customer assets for its own account merely because the customer consents. ESMA states that the CASP cannot retain all staking profits for itself. (Regulation (EU) 2023/1114, arts 66(1)–(3) and 70(1); ESMA Q&A 2607, 9 July 2025.)
The supplier's restricted signing authority
The proposed allocation of a validation key needs a technical change. An unrestricted BLS key can sign a voluntary exit as well as routine duties. It can produce conflicting messages that cause slashing, and it can authenticate a block with a different execution fee recipient. Retaining withdrawal credentials therefore leaves material powers with the operator if it holds that key without restriction. (Ethereum consensus specifications, Phase0 Honest Validator, get_block_signature and get_attestation_signature; Electra Beacon Chain, process_voluntary_exit; Bellatrix Honest Validator, block proposal.)
The recommended arrangement keeps signing material under CASP control, outside the supplier's administrative reach. The supplier receives neither the private key nor a recovery or signing share. The South African company runs execution and consensus nodes and submits authenticated requests for approved validator duties. A CASP-controlled signing service checks those requests before signing. The CASP alone controls key generation, recovery, signing policies, access revocation and emergency administration. These are proposed design conditions, distinct from handing the supplier a raw signing key.
The signing service must check the chain, validator identity, permitted message and actual data being signed. It must reject conflicting requests, preserve signing history through restart and failover, and reject requests outside approved duty times. It must enforce the CASP's execution fee recipient and reject supplier requests for voluntary exits or unrestricted signing. Checking a displayed field is inadequate if the supplier can submit a different signing root, which is the cryptographic value authenticated by the signature. Administrative accounts, backups and direct interfaces must obey the same allocation. Remote signing is supported by current developer documentation; the required restrictions depend on the deployed implementation. (Ethereum consensus specifications, Phase0 Beacon Chain, compute_signing_root; Phase0 Honest Validator, Protection best practices; Consensys, Web3Signer, Introduction, Private key management best practices and Slashing protection.)
The initial service should exclude external services that build or relay proposed blocks, and additional reward-routing arrangements. Those mechanisms can introduce payment paths that a single fee-recipient check does not govern. Compounding credentials and consolidation should also require separate approval. Consolidation can move a validator balance to a target with a different withdrawal address when the source withdrawal controller authorises it. The supplier must have no authority to initiate that process. (EIP-7251, Specification; Ethereum consensus specifications, Electra Beacon Chain, process_consolidation_request.)
MiCA custody and the supplier's territorial position
On this restricted design, the stronger characterisation is an outsourced technical service. MiCA defines custody through safekeeping or control of cryptoassets, or of their means of access. It does not confine custody to holding the only withdrawal key. A business customer is still a client for MiCA purposes, so the B2B relationship supplies no general exemption. (Regulation (EU) 2023/1114, arts 3(1)(17) and 3(1)(39).)
The supplier neither receives customer ETH nor decides its destination. It has no withdrawal key, recovery share, signing-policy authority or right to use customer assets. Its approved requests support consensus, while the CASP retains the system that authorises signatures and the means to recover operations. Those facts support treating the supplier as an infrastructure contractor under Article 73, rather than a second custodian. The ESMA and EBA report describes signing-key-only validator services separately from custody arrangements. Its description is analytical, rather than a statutory exemption. (Regulation (EU) 2023/1114, arts 3(1)(17) and 73; ESMA and EBA, Joint Report under Article 142 MiCA, 16 January 2025, paras 168–171.)
The strongest adverse argument is that the supplier controls a means of access because its instructions can affect staked value. That argument becomes stronger where the supplier can alter reward destinations, sign outside approved duties or prevent the CASP from recovering control. Causing harm through an operational error does not by itself establish custody; the statutory question remains safekeeping or control. The CASP must enforce those permissions and retain independent recovery; the supplier's actual powers determine custody classification. (Regulation (EU) 2023/1114, art. 3(1)(17).)
MiCA's authorisation requirement applies to crypto-asset services provided within the Union. The supplier's proposed position rests on its activity falling outside the listed services, not on its South African location. If its actual powers amount to custody, the Irish CASP cannot cure that defect through its own permission. Article 75(9) permits the appointment of another custody provider only where that provider is authorised under Article 59. A South African financial-services permission alone would not satisfy that requirement. (Regulation (EU) 2023/1114, arts 2(1), 59 and 75(9).)
The Irish CASP's customer permissions
The Irish CASP should retain the customer-facing staking obligation and obtain explicit consent before committing customer ETH. Staking is not a separately listed MiCA service. The Commission treats intermediary staking involving custody as ancillary to custody and applies the custody requirements. Its answer is official interpretative material, but it does not bind the Court of Justice. (Regulation (EU) 2023/1114, arts 3(1)(16), 59 and 75; Commission answer published by ESMA, Q&A 2067, 20 June 2024.)
The customer agreement must identify the custody service, staking mandate, security arrangements, fees and applicable law. It should explain slashing, reward variability, exit stages and the CASP's use of a technical supplier. The CASP remains responsible for accurate customer statements and for preserving ownership rights. Outsourcing cannot change the CASP's relationship or obligations towards customers. Consent authorises the agreed activity; it cannot contract away mandatory custody duties. (Regulation (EU) 2023/1114, arts 66, 73(1)(b) and 75(1)–(7).)
The CASP must assess transfer services separately from custody. MiCA separately defines transferring cryptoassets between distributed-ledger addresses or accounts on behalf of a person. The Commission requires the relevant permission when the activity meets that definition, even where it accompanies another authorised service. The contracting team must map the deposit, subsequent movements and customer return against that test. Where the CASP itself provides a qualifying transfer, it needs the transfer permission and customer terms required by Article 82. Network validation alone does not amount to accepting and executing a particular customer's transfer mandate. (Regulation (EU) 2023/1114, arts 3(1)(26), 59 and 82; Commission answer, Q&A 2071, 20 June 2024.)
The hypothetical CASP is authorised for custody; it must obtain any separate transfer permission required by its actual activities. The customer documents and operational allocation should be completed before funding any validator. (Regulation (EU) 2023/1114, arts 59, 63 and 82.)
South African financial-services and financial-intelligence treatment
The South African company must analyse its own activities under the Financial Advisory and Intermediary Services Act. Cryptoassets falling within the operative declaration are financial products. Advice and intermediary services remain the relevant statutory categories, even where the customer is an overseas institution. The absence of South African retail customers does not create an exemption from that analysis. (Financial Advisory and Intermediary Services Act 37 of 2002, ss 1 and 7(1); General Notice 1350 of 2022, Government Gazette 47334, 19 October 2022.)
FSCA FAIS Notice 90 of 2022 provides an exemption from section 7(1) for persons rendering financial services in relation to cryptoassets. Its continuing treatment of miners and node operators differs from the general application timetable. A node operator must run software that keeps a complete or pruned blockchain and broadcasts transactions across the network. The recommended supplier must actually perform those functions. A business that only supplies an unrelated hosted service cannot rely on the definition merely by adopting a validator label. (FSCA FAIS Notice 90 of 2022, paras 1, 2 and 3(3)(b).)
For miners and node operators, the exemption continues until amended or withdrawn under the notice. The general requirement to apply between June and November 2023 excludes those categories. All exempt persons remain subject to the requirement to supply information requested by the FSCA, and breach of an applicable condition causes the exemption to lapse. The continuing provision therefore cannot be confused with temporary relief for an outstanding application. (FSCA FAIS Notice 90 of 2022, paras 3(1)–(3) and 4.)
The notice is worded by category of person; it does not expressly say that a node operator may perform only node functions. That is not a sound basis for adding custody, personalised investment recommendations or customer asset administration without a fresh assessment. The FAIS definitions reach advice about financial products and specified intermediary activities involving their administration or safekeeping. The defensible initial scope confines the supplier to the defined infrastructure service and records the exemption's actual application. (Financial Advisory and Intermediary Services Act 37 of 2002, s. 1; FSCA FAIS Notice 90 of 2022, paras 1–4; FSCA Communication 30 of 2022, para. 2.6.)
Financial-intelligence obligations require a separate activity test. Schedule 1, item 22 of the Financial Intelligence Centre Act covers specified cryptoasset businesses, including safekeeping or administration of assets or instruments enabling control. The FAIS node-operator exemption does not amend that schedule. The FIC distinguishes a technology provider from the person providing the cryptoasset service, which supports the restricted infrastructure arrangement. Its guidance cannot override item 22 where the supplier's actual powers satisfy the statutory test. (Financial Intelligence Centre Act 38 of 2001, Schedule 1, item 22; FIC Public Compliance Communication 57, 3 July 2023, paras 2.3–2.6.)
If the supplier becomes an accountable institution, it must meet the resulting registration, customer due-diligence, record and risk-management requirements. A retained withdrawal key or customer-facing asset service would require that analysis before launch. Even a business outside item 22 must address suspicious-transaction reporting where section 29 applies. The initial arrangement should therefore document customer identity, fee purpose and actual technical powers, without treating the EU customer's authorisation as a substitute for South African duties. (Financial Intelligence Centre Act 38 of 2001, ss 21–21H, 22–24, 29, 42 and 43B.)
The fiat fee, exchange control and tax
The initial cash flow is payment for a South African company's service to a non-resident. It does not involve exporting South African customers' cryptoassets. The supplier should receive the fee through an authorised dealer with the service agreement, invoice and payment purpose available for classification and reporting. Foreign-currency entitlements remain subject to the Exchange Control Regulations and applicable permissions. The service label does not remove those requirements. (Exchange Control Regulations, 1961, reg. 6; South African Reserve Bank, Currency and Exchanges Manual for Authorised Dealers, section E.)
The current manual permits a customer foreign currency account for a South African legal person supplying services in South Africa to non-residents and receiving the foreign currency in South Africa. Funds in an eligible account can be retained without conversion into rand, while the repatriation requirement remains. A foreign bank account or a later crypto-denominated payment needs its own assessment. The 2026 proposals to change capital-flow treatment cannot supply permission before their implementation. (Currency and Exchanges Manual for Authorised Dealers, E(B)(i)(a)(ff), E(B)(ii)(a)(aa) and E(D); SARB Exchange Control Circular 19/2026, 31 July 2026.)
The fiat service fee is revenue earned by the South African company for its own business. If the company is South African tax resident, the section 1 gross-income test includes revenue received or accrued from domestic and foreign sources. The company must establish its tax residence and account for the fee accordingly. Calling the service crypto staking creates no special income-tax exemption. (Income Tax Act 58 of 1962, s. 1(1), definition of gross income.)
South African VAT zero-rating for an exported service depends on the conditions in section 11(2)(l), including the recipient and the exclusions relating to presence and property. The supplier must retain the evidence required by section 11(3). A foreign billing address alone does not establish the zero rate. For the Irish CASP, taxable imported technical services are generally subject to the recipient's reverse-charge accounting where the service is supplied to its Irish business establishment. Any restriction on input recovery must enter the commercial pricing analysis. (Value-Added Tax Act 89 of 1991, ss 11(2)(l) and 11(3); Value-Added Tax Consolidation Act 2010 (Ireland), ss 12(1) and 34(a).)
Outsourcing and operational resilience
The Irish CASP remains fully responsible for outsourced operations under MiCA. It must retain enough expertise and resources to assess the supplier, supervise the service and manage its risks. The agreement must preserve information access, cooperation with the competent authority and on-site access. The CASP also needs an outsourcing policy, contingency arrangements and an exit strategy. A clause promising ordinary commercial cooperation is insufficient where it permits the supplier to refuse a regulator's inspection. (Regulation (EU) 2023/1114, art. 73(1)–(4).)
DORA applies to a CASP authorised under MiCA. Running validator infrastructure as an ongoing digital service falls within its information and communication technology (ICT) service analysis. The CASP must assess whether that service supports a critical or important function by examining the consequences of failure. Customer losses and an inability to perform the custody mandate can make that classification appropriate. DORA requires proportionate implementation and contains specified relief for microenterprises, without removing all contract and risk duties. The supplier does not become an EU-authorised CASP merely because DORA requirements pass into its contract. (Regulation (EU) 2022/2554, arts 2(1)(f), 3(21)–(22), 4, 28 and 30.)
Before contracting, the CASP must assess the service's risks, supplier suitability and conflicts, including relevant concentration risk. Where the service supports a critical or important function, Article 29 adds requirements concerning substitutability and third-country subcontracting. Those requirements include insolvency, data recovery and effective enforcement. The CASP must keep the required register of ICT arrangements and notify its authority in the circumstances prescribed for planned services supporting critical or important functions. An outsourced validator is not automatically a designated critical ICT third-party provider. (Regulation (EU) 2022/2554, arts 28(3)–(4), 29 and 31.)
The contract needs service descriptions, locations, service levels, data availability and return provisions, incident assistance and termination rights. For a critical or important function, it also needs measurable performance targets, reporting duties, contingency testing and effective audit and access rights. Those rights extend to the competent authorities and appointed persons. Subcontracting must preserve the CASP's ability to understand the chain of providers and respond to material changes. (Regulation (EU) 2022/2554, art. 30(2)–(3); Commission Delegated Regulation (EU) 2024/1773, arts 8–10; Commission Delegated Regulation (EU) 2025/532, arts 3–6.)
The CASP's continuity plans must address loss of an outsourced critical or important function and undergo realistic annual testing. Permissionless-network disruption also requires timely communication about service recovery, customer assets and the proposed response. A supplier should therefore provide information that the CASP can use in those notices and participate in recovery exercises. The CASP remains accountable for its own plans and customer communications. (Regulation (EU) 2023/1114, art. 68(7); Commission Delegated Regulation (EU) 2025/299, arts 2–5.)
Incident notice should reach the CASP early enough for it to meet its own classification and reporting duties. The supplier should preserve evidence, provide status updates and support recovery under defined escalation contacts. The contract should require access to relevant client, signer and infrastructure records while restricting unnecessary customer data. MiCA requires the CASP to retain service records for five years, with extension to seven years where the competent authority requests it before expiry. Retention periods for supplier records should support those duties and the chosen claims process. (Regulation (EU) 2022/2554, arts 17–19 and 30; Regulation (EU) 2023/1114, arts 68(9) and 73.)
The CASP's records must permit reconstruction of the service and identification of amendments. Custody records must distinguish customer balances and identify outsourced tasks and ownership agreements. Documents defining the CASP's and customers' rights have a retention period measured from termination of the agreement. That clock should not be applied indiscriminately to every node log. (Commission Delegated Regulation (EU) 2025/1140, arts 2–5.)
If the supplier processes personal data for the CASP, the parties need written processor terms covering instructions, security, subcontractors and assistance. Making personal data available in South Africa also requires a lawful international-transfer arrangement. South Africa has no Commission adequacy decision, so the parties must establish an applicable transfer route before access begins. Keeping signing keys with the CASP does not determine where support logs or customer-identifying information can be accessed. (Regulation (EU) 2016/679, arts 28 and 44–46; European Commission, Adequacy decisions, list maintained under art. 45(8).)
Slashing and the custodian's liability to customers
A slashable signing error can destroy part of the existing stake and force the validator to exit. The relevant event is a conflicting proposal or attestation that satisfies the protocol's slashing rules. An invalid message that the network rejects is not automatically slashable, but a rejected proposal can still contain a signed conflicting header that satisfies the slashing rules. Ordinary downtime can reduce rewards and incur penalties; widespread failure to finalise can produce further balance losses. These distinctions belong in the service definitions because the evidence and financial consequences differ. (Ethereum consensus specifications, Phase0 Beacon Chain, process_proposer_slashing and process_attester_slashing; Phase0 Honest Validator, How to avoid slashing; Electra Beacon Chain, slash_validator and process_slashings.)
MiCA requires the custodian to compensate customers for loss of cryptoassets or means of access caused by an attributable incident. Article 75(8) caps that statutory liability at the market value of the lost cryptoassets when the loss occurred. The Commission's staking answer treats losses arising from the staking service and the underlying staking activity as attributable to the CASP. A blanket statement that the customer accepts all protocol losses would conflict with that interpretation. (Regulation (EU) 2023/1114, art. 75(8); Commission answer, Q&A 2067.)
Under Article 75(8), the CASP can demonstrate non-attribution where the incident occurred independently of the relevant service or its operations. The provision includes an inherent distributed-ledger problem beyond the CASP's control. The Commission's treatment of staking means the CASP should not assume that every protocol penalty falls within that exception. A penalty caused by a duplicated validator instance or defective signing process is closely connected to the outsourced operation. Outsourcing leaves the CASP responsible for its MiCA obligations. (Regulation (EU) 2023/1114, arts 73(1) and 75(8).)
Lost prospective rewards require separate treatment. An expectation of earning ETH is different from ETH already credited and then destroyed. Penalties deducted from an existing balance can engage Article 75(8). For an Irish-law consumer service contract, the Consumer Rights Act 2022 imposes service and conformity duties and preserves damages subject to its conditions. It also restricts exclusions and unfair terms. A failure to meet an agreed performance obligation can therefore require a separate contractual-remedies analysis. The MiCA valuation cap should not be presented as resolving every such remedy. (Regulation (EU) 2023/1114, art. 75(8); Consumer Rights Act 2022 (Ireland), ss 75, 77–82, 94–95 and 129–130.)
Contractual recourse against the South African validator
The supplier agreement should allocate losses according to the functions each party controls. Choose Irish law for this B2B contract and specify a dispute forum, evidence access and enforcement arrangements. Irish law implies due skill, care and diligence in a business supply of services. Section 40 permits variation of the implied service terms by express agreement, course of dealing or binding usage. Its consumer qualification should not be mistaken for a general reasonableness test governing every negotiated B2B cap. A term restricting liability or remedies for misrepresentation faces the separate fair-and-reasonable test in section 46. (Sale of Goods and Supply of Services Act 1980, ss 39, 40 and 46.)
The agreement should define recoverable slashing loss, balance penalties, missed rewards and reasonable investigation or recovery costs. It should state how each loss is measured, when its value is fixed and how any currency conversion works. Customer redress paid by the CASP needs an express route into supplier recourse where the supplier caused the covered failure. The CASP's statutory duty to its customers does not itself create an identical indemnity against the validator. (Regulation (EU) 2023/1114, arts 73 and 75(8).)
A reimbursement remitted from South Africa should use an authorised-dealer route appropriate to that payment. An obligation to reimburse in ETH introduces a separate exchange-control question. The agreed remedy should therefore specify a lawful payment method before a loss occurs. (Exchange Control Regulations, 1961, regs 2(3) and 3(1)(c).)
An ordinary fee-based cap can leave the CASP with substantially more customer exposure than supplier recovery. Negotiations should therefore address separate treatment for asset losses, key compromise, unauthorised signatures and deliberate misconduct. Any exclusion must be tested against the governing law and its exact wording. The contract should also state whether service credits reduce damages, replace them for a defined event, or leave asset-loss claims intact. The parties should specify whether any consequential-loss exclusion covers missed rewards or customer compensation.
The supplier should answer for conflicting requests, insecure node operations and unauthorised actions within its control. The CASP should answer for its own signer administration, withdrawal instructions and policy changes. A compromised CASP signer can contribute to a slashing event even where the supplier operates the nodes. The allocation should permit an evidence-based assessment of concurrent failures, with mitigation and recovery duties assigned to each party. The network's penalty alone cannot establish contractual fault. (Ethereum consensus specifications, Phase0 Honest Validator, How to avoid slashing; Consensys, Web3Signer, Slashing protection.)
Preserve the signed conflicting messages, validator identity, chain and fork information, duty assignments, signing history and synchronised incident logs. Record software versions, approved changes, failover actions and the CASP's instructions. The parties should agree custody of those records, access during a dispute and a technical expert process that does not displace regulator access or customer rights. Conflicting signatures produced during failover must be traceable to the responsible instance, policy and signing history, including any restored backup or database.
Protocol changes need an assigned decision-maker and implementation timetable. The supplier should monitor required client updates and implement versions approved by the CASP. Where a fork or another event creates new assets or rights, Article 75(4) gives customers an entitlement based on their positions at that event. A valid customer agreement signed beforehand may expressly provide otherwise. The CASP must immediately record in its register of positions any event likely to create or modify a customer's rights. The supplier contract should distinguish a missed required update from a network event outside either party's operational control. Describing every event as protocol risk would leave those different causes unresolved. (Regulation (EU) 2023/1114, arts 73 and 75(4), (8).)
Insurance must be assessed against the actual insured event. A cyber or professional-liability policy may exclude cryptoassets, contractual indemnities or correlated protocol losses. The parties should examine covered entities, subcontractors, limits, deductibles, valuation and notification conditions before treating a policy as funding for the indemnity. MiCA permits prudential safeguards through own funds, an insurance policy or a comparable guarantee. Where the CASP relies on an insurance policy for that safeguard, the policy must cover Article 75(8) liability among the required risks. That requirement does not establish that the supplier's policy, or a particular limit, will fund the agreed indemnity. (Regulation (EU) 2023/1114, art. 67(4)–(6).)
Exit delays and business failure
The CASP should retain an independent route to end validation. EIP-7002 permits an exit request from the recorded withdrawal address without the supplier's BLS key. If that address is a contract wallet, the CASP must test that its code and permissions can submit the request. The CASP must fund the request and gas, submit it correctly and check the resulting consensus state. The protocol checks eligibility and processes the exit before the withdrawal delay and sweep. Broadcasting a transaction does not establish that the request was accepted or that the ETH is immediately spendable. (EIP-7002, Specification; Ethereum consensus specifications, Electra Beacon Chain, process_withdrawal_request and initiate_validator_exit.)
Customer terms should explain those stages without promising immediate unstaking. The B2B agreement can still impose response times for acknowledging an instruction, reporting eligibility, maintaining operations and escalating a failed request. A normal queue delay differs from a supplier's failure to carry out an assigned task. An outage must not leave the CASP dependent on the supplier's cooperation to regain access. For ICT services supporting a critical or important function, DORA requires exit without disruption to business, limitation of regulatory compliance or detriment to customer-service continuity and quality. That supplier-transition duty does not alter Ethereum's withdrawal queue. (Regulation (EU) 2023/1114, arts 73(1)(b) and 75(6); Regulation (EU) 2022/2554, arts 28(8) and 30(3)(f).)
MiCA requires procedures to return customer assets as soon as possible and to segregate them operationally and legally from the CASP's estate. The Commission's interpretation requires return of the same type of cryptoasset, subject to a separately permitted conversion requested by the customer. A contractual promise to substitute fiat at the CASP's option would not meet that position. Protocol withdrawal returns ETH to the CASP-controlled address. The CASP must then implement the customer's instruction, including return of ETH or the means of access where requested. Keeping an unstaked position in custody is a separate customer choice. (Regulation (EU) 2023/1114, art. 75(6)–(7); Commission answer published by ESMA, Q&A 2320, updated 18 February 2026.)
Segregation must be effective under the applicable law, rather than asserted by the word custody. The Irish launch documents should establish the clients' proprietary interests and how pooled holdings remain legally segregated on insolvency. An Irish-law assessment should test the actual title arrangements and custody records before launch. MiCA's prohibition on creditor recourse to custody assets does not establish every national-law consequence of a deficient ledger or contractual title arrangement. The supplier agreement should give the CASP continued access to configurations and records, prohibit any supplier lien over customer assets and provide for transition on insolvency. The supplier's bankruptcy can still make an unsecured damages claim difficult to recover. (Regulation (EU) 2023/1114, arts 73 and 75(7); Regulation (EU) 2022/2554, arts 29(2) and 30(2)(d).)
Changes that require a different service decision
A supplier-held withdrawal key, shared recovery power or ability to change a withdrawal destination would defeat the initial control allocation. Joint control can fall within MiCA custody even where the supplier cannot act alone. The CASP would then need an authorised custody provider under Article 75(9), or a redesigned arrangement that removes the supplier's custody powers. The related analysis of EU custody structures for a South African supplier addresses that separate custody problem. (Regulation (EU) 2023/1114, arts 3(1)(17), 59 and 75(9).)
Direct marketing of a custodial staking service to EU customers creates a different business. A South African operator that receives their assets, controls access or undertakes qualifying transfers must examine its own Article 59 route. Article 61's exception requires the client's exclusive initiative and cannot support a planned campaign soliciting EU customers. Direct contact alone does not make a purely technical service custody, but the actual asset handling and promises determine the listed services performed. (Regulation (EU) 2023/1114, arts 3(1)(16)–(17), 59 and 61.)
Pooling is also distinct from token issuance. A custodian can keep a ledger allocating interests in pooled stake without creating a transferable token. A liquid-staking token adds issuance, transferability and rights against assets or a provider. Its legal classification depends on those rights. If it is a financial instrument, MiCA excludes it and the relevant securities rules require analysis; otherwise the MiCA token and service provisions must be examined. A promised fixed yield funded through lending or reuse introduces further activities beyond the selected validation service. (Regulation (EU) 2023/1114, arts 2(4)(a), 3 and 4; ESMA and EBA, Joint Report under Article 142 MiCA, paras 174–176.)
The contracting decision should therefore approve only the defined node service and the tested CASP-controlled signing arrangement. Before funding, the parties need the actual permission map, customer consent terms, key and privilege evidence, independent exit procedure and loss-allocation agreement. A change to keys, reward routing, customer access, token issuance or asset reuse should suspend expansion until the affected legal and technical tests are repeated. (Regulation (EU) 2023/1114, arts 59, 73 and 75; Regulation (EU) 2022/2554, arts 28–30.)