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

core: remove contract script check on deploy/update #3052

Merged
merged 1 commit into from
Jul 8, 2023

Conversation

AnnaShaleva
Copy link
Member

This check is good and was present here since #1729, but it was accidently removed from the reference implementation (see the discussion in neo-project/neo#2848). The removal of this check from the C# node leaded to the T5 testnet state diff since 1670095 heigh which causes inability to process new blocks since 2272533 height (see #3049). This check was added back to the C# node in neo-project/neo#2849, but it is planned to be the part of the upcoming 3.6.0 C# node release.

We need to keep our testnet healthy, thus, strict contract script check will be temporary removed from the node code and is planned to be added back to be a part of the next 3.6.0-compatible release.

Close #3049.

@AnnaShaleva AnnaShaleva added this to the v0.101.3 milestone Jul 4, 2023
This check is good and was present here since #1729, but it was
accidently removed from the reference implementation (see the
discussion in neo-project/neo#2848). The
removal of this check from the C# node leaded to the T5 testnet state
diff since 1670095 heigh which causes inability to process new blocks
since 2272533 height (see #3049). This check was added back to the
C# node in neo-project/neo#2849, but it is
planned to be the part of the upcoming 3.6.0 C# node release.

We need to keep our testnet healthy, thus, strict contract script
check will be temporary removed from the node code and is planned
to be added back to be a part of the next 3.6.0-compatible release.

Close #3049.

Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
@AnnaShaleva
Copy link
Member Author

AnnaShaleva commented Jul 4, 2023

@roman-khimov, since we need our T5 machine in a proper working state and we don't know when 3.6.0 is going to happen, I'd suggest to release yet another 3.5.0-compatible release with this fix. After 3.6.0 is released, we'll revert these changes and create 0.102.0.

This fix is compatible with mainnet up to 3712135 and with testnet up to 2294980.

@AnnaShaleva AnnaShaleva requested review from carpawell and removed request for notimetoname July 4, 2023 14:56
@ixje
Copy link
Contributor

ixje commented Jul 5, 2023

@roman-khimov, since we need our T5 machine in a proper working state and we don't know when 3.6.0 is going to happen, I'd suggest to release yet another 3.5.0-compatible release with this fix.

Slightly hijacking here; but if you do create another compatible 3.5.0 release, can you please include #3014 in that as well ? 🙏

@AnnaShaleva
Copy link
Member Author

AnnaShaleva commented Jul 5, 2023

can you please include #3014 in that as well

To be honest, I hope that we'll see v3.6.0 within a couple of weeks (hi, neo-project/neo#2844 (comment)) and then it won't be necessary to release 0.101.3, we'll release 0.102.0 instead (which includes #3014). But if not, then I think it's OK to include #3014 into 0.101.3 as far, it's compatible improvement.

@AnnaShaleva
Copy link
Member Author

Let's convet it to draft, we'll wait until 3.6 is released, no need to hurry.

@AnnaShaleva AnnaShaleva marked this pull request as draft July 5, 2023 10:37
@AnnaShaleva AnnaShaleva marked this pull request as ready for review July 8, 2023 08:38
@AnnaShaleva AnnaShaleva merged commit f611a79 into master Jul 8, 2023
11 of 16 checks passed
@AnnaShaleva AnnaShaleva deleted the remove-script-check branch July 8, 2023 08:40
@AnnaShaleva
Copy link
Member Author

can you please include #3014 in that as well

@ixje, back to your request: I apologize for the misinformation, but we've released https://github.com/nspcc-dev/neo-go/releases/tag/v0.101.3 without #3014, because it's kind of "dirty" release that contains only a single T5 incompatibility fix. We've discussed the 3.6 release date with Steven and Owen, it's scheduled for the next week, so we have to wait a little bit more. #3014 is too good to be included into v0.101.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

T5 testnet stuck at 2272533
3 participants