01 / The proposition
Mammoth is designed to help banks offer digital asset investing, conditional orders, recurring purchases, isolated perpetuals and collateralised borrowing within their own applications.
The bank selects its offering and rollout and performs the final integration. Mammoth provides reusable interfaces and selected integrations, together with transaction validation, monitoring, reconciliation and product records.
This public paper describes the intended product model. It is not evidence that every capability, provider integration or bank programme is implemented or available.
02 / Four product modules
The intended offering is organised into four modules. Each retains its own eligibility, customer authority, provider dependencies and operating requirements.
- Wallets, funding and investing: receive, hold and send supported assets; follow the bank-approved funding and cash-out journeys; buy and sell supported crypto and existing tokenised equities.
- Conditional orders and recurring investing: create bounded future instructions, with supported execution authority, cancellation and the necessary bank funding permissions.
- Isolated perpetuals: explicitly commit collateral to an eligible leveraged position, monitor it and close it under the venue’s rules. Unrelated wallet funds are not automatically used to top up that position.
- Collateralised borrowing: supply eligible collateral, borrow a supported asset, monitor the obligation, repay and withdraw collateral when the protocol permits.
03 / The customer experience
The intended normal service lifecycle stays inside the bank application. Customers discover eligible products, review the relevant information and costs, authorise the applicable action and follow its status.
The experience must distinguish received, under review, available, pending, failed and confirmed outcomes where applicable. An initial request, receipt or source-network event is not sufficient evidence of final delivery.
Website demonstrations are illustrative. They do not create accounts, present live market data or execute transactions.
04 / Responsibilities and control
The bank owns the customer relationship, customer checks, eligibility, product selection, fiat account decisions and final integration. Mammoth does not receive independent authority to move bank fiat.
The customer supplies the authorisation required for the product: an exact action or a bounded future instruction where supported. Providers execute the relevant action and apply their own service, issuer, venue or protocol rules.
The proposed customer-controlled wallet model requires bank acceptance. Restricting access to a banking service must not be represented as equivalent to freezing customer-held assets. Detailed signing, recovery and control arrangements are reviewed through the confidential bank evaluation.
05 / The integration path
Evaluation defines the initial products, customers, markets and operating requirements. Design then maps customer journeys, interfaces, data and responsibilities to the bank’s systems.
The bank’s delivery team performs final integration using the agreed Mammoth interfaces and workflows. Validation covers normal journeys, failures, customer authority, reconciliation and operational readiness. A controlled rollout follows the applicable approvals.
Timing is established through a scoped plan. Product development, provider readiness, bank implementation, testing and approval processes are separate dependencies; this paper makes no fixed launch-duration promise.
06 / Scope and material limitations
Product and network support is specific to the selected asset, route, provider and deployment. A provider catalogue does not establish a partnership or mean every integration is included.
Tokenised equities use existing issuer-defined instruments. Direct share ownership, issuer redemption, universal market access and interchangeability between issuer tokens must not be assumed.
Conditional triggers do not guarantee a fill. Recurring execution requires verified authority and funding. Leveraged positions and borrowing can be subject to liquidation. Borrowing collateral must not be assumed to share the isolated-perpetual model.
Continuous monitoring does not guarantee continuous trading or fiat settlement. The intended service includes no on-chain insurance or transaction-reversal facility.
07 / A bank evaluation
A useful evaluation establishes product fit, responsibilities, technical scope, readiness evidence and the practical rollout plan. Detailed technical, commercial, legal and security materials are shared through the agreed confidential process.
Mammoth is headquartered in London. Begin with the public platform and integration explanations, then discuss the evidence and delivery responsibilities relevant to your bank.
- Define the initial product and customer scope.
- Identify responsibilities and material operating constraints.
- Review the applicable provider and integration evidence.
- Agree testing, milestones and the conditions for a controlled launch.
Continue with the integration approach .