The "DIstributed Analytical BLOckchain" Benchmark Framework. (Diablo). Measures blockchains with a focus on real-world applications and workload generation.
The specification of smart contract functions is not generic enough.
The notion of "ftype" is not present on every blockchain. The types of argument can change from a smart contract implementation to another.
I do not think we can go much further than a pair "contract name/path" and "interaction name". It would be up to the blockchain integrator to decide how to interpret the interaction name to make something sensitive (at worst, encoding the parameter in the interaction name e.g. "IncrementCounterBy:1")
The specification of smart contract functions is not generic enough. The notion of "ftype" is not present on every blockchain. The types of argument can change from a smart contract implementation to another.
I do not think we can go much further than a pair "contract name/path" and "interaction name". It would be up to the blockchain integrator to decide how to interpret the interaction name to make something sensitive (at worst, encoding the parameter in the interaction name e.g. "IncrementCounterBy:1")