Interim policy v0.1, May 22, 2026

Issuer and Treasury Governance

This policy defines how Open.Build, the nonprofit sponsor and maintainer of OGCoin, intends to operate the asset while the project is still experimental: issuer access stays cold, treasury movement is deliberate, public claims stay conservative, and all distributions are recorded.

Issuer Rule

Cold Account

The issuer is for asset configuration and governance actions, not routine airdrops, payroll, grants, or market making.

Supply Claims

Conservative

Open Build will not make fixed-supply claims while issuer authority remains active and policy hardening is pending.

Transparency

Publish Records

Distribution, grant, treasury, and liquidity actions should be logged with purpose, amount, account, and transaction hash.

Known Public Accounts

These accounts are public ledger identifiers. They are not secret keys and cannot authorize transactions by themselves.

Issuer account
GDSIFZE6L35WW2VMI2GDEA44HO34QNAAXTC473ZQDQZEUM2HGCC6GY57
Distribution account
GDD6IVZJVY3ZFWJ5T5BCZDURLF64ZTQJDDR5X5A7XEDJYTEC6ISDGWZB
Issuer co-signer
GBZAC66WWHFU2FEOG5KECSEVR6EJO7BYK63UGB52SENDN4JEJTJEVK5L
Treasury account
GDMAMIC6SBYCF4NUQ6RBTUIFB5WWWS3TTDHXNCOUOLDFEPK5XOOU525F
Treasury approval signer
GAPBRE2R7EQXWA5DXTI2DNPFFL24DXJ7UQ5AL453CV7M3E2V2B64E473
Treasury recovery signer
GBBFU6277F7XXRI3IF3J4FUE4YZTE5EO4KDNHAWAFSOGKXT6LJKQHVF5
Grant account
GAY2LYDC2YSAQ4VBQTG64LFZZHUB52UP3ACBTWLBWBDFBNH3ZCIWYFQV
Liquidity account
GAL3OOPQRNZ3MFX3AUR45M7P2DBF5LWSH3XWFI5CN7SZEMQWLOOOCRRC

Signer Safety

  • Secret keys, seed phrases, and hardware-wallet recovery material must never be committed, emailed, posted to chat, or stored in project docs.
  • Every signer-changing transaction should be generated as unsigned XDR, reviewed by a human, signed in a trusted wallet or hardware signer, and submitted manually.
  • The impact treasury uses a 2-of-3 signer policy: treasury master, approval signer, and recovery signer each have weight 1; medium and high threshold actions require 2 signer weights.
  • Emergency signer recovery and key rotation should be rehearsed on Stellar testnet before mainnet changes.

Issuer and Supply Policy

  • The issuer account should not be used for routine payments, grants, payroll, airdrops, liquidity, or experiments.
  • No additional OGC should be issued without a public proposal, approval by project leadership, a waiting period of at least seven days, and a post-transaction ledger record.
  • No public fixed-supply claim should be made until issuer authority is either locked, multisig-controlled, or governed by a stronger signed policy.
  • Any issuer configuration change should be documented with purpose, transaction hash, date, signer, and expected user impact.

Treasury and Distribution Policy

  • Distribution batches must be opt-in and trustline-based.
  • Recipient lists should be validated locally before signing any transaction.
  • Each batch should have a stated purpose, maximum amount, approver, transaction hash, and public summary.
  • Official app, campaign, marketplace, and sponsorship payments may use the disclosed 95/5 split defined in the OpenGreenCoin Impact Policy.
  • Direct peer-to-peer transfers, grants, payroll, refunds, and treasury disbursements do not use the impact split.
  • Employee or contractor distributions require separate written consent, valuation support, and payroll/tax review.
  • Treasury wallets should not be used from automated jobs that hold secret keys.

Grant Guardrails

Grant programs must publish eligibility, review criteria, batch size, and records before larger allocations. OGC grants are discretionary and do not create employment, ownership, or redemption rights.

Liquidity Guardrails

No one should promote OGC as readily tradable until a documented OGC/XLM market-making or liquidity-pool policy is published. Initial liquidity should be small, reversible, and publicly logged.

Review Cadence

This policy should be reviewed before each campaign, after any signer or treasury incident, and at least monthly while OGC is in pilot mode.

Next Policy Tasks

  1. Keep the public transparency log current after every distribution, grant, treasury, or liquidity action.
  2. Require official routed-payment integrations to use the published impact policy and machine-readable configuration.
  3. Review pilot limits before any increase and require public approval before expanding treasury, grant, or liquidity exposure.
  4. Review impact, liquidity, and treasury policies at least monthly while OGC remains in pilot mode.