# EDGAR Filing Document

**Accession Number:** 0001974395
**File Stem:** 0001493152-26-031215
**Filing Date:** 2026-6
**Character Count:** 17000
**Document Hash:** fcaf06b396b04947e197f2467a777f85
**Contains OCR:** False
**Source Format:** 

## Filing Content

## Filing Summary
**0001493152-26-031215.hdr.sgml**: 20260630

**ACCESSION NUMBER**: 0001493152-26-031215

**CONFORMED SUBMISSION TYPE**: 424B3

**PUBLIC DOCUMENT COUNT**: 1

**FILED AS OF DATE**: 20260630

**DATE AS OF CHANGE**: 20260630

**FILER**: 

**COMPANY DATA:**
- **COMPANY CONFORMED NAME:** Figure Certificate Co
- **CENTRAL INDEX KEY:** 0001974395

**ORGANIZATION NAME:**
- **EIN:** 923576834
- **STATE OF INCORPORATION:** DE
- **FISCAL YEAR END:** 1231

**FILING VALUES:**
- **FORM TYPE:** 424B3
- **SEC ACT:** 1933 Act
- **SEC FILE NUMBER:** 333-275154
- **FILM NUMBER:** 261138225

**BUSINESS ADDRESS:**
- **STREET 1:** 650 CALIFORNIA STREET
- **STREET 2:** SUITE 2700
- **CITY:** SAN FRANCISCO
- **STATE:** CA
- **ZIP:** 94108
- **BUSINESS PHONE:** (310) 592-0097

**MAIL ADDRESS:**
- **STREET 1:** 650 CALIFORNIA STREET
- **STREET 2:** SUITE 2700
- **CITY:** SAN FRANCISCO
- **STATE:** CA
- **ZIP:** 94108

**Filed Pursuant to Rule 424(b)(3)**

**Prospectus Supplement**

**Registration No. 333-275154**

**FIGURE CERTIFICATE COMPANY**

**SUPPLEMENT DATED JUNE 30, 2026** 

**TO THE PROSPECTUS DATED APRIL 24, 2026**

This prospectus supplement (this "Supplement") is part of and should be read in conjunction with the prospectus of Figure Certificate Company, dated April 24, 2026 (the "Prospectus"). Unless otherwise defined herein, capitalized terms used in this Supplement shall have the same meanings as in the Prospectus. References herein to "we", "us", or "our" refer to Figure Certificate Company unless the context specifically requires otherwise.

The purpose of this Supplement is to update the Prospectus with respect to approved blockchains used by FCC.

The following updates to the Prospectus are effective immediately:

&nbsp;&nbsp;&nbsp;&nbsp;1. The
 following replaces the section titled "*Overview of Digital Asset Securities and the Use of FCC's Blockchain-Integrated System*" found on page 2 of the Prospectus
 in its entirety:

The Certificates offered by FCC are issued as digital asset securities using open source, public, blockchain-based distributed ledgers that are secured using cryptography (each referred to as a "blockchain"). Each blockchain records issuances and transactions between two parties in a verifiable and permanent way, referred to as "immutability." FCC's transfer agent maintains the official record of Certificate ownership via a proprietary blockchain-integrated system that utilizes features of traditional book-entry form and one or more public blockchain networks. Because the transfer agent maintains the official record of Certificate ownership through a combination of on-chain and off-chain information, the Certificates are characterized herein as "digital asset securities." For more information, see "*Digital Asset Risks*."

FCC currently uses the Provenance Blockchain as the primary public blockchain and purchasers of Certificates may initially hold their wallets on the Provenance Blockchain. However, FCC may also use the Solana, Stellar, Avalanche, Sui, Tempo and other suitable blockchains for accounts upon request. The transfer agent's blockchain network suitability framework is described in greater detail in the section "*Suitability for Blockchain Networks*" and includes certain key standards such as redundancy qualities, continuous uptime, block time, and transaction fees. Potential and existing Certificate holders must contact FCC's transfer agent to determine the ability to hold Certificates on a blockchain other than an approved blockchain and the availability of the other blockchain. Approval to hold a Certificate on a blockchain other than an approved blockchain is subject to the sole discretion of FCC and its transfer agent. For more information regarding suitability criteria for the available blockchain networks, see "*Blockchain Network Suitability Framework*."

