Gather metrics on deployed contracts using Glow #146

Open kwannoel opened 3 years ago

In GitLab by @fahree on Mar 5, 2021, 00:07

null

In GitLab by @fahree on Mar 5, 2021, 00:11

It should be relatively easy to distinguish contracts using Glow from contracts compiled with Solidity: the -contract-init functions in gerbil-ethereum/evm-runtime.ss are quite different from their equivalent in Solidity or any other language, so we could pattern-match on them.

Then, we can run a daemon that watches the Cardano EVM Devnet (and, in the future, other chains) and gathers statistics on how much Glow is being used or not.

In GitLab by @fahree on Mar 5, 2021, 00:15

assigned to @Akaa

In GitLab by @fahree on Mar 22, 2021, 23:16

One way to make that much easier would be to always use our CREATE2 proxy contract to create contracts, and assume that only we use the proxy, for now.

In GitLab by @fahree on Mar 22, 2021, 23:18

Otherwise, a "simple" pattern-matcher that looks whether code was the output of either stateful-contract-init or stateless-contract-init plus watching all on-chain transactions... ouch.

In GitLab by @fahree on Mar 23, 2021, 02:29

OK, put this one on ice for now, until we implement https://gitlab.com/mukn/glow/-/issues/157

In GitLab by @fahree on Mar 24, 2021, 04:21

marked this issue as related to #157

In GitLab by @fahree on May 12, 2021, 04:22

assigned to @fahree and unassigned @Akaa

In GitLab by @ApolloUnicorn on May 12, 2021, 04:23

assigned to @isd

In GitLab by @alex413 on May 18, 2021, 03:40

What's the rough deliverable date for this?

Glow-Lang / glow

Gather metrics on deployed contracts using Glow #146