Skip to content

Create an API #2

@SamWilsn

Description

@SamWilsn

The first step of this task is to design an architecture, and create sub-tasks to track the implementation.

The simulation needs to be driven by some outside input provided by the user or client program. The specifics of the API are fairly open. Some possible avenues could include HTTP, grpc, or whatever else suits the data and use case.

The API provided by the simulation itself doesn't necessarily have to conform to the input to the client tooling.

Important features of the API include the synthesis and inspection of chain state.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions