I have begun coding a script (with database) that should include all basic functions required to accept monero (deposit/purchase,withdraw/transfer,check balance).
While doing this I can also document the functions. I'm using the available pre-built libraries for development, it seems some
parameters I need to make it scalable are currently not included in those, or maybe I'm missing something (asking on irc).
Once these issues are resolved I'll continue development.
To get an idea, this is what it looks like currently (and incomplete)
Click here to view a demonstration image![/img]
Feel free to give suggestions.
Hi, I almost never post on this forum but I wanted to say that this effort is crucial and hugely appreciated, TheKoziTwo. As soon as this guide is published I think we'll see a significant increase in implementation, from shapeshifter.io to cryptsy to marketplace and auction sites to niche sites, etc etc.
Since it seems you're coding an entire example application and waiting for ideal circumstances, I wonder if someone could offer an impromptu diy guide on how to communicate with the monero daemon from a server-side scripting language, the way it's currently done on Poloniex etc., for people like me (self-taught programmers, say, who don't want to wait on core development to get this economy started). It could be as simple as "google how to do this, this, and this, put them all together, oh, and I recommend this great book on best security practices while you're at it", or even "You idiot! Don't you know anything? Just put ____ in ____ and write a ____ script". That would be a starting point and I can find my way from there.
Here is my perspective
This project allows developers to flawalessly access the functionailty of Monero applications through the Core assemblies' RPC services. As the software is open-source, everyone can contribute, achieving the best performance and reliability for end-users.
Why is this API necessary?It makes the implementation of Monero extremely easy for merchants, wallet builders, and all the other developers who are interested in working with (or accepting) Monero. Also, the core developers can concentrate more on the internals
(instead of spending time on the official GUI client), which means that the currency should advance faster.
Is it cross-platform?The first 3 releases of the API were only made for desktop PCs running Microsoft .NET Framework 4.5 or higher, thus, resulting in a smaller userbase than wanted. Since v3, the project has been split into 2 subprojects, one which is responsible for communicating with the daemon and the account manager's RPC channel, and one which can manage the required processes on PC.
What kind of platforms can utilize the power of Monero API .NET, then?Basically every device which has support for running the Microsoft .NET Portable Framework v4, and more: Microsoft is planning to provide native (C++) compilation of C# assemblies very soon, and this process can be even faster since .NET Core has been made open-source.
The project can run on PCs (Windows; Mac and Linux with Mono .NET), mobile phones (Windows Phone; Android and iOS with Xamarin), and even on video game consoles like Xbox.
How does it work?As I have already mentioned above, the project consists of 2 parts: MoneroAPI, and MoneroAPI.Extensions. The first one is built as a PCL
(portable class library) and is multiplatform, while the extensions are desktop-only and contain functions for hosting a full node. Basically, MoneroAPI is preferable for lightweight, client-only applications, and MoneroAPI.Extensions adds support for hosting the Monero Core processes with ease.
There is a demo project included in the GitHub repository for a more technical explanation.
Please consider donating to one of the addresses in my signature if you like this project or want to support its development.