New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libclient API #351

anonimal opened this Issue Sep 12, 2016 · 2 comments


None yet
2 participants

anonimal commented Sep 12, 2016

By submitting this issue, I confirm the following:

  • I have read and understood the contributor guide.
  • I have checked that the issue I am reporting can be replicated or that the feature I am suggesting is not present.
  • I have checked opened or recently closed pull requests for existing solutions/implementations to my issue/suggestion.

Place an X inside the bracket to confirm

  • I confirm.

Moved from roadmap.

Ideally, all future client->core interaction will be done through libcore's API. We could refactor client into components which will work with libcore's API. If there is enough demand, we may also implement I2CP as a client service.

More details to come. Depends on a finished #350.


This comment has been minimized.


anonimal commented Oct 2, 2016

In today's meeting, we agreed to start by implementing a C++ Streaming API for monerod to hook into. Next will be a Datagrams API, also C++.

Whether we create a unified client API for both protocols has yet to be discussed. More details to come.


This comment has been minimized.


anonimal commented Sep 7, 2018

NOTICE: THIS ISSUE HAS BEEN MOVED TO GitLab. Please continue the discussion there. See #1013 for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment