# PUP-33: Scale Parameters And Capacity for Evolution (SPACE) **URL:** \ **Category:** Parameters\ **Tags:** proposal\ **Created:** [March 11, 2024, 8:45pm UTC](https://forum.pokt.network/t/pup-33-scale-parameters-and-capacity-for-evolution-space/5104 "2024-03-11T20:45:45Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![poktblade](https://forum.pokt.network/user_avatar/forum.pokt.network/poktblade/32/903_2.png) [@poktblade](https://forum.pokt.network/u/poktblade)\ **Post date:** [March 14, 2024, 9:10pm UTC](https://forum.pokt.network/t/pup-33-scale-parameters-and-capacity-for-evolution-space/5104/5 "2024-03-14T21:10:23Z")
Nodies currently holds 20 app stakes staked into 5 chains, each 20M each per session (the other 6 we have are unused). Assuming best case scenario (or rather worst case scenario for block space) for our gateway, we take up 2MB of block space and have access to upwards to 9.6B relays a day assuming uniform distribution of traffic. (20M \* 20 \* 24). Obviously, the best case scenario is likely not to happen as our traffic is not uniform and not every node operator will be effective in a session. But it does give us a better general idea. The other gateway operators that are coming onboard are expected to adopt the gateway server which will exhibit the same behaviors that Nodies gateway is showing on chain. With this, we should be able to scale upwards to roughly 3-4 more gateway (2MB each) operators if they have the same traffic patterns as us based off @RawthiL [research](https://forum.pokt.network/t/block-sizes-claims-and-proofs-in-the-multi-gateway-era/5060/23) I support this proposal. Thanks everyone for the analysis and help --- _[View the full topic](https://forum.pokt.network/t/pup-33-scale-parameters-and-capacity-for-evolution-space/5104)._