[Federation Name]: International Operations Decisions

Status: Decisions the founding member groups need to make together before adopting bylaws. These are the operational specifics that don’t belong in bylaws but do shape how the Federation works across borders. Each section names a decision, lays out the tradeoffs, and suggests a starting position to argue with.

1. Banking and currency

Decision: What banking infrastructure does the Federation use, and how does money move to international member groups?

Context. US-based banks (Mercury, Relay) are fast and cheap for domestic operations but slow, expensive, or impossible for international transfers. SWIFT wires from a US bank to a small German nonprofit can cost $30–50 per transfer with multi-day delays and frustrating intermediary-bank reductions. This is a real friction point. It will hit the Federation the first time someone tries to send a £500 reimbursement to a London organizer.

Options:

1. Mercury or Relay for US-only operations, plus Wise Business for international. Domestic operations are smooth, and international transfers go through Wise’s multi-currency infrastructure (typically under 1% fees, real exchange rates, hours not days). This is the standard play for US-incorporated organizations with international reach.
2. Wise Business as primary. Skip the US-only banks. Wise provides USD, EUR, GBP, and 50+ other currency accounts in a single dashboard, with local routing details so a German member group can receive EUR via SEPA transfer at no cost. Slightly less polished than Mercury for pure-US workflow but dramatically better for the federation case.
3. Mercury plus Wise plus a European banking relationship for EU-specific funder requirements. Some EU foundations cannot send money to a US bank account, regardless of how the receiving entity is structured. If a major EU funder is on the horizon, the Federation may eventually need an EU-domiciled banking relationship, but this is a problem to solve when it appears, not preemptively.

Suggested starting position: Wise Business as primary, Mercury for US-domestic operations only if needed. Reassess after the first year.

Action: Open Wise Business account once the entity exists and has an EIN. Wise requires both for US entity onboarding.

2. Insurance: the actually hard one

Decision: How does the Federation extend liability coverage to events run by member groups outside the US?

Context. Nonprofits Insurance Alliance of California (NIAC) covers US events well, Canadian events sometimes, and EU/UK events generally not. A liability policy issued in the US does not simply “work” in Germany. Many EU jurisdictions require event insurance to be issued by an insurer licensed in that country.

Options:

1. NIAC covers US events; international member groups carry their own coverage. Cleanest legally but creates a two-tier reality where US member groups receive a tangible benefit and international ones don’t. Contradicts the equal-voice principle in practice, even if not on paper.
2. NIAC covers US events; the Federation subsidizes local insurance for international member groups. The Federation pays or reimburses for member groups to obtain locally-appropriate coverage. More expensive but preserves equality. Requires a written reimbursement policy with caps and standards.
3. Find a global insurance broker that can write multi-jurisdictional event coverage. Some specialty nonprofit insurance brokers (Hiscox, Lockton, Marsh) can write international event policies. Expensive but unified. Worth a quote conversation in year 2 when the Federation has a real budget.
4. Hybrid: NIAC for US, Hiscox or similar for major EU/UK events, member-group-carried for smaller events under a defined threshold. The realistic answer for most international federations.

Suggested starting position: Year 1, NIAC for US events plus a written commitment in the Federation’s policies to subsidize equivalent local coverage for international member groups, up to a defined annual cap per member group. Year 2, get quotes from international brokers and decide whether to consolidate.

Action: Add insurance subsidization policy as a Board priority for adoption within 90 days of incorporation. Budget line: $2,000–5,000/year initially for international coverage subsidies.

3. Funder due diligence and US tax compliance

Decision: What documentation does the Federation maintain to make it easy for funders to give cleanly and for the Federation to redistribute funds internationally without IRS problems?

Context. The Federation will be a US 501(c)(6). When it receives grants from US funders (Bluesky, Modal Foundation if US-based) and redistributes some of those funds to non-US member groups, the funder may want documentation that satisfies US tax-compliance rules. This is particularly true if the funder is a private foundation, in which case expenditure responsibility rules under IRC § 4945 apply to the funder. This is the funder’s problem more than the Federation’s, but the Federation needs to be set up to make their compliance easy.

When the Federation makes payments to non-US member groups or individuals, the Federation also has tax reporting obligations:

• Form W-8BEN-E from each non-US member-group organization (the analog of W-9 for US payees)
• Documentation of the charitable purpose of each disbursement
• OFAC sanctions screening of recipient organizations and their key people
• Record-keeping sufficient to demonstrate that funds were used for the stated purpose

