Summary

  • On 3 May 2026, ICANN’s Board authorized a one-time contribution of up to US$1 million to the IGF from forecast FY26 surplus, subject to the President and CEO being satisfied with the governing terms.
  • The published rationale says ICANN intended to seek exclusive use for IGF Secretariat operations, ICANN consent for another use, the lowest possible UNDESA overhead and exclusion of advocacy positions such as the Global Advocate.
  • The record checked for this Article establishes an authorization and contemplated conditions. It does not establish an executed agreement, recipient acceptance, a transfer, an allocation or expenditure.
  • A public contribution-term receipt should preserve each state and material restriction while protecting bank details, signatures, legal advice, security controls and personal data. The same rule should cover every major donor.

A gift with a perimeter

Large institutional gifts are usually narrated through their amount. The number supplies scale, the recipient supplies virtue, and the approval supplies a date. The terms disappear into the plumbing.

ICANN’s proposed one-time contribution to the Internet Governance Forum reverses that order. The interesting fact is not only the US$1 million. It is the perimeter that ICANN described around the money.

On 3 May 2026, the ICANN Board authorized the President and Chief Executive Officer, or a designee, to make a one-time contribution of up to US$1 million to the IGF. The source was forecast surplus from the financial year ending 30 June 2026. The authority was conditional: the executive first had to be satisfied with the terms governing the contribution.

The minutes of that meeting preserve the unanimous vote and the same rationale. They add an authoritative record of the decision, not evidence that the later agreement and payment stages were completed.

The rationale republished with the resolution explains what ICANN expected those terms to do. It contemplated a commitment from the United Nations that ICANN’s contribution would be used exclusively for operations of the IGF Secretariat. Another use would require ICANN’s prior consent. ICANN would seek the lowest possible overhead charge by the United Nations Department of Economic and Social Affairs. And the money would not support advocacy positions, with the Global Advocate given as an example.

This is unusually specific public language for a contribution that had not yet completed the recipient’s own process. It is neither a receipt for payment nor a final agreement. It is a map of the control surface ICANN wanted.

The resolution is state one, not the whole transaction

The first discipline is to keep verbs in their proper order.

The Board authorized. The rationale described terms that ICANN intended to seek. The President and CEO was empowered to proceed if satisfied. None of those verbs means that the United Nations accepted every condition, signed an agreement, received the money or spent it.

That distinction is visible in the IGF’s own donation process. A prospective donor makes a pledge. The contribution is reviewed and accepted. A Standard Trust Fund Agreement is signed. The donor then transfers the funds. Those states may occur close together, but they are not interchangeable. A public record that jumps from Board authorization to “donation” collapses negotiation, acceptance and execution into one reassuring noun.

ICANN’s Contracting and Disbursement Policy reinforces the need for separation. It distinguishes Board authorization from officer approval, payment execution and later reporting. The policy does not establish the later state of this particular proposal. It tells us why an approval minute should never be treated as a bank confirmation.

The checked IGF donor-contribution table cannot close the gap. The page states that it was last updated on 2 February 2026, three months before the Board vote. Silence in a stale table establishes neither later payment nor later nonpayment. It merely identifies another state that has not yet become visible on that surface.

The appropriate sentence is therefore narrow: ICANN publicly authorized an offer, disclosed the principal terms it expected to pursue and conditioned execution on executive satisfaction. The subsequent states remain unproven in the public package examined here.

Why operations, and why exclude advocacy?

The proposed boundary makes sense only in the institutional setting that produced it.

The IGF is a United Nations-convened forum for multistakeholder dialogue on public-policy issues relating to the internet. The Tunis Agenda carefully limits that mandate. The Forum is to discuss, facilitate discourse, identify emerging issues and promote exchanges of information and best practice. It has no oversight function and does not replace existing arrangements, mechanisms, institutions or organizations. It does not take part in day-to-day or technical operations of the internet.

The WSIS+20 outcome made the IGF permanent. Permanence matters for planning, staff continuity and institutional memory. It does not convert a forum into a regulator, an operator or a principal for every organization that participates in it. A permanent forum remains a forum.

ICANN, by contrast, has a bounded technical mission. Its Bylaws require it to act within that mission, transparently, accountably and with fiscal responsibility. Its FY26–30 Strategic Plan includes expanding alliances that support the multistakeholder model. Administrative stability for the IGF can plausibly advance that strategic objective: meetings have to be organized, participation supported, institutional knowledge preserved and capacity work administered.

Advocacy is a different functional category. The IGF describes the Global Advocate for Human-centric Digital Governance as a UNDESA-designated, IGF-affiliated and public-facing role. The United Nations’ announcement of the appointment emphasizes communication and outreach. The role may also support fundraising where authorized.

Nothing in that description makes the role improper. Nothing in ICANN’s rationale demonstrates that the role sought, received or was denied ICANN funds. The exclusion instead reveals ICANN’s own line-drawing: Secretariat operations were presented as close enough to its mission; advocacy positions were placed outside the proposed use of this particular contribution.

That is a legitimate distinction for a donor with a limited mission to propose. It is also a distinction whose final form should be observable. Was “advocacy position” defined? Did the recipient accept the example, narrow it or replace it? Would ordinary Secretariat communications count? Could the money support an event at which the Global Advocate speaks? A public term receipt need not publish negotiating correspondence to show the operative boundary.

One donor’s consent right is not a veto over the Forum

