BTG Pactual’s ReitBZ Reaches Tezos in Institutional Tokenization Test

Banco BTG Pactual’s ReitBZ security token was formally issued on the Tezos blockchain on May 22, 2020, according to the Tezos Foundation’s subsequent chronology of ecosystem events. The transaction extended an investment product originally issued on Ethereum in May 2019 onto a second public blockchain.

The event mattered less as a cryptocurrency-market catalyst than as an institutional experiment. A large investment bank was testing whether blockchain infrastructure could represent investor claims connected to conventional assets while preserving identity checks, transfer restrictions and other controls expected in a securities offering.

The chronology requires a qualification. BTG Pactual announced on May 19, 2020, that it had “officially issued” ReitBZ on Tezos, while the Tezos Foundation’s September 2020 report dated the issuance to May 22. The surviving sources do not explain whether May 19 marked the public announcement and May 22 a final operational step, or whether the difference reflects inconsistent recordkeeping. The May 22 date is therefore supported, but not with transaction-level precision.

A real-estate product, not a new cryptocurrency

ReitBZ was designed to provide economic exposure to a portfolio of distressed Brazilian real estate. Its issuer was Reit BZ Limited, a Cayman Islands foundation company, while BTG Pactual and group company Enforce handled investment selection and management. The offering documents described the token as a security token and required know-your-customer and anti-money-laundering procedures.

The offering was not open everywhere. Its documents excluded residents or nationals of Brazil and the United States, among other restricted jurisdictions. That structure is important: issuing units on a permissionless blockchain did not make participation permissionless. Access to the investment remained governed by the issuer’s eligibility and compliance rules.

BTG Pactual reported on May 19 that ReitBZ proceeds had been used to acquire 238 real-estate units in August 2019 and another 85 in December 2019. That is 323 units by straightforward addition, not an independently audited portfolio count. The bank said 181 units had been sold by May 19 and that the first profit distribution was scheduled for May 2020. Those statements were contemporaneous issuer claims; the cited records do not independently verify the properties, sale proceeds or investor returns.

Why the second chain mattered

The original ReitBZ implementation used Ethereum. BTG Pactual characterized the Tezos deployment as the product’s first non-Ethereum issuance and as a test for more complex security-token offerings. Using another chain allowed the bank to examine Tezos smart contracts, operational controls and settlement tooling without abandoning the underlying investment structure.

A March 13, 2020 security review by Least Authority examined the Tezos ReitBZ contract code supplied for assessment. The audit is evidence that technical review preceded the May deployment, but an audit does not eliminate software, custody, governance or legal risk. The available report also does not establish how much ReitBZ supply was active on Tezos on May 22 or whether equivalent Ethereum units were retired, mirrored or otherwise reconciled.

For Tezos, the issuance supplied a concrete institutional use case beyond trading the network’s native asset. For BTG Pactual, it was a controlled test of whether public-chain infrastructure could support a managed investment product. Neither point establishes broad adoption, secondary-market liquidity or regulatory approval.

Later context

BTG Pactual reported on July 27, 2020 that ReitBZ had begun operating on Tezos during May and announced a first portfolio-profit distribution using an Ethereum smart contract. That later disclosure helps confirm the project continued after May 22, but it should not be read backward as evidence that the Tezos version already had liquid trading, completed distributions or proven scale on the event date.