Written Culture and its Importance
To foster transparency and clarity of thought, we at Coherent want to start off on the right foot as a company and establish a culture of writing well. Whether it’s internal communication or making our documentation as approachable as possible for developers, clear writing comes from clear thinking - it requires us to invest more time into shaping our ideas before we share them. Hence, we want to make quality writing a pillar of our company.
As a result, we’ll be writing memos to the public in the form of regularly published blogs, allowing all to see the progress we’ve made and share in the lessons learned. We’ll be sharing updates on our product line and also just write pieces on topics we’re really excited about in Web3. And if you ever have any feedback or just want to chat, feel free to drop us a line on Twitter @coherentapi, @orange_juicetin, or @carlcortright.
Though an unexpected product we never foresaw coming, we’re happy to announce that starting today we’ll be offering a contract ABIs endpoint! In addition to returning an ABI, we also provide contextual data such as its standard (ERC20, 721, etc.), the contract’s verification status, its symbol, and more. Docs can be found here under docs.coherent.sh.
The main improvements come from its higher-fidelity offering of “repaired ABIs” for a broader variety of contracts compared to what Etherscan provides. This is done through our internal processes of mending incomplete ones using event fragments - thanks to some help from @Metagame, we were able to work off the existing contributions from Brenner in order to incorporate these manually scraped fragments into our decoder. We’re still midway in terms of ironing out some kinks in our process, but for now the endpoint still has full functionality in returning more reliable, consistent responses.
We decided to release this endpoint after our own struggles working with the Etherscan API, a relatable problem for most developers. It wouldn’t reliably provide us ABIs capable of decoding all the data we were working with - for certain contracts that weren’t verified, they would be incomplete or outright inaccurate at times. Other times, multiple ABIs would be returned for a single contract, leaving it up to us to test each one to determine the right one. Not to mention parameter names varying from ABI to ABI, adding to the overall bugginess and inconsistency. Our hope is that this endpoint can offer a clean solution to that for all Web3 developers.
Our whole team has been working extraordinarily hard these past two weeks to also launch a product we’re extremely excited about: readable user transaction history! We’ve talked to many of you already concerning your data needs, and our hope is that this endpoint can address a lot of shortcomings in the current API landscape. Docs here.
We’re currently live-indexing and working on backfilling all our historic data as we speak, and the product is available in production for our alpha testers to play around with more recent transactions closer to the chain-tip.
When you put in a given user’s address, you receive an array of enriched transactions composing a user’s transaction history.
On that note, fill out our alpha signup form if you’re interested in using it and we’ll get back to you pending capacity. And if you’re already onboarded, we love hearing from our users, so let us know about any bugs you’re experiencing or other features you’d like to see!