Public blockchain networks require the payment of certain transaction fees to validate a transaction on the applicable network. These fees, which will vary from network to network, are typically paid in the native digital asset for the operation of the blockchain network. See "*Native Digital Assets of Blockchain Networks*." Such transaction fees are intended to protect the blockchain networks from frivolous or malicious computational tasks. Transaction fees will be the responsibility of FCC or its affiliates, and Certificate holders will not be required to purchase any native digital asset to transact on the applicable network; provided, however, that any transfer to or from a non-approved wallet will be invalid and the transaction fees will be the responsibility of the parties to the invalid transfer. See "*Blockchain Network Transaction Fees*."

&nbsp;&nbsp;&nbsp;&nbsp;2. The
 following replaces the section titled "*Multi-Chain Support and Network Suitability Framework*" found on page 17 of the Prospectus in its entirety:

FCC currently uses the Provenance Blockchain as the primary public blockchain and purchasers of Certificates may initially hold their wallets on the Provenance Blockchain. However, FCC may also use the Solana, Stellar, Avalanche, Sui, Tempo and other suitable blockchains for accounts upon request. Please contact the Transfer Agent at support@figuremarkets.com to determine your ability to hold Certificates on a blockchain other than an approved blockchain and the availability of the other blockchain. Approval to hold your Certificates on a blockchain other than an approved blockchain is subject to the sole discretion of FCC and its Transfer Agent. For more information regarding suitability criteria for the available blockchain networks, see "*Blockchain Network Suitability Framework*."

In the event of an authorized transfer from one approved blockchain to another approved blockchain, the transfer can be accomplished through the "burning" or "vaulting" of Certificates recorded on one blockchain and the "minting" of Certificates on the other blockchain. For example, assuming 100 Certificates are initially recorded on the Provenance Blockchain and a subsequent request to transfer the 100 Certificates from the Provenance Blockchain to Solana is approved, the Provenance Blockchain record would initially reflect the ownership of 100 Certificates and ultimately a burning or vaulting of 100 Certificates upon successful transfer, and the Solana blockchain record would reflect the minting and delivery of 100 Certificates. In such a situation, no new Certificates are created on the official record of Certificate ownership; rather, record ownership of Certificates is merely transferred from one blockchain to another.

The suitability of a blockchain network is determined by the Transfer Agent using a framework that specifies minimum acceptable standards for public blockchains used by FCC. The Transfer Agent's blockchain network suitability framework is described in greater detail in the section "*Suitability for Blockchain Networks*" and includes certain key standards such as redundancy qualities, continuous uptime, block time, and transaction fees. The Transfer Agent may migrate away from a blockchain network used by FCC if the blockchain network fails to meet the key standards of the Transfer Agent's suitability framework for sustained periods of time.

&nbsp;&nbsp;&nbsp;&nbsp;3. Information
 about each blockchain network used by FCC found on page 20 of the Prospectus under the section *"Blockchain Network Suitability Framework"* has been revised to read as
 follows:

---

