Short answer
AERLink is the name Aeredium uses for its intended bank and payment-rail connectivity layer. Its purpose is to let value move between blockchain networks and traditional financial infrastructure without treating the bank side and the on-chain side as separate, manually reconciled systems.
In the proposed architecture, Kima-derived settlement technology supplies the interoperability foundation, AERKey supplies threshold authorization, and Aeredium supplies the TEE-attested execution and settlement environment. AERLink is the connective layer intended to expose that infrastructure to bank APIs, payment providers, and institutional workflows.
The distinction between architecture and deployment matters. White paper v3.7 describes bank connectivity as an intended primitive. The June 25 AMA said the work was still being reprogrammed from the Cosmos environment into Aeredium. Later official homepage wording calls AERLink “shipping” and shows a bank-rail flow as “live.” Without a named integration, public interface, or verifiable transactions, this guide treats production status as unresolved.
AERLink at a glance
The problem AERLink is intended to address
Blockchains and banks operate through different technical and compliance systems. A blockchain can settle a token transfer continuously, while a bank transfer may depend on account permissions, payment windows, jurisdiction, message formats, and a regulated intermediary. Connecting the two normally requires an application layer that coordinates instructions across both systems.
AERLink's proposed role is to make that coordination part of Aeredium's financial infrastructure. The target is broader than moving a token from one chain to another: it includes workflows in which one side of a transaction is a bank account, payment provider, fiat rail, or regulated asset platform.
That makes AERLink relevant to stablecoin issuance and redemption, real-world asset payments and distributions, institutional crypto-to-fiat settlement, and applications that need a verifiable on-chain record alongside an external payment event. These are target use cases, not evidence that each integration is already available.
How the intended settlement flow fits together
A financial instruction begins
A user, institution, wallet, or application requests a transfer involving an on-chain asset, a fiat rail, or both. Identity, account, and compliance requirements depend on the external provider and jurisdiction.
AERLink coordinates the external connection
The intended role is to connect the instruction to the relevant bank or payment API and coordinate it with the blockchain-side settlement path.
AERKey authorizes without assembling a key
Where cryptographic authorization is required, AERKey's threshold shares are intended to produce a standard signature without any party holding a complete private key.
Aeredium records the settlement leg
On-chain execution is intended to settle inside Aeredium's TEE-attested environment. Transactions submitted to Aeredium use AERX gas under the published token-utility model.
This is an architectural reading of the published materials. A production integration may add provider-specific authorization, compliance checks, failure handling, reconciliation, refunds, and settlement timing. Those operational details have not yet been publicly documented at integration level.
Why AERLink is not presented as a conventional crypto bridge
A conventional lock-and-mint bridge locks an asset on one blockchain and issues a wrapped representation on another. Security depends on the bridge contracts, its validator or signer set, and the custody of the locked assets.
AERLink is presented differently. It inherits Kima's thesis of threshold-signature settlement without wrapped tokens and extends the target beyond blockchain networks to bank and payment APIs. The intended result is coordinated native settlement rather than a synthetic asset issued by a bridge contract.
The design claim should not be mistaken for proof of risk elimination. Bank APIs introduce permissions and counterparty dependencies; external payment rails can reverse, delay, or reject transactions; and the complete cross-system failure model has not been published. Independent review must examine the deployed implementation, not only the architecture.
How AERLink relates to Kima, AERKey, and StablePro
Is AERLink live?
The honest answer is that the available statements do not yet resolve that question. The evidence currently supports three separate conclusions:
- The architecture is documented. White paper v3.7 names AERLink bank connectivity and describes the wider Kima-Aeredium merger architecture.
- Migration work was explicitly acknowledged. The June 25 AMA described AERLink as being reprogrammed from Cosmos into Aeredium and indicated additional engineering time may be required.
- Later marketing language is stronger. The current official homepage calls AERLink “shipping” and labels a bank-rail flow “live,” but does not identify a bank, payment provider, public endpoint, transaction record, or regulatory scope.
Until those statements are reconciled with public evidence, CryptoWisdomHub labels AERLink as an intended capability with disputed deployment status—not as confirmed production bank infrastructure.
What would confirm production deployment?
A named financial integration
A bank, regulated payment provider, or institutional platform publicly confirming the integration and its scope.
A documented interface
Developer documentation, API behavior, supported transaction types, permissions, limits, and settlement guarantees.
Verifiable transaction evidence
Public settlement records or a reproducible demonstration connecting an external payment event with an Aeredium transaction.
Security and failure analysis
An audit or technical specification covering API compromise, replay protection, reversals, reconciliation, key authorization, and provider outages.
Primary sources and status notes
White paper v3.7 · May 2026
Names AERLink bank connectivity, the Kima integration, AERKey threshold management, and the wider intended settlement architecture.
Kima/Aeredium AMA · June 25
Described the bank-rail work as migration and R&D, including reprogramming from the Cosmos environment into Aeredium.
Official homepage wording
Uses “shipping” and “live” language without the public integration evidence needed to determine production scope.
Frequently asked questions
What is AERLink?
AERLink is Aeredium's intended connectivity layer between blockchain settlement and bank APIs, payment networks, and fiat infrastructure. It is based on technology and concepts inherited from Kima Network.
Is AERLink live?
Its production status is disputed. A June AMA described migration and R&D work, while later official homepage language calls it “shipping” and “live.” No named integration or public transaction evidence currently resolves the difference.
Is AERLink the same as Kima Network?
No. Kima is the technology lineage and community being integrated into Aeredium. AERLink is the name used for the intended bank and payment-rail connectivity capability within the Aeredium architecture.
Does AERLink use AERKey?
The intended architecture places Kima-derived settlement under AERKey threshold authorization. AERKey handles cryptographic signing; AERLink handles connectivity to external financial systems.
Does AERLink make banks trustless?
No. A bank or payment provider remains an external institution with its own permissions, compliance duties, operating hours, and failure modes. AERLink aims to coordinate those systems with verifiable blockchain settlement; it does not remove their institutional dependencies.
Continue researching
Related guides
Editorial note: CryptoWisdomHub is independent and is not affiliated with Aeredium, Kima Network, or StablePro. Architecture descriptions are separated from verified deployment evidence throughout this guide.