BitKuruş
Wallet

Reference document

BitKuruş — Exchange Listing Package

This is the authoritative version, rendered from the project's own source document rather than retyped — so it cannot drift from what the team maintains.

All documents Summary page

Note: Reference documents are maintained in English. A Turkish summary of this material is on the summary page.

A single index of everything a Turkish exchange (BTCTurk, Paribu, Bitci, ICRYPEX, …) needs during listing due-diligence. Hand this folder — plus the operator-supplied legal/audit items — to the exchange's listing team.

The public entry point is /for-exchanges (alias /listing). That page carries this same material in Turkish and English and links every document below, so it is the single URL to put in a listing application. Every document here is also served from the site at /docs/library/<name>, so a reviewer never needs repository access.

1. Project overview

  • Asset: BitKuruş (ticker BK$), 18 decimals, 64-hex Ed25519 addresses.
  • What it is: a UTXO-style token ledger with Ed25519 signing and multi-node signed-gossip replication. See README.md and the public /about page.
  • Honest status: trusted-federation prototype, not BFT. See THREAT_MODEL.md.

2. Tokenomics

  • Public page: /tokenomics (TR/EN, live supply figures).
  • TOKENOMICS.md — 21,000,000 hard cap, distribution, validator commission (bounded tail emission), cap-vs-inflation reconciliation.
  • Live supply feeds (plain number, CMC/CoinGecko-ready):
    • GET /api/supply/circulating
    • GET /api/supply/total
    • GET /api/supply/max

3. Technical integration

4. Security

  • SECURITY.md — disclosure policy + bug bounty.
  • THREAT_MODEL.md — defended vs. accepted risks.
  • Cryptographic layer: app/Services/Crypto/* (Ed25519, canonical JSON).
  • Independent verifier: bitkurus-ledger-verifier.
  • Third-party audit report: place PDF in docs/audits/ when complete (tracked, in progress).

5. Compliance & legal

  • compliance.md — non-custodial model, KYC/AML division of responsibility, MASAK positioning.
  • Public legal pages: /terms, /privacy, /risk.
  • Governance, validator distribution, source availability and audit status: /project — including the items that are not finished yet.
  • Operator-supplied: legal entity registration, responsible team & contact, jurisdiction, any token-allocation disclosure. These are filled into the entity block in config/bitkurus.php; the public pages render from it.

6. Reliability

  • Test suite: tests/ (transaction engine, replication, supply cap, production-safety). CI: .github/workflows/ci.yml (Pint + PHPUnit + 4-node Docker testnet integration).
  • Health & monitoring: GET /api/health, php artisan replication:status.
  • Network status page: /status.

7. Pre-listing checklist (operator)

  • Legal entity + responsible team documented.
  • Third-party security audit report attached in docs/audits/.
  • Validator nodes distributed across ≥2 independent hosts/networks (see scripts/federation/nodes.conf).
  • Legal pages carry no unfilled placeholders (asserted by WebPagesTest::test_legal_pages_never_publish_unfilled_placeholders).
  • entity block populated in .env so the legal pages publish the registered company details instead of the "pending" notice.
  • Token-allocation disclosure prepared.
  • Exchange integration validated against a testnet node.