Smart contract identity for orgs and agents

Transcript

Hello or hey everyone. So, I'm Nishal, co-founder of Inscribe. And today I will demo what we built with the Inscribe and what we are releasing next. So, we started Inscribe with the problem what we all face, that's the hex address in the Ethereum UI, right? We all scared, like even if it's a new user or an exper- experienced web3 user, we all see this hex addresses everywhere and we are when we are interacting with smart contract, we fear them. Like how many of you have this fear? Like I do. Yeah, quite a lot, right?

So, people do name their wallets, but smart contract naming is less than 2%, which is like very, very, very low. So, what solutions we have right now? People go to blockchain explorers or set the nickname for the contracts. But these solutions are centralized, right? What if every wallet, every contract can have a name which through which you can, you know, trust the domain via the ENS. So, let's suppose you are interacting with a registrar on ENS and you see this name v1.registrar.ens.eth, then you can instantly, you know, trust this because it belongs to ens.eth.

And you can safely interact with it. So, we had this contract naming season with ENS now and we distributed over 4.5 K of ENS token to the developers and protocols to, you know, spread awareness and even start an initiative and adoption of smart contract naming. So, it is still going on. You can go to Inscribe and name some contracts. So, during this time of smart contract naming season, we understood like naming is not enough. Like we need to have some metadata attached to the names so we can understand more about the contract. So, right now, when I'm a user, right? And I

try to find audits or even like, you know, which this contract belongs to, it's really hard for me. It's like fragmented over the websites, scattered over the website and GitHub. What if you have all this data on chain at a single platform and even like at wallets or blockchain explorers. So, you can see, okay, this contract belongs to Inscribe and these are the socials, avatar, what are the technical details like category, the license, docs, and you can also have security audits directly there.

So, I think this will make all our lives very easy and people will, you know, start interacting with smart contracts freely. And we also have APIs so you can directly integrate into your product. Okay so the naming, ENS naming and metadata can be hierarchical just like a mirror to DNS. So, what you can do is you can import your DNS on ENS. Like here we have web3project.org and we can import it and we can set a hierarchical at different levels like 2LD, 3LD, and 4LD. Let's suppose we start with 2LD and you can have your project or brand information. Then you can branch out in 3LDs for your products

or services like different um app, wallet categories. And you can set those metadata in this. And then at the sub levels, you can also do on chain versioning, which Vitalik was talking about in Devcon, right? Like you can have, okay, this is a V1 app, then the V2, version two, and you can also attach the release artifacts and audits directly into this. So, projects are embracing this on chain identity and these are some of the projects we are working with. Some has already announced and some are in progress.

But currently, the challenge still is a lot of users are using ENS just for individual identity, right? And orgs and teams are not fully utilizing the ENS, the full capabilities of ENS to have a protocol identity. Like you won't see many organization which are, you know, storing all the information on ENS, on on chain. So, we developed this next evolution of Inscribe where these orgs and team can easily manage their on chain identity and which is also accessible to your agents and visible to your users.

So, some of the features like shared workspace for your manage for managing names. Then you can track all your activity. Then you have batch operations, multi- multi-sig support. Then ability to add org or contract and even agent metadata. Then you have API and CLI access for agents. And lastly, we are also introducing smart account and smart session support. So, I'll just go to the demo. So, this is our current app where you can name all your contracts easily. Just need to paste your address and you can create a new name. It will create a

subname or you can use an existing one. And you can choose L2 chains. And just name your contract. Also, if you want to batch name your contract, that is also possible. You can upload the CSV with all the contracts and names and you can batch name your contract. And then if you want to deploy new contract with a name, that is also possible in a single transaction. So, this was our current version of Inscribe. And here also, if you want to find the smart contract metadata or even want to see the hierarchical view of contract. So, this is the smart contract matter I I was showing before. Here this is the primary name. And you can find socials of project avatar and then technical details and also the contract

ABI source Sourcify yeah. This this basically via Sourcify. Then you have contract Okay, this is too fast. Okay, let's go uh This is the the hierarchical view where you can see, you know, the text records are set at different level. Like some of the brand assets are here and others are at different level and you can see it easily. Okay, so This is our the new UI which we are going to release very soon. And here you can create new orgs.

So, okay. So, I will just try to I have recorded this. So, I'm trying to create a new org maybe ECC demo. And you can add your members here directly, invite them. And to set up the org, you have like five steps. So, first we are we will be releasing on mainnet soon. And the second step is selecting an 2LD. So, I have many, but yeah, I will be selecting ECC demo here. You can also import your DNS on the ENS via this.

