# \[Proposal\] Standard Address Upgrades **URL:** \ **Category:** Aztec\ **Tags:** rfp, upgrades\ **Created:** [September 29, 2023, 4:24am UTC](https://forum.aztec.network/t/proposal-standard-address-upgrades/2353 "2023-09-29T04:24:04Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Anon](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@Anon](https://forum.aztec.network/u/Anon)\ **Post date:** [September 29, 2023, 4:24am UTC](https://forum.aztec.network/t/proposal-standard-address-upgrades/2353/1 "2023-09-29T04:24:04Z")
_(an adaptation of [Zcash Unified Addresses](https://zips.z.cash/protocol/nu5.pdf#unifiedpaymentaddrencoding) ([ZIP316](https://github.com/zcash/zips/issues/470)))_ This is an extension of [social consensus](http://forum.aztec.network/t/upgrade-proposal-non-govnernance-via-social-consensus/611), compatible with [PBS](http://forum.aztec.network/t/proposal-pbs-proposer-builder-separation/2283). PBS introduces a stakeholder set, whose signatures are required to progress each rollup. Because PBS allows stakers to run on low-end hardware, it is acceptable to assign a single stakeholder set to multiple concurrent rollups. The PBS stakeholder set is then assigned, via social consensus, additional rollups as needed. If a rollup’s based block rate is consistently and considerably higher than its staked block rate, it transitions into a based-only rollup. # Unified Addresses: Adding a new rollup Once social consensus has been acheived, a new address type is added to a Unified Address standard, like in Zcash. The unified address format is a concatenation of multiple [Aztec addresses](https://docs.aztec.network/concepts/foundation/accounts/keys#addresses-partial-addresses-and-public-keys) for different protocol versions. See Zcash for a complete [example](https://zips.z.cash/protocol/nu5.pdf#unifiedpaymentaddrencoding). # Removing a rollup If a protocol becomes deprecated (e.g. a vulnerability is found), the address type is marked deprecated in the standard.