-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notary native contract #2897
Comments
They have too many things at the same time, some parts from them are already merged (like attributes) and there even were bugs found and fixed during the process. We're going step by step and piece by piece now. In fact, this was the way Notary was implemented in NeoGo way back when, there was no single monstrous PR delivering all of it, we've moved component by component (there is enough of independent parts there). The main thing is that
Even though it still won't be able to process Notary P2P payloads (but that'd be the next step). |
Close #2897. Signed-off-by: Anna Shaleva <[email protected]>
Close #2897. Depends on #3175. Signed-off-by: Anna Shaleva <[email protected]>
Summary or problem description
Add a new native contract, Notary, with all of the associated logic from #1573 (comment)
Do you have any solution you want to propose?
The GAS locking mechanics of it is rather trivial,
verify
is a little more complex and it affects the NotaryAssisted attribute a bit as well (dynamic fee).Target Neo Version
Where in the software does this update applies to?
Depends on #2896 and #2895. With this implemented C# will be able to process NeoFS sidechains.
The text was updated successfully, but these errors were encountered: