Tokenised GBP (TGBP)

Tokenised GBP (TGBP): How the Sterling Stablecoin Works and Where Its Risks Sit

Tokenised GBP is a reserve-backed sterling token issued by BCP Technologies Ltd. Its design combines fiat redemption, multi-chain distribution and institutional settlement, but access, reserve claims, contract administration and third-party banking remain central dependencies.

What TGBP is designed to do

Tokenised GBP, or tGBP, is intended to represent one British pound on public blockchains. The issuer describes it as a stablecoin backed by cash and cash equivalents, with token issuance linked to GBP transfers into the issuer’s banking arrangements. Its stated use cases include exchange liquidity, payments, remittances, decentralised finance and settlement for tokenised funds and other real-world assets. These are described as intended applications rather than evidence that every use case has achieved material adoption.

The project says tGBP went live in May 2025 and is offered by BCP Technologies Ltd. The website also says that BCP is registered with the United Kingdom Financial Conduct Authority for relevant crypto-asset activities under the money-laundering regulations, while separately stating that tGBP is not electronic money and is not protected by the UK Financial Services Compensation Scheme. The regulatory registration statement is an issuer disclosure; users should distinguish it from approval of the token’s value or a guarantee of redemption.

Issuance, redemption and the reserve model

According to the terms, tGBP is issued against GBP deposits made to BCP, and BCP commits to redeem one tGBP for one GBP subject to eligibility, applicable law, fees and compliance procedures. The terms state that reserves may consist of GBP or GBP-denominated assets held with regulated financial institutions in segregated accounts. They also allow reserve assets such as bank deposits, UK Treasuries and money-market funds, subject to the issuer’s stated policy and applicable requirements.

The redemption promise is not identical to an unrestricted, permissionless cash-out facility. The terms say that a holder must be eligible for and successfully register a BCP account to redeem directly with the issuer. They also allow limits or fees and permit suspension of services for fraud, sanctions, regulatory or terms-related reasons. This makes the token transferable onchain, while direct issuer redemption remains dependent on an offchain account relationship and compliance checks.

Transparency and what can be checked

The project’s transparency page reports monthly independent reserve attestations and provides dated reserve materials for June, May and April 2026. It also presents an onchain supply snapshot dated September 11, 2026, reporting 19,962,306 tGBP issued onchain. These materials can help compare reported liabilities with reported backing, but an attestation is a time-specific view rather than continuous proof that every token can be redeemed at every moment.

The issuer also says that OpenZeppelin has reviewed the smart contracts and links to reports described as 2024 and 2025 audits. The Base contract page, however, displays no submitted contract-security-audit record in its explorer audit field. That does not disprove the issuer’s separate audit claim, but it means readers should inspect the actual reports, their scope, the audited deployment addresses and any unresolved findings rather than treating a general audit reference as a complete security conclusion.

Multi-chain architecture and contract control

The website lists tGBP contracts on Ethereum, Base, Solana, Arbitrum, Polygon, BNB Chain, Gnosis Chain and Avalanche. The supplied YearBull network list covers five of those networks, so network coverage may change independently of the local page metadata. Moving the token between networks is therefore a practical dependency: users must confirm the correct contract, bridge or issuer-supported route before transferring funds.

On Base, the listed address is an ERC-20 transparent upgradeable proxy. The explorer identifies an administrator and exposes upgrade functions through the proxy pattern, while the implementation imports LayerZero interfaces. The observable implication is that the deployed token is not immutable code: an authorised administrative party can change the implementation subject to the contract’s controls. This may support maintenance and cross-chain functionality, but it also creates governance and upgrade risk for holders who rely on the token behaving the same way over time.

Who the system is aimed at

The product is positioned primarily for institutions, exchanges, payment service providers, remittance distributors and users of tokenised financial assets. The homepage says institutional access is available through the Archax platform and describes minting through UK Faster Payments or CHAPS for eligible businesses. It names exchange distribution and payment partners, but the presence of a logo or stated distribution relationship should not be read as proof of liquidity, unrestricted access or ongoing availability in every jurisdiction.

For a newcomer, the key distinction is between holding a token in a wallet and having a direct redemption route. Secondary-market users may trade tGBP on venues or use it in protocols without having a BCP account, but the issuer’s contractual redemption rights remain conditioned on eligibility and account registration. The practical value of the token therefore depends on both onchain transferability and the continued operation of issuer, banking, exchange, custody and payment-rail relationships.

Governance, dependencies and open questions

The reviewed materials do not present a token-holder governance system, public voting process or decentralised upgrade framework. The Base deployment instead uses an administrator-controlled transparent proxy, making issuer or administrator control a central part of the system’s governance model. Important unanswered questions include the identity and operating procedures of the upgrade administrator, the exact scope of any freeze or blacklist functions in the implementation, the legal treatment of reserve claims in insolvency, and how cross-chain supply is reconciled.

Key takeaways

• TGBP is designed as a one-pound sterling token backed by GBP or GBP-denominated reserve assets.
• Direct redemption is conditional on eligibility, compliance checks and a BCP account relationship.
• The issuer reports monthly reserve attestations and publishes onchain supply information, but these are time-specific transparency measures.
• TGBP is distributed across multiple networks, creating contract-address, bridging and supply-reconciliation dependencies.
• The Base deployment uses an upgradeable proxy with administrative control rather than an immutable contract.
• The product is aimed more directly at institutions, exchanges, payment firms and tokenised-asset settlement than at unrestricted retail cash access.

Risks and open questions

• Reserve assets, banking arrangements and monthly attestations require ongoing review; a dated attestation does not remove liquidity, custody or counterparty risk.
• Direct redemption may be unavailable to holders who cannot open or maintain an eligible BCP account.
• The Base contract is upgradeable, so administrator actions or implementation changes could affect token behaviour.
• Cross-chain deployments create risks involving bridges, messaging systems, contract mismatches and supply accounting.
• The reviewed materials do not establish a public token-holder governance process or explain all administrator powers in a single governance document.
• Exchange availability, liquidity and payment-partner access may vary by jurisdiction and can change without creating a change to the token contract.