ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
brown cells are parameters you can adjust
green cells are from measurement of Reddit's contracts running on Arbitrum
2
3
workload factor1
times Reddit's nominal workload
4
fraction of users who claim tokens20%
5
in batchesin batches
6
MIX OF OPERATIONSops per daybatch sizeavg L1 gas per opavg L2 ArbGas per op
number of records at L2 (assuming system remembers 1 year of ops)
7
mass minting20,000500034064,37914,610,000
<--- number of accounts assumed
8
claim4,000147,010720,0612,922,000
9
subscription5,000174,901282,7193,650,000
10
burn15,000523,350151,1590
11
transfer20,000693,255105,3220
12
nominal operations per day60,000
13
14
number of invited Arbitrum validators8
15
value of chain, per account$1
16
interest rate (annual)6%
17
Ethereum gas price $ 0.000012
18
19
computation cost per CPU-second$0.00003
(based on Amazon EC2 t3a.xlarge default config)
20
storage cost per GB-day$0.01
(based on Amazon EBS default config)
21
22
COMPARING APPROACHES
mass minting approach
claim-only approach
23
L1 gas / day146,655,000167,895,000
24
L2 ArbGas / day7,075,000,0008,667,664,000
25
26
VALIDATOR-INDEPENDENT COST / DAY
27
L1 gas$1,759.86$2,014.74
28
active validator capital lockup$4.80$4.80
29
30
PER-VALIDATOR COST / DAY
31
computation$0.002$0.002
32
storage$0.009$0.003
33
34
Total system-wide cost / day$1,764.75$2,019.55
35
Total system-wide cost / nominal operation$0.029$0.034
36
37
RESOURCE UTILIZATION
38
fraction of total worldwide L1 gas used0.23%0.26%
39
fraction of Reddit L2 Arbitrum chain capacity used0.08%0.10%
40
41
NOTES AND ASSUMPTIONS
42
Reddit's contracts were modified to add mass minting functionality (otherwise completely unmodified)
43
minting can be done in batches of 5000 operations
44
other ops grouped by optional aggregator into 1 batch per 5 minutes
45
cost "in batches" is total cost, divided by total number of ops; includes (amortized) per-batch costs
46
assume conservatively that 56 bytes of memory used per funded account and per subscription
47
"value of the chain, per account" is how much users value their L2 points, averaged over all users
48
number of accounts the system must track = number of mint events in one year
49
ArbGas measures L2 computation cost; single-CPU validator can do at least 100 Million ArbGas per second
50
"nominal operations" includes an operation for each token granted, but not for claims
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100