EIP Editing Office Hour #96 (EIP + ERC)

Transcript

[music] Welcome to EIP editing office hour meeting number 96.

This is added as agenda on Ethereum/PM GitHub repository and the issue number is 207. On agenda, we have a bunch of review, miscellaneous and uh draft proposals. We are also joined by some of the authors. Sam, maybe you can start with the review proposal and we can drop the link in the chat with other PRs for which authors are already here on the call. >> Sounds good. So, we'll get started with 7673. And oh, this is should be pretty easy.

String support format for human readable address. There we go. The problem is the address tokens. Perfect. uh shall depict addresses as B of X decimal shall accept B6 emoji strings should recognize interpret strings of exactly 20 consecutive emoji as addresses when all of them are valid. Okay. Heat.

Um, I don't know. This is This is funny. I like it, but it's funny. It's reference implementation. >> Funny and probably colorful. >> Yeah. Yeah. Interesting. Um, let's prove that. And then I want to leave comment on this. Uh, what's the name of this? It's

There it is. 256 emoji. Okay,

moving on. Next one. Next one. I'm not very clear like is it for all CIO just specific for this one but have added it because it was of another editor so he may not be able to do it. >> Sure. [sighs and gasps] comma change. Oh yeah, this this is Yeah, just do not merge. >> Okay, >> easy enough.

[sighs] Okay, 7945 Okay. Confidential transaction supported token outlines a funible token interface that hides per account balances boosting privacy and deps. That's nice description. There's a bunch of authors. Cool. Draft review. Okay. Classic token contracts 20. Enable the token holders to make transfers. Hey, nice people actually citing things.

Uh, Alex with a modifying blockchain protocol. Actually, let's take a look. This is in review, right? So, we can see how that renders. This is 7945. 7945. Hey, perfect. They render correctly. Uh, how it comes to the latter way. That's kind of awkwardly worded. Confidential transactions have been implemented many blockchains either natively or through blockchain protocols or through smart contracts like Zether without modifying.

Okay. Now when it comes to the latter way. Um however a few standards Uh, that's still kind of clunky, but

use applications to check whether token contract supports coverage transactions or not. So, and so hardly can Oh, that's still really weird. [sighs and gasps] Um, and so hardly, so so Okay. Consequently, this proposal is to confidential transaction supported token contracts.

such standard interface be such a standard interface unless co transactions and tokens to be applied by certain parties which is sensitive to transment over privacy preserving applications. Okay. okay. So Okay, fine. [laughter]

The proposed contract influences two interfaces I committed in a confidential token. Um, okay. So Oh, This is ERC 7945. 7 945.

Okay, let's see. Let's grab this. Go like that. Go up here. Paste this here. Intern 7 945. How's that going to look? That looks perfect.

Okay. Optional [snorts] this mythic beast. Yeah. Okay. Fine. Covenant balance off. That's fine. There's [music] extra space there. [gasps] Co transfer transfer value tokens. No, that's not a We can go here. Copy that.

[sighs and gasps] And we can leave a comment on here. Oh, I already made that comment. Cool. >> [sighs and gasps] >> Um Tre's value amount of tokens cause fallations completely customized approve system [gasps] confident that's all fine. Fine.

Neat. Hey, sound. Yeah.

Good. Great. Okay. So, then we can go here. I think all of these are pretty minor and we're only going into review. You know what? I'm I'm not going to approve. >> All right. Where do we want to go next? >> So for the next one is um 168 which is in review status going into review status and we are joined by the author Cyber Century.

>> Okay. Ah yes I'm sorry I haven't gotten back to your Discord messages yet. I will eventually. >> no worries. Thank you, son. >> Yeah, I guess that was also a question. I I believe uh you would create that call for input, Sam. >> Uh, anybody can make it. Um, >> okay. >> But that has to be done on EIP GitHub repository. Is that correct?

>> Yeah, exactly. So >> maybe we can let him know the repo correct repo to make that. >> So um you can create an issue on here and there is a template for call for input. Um you can fill it out and uh it should be pretty self-explanatory. yeah. >> got it. Yeah, I'll do that one um this evening. Thank you. [snorts] Okay, change since last review.

Sam, if you got any questions on these um two changes that you can see here, just um ask away. We'll do. Thank you. Okay, so I [music] think we're good. Okay. Yeah, I think this looks good. Um,

>> cool. >> Sounds good. We have next 1606 which is again by Cyber Centry. Maybe we can jump on that and um answer open questions. It was already reviewed by you I [music] guess last week. Yeah, I doubt there's anything that needs to change on this. It's [snorts] I think my other objection was probably the same. Anyways, let's give it a read.

everybody Easter operations is defined in [music] 437. Okay. 712 is that there? Yeah. Okay, cool.

>> So, I have uh a note here. I noticed uh this EIP consists of 8004 in um required section. So my understanding is this proposal may not go beyond draft unless 8004. Yes. So yeah dear author please take a note of that. If you want to proceed this proposal forward you might have to work with the authors of 8004 as well >> book. Next we are joined by author for PR1609 David.

Nice. Okay. Sandbox smart wallet. Sandbox smart wallet. Okay. So I think we can Uh automation for agents and wallet is

an industry path. Okay. and many pressures. Through agents in a wallet is an industry path.

There's something weird about that, but I can't put my finger on what. Um, spend and then um including session keys base policy and trusted execution environment based policy [clears throat] engine engines engine anyway shared account key exist.

Okay. The state owns a smart wallet specifically for agents of high frequency trading entities to operate in a completely sandbox to detached environment while still enabling the owner to have granted control over the sandbox smart wallet. Automation through an agent

infrastructure as a wallet is an inevitable flow of the industry. Other agents bring in a highly autonomous system with convenience. It is important that these adoptions should incorporate security mechanisms together. Session key like architecture. Although having the advantage of shared owner wallet has limitations on the security of postures unless imposed with an enforced wireless mechanism that limits the access of the session key. T-based policy engine although comes

with A shared account key can despite most intuitive and convenient solution gives a limited access to the wallet unless the user explicitly approves its operation. Um, this proves an interface for agents that operates in a sandbox attached environment from the owner account.

Well, the owner. Okay. Complete sandbox account for agents. separates it execution by agent account that the possibility of security future hallucination of AI agents from impacting the owner account unintended key graded permission driven shows the owner while inherently brings in permission evasion issues unless imposing weight list driven approach the sandbox approach makes the standard free

for these concerns free [snorts] concerns owner account persist consistently having access to sandbox wallet. This the relationship between owner account and sandbox wallet is one directional. The owner account has permission to withdraw the sandbox account. let's include the following interface.

So, let's go up here. Let's go here. This Ally Actually, there is a [music]

function to see if the agent is active with the key. But yeah, it may be a good idea to actually have uh a [music] strct >> uh return with the key. It's actually in uh similar to like diamonds like having the fastest function that returns the whole uh diamond mapping. >> Okay. Yeah, that makes sense. >> Usually for like offchain usage. >> Yeah. Yeah, that makes sense. It It's definitely not required. Okay. 65 Wait a minute.

165. A checker card must implement the following interface. Pre check. So 73 here. We got

there. Sorry, that's supposed to be review. So 173 23 Free Pretty

173. cool. Where are we up to next, Puja? >> Um, I I know there are more PRs, but there was a comment by an author if if you would want to maybe take it now or address later for PR1330 on EIP GitHub repository. So this is going to draft

some sub two and five. Okay. [gasps] So what we will do Match verification compatibility was

preferred. So, Is there a way to link specifically to

this? There is. Perfect. >> [sighs] >> Yeah, I think this is an effective way of letting them know what's the next step is. Cool. Back to going through some review.

>> So, we don't have too much time. If you would want to maybe go through some type of miscellaneous, we can cover that. >> Sure. Definitely. law hash. Okay, so this requires a review by an author. so test cases assume calling get blob gas price header as defined in gas accounting and the current blocks header returns seven away blob base fee should

push the value seven on the stack. So that means this should be blob base fee. So 4 a is blob base fee. Yeah. So that looks good. And I guess let's go here. Now I'm going to check that gas equals 2.

I hate reading these tests. Um, yeah, there's not going to be anything in here that tells me what the actual op code is, of course. So if we go to test tools okay so we go here and then we need to

find so that's dot VM op code. It's a 4A. Yeah. Okay. So, I'm reasonably confident that that is correct. Don't need that. Don't need that. This one. And how long has this been open for? [gasps and sighs] Several months. Uh I don't really like force merging these but okay

moving on to the next one at final and living to draft stage. >> I mean there are these next two are associated with call for input. It's up to you if you want to take it now or maybe later. It's totally fine. >> Yeah. The other one as well, so we [music] can skip. Yeah, this is cool. [laughter] Wait, is this a draft or is this a >> Yeah.

>> Yeah, this is fine. Okay. Fix spelling errors in documentation. Dex ran but didn't approve it. Actual implementation tokens may explicit. Yeah, those are definitely typos.

Tonight. Yep. Okay.

I guess I can just approve this. I don't need to force merge. Yeah. Then I think anything else is going to be uh too long to get into. All right. Cool. Well, thanks everybody for coming up. Oh, sorry. >> Sorry. Uh, for the remaining five minutes, Sam, would it be okay if you could have another look into the send box smart wallet PR? I actually quickly resolved all the uh comments that you had. Thank you.

Oh yeah, I'll also update then. I can take care of those. Um Awesome.

>> Yeah. Thanks for the review. >> No, no problem. Take care. >> Thank you, Sam. And dear audience, we will be back next week with another set of office hour for you [music] and we'll be joined by editor Yam. Thank you everyone for joining us yet today. >> [music] What's up?