EIP Editing Office Hour #45

Transcript

welcome to EIP editing office hour meeting 45 this is issue number 360 on agenda we have one proposal moving towards final a bunch of PRS for review and few miscellaneous along with the draft proposals thank you Sam for joining us here uh perhaps we can start with the final proposal and in the meantime if anyone has has any PR specific PR they would want you to review um they can just ping the number on chat sounds good all right so what are we looking at

here today okay yeah I think we've seen this one um let's take a look at the discussions thread anything new and exciting going on probably not yeah okay I think we're good uh so the verifi generated contactable token standard extension GC

[Music] great verif model toate unart good okay implement the RC yep okay to

interface okay y I don't think this has changed at all since the last time I looked at it which is perfect and specification hello hello hello test cases perfect good what changed on this sline nothing all

right good to go all right so uh um are you guys looking for any particular uh P requests to be reviewed do you have any questions about the EIP process okay so it seems that take has a PR uh take if you could share the pr number we can perhaps review that one or anyone else if you have any particular PR please share it or drop your questions we'll be happy to take it yep in the meantime we can perhaps move towards the review proposal sure so 6734 so this is moving into

[Music] review [Music] um okay all right yeah this one I looked at before I'm pretty sure it was just removing 3220 okay I'll get this a good a good read though all right L2 token list token list ensures the correct identification of tokens

from different out layer L1 L2 or side chains all right describes Jason token okay work okay okay yeah so I think this will be fine

specification section is probably good uh rationale okay [Music] LD okay yeah that's fine I just have to force merge this one all right so 8454 did you have any particular questions about this one or you just

want somebody to take a look at it this is yeah so this is take one here uh we're trying to write this uh uh EIP it's our first time doing it uh so definitely help would be would be uh very much appreciated uh at this moment uh we are told that uh uh because the EIP design includes some form of a a pattern that uh was actually fought originally by my company uh we actually have to wave off everything before we can proceed with even the uh con before the EIP is even considered uh while my understanding was that uh you know we are prepared to you know have certain

wavers once the EIP is about to be you know published or so uh but not so early in the process so so we're hoping to understand where the where they go come here um so I am not a lawyer um all I can say from like the perspective of the eips process is that um we have an included patented information as far as we're aware in the repository before um and I'm very hesitant to include it um without some kind of a license or waiver um at all so as soon as we merg this pull request it will appear on the E's website um

so that's kind of like an endorsement from you know the EIP editors that you know it's starting the process and that it's it's good to go um and I'm just not comfortable giving that kind of um approval without you know some assurance that people who implement the standard aren't going to get sued for patent infringement I understand um I mean if we if we give some if if we have to say that uh uh if if you implement it according to the eventual standard uh and and it's not for commercial purposes uh we can wave that Grant would would that be something that's acceptable

um I think we'll have to start like a longer more formal discussion about this um like we have a process called call for inputs and um I I I I think even with a not for commercial purposes restriction might be too much of a restriction um because obviously a lot of people who are building on um ethereum do so for commercial purposes like um Bess and teu the consensus clients are um like they they are providing Commercial Services along with those clients and I I wouldn't want that to be a problem for you know consensus and

yeah um so so how so maybe I turned the question the other way around I mean when people submit an EIP um maybe they were infringing on someone else else's design that they never knew about and this got into the process how how do you then resolve something like this um we it hasn't come up before um and if it does then um we'll figure out how to deal with it at the time uh but yeah it's uh it's definitely difficult we we've tried to uh we made a few attempts to get like a a patent waiver um into the into the process um

but like I said none of us are lawyer lawyers we're all technical people so we're very hesitant to even like wait into that area without some legal support I see yeah um so yeah I guess if you don't want to make a waiver ahead of time we can start What's called the call for input we can get input from all of the editors uh and have a formal decision on it if you'd like I can start that today um yes if if you could that would be help yeah four all right so I'll um I'll get started on that after the

call um sorry I can't be of more more help here it it's it's a it's already an amazing progress for us because we've been trying to BU we been hitting walls every quo so this is great happy to help um so what we off to next I guess on to the next review yep perfect 6909 single contract all right uh the following specif is multi token contract just a simplified

alternative to ERC 1155 multi token standard in contrastc 1155 callback batching remove the interface the permission system is a hybrid operator approval scheme okay minimum requ okay uh bat calls in the specification okay requir for each transfer and B transfer to Contra accounts transfer from transfer by useful okay

H all right okay okay is operator transfer okay prove set operator this all looks good uh let's go down to their rationale section well the

