images and what link?

lets revert back to dotnet 8 please, cant use dotnet 9 for now.

That is unnecessary, a update coming out next month that fixes the issues. Unless we have a new release coming out this month. then no reason to revert it.

lets revert back to dotnet 8 please, cant use dotnet 9 for now.

What can't you use? If the problem is neo-devpack-dotnet then revert for that project. No need to revert neo repo. You can also fix the issue, if you compile the neo.vm to dotnet standard then import it. Instead of building as dotnet.

Plus I warned you all and didn't listen to me. So now I'm not going back to dotnet 8.0.

But are you sure that the neo core itself is not affected by this bug in dotnet 9? Because BigInteger arithmetic is widely used in the core (not only in VM).

Only thing that isnt working is GetBitLength or invalid bit length, and in the neo.vm is the really the only the place this happens.

and in the neo.vm is the really the only the place this happens.

If it's true, then I'm not against of this PR.

But in general I'd expect the same dotnet version to be used within the whole stack. It's the way how we build software in nspcc-dev org, and it's a good practice, the whole stack has the same minimum required Go version, so I'd expect the same from the neo-project org. So if we take a decision to revert to dotnet 8, then every project should be reverted.

Looks like elliptical curve uses GetBitLength too. However all test are showing the correct output. So i dont know what neo-devpack is doing to have trouble with BigInteger.