[davidatwhiletrue]

Summary

Moves CES parser to its own nuget package. No changes to implementation. Documentation and examples updated with new namespace and reference project.
Updates SDK version to 3.3.0.

TODO

Checklist

• Code is properly formatted
• All commits are signed
• Tests included/updated or not needed
• Documentation (manuals or wiki) has been updated or is not required

[Comp0te]

Reviewed the move of the CES parser into its own Casper.Network.SDK.CES project and package, including the publish workflow and docs. One small follow-up on how the new package is referenced from source.

[Comp0te]

This note points NuGet users to Casper.Network.SDK.CES, but the "Add a reference to the source code" section just below still names only Casper.Network.SDK.csproj. CES no longer compiles into that project. So anyone who references the SDK from source and then follows the CES guide gets unresolved Casper.Network.SDK.CES / CESParser symbols.

Could that section also mention the CES project, e.g. dotnet add reference ../casper-net-sdk/Casper.Network.SDK.CES/Casper.Network.SDK.CES.csproj?

Basis

• CESParser moved from Casper.Network.SDK/CES/ to Casper.Network.SDK.CES/CESParser.cs, and Casper.Network.SDK.csproj has no reference to the new project.
• The source-reference section is unchanged by this PR. The other docs that mention CES (CasperEventStandard.md, README.md, the CES README_nuget.md) only give the dotnet add package route.

[Comp0te]

LGTM