oper Okay this not always okay yeah this is explaining stuff perfect while batching operations is useful should the c um okay good not Backward Compatible we have a reference implementation perfect okay and then we have copyright awesome so that can move in review 7417

okay smart contract Service okay the multi token on the CH early the CP introduc the concept of cross chain state of operability by creating a service to upgraded to RC 223 tokens time the conversion must deposit tokens one standard to the converter contract okay cool that's easy okay convert a contract must accept deposits

ofce okay yep that makes sense this is all good standardization so raer contracto the create two upod addresser okay so creates newc 23 rapper for a given rc20 token it does not exist reverts if it already exists Returns the address of the new raer okay tooy cont standard Pro transfer functions okay verify okay

from the transaction [Music] sender okay Okay C tokens

Okay so [Music]

pater for all

right okay so 747 and then trans transparent financial statements okay okay 776 so let's go take a look at this okay that it's not done I love when people do that all right AP for to ensure open

transparent financial data for all investors so um um um so

uh okay okay good so let's take this API that enables evm based blockchain companies protocols to publish their financial specific onch transparent smart

contracts um so yeah okay that enm uh soal protocols to fincial information

specifically income statements and bishes on chain and transparent access through smart contracts the model used by Trad companies in traditional stock markets like the SEC uh Q10 filings the financial statements include key information Revenue cost for good sell operting okay ear before interest ands per okay cool okay the modification this bring

seriousness to the crypto um kind of odd capitalization here Market uh most2 tokens repr

represents [Music] okay functions commodi such as consent to be SP the platform they publicly tra and advertise share working practice without any public Okay add that most token research analytics reports can currently found on the internet oral substack or Twitter posts okay the CIP will improve that giving users investors transparent clear and factual financial information to okay um for

okay okay % us shares and the financial numberb is displayed in this um Financial numbers just um that's a little unclear uh all transparent financial statements

must Implement rc20 is optional metadata extension y the name and simple function okay meth visibility public uh let return the St must be less or equal

to end time Stand start time stamp it's less than time stamp okayu turn struct okay

St total earnings from selling products and services cost of goods sold okay Returns the address of the individual State re is True Value the publicly displ for okay that makes sense F am I reading this wrong uh we saw that earlier which one had that was this one it's probably this one um yeah so name has yeah um

um okay uh total rin a time period okay number of goods sold then okay operating expenses operating income sure

B okay returns net income for the period oper income P okay for share okay so P consider so because find Theo choices

me for okay uh you see is enfor implementation okay income

statement yeah okay back comp okay um right okay

um code proposal itself must be cc-10 um to this and move it to sets directory link to it here all right security

[Music] [Music] considerations okay otherwise yeah cool comment so that was 659 so next we have a bunch of proposals which are related to 7702 it seems like many people are making PR I'm just wondering how to manage that because if you merge one's PR the other PR would be you know uh creating conflict and things like that so if you would like to maybe take a look at it yeah yeah um these are mostly

up to Matt I don't really um follow 7702 anymore um so how however he wants to do these is how how they can get merged perfect then I can check with him yeah I think I try to put it in in order and following comments like okay if he's fine with merging kind of thing but yeah I can take it him okay thank you uh 7600 72 still describ is for one transaction not some the other summaries okay so this seems like very simple one and I checked 7600 it still says uh last few

words yeah okay so this is up to Tim to merge when um he gets the chance I guess okay um yeah okay salana storage cool so the following standard extension to the Cross chain Storage R protocol introducing Storage R for salana yep okay and what's going on here ah yes okayed

reading okay okay cool let's go give this a read all right Sal star cross chain storage protocol incorporating storage okay cool good require 7700 the following St is an extension to the Cross chain storage protocol introducing the storage rou for Sal blockchain with this specification can defer contract blockchain core functionality provided that the client is equipped to handle Sal of transactions uh

3668 okay so need eight uh comp format by an appropriate HP Gateway where can retrieve generic contracts okay cool uh question describes three EXN forting Storage storage targeting Sal storage provider uh L2 databas both have centralized and Catal stack good yeah that's fine SL is a low cost L1 solution that is supported alongside ethereum by multiple wallet providers or sub agnostic protocols on

eums okay good let's look at images schema SVG uh yeah that's fine okay stor additional okay okay wait how does this workt handling okay son storage RoR requires that the hex encoded program ID the manager account block program ID

okay set value get metad from onchain sources so you call get metadata and you get back program ID and account Road storage call okay I see since naely uses okay the account using B 5 okay example must be converted to key okay fine yep okay that's

