{"id":"HqsmiDhdysw","title":"NEP-655: Universal Accounts and a Quantum-Safe Path for NEAR","description":"The NEAR Protocol Working Group met to discuss and vote on NEP-655, a proposal for universal accounts.\n\nNEAR currently has two ways to create an account without a named registration. Implicit accounts come from an ED25519 key, and deterministic accounts come from initial code and data. Neither one gives you a quantum-safe option from day one.\n\nUniversal accounts would bring both systems under one model. An account’s ID would derive from its initial state, and that state can include code, data, and access keys. That last piece lets an account start life with the key setup it needs, quantum-safe keys included.\n\nWatch the full discussion to hear how the working group weighed the proposal and where the vote landed.","channel_name":"NEAR DevHub","published_at":"2026-11-03T00:00:00.000Z","thumbnail_url":"https://img.youtube.com/vi/HqsmiDhdysw/hqdefault.jpg","transcript_text":"Perfect. And let me just share this. No, sorry. Share. No slideshow. Are you Can you see my slideshow? Yeah. Is it okay? Perfect. Then it's been sharing. Okay. Then welcome everyone to another protocol work uh group call uh where today we're going to be discussing and voting for NEP 655 universal accounts. Uh this was created by Adam but sadly enough he could not make it to the call. So I'm going to be presenting on uh his side. So until universal account, universal accounts, we had basically implicit accounts that were able to were derived from uh uh ED25519 key and deterministic accounts which were derived deterministically from an initial state which was code and data but no keys. So there was no way to deterministically derive an account that is quantum safe from the get-go. Uh now in NEP655 we can we get kind of bu best of uh both worlds which is like we get accounts that are derived from an initial state which includes code data and access keys and this is a new type of account so everything keeps working there's no need to migrate anything and it's going to be stabilized at protocol version 88 which I think is coming out pretty soon now universe Personal accounts uh are uh are identified by a 0 plus 54 characters which are the base of the um h the encoding of the state in it byes and this state in it is composed by code which can be an optional reference to a global contract. It has to be a global contract. Uh data which is the storage entries that are going to be right on the initialization of this uh account and access keys which are full access keys only. This is important to be said and they can be uh postquantum keys MLDDSA 65 keys since they are like store as 32 by hashes. So it just cost us the same as classical keys. You can add any type of key if I remember correctly. But the important part is that you can actually derive a key with quantum and uh the populated fields actually decide the kind of account that you're creating because it can be an account with only keys or with contracts or both. Uh so in order to create uh one of these new universal accounts what you have to do is you build a state in it and hash it into the ID. You don't need to have a chain access for this. Then you make a transfer to the ID to create the account and initialize and then you perform a new action into the blockchain which is universal sitting in it uh which will install the code data and keys and until you do that actually all of the other actions that you try to do with the account will just fail with account.initialize. uh and if you try to uh repeat the universal state in it on an initialized account, it's just a no operation and the deposit is refunded to the to the user. So there were some key technical decisions made uh for universal accounts. Um uh the first one is that the populated fields decide what account is and like right now there's like one version of state in it but there might be version two uh instead of changing version one. Uh the account starts uninitialized. So it it is inert until uh there is a universal state in it action and then there's no address. So a mistype ID is still a valid ID and it's up to the wallets and not the protocol to to to check them. Uh in order to implement this there were like a couple of operational impacts. uh to start uh RPC indexers and extrollers must tell uninitialized uh apart from non-existing uninitialized accounts uh wallets and they need to handle the the state in it and there's a limit per receipt of 1,024 access keys so yeah and the creator pays the gas never the new account and well specifically Rosetta RPCs emits no operation when you try to do this universal state in it. So Ross database observers do not see account uh creation and that's the introduction of the NEP. Now we do have here uh Mate who was one of the subject matter experts reviewing. Uh so could you give us you know like what you think about it benefits if you have any doubts of it and you approve it so I guess just say that like why you approve it. Yeah. Well uh I did approve it already. It's in the it's on the GitHub issue right sorry on the on the PR. But uh I think this is great because it was there was a mess in all these implicit accounts and uh and uh the state in it and it accounts and the key being encoded inside the account ID and so on and uh we wanted to unify all this at the same time as providing some general way of creating these implicit accounts that also support postquantum uh keys which was which was one of the one of the main uh reasons why I even started working on this and yes and so I think the others still work it's it's something new nothing breaks but uh it's a it's a more general way of creating implicit accounts that allows you to use code you can identify an account account by a code and I don't know whether it makes sense to go into all these technical decisions and technical details that that you also skimmed over. Uh whoever wants to look at those discussions that we had, they they can look at GitHub. But uh it it just enables to create post quantum implicit accounts which is a big benefit and it subsumes all the other implicit style accounts that we had. Yeah, perfect. Yeah. Yeah. And I actually I completely agree. If anyone wants to actually go and see what the NP is saying, please go and read it. Uh so yeah, perfect. Uh we have here two members of the work group. Uh Michael, uh I always name you first. I don't know why, but you're like, so what's your opinion and what's your voting status for this NP? So, I left a comment on on the poll request as well on on GitHub, but I'll I'll reiterate it here that uh I I do think we should approve this this NEP. I I agree with Mate. It's it's very nice to see sort of unifying all of the previously disperate things that we had going on for implicit counts. Um the only concern that I had um which is which is not blocking at all is there's a sort of technical detail in the NEP about forward compatibility where the idea is that at the protocol level the actual state inites are sort of totally opaque. There's no um there's no assumed structure to them. um the the structure sort of gets introduced in the state the way the state in an action gets processed and there's also a host function that will interpret it as well and we think all that's fine we think all that's good um it's nice to to be thinking about this forward compatibility thing but there's a line about this being good for contracts because they don't have to be aware of future potential other ways of structuring these bites if we do introduce a v2 on the uh state in state init data for example but I don't based on my understanding of it I don't know if that's true because part of the point of these uh deterministically derived account ids is that the contract is only interacting with specific addresses that it understands right that it knows is following its own protocol right the whole the whole point was enabling sharded contracts Um, so like in a sharded wallet for example, it should only receive tokens from other instances of the same sharded wallet protocol that it's following. And the only way it can check that is by looking at the state in it. So it needs to be able to decode the state in it to to check it itself. Um, again, I think that's sort of like a non-issue for the MEP itself. I I do like the the the design and everything, but there was just, you know, some phrasing in in the in the description that I wanted some clarification on, but otherwise, yeah, looks looks good and I'm happy to take that discussion offline as well. Um, again, not blocking for for voting purposes. Perfect. Thank you so much, Anton. Anything you want to add and your uh vote? Um, I just dropped my approval on the GitHub pull requests as well and uh I I mean I agree with Michael. So I think the as it as far as it applies to shorted contracts, you're right that there's this future thing is not really too relevant. But the cool thing about these is that it doesn't have to be an a shorted contract to be usable. It actually it applies in other places as well where I think this this becomes slightly different issue overall. Um, I've been already for quite some time not too happy about the fact that regular new accounts have a very good and strict separation of identity, authorization and behavior. I mean identity is like your new account. Authorization is whatever access keys that you can retake. They're not tied to identity and then behavior being when you create your account there's like some default behavior but then you can deploy contract, remove contract, you can do whatever. So like all of these thing three things were completely decoupled. But for implicit accounts, east uh accounts or implicit accounts, that was not the case. The behavior was hard-coded for east accounts. The identity and authorization were all tightly coupled for implicit accounts. And this is kind of the step in the right direction to truly decouple all three of these and like give you ultimate flexibility when you initialize with whatever you like. You want to be define a different behavior. You go ahead and and define your own global contract and you use that. you want to define something else, it's up to you. So yeah, this is like this is an ultimate thing and hopefully it is indeed the last time we need to introduce any new account ID and it will be just just the ultimate replacement. Okay, perfect. Thank you so much. Uh also thank you to Adam that was not here but you know he championed the whole NP so that's great. We always thank them. Mate, I see that you raised your hand. Please go ahead. Yeah, maybe just one one note for people to understand uh which is crucial that the the ID is derived from the initial state of the account, but nothing forces anybody to keep the same contract or keep the same data. It just what it's initialized with and then all of it can change, right? That this is this is goes sort of what what Anton was saying. Yeah, thank you so much for for for adding that. And when I was seeing it personally as someone that is part of the of the community, uh I never really got deterministic accounts, but universal accounts they like you immediately understand why they're important and how much it can be used. So I'm very happy that they add this and I do resonate with what you say, Anton. I really hope this the last time that we have to add an an account type. Okay, so we have the approval from everyone. Uh, thank you so much everyone and this nap is by all intended purposes approved and see you in the next one I guess. Bye everyone. Thanks. Bye. Bye. Bye.","transcript_synced_at":"2026-11-04T03:45:58.932Z","segments":[{"start_seconds":2,"text":"Perfect. And let me just share this. No, sorry. Share. No slideshow.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=2s"},{"start_seconds":11,"text":"Are you Can you see my slideshow? Yeah.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=11s"},{"start_seconds":16,"text":"Is it okay? Perfect. Then it's been sharing. Okay. Then welcome everyone to another protocol work uh group call uh","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=16s"},{"start_seconds":24,"text":"where today we're going to be discussing and voting for NEP 655 universal accounts. Uh this was created by Adam","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=24s"},{"start_seconds":32,"text":"but sadly enough he could not make it to the call. So I'm going to be presenting on uh his side.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=32s"},{"start_seconds":39,"text":"So until universal account, universal accounts, we had basically implicit accounts that were able to were derived","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=39s"},{"start_seconds":48,"text":"from uh uh ED25519 key and deterministic accounts which were derived deterministically from an","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=48s"},{"start_seconds":55,"text":"initial state which was code and data but no keys. So there was no way to deterministically derive an account that","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=55s"},{"start_seconds":64,"text":"is quantum safe from the get-go. Uh now in NEP655 we can we get kind of bu best of uh both","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=64s"},{"start_seconds":74,"text":"worlds which is like we get accounts that are derived from an initial state which includes code data and access keys","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=74s"},{"start_seconds":82,"text":"and this is a new type of account so everything keeps working there's no need to migrate anything and it's going to be","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=82s"},{"start_seconds":90,"text":"stabilized at protocol version 88 which I think is coming out pretty soon now universe Personal accounts uh are uh are","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=90s"},{"start_seconds":100,"text":"identified by a 0 plus 54 characters which are the base of the um h the","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=100s"},{"start_seconds":108,"text":"encoding of the state in it byes and this state in it is composed by code which can be an optional reference to a","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=108s"},{"start_seconds":117,"text":"global contract. It has to be a global contract. Uh data which is the storage entries that are going to be right on the initialization of this uh account","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=117s"},{"start_seconds":126,"text":"and access keys which are full access keys only. This is important to be said and they can be uh postquantum keys","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=126s"},{"start_seconds":134,"text":"MLDDSA 65 keys since they are like store as 32 by hashes. So it just cost us the","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=134s"},{"start_seconds":142,"text":"same as classical keys. You can add any type of key if I remember correctly. But the important part is that you can actually derive a key with quantum and","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=142s"},{"start_seconds":151,"text":"uh the populated fields actually decide the kind of account that you're creating because it can be an account with only","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=151s"},{"start_seconds":157,"text":"keys or with contracts or both. Uh so in order to create uh one of these","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=157s"},{"start_seconds":164,"text":"new universal accounts what you have to do is you build a state in it and hash it into the ID. You don't need to have a chain access for this.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=164s"},{"start_seconds":175,"text":"Then you make a transfer to the ID to create the account and initialize and then you perform a new action into","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=175s"},{"start_seconds":183,"text":"the blockchain which is universal sitting in it uh which will install the code data and keys and until you do that actually all of the other actions that","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=183s"},{"start_seconds":192,"text":"you try to do with the account will just fail with account.initialize.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=192s"},{"start_seconds":197,"text":"uh and if you try to uh repeat the universal state in it on an initialized account, it's just a no operation and the deposit is refunded to the to the user.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=197s"},{"start_seconds":208,"text":"So there were some key technical decisions made uh for universal accounts. Um uh the first one is that","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=208s"},{"start_seconds":215,"text":"the populated fields decide what account is and like right now there's like one version of state in it but there might","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=215s"},{"start_seconds":223,"text":"be version two uh instead of changing version one. Uh the account starts uninitialized.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=223s"},{"start_seconds":231,"text":"So it it is inert until uh there is a universal state in it action and then","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=231s"},{"start_seconds":238,"text":"there's no address. So a mistype ID is still a valid ID and it's up to the wallets and not the protocol to to to check them.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=238s"},{"start_seconds":249,"text":"Uh in order to implement this there were like a couple of operational impacts. uh to start uh RPC indexers and extrollers","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=249s"},{"start_seconds":257,"text":"must tell uninitialized uh apart from non-existing uninitialized accounts uh wallets and","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=257s"},{"start_seconds":266,"text":"they need to handle the the state in it and there's a limit per receipt of 1,024","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=266s"},{"start_seconds":274,"text":"access keys so yeah and the creator pays the gas never the new account and well specifically Rosetta RPCs emits no","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=274s"},{"start_seconds":283,"text":"operation when you try to do this universal state in it. So Ross database observers do not see account uh creation and that's the introduction of the NEP.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=283s"},{"start_seconds":296,"text":"Now we do have here uh Mate who was one of the subject matter experts reviewing.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=296s"},{"start_seconds":304,"text":"Uh so could you give us you know like what you think about it benefits if you have any doubts of it and you approve it","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=304s"},{"start_seconds":313,"text":"so I guess just say that like why you approve it. Yeah. Well uh I did approve it already.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=313s"},{"start_seconds":322,"text":"It's in the it's on the GitHub issue right sorry on the on the PR. But uh I think this is great because it was there","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=322s"},{"start_seconds":331,"text":"was a mess in all these implicit accounts and uh and uh the state in it","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=331s"},{"start_seconds":339,"text":"and it accounts and the key being encoded inside the account ID and so on and uh we wanted to","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=339s"},{"start_seconds":348,"text":"unify all this at the same time as providing some general way of creating these implicit","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=348s"},{"start_seconds":357,"text":"accounts that also support postquantum uh keys which was which was one of the one of the main uh reasons why I even","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=357s"},{"start_seconds":365,"text":"started working on this and yes and so I think the others still work it's it's something new nothing","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=365s"},{"start_seconds":374,"text":"breaks but uh it's a it's a more general way of creating implicit accounts that allows you to use code you can identify","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=374s"},{"start_seconds":383,"text":"an account account by a code and I don't know whether it makes sense to go into all these technical decisions and","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=383s"},{"start_seconds":391,"text":"technical details that that you also skimmed over. Uh whoever wants to look at those discussions that we had, they they can look at GitHub.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=391s"},{"start_seconds":402,"text":"But uh it it just enables to create post quantum implicit accounts which is","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=402s"},{"start_seconds":409,"text":"a big benefit and it subsumes all the other implicit style accounts that we had.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=409s"},{"start_seconds":415,"text":"Yeah, perfect. Yeah. Yeah. And I actually I completely agree. If anyone wants to actually go and see what the NP is saying, please go and read it. Uh so","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=415s"},{"start_seconds":424,"text":"yeah, perfect. Uh we have here two members of the work group. Uh Michael,","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=424s"},{"start_seconds":431,"text":"uh I always name you first. I don't know why, but you're like, so what's your opinion and what's your voting status for this NP?","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=431s"},{"start_seconds":440,"text":"So, I left a comment on on the poll request as well on on GitHub, but I'll I'll reiterate it here that uh I I do","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=440s"},{"start_seconds":447,"text":"think we should approve this this NEP. I I agree with Mate. It's it's very nice to see sort of unifying all of the","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=447s"},{"start_seconds":454,"text":"previously disperate things that we had going on for implicit counts. Um the only concern that I had um which is","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=454s"},{"start_seconds":462,"text":"which is not blocking at all is there's a sort of technical detail in the NEP about forward compatibility where the","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=462s"},{"start_seconds":469,"text":"idea is that at the protocol level the actual state inites are sort of totally","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=469s"},{"start_seconds":476,"text":"opaque. There's no um there's no assumed structure to them. um the the structure","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=476s"},{"start_seconds":483,"text":"sort of gets introduced in the state the way the state in an action gets processed and there's also a host function that will interpret it as well","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=483s"},{"start_seconds":492,"text":"and we think all that's fine we think all that's good um it's nice to to be thinking about this forward compatibility thing but there's a line","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=492s"},{"start_seconds":500,"text":"about this being good for contracts because they don't have to be aware of future potential other ways of","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=500s"},{"start_seconds":509,"text":"structuring these bites if we do introduce a v2 on the uh state in state","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=509s"},{"start_seconds":515,"text":"init data for example but I don't based on my understanding of it I don't know if that's true because part of the point","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=515s"},{"start_seconds":524,"text":"of these uh deterministically derived account ids is that the contract is only","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=524s"},{"start_seconds":532,"text":"interacting with specific addresses that it understands right that it knows is following its own protocol right the whole the whole point was enabling sharded contracts","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=532s"},{"start_seconds":540,"text":"Um, so like in a sharded wallet for example, it should only receive tokens from other instances of the same sharded","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=540s"},{"start_seconds":549,"text":"wallet protocol that it's following. And the only way it can check that is by looking at the state in it. So it needs to be able to decode the state in it to","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=549s"},{"start_seconds":556,"text":"to check it itself. Um, again, I think that's sort of like a non-issue for the MEP itself. I I do","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=556s"},{"start_seconds":564,"text":"like the the the design and everything, but there was just, you know, some phrasing in in the in the description that I wanted some clarification on, but otherwise, yeah, looks looks good and","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=564s"},{"start_seconds":572,"text":"I'm happy to take that discussion offline as well. Um, again, not blocking for for voting purposes. Perfect. Thank you so much, Anton.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=572s"},{"start_seconds":582,"text":"Anything you want to add and your uh vote? Um, I just dropped my approval on the GitHub pull requests as well and uh","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=582s"},{"start_seconds":590,"text":"I I mean I agree with Michael. So I think the as it as far as it applies to shorted contracts, you're right that","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=590s"},{"start_seconds":597,"text":"there's this future thing is not really too relevant. But the cool thing about these is that it doesn't have to be an a","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=597s"},{"start_seconds":606,"text":"shorted contract to be usable. It actually it applies in other places as well where I think this this becomes slightly different issue overall. Um,","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=606s"},{"start_seconds":615,"text":"I've been already for quite some time not too happy about the fact that regular new accounts have a very good","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=615s"},{"start_seconds":623,"text":"and strict separation of identity, authorization and behavior. I mean identity is like your new account.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=623s"},{"start_seconds":629,"text":"Authorization is whatever access keys that you can retake. They're not tied to identity and then behavior being when you create your account there's like some default behavior but then you can","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=629s"},{"start_seconds":637,"text":"deploy contract, remove contract, you can do whatever. So like all of these thing three things were completely decoupled. But for implicit accounts,","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=637s"},{"start_seconds":645,"text":"east uh accounts or implicit accounts, that was not the case. The behavior was hard-coded for east accounts. The","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=645s"},{"start_seconds":653,"text":"identity and authorization were all tightly coupled for implicit accounts.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=653s"},{"start_seconds":656,"text":"And this is kind of the step in the right direction to truly decouple all three of these and like give you ultimate flexibility when you initialize","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=656s"},{"start_seconds":664,"text":"with whatever you like. You want to be define a different behavior. You go ahead and and define your own global contract and you use that. you want to define something else, it's up to you.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=664s"},{"start_seconds":676,"text":"So yeah, this is like this is an ultimate thing and hopefully it is indeed the last time we need to introduce any new account ID and it will be just just the ultimate replacement.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=676s"},{"start_seconds":690,"text":"Okay, perfect. Thank you so much. Uh also thank you to Adam that was not here but you know he championed the whole NP so that's great. We always thank them.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=690s"},{"start_seconds":701,"text":"Mate, I see that you raised your hand. Please go ahead.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=701s"},{"start_seconds":703,"text":"Yeah, maybe just one one note for people to understand uh which is crucial that the the ID is derived from the initial","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=703s"},{"start_seconds":711,"text":"state of the account, but nothing forces anybody to keep the same contract or keep the same data. It just what it's initialized with and then all of it can","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=711s"},{"start_seconds":720,"text":"change, right? That this is this is goes sort of what what Anton was saying.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=720s"},{"start_seconds":725,"text":"Yeah, thank you so much for for for adding that. And when I was seeing it personally as someone that is part of","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=725s"},{"start_seconds":732,"text":"the of the community, uh I never really got deterministic accounts, but universal accounts they like you","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=732s"},{"start_seconds":740,"text":"immediately understand why they're important and how much it can be used.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=740s"},{"start_seconds":744,"text":"So I'm very happy that they add this and I do resonate with what you say, Anton.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=744s"},{"start_seconds":748,"text":"I really hope this the last time that we have to add an an account type. Okay, so we have the approval from everyone. Uh,","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=748s"},{"start_seconds":755,"text":"thank you so much everyone and this nap is by all intended purposes approved and see you in the next one I guess.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=755s"},{"start_seconds":764,"text":"Bye everyone. Thanks. Bye. Bye. Bye.","url":"https://www.youtube.com/watch?v=HqsmiDhdysw&t=764s"}],"youtube_url":"https://youtube.com/watch?v=HqsmiDhdysw","url":"https://near-pedia.xyz/videos/HqsmiDhdysw"}