Yamale

Institutional payments infrastructure

Money that moves in seconds, between institutions that know each other.

Yamale settles payments between banks, funds and businesses in the time it takes to read this sentence — carrying the reference and purpose codes reconciliation actually needs, on a network where every participant has been approved rather than merely allowed.

The problem

A cross-border payment between two institutions still takes days, passes through correspondents that each take a cut, and arrives stripped of the reference that would let anyone match it to an invoice. The money is fine. The information about the money is what gets lost, and reconciling it is somebody's whole job.

Public blockchains fix the speed and lose everything else: no idea who is on the other side, no licensed issuer behind the currency, no way to satisfy a supervisor asking who processed a transaction.

Yamale keeps the speed and puts the accountability back.

What it does

Payments

Credit transfers shaped like ISO 20022, the standard banks already use. The end-to-end reference and purpose code are first-class fields, not a memo — so a payment arrives already matched to what it was for.

Currencies

Fiat-referenced tokens with exactly one approved issuer each. Only that issuer can mint or redeem, and the permission is a governance decision recorded on the chain rather than a setting in a config file.

Treasuries

Shared funds with roles, spending limits and time locks. Money committed to somebody — a vesting grant, a scheduled disbursement — leaves the spendable balance entirely and cannot be redirected by anyone.

Trading

Liquidity pools anyone may open or add to, so a holder of one currency can move into another without leaving the network. Prices come from the pool's own reserves.

Prices

Exchange rates agreed by the validators, weighted by stake, so moving one costs as much as attacking the network. Real-world assets are valued instead by an appointed independent party, and every figure stays attributed to whoever signed it.

Recovery

A validator can freeze a stolen balance in the block they see it move — because a theft takes minutes and a vote takes hours. Taking it needs two thirds of the validator set, goes to one address set by governance, and leaves a public record of who accused whom, on what evidence, and how every validator voted. Cases that failed stay on that record too.

Governance

Who may validate, who may issue, who may route payments — every one of those is a vote of everyone who has staked, with the decision and its reasoning kept on the chain next to what it authorised.

Four decisions that shape everything else

The validator set is closed. The ledger is not.

Block production is a decision the network makes by vote, because an institution has to be able to say who processes its transactions. Reading the chain, holding currency and being paid need nobody's permission.

A commitment is stronger than a policy

When a treasury commits funds to somebody, they leave its spendable balance. No administrator, no governance proposal and no group of signers clearing their threshold can spend them. That is enforced by where the money sits rather than by a rule that checks — which is the difference between a commitment and an intention.

A value too old to trust is not a value

Every price carries when it was observed and how old that makes it. Nothing is silently frozen at its last known number: a feed that stops becomes explicitly unusable, and the operations that act on a price immediately refuse a stale one rather than guess.

Supply is capped, and approaches the cap

New issuance decays geometrically, so the total ever created converges on a fixed number instead of growing indefinitely. What validators earn is predictable years ahead.

Where the project actually is

Yamale is pre-testnet. The chain runs, the modules are built and tested, and the launch ceremony has been rehearsed with three validators reaching consensus. It has not been deployed to real infrastructure, and it has not been audited by anybody outside the project.

  • Payments, currencies, treasuries, trading, staking, governance, prices — built and covered by tests
  • Genesis ceremony rehearsed end to end; deployment scripts verify their own output
  • Block explorer with a plain-language view and a full technical view
  • Not yet running on real hosts, and not externally audited
  • Lending against real-world assets is a later phase — the valuation layer it needs is in place, nothing consumes it yet

Everything above is documented in the open, including the parts that are missing: the documentation keeps its own honest list.

Look at it yourself

A single-node network takes about two minutes to start, and the explorer points at it without any further setup.