Options:

1. Build the documentation infrastructure from day one. Every member group, US or international, completes a standard onboarding packet that includes (for non-US groups) a W-8BEN-E, an OFAC-screened officer list, and a charitable-purpose affirmation. More work upfront. Bulletproof when a funder asks.
2. Build documentation reactively when funders require it. Lower upfront friction, higher risk of scrambling when a major funder applies expenditure responsibility requirements.

Suggested starting position: Build it from day one. The first major grant arriving with conditions the Federation can’t meet is the kind of problem that delays funding by 60+ days.

Action: Develop a Member Group Onboarding Packet that includes jurisdiction-appropriate tax forms, OFAC self-certification, and charitable-purpose affirmation. Adopt within 60 days of incorporation.

4. Data protection and GDPR

Decision: What is the Federation’s privacy posture for handling personal information about member-group organizers, event attendees, and others?

Context. With EU member groups, GDPR applies. With UK member groups, UK GDPR applies (substantively similar, with post-Brexit divergences). The Federation will hold personal data: organizer contact info, board member details, attendee information for Federation-level events. Even a US-incorporated entity processing personal data of people in the EU or UK is subject to these rules.

Options:

1. Minimal data approach. The Federation holds as little personal data as possible. Member-group rosters live with member groups. Event registration lists live with the event organizer. The Federation holds only what it absolutely needs (a designated delegate per group, board members, financial counterparties).
2. Centralized data with full GDPR compliance. The Federation builds out the privacy policy, data processing agreement templates, data protection officer (DPO) function, breach notification process, subject access request process. Full compliance is real work and ongoing cost.

Suggested starting position: Minimal data approach, plus a basic privacy policy and a DPA (Data Processing Agreement) template for any vendor handling personal data on the Federation’s behalf. The Federation does not need a full DPO in year one if it minimizes data collection. Revisit in year two if data holdings grow.

Action: Adopt a written Privacy Policy within 90 days of incorporation. Use the iubenda or PrivacyPolicies.com templates as a starting point, then have it reviewed by counsel.

5. Working language and translation

Decision: What is the working language of the Federation, and what (if any) translation does it commit to?

Context. This is more cultural than legal but matters for whether international members feel like first-class participants or like guests at someone else’s meeting.

The Japan factor specifically: Most AT Protocol-curious developers in Japan speak working-level English, but governing in a second language is harder than reading in one. A German organizer can read English bylaws and govern in English without much friction. A Japanese organizer may struggle to participate in detailed governance debates conducted in English, even if their reading comprehension is fine. The Federation’s translation commitment for Japan needs to be more concrete than for European jurisdictions.

Options:

1. English as working language, no translation commitment. Most efficient. Excludes member groups whose organizers have limited English. Realistic given AT Protocol community’s current English-dominance, but worth naming as a temporary state.
2. English working language, with translation accommodations on request. Materials translated for member groups that request it. Meetings provide live translation when feasible. Documents that affect rights (bylaws, code of conduct) are translated into the working languages of all member-group regions.
3. English working language, with active translation funded for non-Anglophone member regions. The Federation maintains translated versions of governance materials (bylaws, code of conduct, current voting items, financial summaries) in the primary working languages of every member-group region. For the current membership, that includes Japanese, German, French (covering both EU members and Canadian francophone members), and any other language a member group’s organizing committee identifies as the language they govern in. This is a real budget line.
4. Multi-language from day one. Bylaws, code of conduct, member communications all in English plus a defined set of working languages. Expensive and slow.

Suggested starting position: Option 3, active translation funded for non-Anglophone member regions. English remains the working language of the Federation because of the AT Protocol developer community’s current English-dominance, but the Federation commits real budget to translating governance materials into Japanese, French, German, and other working languages on a rolling basis. Translation is the Federation’s investment in equal voice, not the member group’s burden. Volunteer-translated versions from member groups themselves are accepted and welcomed.

Action: Add a Language Policy statement to the Federation’s policies. Budget line: $3,000–8,000/year for translation services in year one, scaling with membership growth. Identify a translation vendor (Smartling, Crowdin, or similar for ongoing translation; individual translators for one-off bylaw and policy work) by month 6.

6. Trademark and branding

Decision: How does the Federation protect its name and branding across multiple jurisdictions?

Context. US trademark registration covers the US. EU trademark registration covers the EU. UK trademark registration covers the UK. These are three separate filings with separate fees, separate maintenance, and separate enforcement processes.

