Enjoy ! The Fat Boy will be an interesting shave . <| sep |> But my dick is associated with violence <| sep |> I don ' t care if the leafs lose ! Yeah , they heard you . <| sep |> Lost Found by Charles Duncan <| sep |> It ' d be cool if DC Films does a New Gods movie as a prequel to the modernday DCEU , setting up Darkseid ' s origin . <| sep |> This guy lifts . <| sep |> Si me pongo en plan trascendente dudo mucho que pueda descansar en paz si realmente existe el alma o la conciencia que es igual de intangible ms all de este mundo terenal <| sep |> Are you honestly saying that the amount of bytes has no meaning in the new system ? None at all is perhaps a bit strong , but much less meaning than weight . Disk space required for archival nodes is only loosely coupled because the archived data can be compressed archival also need only be a small fraction of the total resources used by the system . Effect on cost to run a full node is much more strongly driven by the UTXO impact , which is much better reflected by weight . Lets walk directly down your list Disk space requirements for archival nodes . Only weakly what impacts that is compressed size , and archival requirements are only a small proportion of the total cost because this is something that could be done on a relatively small percentage of the nodes with the most resources . Verification time . Nope , N 2 validation costs in presegwit leaves validation times all over the map . As an aside , several of the hardfork proposing implementations XT and Classic , at least simply don ' t perform any signature validation for blocks where miners have given them an old enough timestamp . Most of validation time is UTXO lookups , which depend on the size of the UTXO set esp how much of it fits in ram . RAM usage . ram usage doesn ' t get directly changed by any of these things , though to keep constant performance cache sizes needs to go up with the UTXO set size . So it is related to nonwitness size . You ' ve also ignored many major factors . For example the disk space usage for the nonarchival nodes ! Pruning lets nodes discard witness data . Today a nonpruned node takes about 100 GB of space , while a pruned node takes about 2 . 5 GB of space . You ' ve ignored the resource usage for a SPV client spv clients need to receive nonwitness data .