z-logo
Premium
AWP1/ZFAND6 Functions in Pex5 Export by Interacting with Cys‐Monoubiquitinated Pex5 and Pex6 AAA ATPase
Author(s) -
Miyata,
Okumoto Kanji,
Mukai Satoru,
Noguchi Masafumi,
Fujiki Yukio
Publication year - 2012
Publication title -
traffic
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 2.677
H-Index - 130
eISSN - 1600-0854
pISSN - 1398-9219
DOI - 10.1111/j.1600-0854.2011.01298.x
Subject(s) - biology , microbiology and biotechnology , peroxisome , aaa proteins , biogenesis , ubiquitin , signal transducing adaptor protein , biochemistry , atpase , receptor , signal transduction , gene , enzyme
During biogenesis of the peroxisome, a subcellular organelle, the peroxisomal‐targeting signal 1 (PTS1) receptor Pex5 functions as a shuttling receptor for PTS1‐containing peroxisomal matrix proteins. However, the precise mechanism of receptor shuttling between peroxisomes and cytosol remains elusive despite the identification of numerous peroxins involved in this process. Herein, a new factor was isolated by a combination of biochemical fractionation and an in vitro Pex5 export assay, and was identified as AWP1/ZFAND6, a ubiquitin‐binding NF‐κB modulator. In the in vitro Pex5 export assay, recombinant AWP1 stimulated Pex5 export and an anti‐AWP1 antibody interfered with Pex5 export. AWP1 interacted with Pex6 AAA ATPase, but not with Pex1–Pex6 complexes. Preferential binding of AWP1 to the cysteine‐ubiquitinated form of Pex5 rather than to unmodified Pex5 was mediated by the AWP1 A20 zinc‐finger domain. Inhibition of AWP1 by RNA interference had a significant effect on PTS1‐protein import into peroxisomes. Furthermore, in AWP1 knock‐down cells, Pex5 stability was decreased, similar to fibroblasts from patients defective in Pex1, Pex6 and Pex26, all of which are required for Pex5 export. Taken together, these results identify AWP1 as a novel cofactor of Pex6 involved in the regulation of Pex5 export during peroxisome biogenesis.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here