Since we are integrating AEternity in our stack, we are developing a .NET SDK for AEternity.
For more information and feedback:
6 Likes
This is great!! How can we help you, what is your project about?
Currently, testing.
All test and integration testing are passing but the devil never sleeps.
There is probably serialization/deserialization issues in contracts. I personally don’t like the code made on that part. Since some Sophia data types are not serialized into a strict json compliant, the reliance on regex for parsing worries me a lot.
You can see our products/projects @ www.blockm3.com
Regards
regarding serialization of the sophia data types do you mean the ACI that is being produced by the compiler?
No, actually, the input and the output of the contracts:
Example: map
[“one”] = 2, [“two”] = 1
or
[1] = “two”, [2] = “one”
This needs a custom serializer and deserializer. Instead of using json parser as generic serializer/deserializer.
1 Like
ok I see. that is also something we need to look at in the java-sdk. we have no easy to use way to pass function parameters to the calldata.
do you already have a working mapper there? I saw that you implemented sth on that side.
Yes there is a mapper.
https://github.com/block-m3/aepp-sdk-net/tree/master/BlockM3.AEternity.SDK/Sophia
But I’m not actually proud of it. Lots of regex 
and fast coding. More extensive tests are needed.