If the Federation eventually creates international Affiliates (per Article XIII of the bylaws), trademark ownership and licensing becomes a real piece of legal architecture.

Options:

1. Don’t register the trademark. Many small nonprofits operate on unregistered common-law trademark rights. Adequate until someone tries to use the name in a way the Federation doesn’t like.
2. Register in US only initially. Lowest cost, covers the home jurisdiction. Approximately $350 USPTO filing fee per class.
3. Register in US, EU, UK simultaneously. Approximately $2,000–3,000 all-in. Useful if the Federation anticipates Affiliates or commercial activity in those regions.
4. WIPO Madrid Protocol filing. Single international application covers up to ~130 countries with one filing process. Approximately $1,000 base plus per-country fees. The cleanest path for going global.

Suggested starting position: Wait. Don’t trademark anything until the Federation has settled on its actual name and operated under it for at least 6 months. Premature trademarking is a common waste of money for early nonprofits. Revisit at year 1 when the name is stable.

Action: Defer. Add to year-1 review agenda.

7. Time zones, meeting cadence, and the founder-tax problem

Decision: What is the meeting schedule, and how does the Federation prevent founder tax: the slow accumulation of decisions made by whoever was awake when something came up?

Context. Founders almost always end up doing more than members because they’re the ones available. In a US-led founding membership, this means decisions tend to drift toward US Pacific or Eastern hours. Without explicit countermeasures, the EU, UK, Canadian, and Japanese member groups effectively get a smaller share of governance even with equal votes.

The Japan factor specifically: With member groups spanning Tokyo through Los Angeles, there is no synchronous meeting time that works for everyone awake. Tokyo to LA is a 16–17 hour offset. A 9am Tokyo call is 4pm previous-day Los Angeles, 7pm previous-day NYC, midnight London. There is no overlap window where Tokyo morning and California morning coexist. Async-default is the only structure that gives Japan equal participation. Any drift back toward “let’s hop on a call” excludes Tokyo.

Options:

1. Synchronous-first. Set a fixed quarterly meeting time. Anyone can attend or send their delegate. This favors whoever can attend most easily and disadvantages the time zones furthest from the meeting’s anchor.
2. Async-first with synchronous as needed. Most decisions happen through written ballots and discussion threads with multi-day response windows. Synchronous meetings exist for matters that need real-time deliberation. This is what the bylaws as currently drafted reflect.
3. Two-window meeting schedule. Every Federation meeting is held twice: once in a time window friendly to the Americas (5pm Pacific / 8pm Eastern), once in a window friendly to EU/UK (7pm CET / 6pm GMT). For Japan, a third window (9am JST) becomes part of the rotation. Doubles facilitator time but produces real equity.
4. Async-only for binding decisions. Synchronous gatherings exist for relationship-building, brainstorming, and community, never as the place where binding votes happen. Votes happen in written ballots with 14-day windows so every time zone has equal opportunity to participate. Sync gatherings remain valuable but not load-bearing.

Suggested starting position: Async-only for binding decisions is the cleanest answer when Japan is in the membership. Synchronous gatherings continue for relationship-building, working groups, and informal coordination, with rotating times across at minimum three time-zone windows (Americas, EU/UK, Asia-Pacific). The bylaws already make written ballot the default; this is a values commitment that says default means always for things that count.

Action: Adopt this as a written Meeting Practices document, separate from the bylaws but referenced by them. Make sure the working group includes someone from the Asia-Pacific region in drafting the document.

8. The state of the world: a non-bylaws-but-real consideration

Decision: How does the Federation handle the possibility that a member group’s jurisdiction becomes hostile to its work?

Context. AT Protocol is a decentralized social protocol. Decentralized social tools have, in some jurisdictions, attracted regulatory hostility, surveillance, and outright bans. A future member group might be in a jurisdiction where their work becomes legally fraught: censorship law in the UK, the EU’s DSA in certain interpretations, more dramatic situations in Russia, China, or other places.

Options:

1. Pretend this won’t happen. It might not. It might.
2. Build in resilience. The Federation explicitly recognizes that member groups in different jurisdictions face different risk profiles. The Federation does not require any member group to engage in activity that would expose its organizers to legal risk in their jurisdiction. The Federation may provide solidarity funds, legal referrals, and platform for affected member groups, but does not promise rescue from sovereign-level harms.

