AIB maintains live register of EECS Registries connected to the AIB Hub for GO transfers
ImplementationAIB publishes and continuously updates a list of AIB Members that operate an active EECS Registry handling issuance, import and export of EECS Guarantees of Origin, all of which are actively connected to the AIB Hub. Imports and exports are permitted for all listed registries unless a restriction is explicitly noted in the table. AIB states this is not a full list of AIB Members and Observers, since some members have not yet implemented an EECS Registry or not yet connected to the AIB Hub.
Cross-border transferability of Guarantees of Origin under the EECS scheme depends on whether a domain's registry is live and connected to the AIB Hub, and whether import or export restrictions apply. The register is therefore the operational reference determining which GO issuing bodies market participants can actually trade with, and it delineates the effective perimeter of the interoperable European GO market from the wider AIB membership.
This is an operational, continuously maintained reference rather than a discrete regulatory decision, and its market-design significance lies in the connectivity perimeter it defines. In the EECS architecture the AIB Hub is the interoperability layer through which GOs move between national registries; a domain that is an AIB Member but has not implemented a registry or not connected to the Hub is, for trading purposes, outside the pool. The default rule stated on the page — imports and exports allowed unless explicitly restricted — is itself a design choice favouring open transferability, with restrictions handled as named exceptions rather than as a permissioning regime. For suppliers and traders performing disclosure and cancellation, the practical effect is that counterparty and sourcing decisions must be checked against the current state of this register, since additions of newly connected domains expand liquidity and any noted import or export restriction fragments it. The source supplies no version identifier, effective date or scheduled change, so no forward-looking design trajectory can be inferred; the appropriate treatment is to track the register as a standing implementation artefact and to log substantive changes to its membership or to noted restrictions when AIB publishes them. Confidence in the underlying facts is high but the event is low-substance, and the entry should be revisited if AIB publishes a dated change to connectivity status.
AIB EECS Rules (voluntary European GO scheme, operating within the Guarantees of Origin framework)
—