> For the complete documentation index, see [llms.txt](https://docs.agant.io/Y83ivqmfOiUspagNyFg6/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agant.io/Y83ivqmfOiUspagNyFg6/tokens/gbp-stablecoin-gbpa.md).

# GBP Stablecoin (GBPA)

GBPA is a **GBP-backed stablecoin** issued by Agant Finance Limited. It is pegged 1:1 with British pound sterling (GBP), fully backed by cash deposits, repo, MMFs and short-duration gilts, and is redeemable at face value.

Issued to be compliant with applicable UK regulations, GBPA provides a reliable, transparent, and secure digital representation of GBP for use across digital asset ecosystems.

Chain-agnostic by design, GBPA leverages [LayerZero](https://docs.layerzero.network/v2/concepts/getting-started/what-is-layerzero) to enable seamless [cross-chain](#cross-chain-compatibility) functionality and future-proofed token architecture.

GBPA will launch on multiple networks including Solana, Ethereum and Base. See [supported networks](broken://pages/ihpHzXpIK38886nAg1Ws) for more information.

### Cross-Chain Compatibility

To enable seamless cross-chain functionality and future-proof GBPA token architecture, we leverage LayerZero’s [Omnichain Fungible Token (OFT) standard](https://docs.layerzero.network/v2/concepts/applications/oft-standard).

[LayerZero](https://docs.layerzero.network/v2/concepts/getting-started/what-is-layerzero) is a cross-chain messaging protocol that enables native token interoperability. Built on top of the [ERC-20](https://ethereum.org/en/developers/docs/standards/tokens/erc-20/) and [Token 2022](https://spl.solana.com/token-2022) standards, it allows GBPA to exist and operate across multiple blockchains while maintaining a single source of truth for supply.

Tokens can move securely between blockchains without wrapping or intermediaries, maintaining consistent supply and state.

### Contract Overview

GBPA is deployed using the native token standard on each [supported network](broken://pages/ihpHzXpIK38886nAg1Ws), with LayerZero’s OFT standard enabling consistent cross-chain functionality.

Deployments on EVM-compatible chains (Ethereum, Base) use LayerZero’s *OFTUpgradeable* contract, an omnichain extension of the [ERC-20 standard](https://ethereum.org/en/developers/docs/standards/tokens/erc-20/). This upgradeable structure allows Agant to introduce new functionality in response to regulatory or technical developments without requiring user action.

The Solana implementation uses the [Token 2022](https://spl.solana.com/token-2022) (Token Extensions) Program, enabling additional functionality while maintaining compatibility with the standard Solana Program Library (SPL) format. The [Permanent Delegate](https://spl.solana.com/token-2022/extensions#permanent-delegate) extension is enabled to support future regulatory requirements. [Native Metadata](https://spl.solana.com/token-2022/extensions#metadata) is also enabled, ensuring metadata is stored with the token and verifiably linked to its mint.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.agant.io/Y83ivqmfOiUspagNyFg6/tokens/gbp-stablecoin-gbpa.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.