Skip to main content
Mainnet product guide draft · English v1.0 · 7 October 2026 Docs Home · Funds · DigiFT Product References The ARCO ecosystem connects assets and strategies, settlement and liquidity, and user services to vaults. Its common vault structure links each partner’s role to product-specific contracts and operating routes. DigiFT is a representative asset connection case.

​
Partner roles

​
DigiFT connections

This case is based on ARCO and DigiFT’s strategic MOU to expand institutional tokenized asset distribution. ARCO vaults, apps and transaction operations connect to each product’s external issuance, distribution, management, custody and settlement roles. The roles of DigiFT and underlying product parties follow the relevant official materials and contractual scope. uMINT is a case of DigiFT on-chain distribution of a UBS product. For bEQTY, BNY provides investment management services. ULTRA separates FundBridge Capital’s issuance, Wellington’s sub-management, Libeara’s tokenization infrastructure and DigiFT’s distribution. See DigiFT Product References for each product’s role table and official announcements. GIWA ProductToken represents the quantity of an ARCO product. Product-specific contracts define its rights relationship to externally issued tokens or underlying fund units, and the asset purchase, custody and redemption routes. The specifications also set out the scope in which conditions shown in the app or external announcements apply to the ARCO product.

​
Finding products and references

The planned GIWA onboarding list and app introduction links do not establish current trading availability. Launch and trading availability follow each product’s official announcement.

​
Partner onboarding criteria

Linked product guides specify the exact underlying product and class, rights, issuer, manager, custodian and settlement parties, supported networks and payment assets, and eligibility, KYC and transfer conditions. Pricing sources, valuation dates and currencies, costs and distribution methods, and redemption liquidity and processing schedules are also defined. External product values are distinguished from ARCO’s applied conditions, and finalized values from planned onboarding status. See DigiFT Product References for product specification fields and their connection to common ARCO components. Trading integration follows each product’s catalog and official deployment specifications; common calls follow the Developer Guide.