English Product Guides

NajmBahar: Integrated Finance for Cooperative Groups

NajmBahar is EarthCoop's economic and financial subsystem. The Current product already contains real account, sub-account, fee, transaction, project and investment services. ECON defines the broader Normative reference architecture that every monetary implementation must respect. Some end-to-end integrations remain In development, so a rule defined by ECON must not be described as a live user workflow unless the current product also supports it.

Bahar and Gol

Bahar is the monetary unit. Gol is the subunit of Bahar:

1 Bahar = 100 Gol

Gol is a precision unit inside the Bahar system, not a separate currency.

Dim and Active Bahar

NajmBahar distinguishes monetary state:

• Dim — created Bahar that is not yet spendable between independent economic actors.
• Active — Bahar that has passed an authorized Activation route and can participate in valid spending and Transfer subject to policy and account rules.

A balance can therefore exist without being freely transferable. Dim is not merely a UI label or temporary lock; its non-transferability across independent owners is a monetary invariant.

Canonical monetary events

ECON separates seven canonical monetary events:

1. Creation — brings new Bahar into existence through a legally authorized source.
2. Activation — changes eligible existing Dim Bahar into Active Bahar. Activation is not Creation.
3. Transfer — moves existing Active Bahar between valid economic accounts.
4. Commitment — records an obligation/reservation without pretending that a Transfer has already happened.
5. Taxation — records a tax event under the applicable economic rule.
6. Cancellation — cancels Bahar where the governing rule authorizes cancellation.
7. Retirement — permanently removes Bahar from monetary supply through the authorized retirement process.

These events must not be collapsed into a generic balance edit. Operational account movement or release of a restriction is not a new eighth monetary event.

Current transaction core

The current NajmBahar transaction layer applies explicit safety rules rather than treating every account-to-account move as equivalent:

• movements between an owner's own eligible main/sub-account structure can preserve the explicit money state;
• Dim cannot be transferred between independent users or entities;
• cross-owner sub-account movement requires Active Bahar and a canonical executor;
• system operations and treasury-directed movements use their own explicit paths;
• policy or rollout gates can restrict a transfer even when the accounts themselves exist;
• monetary operations are designed around transaction safety, idempotency and reconciliation rather than direct balance mutation.

Creation and initial credit

Under ECON, the ordinary Creation source is a valid unique human economic membership. The initial credit is created as Dim, not Active. Creation therefore does not make the full initial credit immediately spendable.

The fundamental amount and value-measure rules belong to ECON and cannot be changed merely by an administrator editing a setting.

Activation

Activation converts eligible existing Dim into Active Bahar through an authorized route. The recognized routes include the membership-fee mechanism, participation-point entitlement, approved public-project financing and authorized equal General Activation under the conditions established by ECON.

An invitation reward or participation point is not itself Bahar. Where participation creates an activation entitlement, the entitlement acts on already-created Dim rather than creating new money.

Annual membership fee

The current base annual membership fee is 12 Bahar, subject to authorized monetary policy. Its legal allocation is:

| Allocation | Current base |

| --- | ---: |

| Operations and wages | 6 Bahar |

| Central insurance | 3 Bahar |

| Money retirement | 3 Bahar |

The current implementation can resolve the applicable amount from an effective versioned monetary policy and retains technical fallback configuration for compatibility. Configuration is execution infrastructure; it is not legislative authority.

Projects and investment

Project approval is a project/governance fact, not a Transfer. For public projects, the reference architecture separates Commitment, Activation, Transfer, and arrival of Active Bahar in the Active Project Fund. See Projects overview for the full sequence.

Investment contracts and assets can record value and economic entitlements, but asset appreciation or accounting value does not constitute Creation of Bahar.

Audit and accounting boundary

Monetary truth belongs in auditable ledger events. Account balances should be derived and reconciled from valid operations rather than changed through opaque manual edits. Money Ledger facts are also conceptually separate from Asset Ledger and Liability Ledger facts: an asset, receivable, obligation or valuation is not automatically money.

Current product vs reference architecture

The transaction, account, fee and project cores are real current product capabilities. The complete ECON architecture — including every Activation route, treasury/fund lifecycle, retirement obligation and public-project monetary chain — should be treated as the Normative reference architecture where the live end-to-end path has not yet been completed. Such integrations are In development, not silently assumed.

Explore NajmBahar features