Unified Developer Experience: Single API for Multiple Chains

Transcript

[Music] Hello everyone. Um hope you're enjoying cans and uh please stay hydrated. Uh the weather is really really hot. Even from for Malaysian it's still very hot. Uh yeah. So um my name is Caven and uh I wanted to speak about some of the enhancement that we made at EtherCAN for API. Uh yeah so uh what we've been working on for the past year is to unify our API experience since we host many of the explorers as well and this would help uh developer and user uh to build.

So the challenges that we usually have is that the data are trapped in chain specific silo. uh there are in individual explorer and uh whenever a explorer spin up uh developer will have to create an account u you know and create an API keys and they have to juggle for many many other networks that we have uh and it kind of annoying uh you know one explorer and one API key and then explore specific endpoints and and scaling uh your application will be hard if you're deploying on the multi-chain.

So what we change here is that uh we introduce our etherscan API v2 and uh yeah so with API v2 you will be able to with a single API key single dashboard to unlock all 60 chains um and u with one subscription as well. So you would not have to uh juggle with multiple subscription at uh different explorer and uh with that also we made all the endpoint consistent uh so you would not have to have uh issues with uh individual endpoints on specific network.

Yeah. So the recap will be uh before that you will have separate API key separate account for one explorer and um there are multiple base URL uh you would have to know the explorer um and uh yeah you will have custom deployment scripper chain if you would like to verify some contracts and there are always inconsistent endpoints but uh with the new changes uh everything is consolidated uh one key for all chains that we support and um yep single single endpoint uh you just need to define your chain ID to pull that specific data and uh we do also unify our verification workflow u and there are also the consistent JSON return.

So uh before this uh whenever you would like to get some data from particular network uh you would have to know uh the explorer URL uh you would have to know that we support a particular network uh with the URL as well. But for now using etherscan API v2 you would have to just put in the chain ID and uh we do have the URL later that I can share that you were able to look at all the chain ID that we support. Yeah. So we support more than uh 60 plus chains uh mainet and test net as well.

Uh and this is the URL. I will share a QR code later that uh you guys will be able to access the entire list of uh chain that we support. Uh we also as I mentioned uh we unified all our endpoints uh account contract transactions for token uh and NFT specifically you were able to get the metadata prizes as well holders. Uh this is particular important if you have uh if your deployment include bridging to other networks as well. uh yeah stats and we do also have our pro endpoints uh which is a little bit more on the richer uh data set you are able to tap into

uh and uh the most uh the most sought after feature will be the ver contract verification uh that we have and back then it was crazy uh because developer would have to have uh separate uh workflow for individual network and uh with ether scan API v2 to we are going to change that. Yeah. So you will just have to specific chain ID uh and uh you can send verification through very very very quickly uh without even messing around with uh different base URL.

Yeah. So back then uh for your ongoing contract uh development you would have to have custom script and we work a lot with developers directly to uh work with them in terms of their feedback uh how can we make things better and also uh our latest uh API v2 has been integrated uh within foundry hardhead and remix as well. So that will make things a lot easier for developers. Uh next I'll be sharing a little bit more on the use cases on what um our API is able to do.

Uh as you know on ether scan we are progressively tagging addresses and also tagging uh contracts. Uh user will be able to use our API to identify this contract addresses. uh most of the UI interface out there will just show a uh contract address and for developers you're able to use our API to return a name towards the address that is being tagged on the explorer and this will essentially give user a little bit more confident uh a little bit more understanding on what they're interacting with. Uh we do have a very long list uh of uh name tags for contracts as well and we work with developers directly to tag them. So uh

please feel free to use them and if you have any feedback uh let us know. Uh the other thing is on the API return we do return a lot of uh uh some additional data. We do have the notes that is on the explorer. If it's a warning if it's being uh it's a fishing attempt or um it's an issue with the address we do have them on notes as well. And uh we do also have the general label towards the address like if it's a fishing hack address, if it's an exchange and the reputation as well. Uh yep, this can be integrated into your workflow. Uh have your user confidently u interact with certain addresses.

Um in terms of uh accounting as well we do work with a couple of accounting partners uh where users now has the uh they interact with multiple network uh to be simple and uh for accounting purposes it's really hard to track each of every one of them and now it make things a little bit easy uh they would just have to uh call and uh get the list of transaction for every uh network they interact with and uh their balances uh the activities as well. So this is very helpful for uh tax and accounting purposes.

Uh yeah, we also do return the transaction type. So if it's a swap or if it's a transfer, it does helps with uh categorizing and also accounting purpose. Uh a swap is different from a transfer and that can be really uh quickly identified through the functioning being returned in the API. So this is something it's uh very useful as well. Yeah. So I think that is the end. Um and uh you can scan the QR code to uh get the uh directly to the doc and if you have any question uh happy to answer them.

[Applause] Is there any question for the speaker? Yep. I see. Hello. My address, my question is about how can you help to fight against address poisoning? Yeah. So, we do have on the front end uh uh we do have a mechanism on the front end that uh prevents uh address poisoning. um you were able to look at that uh on the front end, but at this point in time, I'm not sure if that's included in the API. Uh but we could

connect after that and I can get back to you if that's available on the API as well. Okay, thank you. Any questions here? I think no more questions. Thank you very much. [Music]