# Program facts

The on-chain program at a glance, and how to check what is deployed yourself.

## At a glance

| | |
| --- | --- |
| Program ID | `8ZpbTPnDECPTDGN5VHHKH5gfer6EUTnRHcFwfUAbkJDg` |
| Network | Solana mainnet. Genesis hash `5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9d`. The program writes it into every market and position, and refuses any market or position that carries another. |
| Loader | BPF upgradeable loader, `BPFLoaderUpgradeab1e11111111111111111111111` |
| ProgramData account | `J1hgFyeMPiY2GfvKrGejVVigwcxKZ8B2BCwkCt4NS73f`. It holds the program bytes. |
| Upgradeable | Yes. covr can upgrade the program. See [Admin and upgrade powers](https://docs.covr.markets/users/contract/admin-and-upgrades.md). |
| Deployment ID | `0x13a01f9d69929d8b65db7e9a6cc0805075876a8a66664e4ef30dd26f635527e2`. Stored in every market, position and maker registration, and mixed into every quote signature, so a quote for this deployment cannot be used anywhere else. |
| Framework | Anchor 1.2.0 |
| Version | The program has no on-chain version number. A build is identified by the SHA-256 of its bytes. See [Build fingerprints](#build-fingerprints). |

| Tokens | |
| --- | --- |
| Covered-call payment | USDC, `EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v`, 6 decimals, SPL Token. The program accepts no other payment mint for covered calls. |
| Put payment | The market's payment token: a plain 6-decimal SPL Token mint, not native SOL, different from the asset. Token-2022 mints are refused. The maker must approve that exact mint in its put policy, and each policy binds one mint. |
| Collateral and put assets | SPL Token or Token-2022 mints. Native SOL is refused. |
| Flash exercise pairs | Covered calls: JitoSOL with USDC. Puts: JitoSOL with USDC, and JitoSOL with USDT. Adding a pair needs a program upgrade. |

The put rows apply from the program upgrade of 4 November 2026, which added cash-secured puts. See [Version history](#version-history).

[Accounts](https://docs.covr.markets/users/contract/accounts.md) lists every account the program owns, with its address seeds.

## Build fingerprints

| Build | SHA-256 of the program bytes | Size |
| --- | --- | --- |
| Current release, with cash-secured puts, live since 4 November 2026 | `59fb4cd6fb9f22ed82037aa63d2917e9695f335483eb51d2fb7d22de23f12e06` | 2,427,600 bytes |
| Previous release, with flash exercise of covered calls, live from 22 October 2026 until 4 November 2026 | `473de63c44eae678b3530767bc36002e3097767c314eb1cba15cff9e70c79602` | 1,840,304 bytes |
| Earlier release, live from 9 October 2026 until 22 October 2026 | `90907e09d8756141f946ae8e8090129b2ab869c005de58f713a787cb075e1ca5` | 1,813,120 bytes |

If the deployed bytes match a row, that build is running. If they match none, the program has changed since this page was written: ask covr first by DM to [@covrdotfun](https://x.com/covrdotfun) on X.

## Check the deployed program yourself

These steps use only the standard Solana CLI and read-only calls. Use the `finalized` commitment so you read settled state.

**1. Confirm the network.** It must print `5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9d`.

```sh
solana genesis-hash --url mainnet-beta
```

**2. Inspect the program.** This prints the ProgramData address (it must be `J1hgFyeMPiY2GfvKrGejVVigwcxKZ8B2BCwkCt4NS73f`), the upgrade authority, the slot of the last deployment and the data length.

```sh
solana program show 8ZpbTPnDECPTDGN5VHHKH5gfer6EUTnRHcFwfUAbkJDg --url mainnet-beta --commitment finalized
```

**3. Save the program bytes.** `solana program dump` writes everything stored after the 45-byte ProgramData header.

```sh
solana program dump 8ZpbTPnDECPTDGN5VHHKH5gfer6EUTnRHcFwfUAbkJDg covr.so --url mainnet-beta --commitment finalized
```

**4. Hash the build-length prefix.** ProgramData can be longer than the build, so hash exactly the build's size. For the current release, with cash-secured puts, that is 2,427,600 bytes. Use 1,840,304 to check the previous release, or 1,813,120 for the earlier one.

```sh
head -c 2427600 covr.so | shasum -a 256    # macOS
head -c 2427600 covr.so | sha256sum        # Linux
```

**5. Check the rest is empty.** Any bytes after the build must be zero. This must print `0`.

```sh
tail -c +2427601 covr.so | tr -d '\000' | wc -c
```

You can also read the ProgramData account directly and skip its header yourself. The header is 45 bytes: a 4-byte account type (3), the 8-byte slot of the last deployment, a 1-byte flag and the 32-byte upgrade authority.

```sh
solana account J1hgFyeMPiY2GfvKrGejVVigwcxKZ8B2BCwkCt4NS73f --output-file programdata.bin --url mainnet-beta --commitment finalized
tail -c +46 programdata.bin | head -c 2427600 | shasum -a 256
```

> [!TIP]
> Note the slot of the last deployment when you start using covr. Any upgrade changes it, so a changed slot tells you to check the fingerprint again.

## Version history

| Date | Build | What changed for you |
| --- | --- | --- |
| 10 September 2026 | `ff5a0ba5…`, 440,288 bytes | First mainnet deployment. Covered calls on JitoSOL, paid in USDC, in the original market and position format. |
| 6 October 2026 | `65f942cf…`, 1,798,648 bytes | The current market and position accounts (`MarketV3`, `PositionV3`) and per-asset limits for each maker. covr's app stopped opening positions in the original format. Positions already open kept their exits. |
| 9 October 2026 | `90907e09…`, 1,813,120 bytes | Tokenized-stock collateral on restricted markets, which settle in two steps. |
| 22 October 2026 | `473de63c…`, 1,840,304 bytes | Flash exercise of covered calls: the maker can sell the collateral and pay your strike inside one transaction. You receive exactly the strike, as with any exercise. |
| 4 November 2026 | `59fb4cd6…`, 2,427,600 bytes | Cash-secured puts: 25 new instructions for put markets, put positions, their exits and flash exercise of puts. The program cap on one JitoSOL order rose from 2 SOL to 50 SOL of stake-pool value. |


## Why the source is private

covr has not published the program source. These contract pages are the public description of the program: every account, field, instruction, check and state change. You cannot rebuild the program from them. You can check that the program on chain is the build they describe, using the fingerprints above, and you can watch for upgrades.

---

Source: https://docs.covr.markets/users/contract/program-facts · Part of covr Docs, https://docs.covr.markets/llms.txt
