You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for the Account Info Standard in the .Net SDK clients library to ease the process of retrieving account information.
Motivation
The lack of built-in support for the Account Info Standard in the .Net SDK makes it cumbersome to retrieve that information. Providing a streamlined method would enhance the SDK's utility.
Guide-level explanation
Introduce a new class or method in the client library to handle Account Info Standard operations.
Example usage would involve calling this new method to either fetch a URL to the JSON file or a type-safe wrapper around the JSON data.
Reference-level explanation
The new feature could be implemented in the clients library as a contract client. Two modes could be supported:
A simple mode where the client is provided a URL to the JSON file or update it to a new URL.
A more advanced mode offering a type-safe wrapper around the JSON file.
For contract hashes, these could be stored for MainNet and TestNet but configurable for internal test networks. The file name also has to be set to the chain-spec (casper vs casper-test).
Important Note - would be nice if that could be handled automagically:
Payment: The set_url entry point call payment should be 10 CSPR. The deploy may fail with an "Out of gas" error if a smaller amount provided. For the consecutive set_url calls the advised payment amount is 0.5 CSPR
Summary
Add support for the Account Info Standard in the .Net SDK clients library to ease the process of retrieving account information.
Motivation
The lack of built-in support for the Account Info Standard in the .Net SDK makes it cumbersome to retrieve that information. Providing a streamlined method would enhance the SDK's utility.
Guide-level explanation
Reference-level explanation
The new feature could be implemented in the clients library as a contract client. Two modes could be supported:
For contract hashes, these could be stored for MainNet and TestNet but configurable for internal test networks. The file name also has to be set to the chain-spec (
casper
vscasper-test
).Important Note - would be nice if that could be handled automagically:
Source
Drawbacks
This feature could add extra maintenance workload and potential complexity to the clients library.
Rationale and alternatives
Unresolved questions
Future possibilities
The text was updated successfully, but these errors were encountered: