-
### Component
Forge
### Describe the feature you would like
@mattsse in #2098
>this will require a bit of work, basically managing a registry, but would be huge, getting rid of git submod…
-
### Overview
Add Sourcify verification to Ape framework, similar to Etherscan.
Sourcify ([sourcify.dev](https://sourcify.dev)) is a decentralized and open-sourced smart contract verification ser…
-
### Overview
When fetching contract data from a block explorer on a live network, the results are cached in `.ape/{ecosystem_name}/{network_name}/contract_types/{address}.json`, which is very helpful…
-
Hey @pipermerriam :-D! Giveth and Swarm City are looking at building something similar to this (and once we get it working we will likely include others (First on the list is Aragon, then we will star…
-
I'm currently relooking at these problems with a fresh pair of eyes and I'm starting to realize that a lot of our problems can be resolved if we just use ENS + proper resolution results within the ENS…
-
Suggestion is to subclass web3's Contract class and add necessary functionality specifically to streamline testing. Suggested functionality includes:
- [ ] Contract Template handling (Factory vs. I…
-
v0.3
## Phase 1
### Standards
- ERC20
- Impl, Test & FV: [DONE](https://github.com/LayerXcom/verified-vyper-contracts/tree/master/contracts/erc20)
- ERC721
- Impl & Test: [DONE](https://g…
-
Mostly just a semantics thing, why is it "contract_types" instead of something simpler like "contracts"?
Solidity's JSON output puts them into a "contracts" object. Might make for easier compatibil…
-
### What is wrong?
We've seen how the token ecosystem has benefited from having a standard API (ERC20) for interacting with tokens. We need the same for package registries.
### How can it be fi…
-
Opening for discussion, since I know there could a basic caveat; some functions with the same signature could name their parameters differently.
That said, if MetaMask had some way of knowing, for …