The phrase “prior consent” can sound more expansive than it is.

As described in the Board rationale, the contemplated right concerns a change in the use of ICANN’s contribution. It does not confer authority over the IGF agenda, the Multistakeholder Advisory Group, the Leadership Panel, appointments, reports, other donors’ money or the Forum’s outputs. It is a restriction attached to one source of funds.

Yet the restriction is not meaningless merely because it is narrow. Money dedicated to Secretariat operations can shape the capacity of the administrative core. A consent right over repurposing can preserve one function while limiting adaptation to another. An overhead request can determine how much of the nominal contribution reaches programme administration. An exclusion can force cost allocation between donor pools. None of this is proof that ICANN captured the IGF. It is the ordinary way earmarked money creates a control surface.

The right comparison is therefore not between pure generosity and corruption. It is between legible and illegible conditions. In a legible arrangement, a reader can see the donor’s purpose, the recipient’s acceptance, the boundary of any consent right and the reporting path. In an illegible one, institutional actors exchange the same terms, but outsiders are asked to infer them from selective minutes and later totals.

Multi-donor funding can reduce dependence on a single institution. It can also make attribution harder. If each donor’s restrictions are hidden inside a bilateral agreement, no one outside the fund can see whether the combined pool leaves essential work unfunded, whether several consent rights collide, or whether apparently unrestricted programme decisions are constrained by cost-allocation rules. Donor pluralism is a safeguard only when its conditions remain comparable.

The strongest defence of ICANN’s conditions

ICANN has a serious answer to anyone who treats restrictions as inherently suspect.

This was forecast organizational surplus, not the private wealth of a benefactor. The Board owed duties to the corporation and to the mission for which its resources exist. A contribution of this size needed a reasoned relationship to identifier-system stability and to ICANN’s strategic commitments. Requiring use for Secretariat operations, limiting overhead, preserving consent before repurposing and excluding a category believed to sit outside mission are conventional controls, not evidence of a purchased outcome.

The Board Finance Committee’s minutes of 21 April show that the committee did not treat the proposal as a ceremonial grant. It discussed consultation, use of surplus and conditions on use and reporting. The minutes describe the one-time amount as additional to ICANN’s regular annual contribution. Questions about fiscal fit and recipient accountability belong in that discussion.

The rationale also gives substantive benefits: administrative stability, inclusive participation, global dialogue, capacity development and engagement with governments. Those are public reasons against which later reporting can be tested.

The strongest defence, then, is not “trust the donor.” It is that fiduciary and mission discipline required the donor to specify a purpose. A public contribution-term receipt would strengthen this argument. It would show that the Board’s stated limits survived contact with the recipient’s agreement, that the payment followed the required authority chain and that expenditure remained inside the accepted purpose.

A receipt for terms, not a demand for the contract

Transparency does not require publishing everything.

Bank-account details, payment-control procedures, signatures, privileged legal advice, personal data and security-sensitive instructions should remain protected. Negotiators also need room to test language without every draft becoming a public commitment. The proposal here is not publication of the executed agreement line by line.

It is a compact lifecycle record.

The first block should identify the donor and the recipient’s administrative entity, the source fund, the Board authorization, the maximum amount and the public rationale. It should give distinct dates and states for pledge, recipient review, acceptance, agreement signature and transfer. If a stage has not occurred, the field should say pending or not publicly confirmed rather than borrowing the date of the previous stage.

The second block should record the final material terms: permitted purpose, explicitly excluded uses, the scope of any consent requirement, amendment and suspension rights, treatment of unspent balances, refund provisions, and the requested and accepted overhead arrangement. It should say which agreement version governs and whether the full instrument is public, partly public or confidential.

The third block should follow the money without exposing banking information: amount authorized, pledged, accepted, transferred, allocated, spent and returned; reporting cadence; implementation-plan owner; date of the latest report; and closure status. Figures should carry an “as of” date and a currency basis.

The final block should preserve governance boundaries. It should confirm whether the terms give the donor any authority over agendas, appointments, programme outputs or operations beyond the administration of its own contribution. It should retain corrections, amendments and previous states instead of overwriting them.

This is a receipt in the constitutional sense: evidence of who was authorized to do what, on which terms, at which stage. It would allow the public to distinguish a carefully bounded contribution from an implied institutional acquisition.

Apply the rule to every major donor

A disclosure rule written only for ICANN would become a form of editorial targeting. The IGF should use the same receipt for every contribution above a material threshold, and donors should publish the same record from their side.

Uniformity matters because influence is comparative. One donor may require a named programme. Another may exclude communications. A third may impose an overhead ceiling. A fourth may supply unrestricted funds but reserve a refund right. None of those provisions alone reveals the fund’s operating room. Their combined shape does.

The receipt should therefore sit beside, not replace, the IGF’s aggregate donor table. The table answers who gave and how much was received by the reported period. The receipt answers which conditions travel with the contribution and where the contribution currently sits in its lifecycle.

The result would protect the recipient as much as the donor. When rumours claim that a contribution bought an agenda item or an appointment, a bounded record can show that the agreement contains no such authority. When a donor is accused of failing to follow through, the lifecycle can show whether delay sits at pledge, review, signature or transfer. When a programme changes, the amendment history can show whether recipient discretion, donor consent or a refund clause governed the change.

Conditions exist whether or not they are published. The policy choice is whether they remain attributable.