A Cosmos SDK chain that decides every token transfer in one function.

• tokenfactoryToken factoryAny account creates and administers its own bank denom, and decides who may hold it.
• liquidityLiquidityTwo-denom constant-product pools with LP shares, farming and the full pool lifecycle.
• nftrwaNFTAn overlay on the stock NFT store that adds the rules a real world asset needs.
• nftmarketNFT marketA fixed-price secondary market for the tokens the NFT module creates.
• incomeIncomePays income to the holders of a denom and to claimable amounts on single NFTs.

1. 01

   One send decision

   A bank send, an NFT send and a swap settlement all pass through one function, and the first rule that matches decides. For a bank denom there is no second, weaker path.

2. 02

   The blacklist is per denom and absolute

   A blacklist names denoms, not addresses: blocking one token has no effect on any other. A denom with no authority record is never subject to it. The check is absolute. It applies under an open policy, to an admin, to a delegate and to a module authority.

3. 03

   Circulation can be closed

   When the denom admin sets is_restricted, that denom can only be sent to an address that already holds it. The admin, a delegate and a swap leg are exempt. Existing holders keep trading among themselves. This is the on-chain circulation control.

4. 04

   Two-phase execution

   Moving one CenterChain denom into another outside a pool takes two transactions. The holder signs the first and grants a limited permission. A named executor signs the second and settles inside the bounds the holder set. The chain enforces the ceiling, not a price.

5. 05

   The reservation is enforced in the store

   An open swap authorization reserves max_from against the holder balance. A wrapper around the bank key value store rejects any write that would drop a balance below the reservation. This holds whichever code path moved the funds: a pool withdrawal, a direct send or a staking unbonding.

6. 06

   There is no separate account freeze

   The chain has no account level freeze. What exists is a per-denom blacklist, is_restricted across a whole denom, and an income blocklist check that rejects a claim. A transfer barrier is not immutability: the admin of a restricted denom can still burn, force transfer or hand the admin role on.

7. 07

   Compliance is a balance check, not an identity check

   The restricted-denom rule tests a balance. The chain can prove that a recipient already holds the token and cannot prove who that recipient is. Calling it an identity check is wrong in both directions. It blocks nothing extra, and it claims an assurance the chain cannot make.

Go follows the toolchain directive in go.mod. Node.js 20 or above is needed only for the docs site and the frontend. Make is the primary build entry point, and Ignite is not required.

The API reference is generated from a pinned commit, so its pages name the tree they came from. Two explorer surfaces do not answer yet: the node transaction index returns an empty result and the token factory REST endpoints return 501.

The evidence rail above lists only what a source exists for. A security review and a bug bounty program are absent from it for that reason, and the list of claims this page does not make says so.

What is CenterChain?

CenterChain is a Cosmos SDK application chain with five modules of its own.

Does the chain know what a token represents?

No. An on-chain token is a representation, and what backs it is not enforced by the chain.

Which public network exists today?

One, centerchain-testnet-1, with four validators and public RPC and REST endpoints, and its tokens are valueless.

What can the chain enforce about a transfer?

A per-denom blacklist and a restricted-denom rule, both decided in one function that bank sends, NFT sends and swap settlement all pass through.

Does the compliance check identify the holder?

No. It tests a balance, not an identity.

Can an issuer close a token to new holders without freezing existing ones?

Yes. Setting is_restricted rejects transfers to addresses that do not already hold the denom, and existing holders keep trading among themselves.

How does a swap between two token factory denoms work outside a pool?

In two transactions: the holder signs an authorization, then a named executor settles against it within the limits the holder set.

Does the chain compute prices?

No. It enforces the ceiling the holder set, and a better price is never rejected.

Yield, annualised return or interest figures.

The income module stores distribution state and no coupon calendar, and the liquidity module has no annualised query.

Total value locked, transaction counts, user counts, prices or uptime.

No source states a measured value, and the node transaction index answers with an empty result.

A security review, an audit firm or a bug bounty program.

The audit fields in the content contract are still placeholders, and the published documentation names no firm, no audit date and no bounty program. Nothing here stands in for one.

Regulatory status, a licence, a registration or an authority.

The contract line for regulatory status is a placeholder and the published documentation has no counterpart to it.

Identity verification, KYC or personal data handling.

The chain does not know the identity of a holder, and the restriction it does apply is a balance check rather than an identity check.

Fiat movement, off-chain settlement or product maturity terms.

The chain states that it does none of the three.

A permission that expires.

The authorization message carries no deadline or expiry field, so a time-boxed permission is not something the message can express.

A block time as a figure.

The glossary says roughly one second. That is a description, not a measurement, so it is not used as a number here.

A promise that the validator set will grow or spread out.

The documentation states that move as a plan, so it stays a plan on this page and out of the capability list.

Sample data or a sample asset table.

The content contract requires sample data to carry a sample label and a date stamp. No source exists for one, so none is printed.

That REST is unavailable for the modules.

A generated coverage report lists no REST routes for them, but live measurement refuted that: those module queries answer over HTTP with real data. The gap is the transaction index and the token factory REST endpoints, and only those are named.

Compatibility with another chain, including a bridge or an ERC-20 representation.

The published documentation never mentions them. The only bridge text lives in an upstream design file whose own header marks it as a draft.

The corporate relationship between CenterNetwork and CenterChain.

That relationship is defined only in the same upstream design file, which is marked as a draft. The published documentation does not describe it.