Chainlink's runner-up Swift hackathon entry pays a tokenised-share dividend across four chains

Victoria Shinder04 October 2026, 13:002 min read

Chainlink has described the entry it built for Swift's 2026 Hackathon Business Challenge, which Swift selected as the runner-up. In a blog post on 1 October, the company says the prototype automated a cash dividend on a tokenised equity issued across four blockchains, from the corporate action announcement to payment and reconciliation, with no manual step. The challenge question was "Who does what in a tokenised world?"; Chainlink's answer focused on the registrar or paying agent.

The problem it addresses. In traditional markets a paying agent works from one authoritative register of who is owed a dividend. If the same share class is issued on several ledgers, and shares can move between them, there is no single register, and blockchains disagree on when a transaction is final. Holders may also want to be paid on different chains and in different forms of digital money. The existing ISO 20022 messages fix entitlement with a calendar record date and assume payment goes to a bank account; they cannot express an exact snapshot moment or a wallet, chain and settlement token.

How the workflow runs. The Chainlink Runtime Environment receives the corporate action as an ISO 20022 message, validates it, schedules the entitlement snapshot and pay date, reads holder positions from each chain and combines them into one register, with rules for shares in transit at the cut-off so nothing is counted twice or lost. Chainlink's compliance engine checks each wallet against identity, sanctions, tax and eligibility rules before entitlements are calculated, and its data feeds adjust the reference price when the share goes ex-dividend. On the pay date each holder receives a stablecoin or tokenised deposit on their own chain, with the cross-chain protocol CCIP moving the settlement asset where it is not native. Every payment is linked back to the original message.

A proposed standards change. The entry also proposes extending ISO 20022 corporate action and payment messages with an exact cross-ledger snapshot and fields for the beneficiary wallet, target chain, settlement token and on-chain transaction reference.

What it is. The post is Chainlink's own description of a hackathon prototype. It names no issuer, bank or paying agent using it, and gives no date for production use.

What it means

The most transferable idea is the message extension, not the orchestration. Whoever ends up running cross-chain corporate actions, banks will want to receive instructions in ISO 20022, and the standard currently has nowhere to put a wallet or a chain. If Swift's community takes up fields like these, tokenised securities can be serviced through existing back offices regardless of which vendor does the on-chain work.