Hex Trust, an Asia-based crypto-asset custodian, today announced it has partnered with the Klaytn Foundation to enable its customers including financial institutions, digital asset natives, and HNWIs to custody the Klaytn protocol’s native token KLAY with Hex Safe, an institutional-grade custody platform.
A blockchain project spearheaded by South Korean Internet giant Kakao, the Klaytn team recently announced that the Klaytn Foundation, a non-profit entity headquartered in Singapore, will formally officiate its role as the core committee overseeing the scaling of operations and resources for the continued expansion of the Klaytn blockchain and its ecosystem.
With hopes of building on its mission to drive growth in the Klaytn ecosystem, the Klaytn Foundation will begin to accept applications for the Klaytn Growth Fund later this month. The Fund invites developers and users to build applications, developer tools, or lead community-building initiatives to facilitate sustainable growth. Promising candidates will be able to benefit from financial grants and technical consultation.
Klaytn is also strategically partnering with ConsenSys, a leading Ethereum software company, to advance the Klaytn platform’s integrated digital currency efforts in the Bank of Korea’s CBDC pilot.
“Supporting the enterprise-grade Klaytn platform with highly-secure, bank-grade and fully compliant custody services strengthens Klaytn’s position to serve institutional blockchain projects in the region.”
– Calvin Shen, Head of Sales & Business Development at Hex Trust
Hex Trust enables banks and financial institutions to seamlessly integrate digital assets into their business operations in a secure, scalable, and compliant way. The organization has one of the industry’s broadest ranges of digital asset custody support including cryptocurrencies, security tokens, and non-fungible tokens (NFTs). Hex Trust has over 100 institutional clients including banks, financial institutions, exchanges, investment funds, and corporations across Asia and Europe.
Discussion about this post