Willian Mitsuda
Willian Mitsuda
Something a little unrelated, but that is worth being mentioned, Sourcify updates the IPNS hash hourly, and due to contracts being verified constantly, the root hash also changes constantly. Even...
yeap, it is more like a side note for people to be aware of
Hi, yes, I'm using gatsby 2.1.4 and gatsby-plugin-ipfs 2.0.2. The gatsby-config.js contains the pathPrefix: '__GATSBY_IPFS_PATH_PREFIX__' and all links are correctly generated. The exception is the file sitemap.xml that is generated...
@satazor Hi, sorry for the delay.. I thought I'd have some time to take a look at the code, but I hadn't yet...
The backwards compatible change in the specs is here: https://github.com/otterscan/execution-apis/pull/1 And the proposed implementation is live in our test server (you can use an old tx until it is fully...
regarding the UI, I propose we do something similar to the input section, add an output section just below it with raw/decoded boxes.
actually, I'm thinking if we could retrofit a raw tab into the "return value" control you did for the "read contract" (and user will get a raw view for free)...
I have mixed feelings about this one. The approach etherscan uses is indeed to consider each transfer as 1 match in the search results. I thought about using txs as...
note to myself: it needs the API to be finished + UI prototype
temperature checking (for anyone seeing this issue): in the search results, would you prefer to: 1 - clearly see all token transfers for each tx 2 - see a summary...