| | | | | | | |
|:---|:---|:---|:---|:---|:---|:---|
| &nbsp;&nbsp;**Criterion** | &nbsp;&nbsp;**Provenance** | &nbsp;&nbsp;**Solana** | &nbsp;&nbsp;**Stellar** | &nbsp;&nbsp;**Avalanche** | &nbsp;&nbsp;**Sui** | &nbsp;&nbsp;**Tempo** |
| &nbsp;&nbsp;● **Analytics** | &nbsp;&nbsp;**https://provenance.io/pulse/ and https://explorer.provenance.io/dashboard** | &nbsp;&nbsp;**https://explorer.solana.<br> com** | &nbsp;&nbsp;**https://stellarbeat.io** | &nbsp;&nbsp;**https://subnets.avax.**<br> **network** | &nbsp;&nbsp;**https://suiscan.xyz/mainnet/home**<br>| &nbsp;&nbsp;**https://explore.tempo.xyz** |
| &nbsp;&nbsp;**Redundancy Qualities** | &nbsp;&nbsp;**Redundancy Qualities** | &nbsp;&nbsp;**Redundancy Qualities** | &nbsp;&nbsp;**Redundancy Qualities** | &nbsp;&nbsp;**Redundancy Qualities** | &nbsp;&nbsp;**Redundancy Qualities** | &nbsp;&nbsp;**Redundancy Qualities** |
| &nbsp;&nbsp;● **Number of Full Nodes Online** | &nbsp;&nbsp;98 | &nbsp;&nbsp;4579 | &nbsp;&nbsp;38 | &nbsp;&nbsp;1728 | &nbsp;&nbsp;392 | &nbsp;&nbsp; 10 |
| &nbsp;&nbsp;● **Distinct Operating Environment Locations** | &nbsp;&nbsp;9 (see https://observatory.zone<br> /provenance/validators) | &nbsp;&nbsp;520 | &nbsp;&nbsp;12 | &nbsp;&nbsp;10 | &nbsp;&nbsp;13 | &nbsp;&nbsp; 10 |
| &nbsp;&nbsp;● **Third Party code audit** | &nbsp;&nbsp;Informal Systems | &nbsp;&nbsp;Neodyme | &nbsp;&nbsp;n/a | &nbsp;&nbsp;Trail of Bits, Ancilia | &nbsp;&nbsp;Halborn, Zellic, OtterSec, Blaize.Security, Certora, MoveBit, and zkSecurity | &nbsp;&nbsp;Sigma Prime, Zellic<br>|
| &nbsp;&nbsp;**Reliability Qualities** | &nbsp;&nbsp;**Reliability Qualities** | &nbsp;&nbsp;**Reliability Qualities** | &nbsp;&nbsp;**Reliability Qualities** | &nbsp;&nbsp;**Reliability Qualities** | &nbsp;&nbsp;**Reliability Qualities** | &nbsp;&nbsp;**Reliability Qualities** |
| &nbsp;&nbsp;● **Mean Time Between Failures (MTBF)** | &nbsp;&nbsp;∞ | &nbsp;&nbsp;10795 hours | &nbsp;&nbsp;∞ | &nbsp;&nbsp;5397 hours | &nbsp;&nbsp;100% | &nbsp;&nbsp;8,760 hours |
| &nbsp;&nbsp;● **Uptime** | &nbsp;&nbsp;100% | &nbsp;&nbsp;● 99.954%<br> ● 298 minutes downtime<br> ● 1 event<br>| &nbsp;&nbsp;100% | &nbsp;&nbsp;● 99.958%<br> ● 274 minutes downtime<br> ● 2 events<br>| &nbsp;&nbsp;100% uptime since its mainnet launch | &nbsp;&nbsp;99.9% |

---

---

| | | | | | | |
|:---|:---|:---|:---|:---|:---|:---|
| &nbsp;&nbsp;**Criterion** | &nbsp;&nbsp;**Provenance** | &nbsp;&nbsp;**Solana** | &nbsp;&nbsp;**Stellar** | &nbsp;&nbsp;**Avalanche** | &nbsp;&nbsp;**Sui** | &nbsp;&nbsp;**Tempo** |
| &nbsp;&nbsp;**Operational Characteristics** | &nbsp;&nbsp;**Operational Characteristics** | &nbsp;&nbsp;**Operational Characteristics** | &nbsp;&nbsp;**Operational Characteristics** | &nbsp;&nbsp;**Operational Characteristics** | &nbsp;&nbsp;**Operational Characteristics** | &nbsp;&nbsp;**Operational Characteristics** |
| &nbsp;&nbsp;● **Testnet Availability** | &nbsp;&nbsp;Yes | &nbsp;&nbsp;Yes | &nbsp;&nbsp;Yes | &nbsp;&nbsp;Yes | &nbsp;&nbsp;Yes | &nbsp;&nbsp;Yes |
| &nbsp;&nbsp;● **Node Ops Data** | &nbsp;&nbsp;Full history | &nbsp;&nbsp;Full history | &nbsp;&nbsp;Full history | &nbsp;&nbsp;Full history | &nbsp;&nbsp;Full nodes require significant disk space for blockchain history and index files when serving RPC requests | &nbsp;&nbsp;● Chain ID: 42431<br> ● Block Time: 500ms<br> ● Target Throughput: ~20,000 TPS for payment transactions<br> ● Built on Reth SDK (Rust), EVM-compatible (Osaka hardfork target) |
| &nbsp;&nbsp;● **Consensus Method** | &nbsp;&nbsp;Proof-of-Stake based on CometBFT (formerly known as Tendermint Core) as its consensus engine | &nbsp;&nbsp;Proof-of-Stake + Proof-of-History | &nbsp;&nbsp;Stellar Consensus Protocol Proof-of-Agreement (PBFT based) | &nbsp;&nbsp;Avalanche Consensus Protocol | &nbsp;&nbsp;Delegated Proof-of-Stake (DPoS) with Mysticeti consensus protocol achieving 390 millisecond finality | &nbsp;&nbsp;● Simplex consensus<br> ● Tempo will initially launch with a small permissioned validator set and then expand with future validators in order to achieve decentralization |
| &nbsp;&nbsp;● **Mutli-Sig Capable** | &nbsp;&nbsp;Yes, using cosmos-sdk multisig accounts | &nbsp;&nbsp;Native method | &nbsp;&nbsp;Native method | &nbsp;&nbsp;EIP-191 + EIP-712 | &nbsp;&nbsp;Supports Multisig signatures | &nbsp;&nbsp;Yes |
| &nbsp;&nbsp;● **Block Time** | &nbsp;&nbsp;Targeted to be 3.5s on mainnet, current average for last 100 blocks on mainnet as of writing this was 4.42s.<br> instant finality<br>| &nbsp;&nbsp;0.4 seconds | &nbsp;&nbsp;5 seconds | &nbsp;&nbsp;2 seconds | &nbsp;&nbsp;0.24 seconds<br>| &nbsp;&nbsp;Targeted to be 500ms block times with sub-second finality |

---

---

| | | | | | | |
|:---|:---|:---|:---|:---|:---|:---|
| &nbsp;&nbsp;**Criterion** | &nbsp;&nbsp;**Provenance** | &nbsp;&nbsp;**Solana** | &nbsp;&nbsp;**Stellar** | &nbsp;&nbsp;**Avalanche** | &nbsp;&nbsp;**Sui** | &nbsp;&nbsp;**Tempo** |
| &nbsp;&nbsp;● **Account (Public Key) Parallelization** | &nbsp;&nbsp;No | &nbsp;&nbsp;Yes | &nbsp;&nbsp;Yes | &nbsp;&nbsp;Yes | &nbsp;&nbsp;Yes<br>| &nbsp;&nbsp; Yes |
| &nbsp;&nbsp;● **Signature Algo** | &nbsp;&nbsp;ECDSA secp256k1 | &nbsp;&nbsp;EdDSA ed25519 | &nbsp;&nbsp;EdDSA ed25519 | &nbsp;&nbsp;ECDSA secp256k1 | &nbsp;&nbsp;Ed25519 Pure, ECDSA Secp256k1, ECDSA Secp256r1, Multisig, and zkLogin | &nbsp;&nbsp;Supports three signature types. All use Keccak-256 for tx hashing. P256 enforces "low-s" for malleability protection |
| &nbsp;&nbsp;● **Fee Token** | &nbsp;&nbsp;HASH | &nbsp;&nbsp;SOL | &nbsp;&nbsp;XLM | &nbsp;&nbsp;AVAX | &nbsp;&nbsp;SUI | &nbsp;&nbsp;No single native fee token nor volatile gas tokens. Users can pay fees in any supported stablecoin (e.g. pathUSD, USDC.e, other approved stablecoins) |
| &nbsp;&nbsp;● **Effective Operating Cost per Transaction** | &nbsp;&nbsp;$0.003<br> Assuming Bank send to be the most common tx (0.16023717 hash at price of $0.019) | &nbsp;&nbsp;$0.000782 | &nbsp;&nbsp;$0.000006 | &nbsp;&nbsp;$0.35 | &nbsp;&nbsp;Avg 0.002797 SUI<br>| &nbsp;&nbsp;$0.001 |
| &nbsp;&nbsp;● **Static Costs Per Account Per Year** | &nbsp;&nbsp;$0 | &nbsp;&nbsp;$0.25 | &nbsp;&nbsp;$0.50 | &nbsp;&nbsp;$0 | &nbsp;&nbsp;Storage costs are paid upfront in perpetuity with 99% rebateable upon deletion | &nbsp;&nbsp;No recurring annual storage or account maintenance fees |

---

---

| | | | | | | |
|:---|:---|:---|:---|:---|:---|:---|
| &nbsp;&nbsp;**Criterion** | &nbsp;&nbsp;**Provenance** | &nbsp;&nbsp;**Solana** | &nbsp;&nbsp;**Stellar** | &nbsp;&nbsp;**Avalanche** | &nbsp;&nbsp;**Sui** | &nbsp;&nbsp;**Tempo** |
| &nbsp;&nbsp;● **Minimum Initial Client AUM** | &nbsp;&nbsp;N/A<br>| &nbsp;&nbsp;N/A<br>| &nbsp;&nbsp;N/A<br>| &nbsp;&nbsp;N/A<br>| &nbsp;&nbsp;N/A | &nbsp;&nbsp;$10 million USD<br>|
| &nbsp;&nbsp;**Controls** | &nbsp;&nbsp;**Controls** | &nbsp;&nbsp;**Controls** | &nbsp;&nbsp;**Controls** | &nbsp;&nbsp;**Controls** | &nbsp;&nbsp;**Controls** | &nbsp;&nbsp;**Controls** |
| &nbsp;&nbsp;● **Permission Control** | &nbsp;&nbsp;Approved list | &nbsp;&nbsp;● Access list<br> ● Exclude list<br> ● Rate limits | &nbsp;&nbsp;Bidirectional Trustlines | &nbsp;&nbsp;Approved list | &nbsp;&nbsp;Can only be used by owners through private signature keys, with smart contract logic | &nbsp;&nbsp;Built-in RBAC (role based access controls) system that separates administrative responsibilities (additional information at https://docs.tempo.xyz/protocol/tip20/overview#role-based-access-control-rbac) |
| &nbsp;&nbsp;● **Clawback/Administrative Balance Control** | &nbsp;&nbsp;Provenance custom modules | &nbsp;&nbsp;Permanent delegate authority on Smart contract | &nbsp;&nbsp;Clawback flag | &nbsp;&nbsp;Smart contract | &nbsp;&nbsp;Only addresses with access to specific capability objects can perform administrative functions | &nbsp;&nbsp;Function for recovering and seizing assets (additional information at https://docs.tempo.xyz/guide/issuance/manage-stablecoin#using-the-burn-blocked-role) |

---

&nbsp;&nbsp;&nbsp;&nbsp;4. The
 following replaces the section titled "*Native Digital Assets of Blockchain Networks* "
 found on page 21 of the Prospectus in its entirety:

Hash (HASH): HASH has a circulating supply of approximately 20,127,168,371 tokens with a maximum supply of 100,000,000,000 tokens. HASH is used to pay for transaction fees on the Provenance Blockchain.

Solana (SOL): SOL has a circulating supply of 465 million with a total supply of 606 million tokens. Total supply inflates from staking rewards which is currently at 5.1% and declining 15% per annum with a 1.5% minimum. All transaction fees are paid in SOL and a percentage of fees are burned (currently 50%).

Stellar (XLM): XLM has a circulating supply of 29.1 billion tokens with a maximum supply of 50.0 billion tokens. XLM is used to pay for transaction fees on the Stellar blockchain.

Avalanche (AVAX): AVAX has a circulating supply of 393.9 million tokens with a total supply of 443.2 million tokens. The maximum supply of AVAX is 720 million tokens. Total supply increases by staking rewards at 5% rate. All transaction fees on the Avalanche network are paid in AVAX and are burned.

SUI (SUI): SUI has a circulating supply of approximately 3.6 billion tokens, with a maximum and total supply of 10 billion tokens. SUI is used to pay for transaction fees on the SUI blockchain.

Tempo: Tempo has no native token. Transaction fees on the Tempo blockchain may be paid for using approved stablecoins.