Suggested starting position: Build a Risk Recognition statement into the Federation’s policies. One paragraph acknowledging that member groups operate under different legal regimes, that the Federation respects each group’s judgment about what it can safely do in its own jurisdiction, and that the Federation will not require a member group to take actions that increase its legal exposure.

Action: Add to the Code of Conduct or as a standalone policy.

Summary of suggested decisions

These are starting positions. Argue with them. The point is to have the conversation explicitly rather than letting decisions get made by accident.

Per-jurisdiction notes

These are not formal commitments. They are operational realities the founding group should know about for each represented region.

🇨🇦 Canada

Canadian member groups can join the Federation on equal terms without structural complications. CRA does not regulate inbound foreign nonprofit funds the way it regulates outbound charitable disbursements.

Wise Business supports CAD natively with Canadian local routing details, so SWIFT-wire friction is avoided. The US-Canada nonprofit tax treaty is favorable; the IRS treats Canadian registered charities as equivalent to US tax-exempt orgs for some purposes (Notice 99-47).

Canada is officially bilingual, and the French-language translation commitments under Section 5 above apply to Canadian francophone member groups as well as to EU members.

If/when Canadian groups want a sister entity (Pattern B), the Canada Not-for-profit Corporations Act (CNCA) federal NFP corporation is the cleanest path. Online incorporation through Corporations Canada, ~$200 CAD filing fee, bylaws filed within 12 months. Lighter than Belgian AISBL. Likely the easiest international Affiliate path of any jurisdiction.

🇪🇺 European Union

GDPR applies to the Federation’s processing of personal data of EU residents even though the Federation is US-incorporated. Section 4 above addresses the minimal-compliance posture.

EU foundations and governmental funders sometimes prefer or require an EU-domiciled grantee. That preference is the most likely trigger for Pattern B (forming an EU Affiliate).

The textbook sister entity for European federations is the Belgian AISBL, though it is expensive (~€2,000 notary, 6-12 months) and high-friction. German e.V. is simpler if member-group concentration is German. Dutch Stichting is another option. Choose based on where member groups and likely funders are concentrated.

🇬🇧 United Kingdom

A UK-domiciled entity faces its own cross-border friction with EU members. UK is not a frictionless workaround for EU operations.

UK GDPR applies to the Federation’s processing of personal data of UK residents (substantively similar to EU GDPR, with some divergences).

Wise Business supports GBP natively with UK sort code and account number for local SEPA-equivalent transfers.

The standard sister entity in the UK is the Community Interest Company (CIC), which has a built-in asset lock that satisfies the Federation’s bylaws requirement. ~£50 filing plus ~£500 professional fees, 2-3 month timeline.

🇯🇵 Japan

Time zones are the dominant constraint. Tokyo to LA is a 16–17 hour offset. There is no synchronous window in which both regions are awake during working hours. Async-only for binding decisions is essential, not stylistic.

English is widely spoken in Japanese tech communities, but governing in a second language is harder than reading in one. The Federation’s translation commitment for Japanese governance materials should be real, not on-request-only.

Wise Business supports JPY with Japanese routing details. Small Japanese organizations often operate partly in cash, and getting an organizational bank account is harder for unincorporated groups than in the US or UK. Be flexible about disbursement methods.

Code of Conduct enforcement assumes broadly Anglo-American norms by default. The “or equivalent code” provision in the bylaws exists in part so Japanese member groups can apply equivalent norms in ways that work in their context. Japanese organizers know what enforcement looks like in Japan; trust their judgment.

Japanese member groups receiving funds from the Federation may have Japanese corporate-inhabitant-tax implications. This is the member group’s burden, not the Federation’s, but the onboarding documentation should flag it.

The natural sister entity in Japan is 一般社団法人 (ippan shadan hojin), the General Incorporated Association created in 2008 nonprofit reform to make Japanese nonprofit incorporation easier. ~$700 USD total in notary and registration fees, 2-member minimum, articles drafted in English but notarized in Japanese (a Shiho shoshi, judicial scrivener, handles this). The Japanese equivalent of a California Mutual Benefit Corp in spirit and accessibility.

🇺🇸 United States

The Federation’s home jurisdiction. California Mutual Benefit Corp under Corporations Code §§ 7110+. 501(c)(6) tax-exempt status pursued via IRS Form 1024.

State-level “foreign agent” legislation is being introduced in multiple US states with broad definitions that could affect organizations receiving funds from foreign sources. Monitor as this develops. California has not been among the proposing states.

The Federation must screen recipient member groups and key people against OFAC sanctions lists for any disbursements. Standard nonprofit practice.