Summary

  • ICANN’s Board approved a $20 million transfer from the Operating Fund to the Project Fund on 22 October, converting an earlier surplus forecast into a named allocation decision.
  • The decision supplies a pool for future large projects. It does not identify a recipient project or waive the separate Board approval required to use the fund.

One approval can move money without deciding what the money will buy. ICANN’s 22 October Board resolution authorizes a $20 million transfer from its Operating Fund to its Project Fund. That is the completed decision. The public resolution does not authorize a named project, contract or expenditure from the receiving fund, and it does not provide a bank settlement record showing the transfer’s execution date.

The distinction matters because ICANN widened the fund’s purpose in May. Previously called the Supplemental Fund for Implementation of Community Recommendations, it had been tied to projects arising from Board-approved community recommendations. In the May resolutions, the Board renamed it the Project Fund, allowed any qualifying project, and directed management to develop qualification rules. It also said use of the fund still requires Board approval. Broadening eligibility and filling the fund are two separate acts; choosing a project is a third.

The 22 October resolution supplies the missing allocation act. ICANN says its Operating Fund held at least $20 million in surplus as of 30 June, after the organization and Board Finance Committee considered the minimum needed for day-to-day operations. Its fund policy calls for at least three months of operating expenses there. The Board approved the transfer on the committee’s recommendation. In the Board’s account this is an internal allocation with no direct financial impact on ICANN overall, and no direct effect on DNS security or stability.

The Finance Committee’s 1 October minutes, published on 22 October, add the decision trail. Staff said the Operating and Reserve funds were above their minimums and about $20 million was available after accounting for a separate $7 million reimbursement associated with the 2026 new gTLD round and Grant Program. Staff projected that the Project Fund would reach about $69 million after this transfer and an approximately $35 million repayment from 2026-round implementation fees. That $69 million is a conditional projection, not a verified current balance; the minutes do not establish that the repayment had already landed.

Readers should also keep the cash flows apart. The committee discussed possible refunds to applicants because implementation-cost recovery exceeded the amount needed. Those refunds, the reimbursement, the expected replenishment and the $20 million transfer do not describe one interchangeable pot of money. Collapsing them would hide which decision authorizes each movement.

The news is therefore narrow but real: an anticipated surplus became a Board-approved transfer. What remains to be shown is the qualification rule in operation, each project-specific approval and its eventual spending record. A full Project Fund gives ICANN capacity; it does not, by itself, establish how that capacity will be used or whether a proposed project deserves it.