accesscontrol-explorer
accesscontrol-explorer copied to clipboard
Work in progress explorer for AccessControl roles
The mapping from role ids to role names is a huge JSON file generated at build time. It weighs about 1MB (about half when gzipped) which is more than the...
Minor usability tweak, when clicking in addresses to view in an external block explorer, open a new tab instead of navigating outside of Access Control Explorer.
[EIP-3770](https://eips.ethereum.org/EIPS/eip-3770) addresses look like `eth:0x0DA0C3e52C977Ed3cBc641fF02DD271c3ED55aFe` or `poly:0x0DA0C3e52C977Ed3cBc641fF02DD271c3ED55aFe`. They map to CAIP-10 identifiers which look like `eip155:1:0x0DA0C3e52C977Ed3cBc641fF02DD271c3ED55aFe`. We should support EIP-3770 but also CAIP-10 as not all chains will be covered...
We will receive requests to support new chains. We should document the process to deploy a new subgraph for those chains. How do we deal with subgraph updates? Can subgraphs...
The one example we have currently is an Ethereum mainnet contract. We should make sure it always links to the contract on that chain. Somewhat related to #11. We may...
Embed the video for our workshop on the topic: https://www.youtube.com/watch?v=g68PZua0lKQ
The data shown in the explorer is only truthful if contracts are honest. We should have a disclaimer somewhere that a dishonest contract can lie about roles or owners.
In the pattern where a contract is its own admin, in the "Member Of" panel, we should label the contract's own address as "self".
The account view is currently scoped to one chain, but accounts can have roles on multiple chains and it makes sense to want to see all of them at once....