Canary Files Fourth Staked TRX ETF Amendment With 1.10% Fee

Canary Capital has filed Amendment No. 4 to its registration statement for the Canary Staked TRX ETF, giving investors more detail on the proposed fund’s fee structure and staking approach.

The filing, submitted on August 19, discloses a 1.10% management fee. It also outlines a staking strategy under which up to 90% of the trust’s assets could be staked.

That makes this more than a routine ETF paperwork update.

The proposed fund would not simply hold TRX as a passive asset. It would introduce staking into the ETF wrapper, creating a different risk and return profile from a standard spot crypto fund.

Still, the most important detail is regulatory status: the ETF has not been approved. This is a registration amendment, and the required 19b-4 rule change process remains separate.

• Canary filed Amendment No. 4 for its proposed Staked TRX ETF.
• The filing discloses a 1.10% management fee.
• Up to 90% of trust assets could be staked, but the ETF has not been approved.

Staking changes the nature of a crypto ETF.

A standard spot ETF gives investors exposure to an asset’s price. A staked ETF adds another layer because the fund may earn rewards from participating in network validation or staking operations.

That can make the product more attractive to investors who want yield-linked exposure.

It also creates more complexity. Investors need to understand who controls staking, how rewards are handled, what risks exist around slashing or validator performance, and whether staking affects liquidity.

That is why the disclosure matters.

Canary is not only telling the market what the proposed fee would be. It is giving a clearer picture of how the fund may operate if regulators allow it to move forward.

TRX has not had the same ETF spotlight as Bitcoin or Ethereum.

Bitcoin ETFs are already deeply established. Ethereum ETFs are building their own institutional base. Other crypto ETF proposals, including staked products, are now testing how far regulators may allow the category to expand.

A Staked TRX ETF would sit in that next wave.

It would give traditional investors a regulated fund wrapper around TRX exposure, while also attempting to incorporate staking economics. That combination may appeal to investors looking beyond BTC and ETH, but it also raises additional questions for regulators.

Staking has already become one of the most sensitive areas in crypto policy.

The filing should not be mistaken for approval.

A registration statement can be amended many times before a product reaches the market. The SEC may ask questions, request changes, delay review, or block the path entirely depending on the structure.

The separate rule-change process is also critical.

An ETF cannot trade simply because a sponsor files an amended S-1. The exchange listing process must also clear the necessary regulatory steps.

That means the clean read is: Canary is preparing the product and adding detail, but the fund is not live.

The 1.10% management fee is another key detail.

Crypto ETFs compete on fees, liquidity, brand trust, custody, structure, and investor access. Bitcoin ETF issuers have already shown how aggressive fee competition can become once products reach the market.

A staked TRX product may not be directly comparable to a plain spot Bitcoin ETF, but investors will still examine whether the fee makes sense relative to staking rewards, liquidity, and risk.

If approved, the product would need to justify that cost.

The next step is regulatory review.

Investors will watch whether the SEC comments on the staking structure, whether the listing exchange advances the required rule-change application, and whether Canary makes further amendments.

The filing gives the market a clearer look at how the proposed ETF would work. It does not settle whether regulators will allow it.

For now, Canary has moved the Staked TRX ETF proposal another step forward — but approval remains the real hurdle.

This article is based on Canary Capital’s Form S-1 amendment filed with the SEC.

This article was written by the News Desk and edited by Samuel Rae.

This report is based on information released in disclosures at primary source documentation.