fine um okay in order to read crushing data St they must be transl back evm tongue by the okay what is 3668 e 3668 ccip secure yeah okay yeah contracts must include sufficient information the yeah that's what I thought okay okay okay what is just the program

interface on salana call the salana program to read the cross chain data compile yeah above example gener value up the form okay yeah so this is fine why are there fonts um yeah um huh that's really

weird um making it more fancy yeah um what this

so this is U unrelated the license is unrelated to the font it is related to the redistribution of the file exactly yeah okay okay cool um okay and then going to go and comment on here okay

so 3 three yeah 3668 3668 uh security cons okay so let me see 3668 Gateway response data validation um sh this

proposal uh what is this 7694 7694 [Music] cud method standard approach for doing data validation against I cool all right so there's that and now

we can go and take a look at Central can we do 660 I think the author is right here that this sure 660 thanks sure uh do you have any specific questions hey Hi Sam yeah thanks a lot um so yeah actually it's the first time we are submitting an ERC so um we just love to hear and I think the topic is a little bit unconventional so I just hope to um hear your first reactions and thoughts on this proposal please thanks congratulations on getting a very nice number by the way yeah yeah I'm very happy about that too um governance for human robot societies so uh let's

see uh we can get rid of a little bit of this um just say like find interfaces for managing yeah 7 says for their interaction yeah okay that that's great uh we can just make a little shorter okay uh open mind uh yep okay that all looks good so this proposal defines two core interfaces so for um when you mention code um just always put it in back dicks um right yeah I'll do it for this section but just make the change everywhere sure sure um nope no worries okay so this proposal defines two core

interfaces Universal Universal to establish and to create centralized communities governed by specific rule sets the universal inter identity interface establishes a fair and Equitable treatment of sensory computer architectures other than the human brain enabling robots to acquire onchain identities and thereby interact and transact with humans the I Universal Charter enables humans and robots to create join and maintain to leave and then terminate self regulated societies based on predefined real Prov a framework for collaboration and prosperity for mixed societies of humans and robots these interfaces aim to provide a flexibility and enforceable structure for human robot interactions and decentralized systems yeah it's a good abstract um yeah that seems good

um so why why robots and not like uh artificial intelligences like the word choice I mean yeah yeah that's a very good question we had an internal discussion about it as well so um we we decided to go with robot because we we think in capap is two idea the soft part about essentially AI agents and then the the hardware part about actual robots possibly interacting with humans so so hence that makes sense cool uh point birth

time not clear which will set them system okay change okay computer okay two fold one Rob creation okay all right so uh yeah you you've you've set up

uh a very lofty goal I think in your abstract in your motivation um let's let's see how this works in uh in uh [Music] R okay so how Okay okay so um yes

okay so um is it all of it or just most it's all of it okay so yeah yeah I think we also have a reference implementation that um maybe can make it a little bit more clear yeah yeah I'll I'll get down there in a sec um should be um

beavor for okay yes there just a a little bit of

like uh formatting here so um all of this stuff is explaining like why thing or sorry all of the stuff is explaining like how something works um so it should be up in in here yeah so um and then that explain like choices so another thing um yeah so no worries um for okay move Ru

so R right representing the rule damic B yeah okay complies with the specific rule must yep verification okay when the charter subscrib to subscribe for Charter okay so the these events are um it's not defined what generates these events it's just when a charter is subscribed to you must admit the event right okay that makes sense uh R

set okay say human delete the system okay syst rules okay termin contract okay good let we go down here test cases so okay reference implementation

okay so interfaces y okay okay aable sure okay [Music]

okay yeah so I think you're like almost ready for draft just a few small changes here and then you can get it in um great yeah so um just to be clear more about the EIP process um we don't really provide technical review we only provide like uh editorial review of the document and stuff so um once you go into the review St status it's it's kind of up to you to go and find people who would be Implement interested in implementing your standard and getting their feedback on it yeah so um yeah it that's awesome yeah it seems like a really interesting idea um I'm interested to see where it goes um I have to disappear for another call so I

will see you all oh no problem see you thank thank you Sam thank you and sorry but just a we just have a quick question can I uh as you as well so essentially we just posted uh this CRC proposal in the in the mtion Forum as well and we love to get more people involved just wondering if you have any sort of suggestions on um how to do that better yeah generally speaking when we add a proposal in FM page they get some attention and you may get some reviews however when a proposal moves to review status or a little bit closer to last call we also invite author to share sh about their proposal on Peep and EP so

they can uh create more awareness about the proposal and we expect some implementation as well sure sure yeah that's that's awesome thank so much thank you thank you all for joining us here today hope to see you in two weeks