TR Mock Anchor

Region

What BiLira is likely to ship

This mock demonstrates the retail SEP-6 shape: the wallet's end user authenticates with their own Stellar account and is KYC'd by the anchor. BiLira, the Turkish partner this stands in for, is moving in a different direction.

• BiLira has agreed to implement SEP-6 but has not shipped it and has given no date.
• They are moving to business-and-enterprise-only. The likely production path is KYB, then credentialed API access (OAuth2 client-credentials, IP-allowlisted) — not the open flow demonstrated here.
• Their ramp is composed from primitives (deposit, then an explicit swap, then a withdrawal) rather than being atomic.
• If their SEP-6 does arrive it will likely be omnibus-shaped: the integrating business is the SEP-12 customer, and end users are distinguished by memo.

What carries over is the Stellar-side mechanics — trustlines, memos, claimable balances, quote handling, status polling — plus the deposit-reference model. The anchor wiring is the part that changes.

The anchor's own documentation

These are maintained by the mock's author and are the authoritative reference. We link rather than restate them.

• The SEP path — integration guide
• Guide — concepts, Turkish rails, statuses, glossary
• Mainnet — what carries over and what changes
• Source repository

Known issues

• This is a mock, not a live anchor. It is built by an independent developer to model a Turkish ramp, is not operated by BiLira, and moves no real money. Treat it as a sandbox stand-in until a production Turkish anchor ships. More
• The SEP-6 exchange endpoints require a bare asset code in destination_asset / source_asset rather than the SEP-38 identifier the spec calls for. The client sends the form the anchor accepts.
• SEP-12 auto-approves every customer, so the KYC rejection and NEEDS_INFO paths cannot be exercised against this anchor.

Developer scorecard