IO.Swagger - the C# library for the Fireblocks API does not compile

Hello Fireblocks, please can someone assist here?
C# .NET support please - Support - Fireblocks Developer Community
Thanks David

Hi @david.cassell I was able to download the C# SDK from the OpenAPI spec and was able to reproduce the error when running dotnet build I am going to check with the team internally to see if we can fix the OpenAPI generation for C#.

Thanks very much @Mohammed

@david.cassell I was advised that we’ve selected openapi-generator for our autogenerated SDKs. Please try generating the C# SDK this way. I will test on my end.

Hey @david.cassell did the openAPI generator help with C# SDK compilation?

Hey @Mohammed,

Following Oren’s suggestion, the OpenAPI client generated by the tool is now working, with few small tweaks here and there.

The client still did not compile with this approach, but the errors were more easily fixed, like an enum missing a value and a field marked as required but it was not.

We are trying to get a really simple smart contract deployment up and running with Fireblocks but have been blocked to date by the OpenAPI issue and a couple of other issues.

We now get to the point where we deployed a contract and get a INSUFFICIENT_FUNDS_FOR_FEE.
We also get “INTERNAL_ERROR” reported on a 201 POST.

It is progress having all the API requests and objects listed in the intellisense, but we are still not making progress on getting a working POC/validation of Fireblocks working.

Note that beyond that very simple use case, for your reference - our main use test case that we were wanting to progress is this - we have an API and service in .NET/C# that runs through the following use cases - it:

  1. Deploys our smart contracts on-chain (smart contracts as submitted for review to Fireblocks team).
  2. Creates a tokenised share class on-chain.
  3. Creates a simple settlement token on-chain.
  4. Links the two, and allows a subscription order to be placed on the tokenised share class.
  5. A Order Submitted event is emitted and observed by the .NET/C# service.

We have this test case built and working using Nethereum, running against a local test chain, and although a simple PoC it works.

The plan was to get this same use case running in Fireblocks by rewriting the interfacing to use Fireblocks API instead of the calls to Nethereum. From a business test case - it should still be the same and I’d still like to achieve this.

I’ll contact Oren for additional input and help.

Thank you Mohammed

Best regards David

1 Like