Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Getting started

Cosmo-Local Credit (CLC) is a progressive web app for creating, discovering, holding, transferring, and exchanging digital assets, including redeemable vouchers, through independently governed Commitment Pools. The CLC App is available at cosmolocal.credit.

Grassroots Economics Foundation (GEF) operates the App and supporting infrastructure. Unless GEF expressly accepts another role for a particular Offering or transaction, it is not the issuer of a user-created voucher, the Pool Steward of a user-created pool, a custodian, lender, borrower, guarantor, insurer, or redeemer. Issuers are responsible for their voucher commitments, and Pool Stewards are responsible for their pool rules.

Read Concepts and Vocabulary for the exact product layers, roles, actions, values, fees, and status terms used in these docs.

Before creating an account or transacting, read the Terms of Service. In particular:

  • You must be at least 18 years old, have reached the age of legal majority that applies to you, and have contractual capacity.
  • You are responsible for confirming that your account, voucher, pool, or transaction is lawful in every relevant jurisdiction.
  • Wallet credentials must be protected. GEF may be unable to recover a lost wallet or reverse an authorized transaction.
  • Public-blockchain transactions and records may be visible, permanent, and irreversible.
  • A listing in the App is not a GEF endorsement or a guarantee of redemption, value, liquidity, convertibility, or cash-out.

Start with the current App

1. Browse the Market

Open cosmolocal.credit to explore the public Market, the App's discovery catalog. Review the responsible issuer, the promised goods or services, location, availability, and published terms. A Market listing is not automatically an exchange venue, seller relationship, independent valuation, endorsement, or guarantee.

2. Create or access an account and wallet

The App uses an account for profile and session access and a wallet for blockchain authorization. Protect your passkey, paper-wallet material, recovery information, devices, and any other credentials. Review every asset, amount, address, pool, fee, and authorization before confirming a transaction.

3. Create a voucher

A voucher combines several distinct layers:

  1. token-contract mechanics and balances;
  2. the issuer's voucher designation and published terms;
  3. one or more Offering records for associated goods or services; and
  4. the issuer's real-world fulfillment.

Creating or minting a token does not by itself prove that an Offering exists, that the issuer has capacity, or that GEF guarantees redemption.

4. Create or assess a Commitment Pool

A Commitment Pool is a governed arrangement. Its current SwapPool contract can hold supported token inventory and execute direct swaps. Before using or contributing to one, review:

  • the accountable Pool Steward and the current contract owner;
  • the proxy administrator and controllers of configured dependencies;
  • admitted vouchers and other supported assets;
  • exchange-rate or quote methods;
  • the App's “Credit limit”, which is a pool token-balance cap rather than personal credit;
  • Pool and protocol fees;
  • available inventory and the Pool owner's liquidity-withdrawal power; and
  • any separately published contribution, guarantee, reserve, or insurance terms.

A deposit transfers assets to the SwapPool. Protocol v1.1.0 does not mint Pool-share tokens or automatically give the depositor repayment, withdrawal, reward, or governance rights.

5. Use the correct action

  • Send transfers a token balance to another address.
  • Pool swap exchanges one supported asset for another through one SwapPool. On-chain swap settlement does not prove issuer fulfillment.
  • “Redeem” opens the send flow with the token owner's address prefilled. It presents or returns the voucher to the issuer; completed redemption also requires the issuer's promised performance and a discharge record that prevents reuse.
  • “Retire voucher” hides the catalog listing. It does not burn balances, cancel the voucher, or extinguish the issuer's outstanding obligations.
  • Pool liquidity withdrawal lets the Pool owner transfer available inventory.
  • Fee collection sends accrued Pool fees to the configured recipient.

See the practical voucher example for the complete lifecycle.

Current, deployment-dependent, and proposed capabilities

The current App provides a Market and supported flows for accounts, wallets, vouchers, Offerings, pools, transfers, direct Pool swaps, and related records. Availability depends on the active deployment, asset, Pool configuration, device, network, eligibility, provider, jurisdiction, and published terms.

Payment services, support methods, rewards, guarantees, contribution arrangements, and other provider integrations are deployment-dependent. Their responsible party, fees, limits, eligibility, and legal terms must be disclosed where they are offered.

Protocol v1.1.0 provides direct Pool execution and a quote-only SwapRouter. Multi-hop execution, HTLC or escrow routing, batch netting, shared insurance, proposed governance assets, network liquidity programs, and regulated payment rails remain proposed or deployment-dependent unless a specific deployment identifies them as active.

Any future loan or other credit product requires separately presented supplemental and transaction terms. An ordinary transfer, Pool deposit, Pool swap, redemption presentment, fulfillment, or discharge is not automatically a loan, advance, or repayment.

Next, read the Protocol overview, the governance mechanics, or the broader White Paper.