Simulator Output

We are attempting to understand the projected amount of data required to support the base requirements of the system. This page will list a few outcomes depending on certain inputs.

For https://casperlabs.atlassian.net/wiki/spaces/REL/pages/154796068 - We are assuming a base transaction volume of 15 Token transfers / second, for an uptime duration of 4 weeks, with 10 nodes in the validator set. We are not assuming any wasm deployments (while it’s likely that we will have wasm deploys, we also won’t have a steady stream of 15 tts the entire time either)

assumptions we made:
    number of validators: 10
    overall performance of the blockchain [tps]: 15
    round exponent (used by all validators): 14
    era body length [days]: 0.041666666666666664 (= 1.0 hours)
    era tail length [days]: 0.010416666666666666 (= 0.25 hours)
    average size of 1 deploy in bytes: 800
results:
    rounds in era body: 219.7265625
    rounds in era tail: 54.931640625
    total number of blockdag messages in 1 era: 5493.1640625
    average ballot size [bytes]: 329
    average block header [bytes]: 329
    average block size [MB]: 0.18781375885009766
    round length [seconds]: 16.384
    transactions in 1 block: 245
    protocol overhead [%]: 4.015466257878369%
    download bandwidth required by a validator [Mbit/sec]: 0.02336694160476327
    totals for 1 day:
        all blockdag messages: 131835
            blocks: 5273
            ballots: 126562
        transactions: 1296000
        protocol metadata (ballots + block headers) [GB]: 0.04039520717924461
        user data (= transactions) [GB]: 0.9655952453613281
        total blockdag size [GB]: 1.0059904525405727
        gossiping data [GB]: 0.9655952453613281
    totals for 30 days:
        all blockdag messages: 3955050
            blocks: 158190
            ballots: 3796860
        transactions: 38880000
        protocol metadata (ballots + block headers) [GB]: 1.2118562153773382
        total blockdag size [GB]: 30.179713576217182