Skip to content
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

Add a NotaryAssisted transaction attribute #2896

Open
roman-khimov opened this issue Sep 6, 2023 · 0 comments · May be fixed by #3175
Open

Add a NotaryAssisted transaction attribute #2896

roman-khimov opened this issue Sep 6, 2023 · 0 comments · May be fixed by #3175
Labels
Discussion Initial issue state - proposed but not yet accepted
Milestone

Comments

@roman-khimov
Copy link
Contributor

Summary or problem description
Add a new transaction attribute, NotaryAssisted with all of the associated logic from #1573 (comment)

Do you have any solution you want to propose?
Change 50 lines of the code and let this attribute exist. Notary contract mechanics should be stubbed at this point (wrt dynamic fee value (can be static 0.1) and signer checks).

Target Neo Version

  • Neo 3.7

Where in the software does this update applies to?

  • P2P (TCP)
@roman-khimov roman-khimov added the Discussion Initial issue state - proposed but not yet accepted label Sep 6, 2023
This was referenced Sep 14, 2023
@roman-khimov roman-khimov added this to the v3.7.0 milestone Nov 16, 2023
AnnaShaleva added a commit to AnnaShaleva/neo that referenced this issue Mar 6, 2024
Close neo-project#2896. Use a stub for native Notary contract hash since this
contract is not implemented yet. Thus, technically, NotaryAssisted
attribute verification will always fail on real network until native
Notary implementation.

Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva added a commit to AnnaShaleva/neo that referenced this issue Mar 6, 2024
Close neo-project#2896. Use a stub for native Notary contract hash since this
contract is not implemented yet. Thus, technically, NotaryAssisted
attribute verification will always fail on real network until native
Notary is implemented.

Signed-off-by: Anna Shaleva <[email protected]>
AnnaShaleva added a commit to AnnaShaleva/neo that referenced this issue Mar 6, 2024
Close neo-project#2896. Use a stub for native Notary contract hash since this
contract is not implemented yet. Thus, technically, NotaryAssisted
attribute verification will always fail on real network until native
Notary is implemented.

Signed-off-by: Anna Shaleva <[email protected]>
@AnnaShaleva AnnaShaleva linked a pull request Mar 6, 2024 that will close this issue
12 tasks
AnnaShaleva added a commit to AnnaShaleva/neo-devpack-dotnet that referenced this issue Mar 6, 2024
AnnaShaleva added a commit to AnnaShaleva/neo-modules that referenced this issue Mar 6, 2024
@roman-khimov roman-khimov modified the milestones: v3.7.0, v3.8.0 May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Initial issue state - proposed but not yet accepted
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant