Benchmarking Plasma Cash about plasma-cash HOT 1 OPEN

A Plasma chain operator must maintain information about all blocks submitted to the chain. Storage requirements for the operator increase only as blocks are added to the Plasma chain.

Each Block is simply a signature along with a set of transactions.

Block:
('transaction_set', CountableList(Transaction)),
('sig', binary)

A Plasma chain operator will likely store a Sparse Merkle Tree containing the transaction set, but this tree can be re-created from the transaction set.

Transaction:
('uid', big_endian_int),                -- 8 bytes
('prev_block', big_endian_int),         -- 32 bytes
('denomination', big_endian_int),       -- 8 bytes
('new_owner', ethereum.utils.address),  -- 20 bytes
('sig', binary)                         -- 66 bytes

Each transaction, at best, will require 134 bytes of storage. Therefore, a Plasma chain operator, at the very least, should expect to maintain {# of plasma transactions} * 134 Bytes of data.

from plasma-cash.