Then you have manager mode. So, basically there are three managers mode. Like first is safe multi-sig where we will sign and you will also sign and then we can make the transactions. The second is Inscribe where all the transactions are gasless. And we are also about to bring Inscribe smart sessions so you don't need to sign anything. It is also going to be a gasless thing. So, okay. So, once we have this organization setup you need to give manager access of your 2LD. This is not the ownership of your 2LD. It's just a manager [clears throat] access so we can create subnames under your org.

So, once this is done, you don't you can even like unplug your wallet because after this we don't need wallet. All things is going to be gasless and everything will be controlled by the Inscribe. Which is also safe. Okay so now I have already set up organization which I will show here. So, if you see I have some wallets and contracts already preloaded and I can also add also going to add a new address here.

So, I have like many yeah, demo addresses. Okay, so it detects contract automatically. And once we have this this is the name management view where you can see all your name space. Like this ecc.eth and there's a new subname wallets and we have a W1. And I'm going to create a new subname directly. And if you see I'm not signing anything. It's as easy like just you know editing you can say a CSV.

And here I can also add metadata directly. So, suppose like this subname is for contracts. And you can stage your changes. And also similarly, this is a contract one under the contracts and I'm just setting a address. So once all the changes are staged, we can review the changes. Like what are the changes here? So, right now I'm creating two subnames and these are the record changes. And after this, I just need to confirm and execute.

Okay. >> Just give me a second. Yeah, once we hit the execute, you can see the pending transactions and completed transactions uh which are um in the background. And here, you can also manage your organization if you want to add more members or you want to revoke access to from someone, you can do from here.

And then uh you can change the manager access from Inscribe contract to other uh Inscribe contract to other manager access like safe and else. And this is the API keys. So, this is very useful if you want if you have AI agents. Like you can create an API key. Uh let's say I'm I think yeah, Inscribe agent. And you can set the expiry and what are the scope you want. Like if you want to give uh sub name creation and not record uh editing records, you can do that.

And okay, so what I will be doing is Yeah, this is the details of your contract of your organization. So Okay. So, what I'm doing here is you just need three environment variables like the Inscribe API key, the uh org ID, and then the URL. Once you have this, this is the demo AI agent which is I'm uh showing. So, it's basically you can have more complex AI agents um built for you. But here, this is the environment environment variable file with three environments, and this is the skill file which you need to install in your AI agent. Once this is done, which like this this is a demo this is demo stuff,

but yeah, you can have some complex uh you know, AI agents which can directly read your um website or whenever you have a new contract deployed, it can you know, create a sub name. So, what here I'm doing is create a sub name con two uh in Sepolia. So, it will directly use the skill and dip create a new sub name. So, let it complete uh Yeah, so if you see uh it was created successfully.

And this is the transaction hash for it. And if you realize, right? Uh there's no uh signing of transactions. And yeah, you can see it's done. Okay. Uh let's Okay, so um this product is still in beta, and what we are doing currently is, you know, uh asking teams and projects to join an early access where you can uh collaborate with us and join us. Um and you can basically, you know, provide some feedback. Uh so to all the teams who want to establish a full full on-chain identity, uh simplify

their naming operations, and even manage their org metadata, or embrace agents for naming operations, and be the be among the first teams to make on mainnet with full on-chain identity, do join us. Uh scan the QR code, it will uh it will bring the Inscribe website, and you can apply for an early access. So, uh thank you. That's all from my side. If you have any questions, just uh Yeah, thank you. So, I wanted to ask how do you deal with proof of identity in these cases? Let's imagine I want to register the new name Binance, and it

wasn't taken before. What stops me as an attacker to like what is there any KYC being placed or something which actually would make this thing semi-centralized or fully centralized because essentially DNS DNS and proof of web identity is centralized, and I'm interested in how you bridge it to make it decentralized in this case. Yeah, uh it's a nice question. So, we already have like DNS on ENS. So, how it works is uh if you have like maybe Uniswap or Binance.org, right? Uh so, via DNSSEC, you can establish a um link to your ENS name. Uh basically, you can say, "Okay, I have Binance.eth."

And you can also link it to the Binance.org, or you can even use Binance.org as an ENS name. Right? Because you own a Binance.org, right? And via DNSSEC, you are proving it. So, it's like uh that that's how the proving of identity works. In this case, yeah. Okay, we can maybe yeah, uh take it afterwards. Thank you.