The daemon communicates with the network.
The command line wallet does interact with the daemon but it has it's own commands, does not invoke commands on the daemon.
Both of these are standalone applications.
A wrapper would be an abstraction of some sort that invokes the commands on a parent application through a secondary interface.
The command line wallet does interact with the daemon but it has it's own commands, does not invoke commands on the daemon.
Both of these are standalone applications.
A wrapper would be an abstraction of some sort that invokes the commands on a parent application through a secondary interface.
Thank you this is a proper explanation. So would the (official GUI/CLI) interface be more correctly described as middleware?
The train is already gone...
Only for those that think of the train going to the next station, we prefer to think of it as going to the end of the line.
I like the fact people are thinking in terms of XMR/USD now.
I would speculate that is was the same person, testing the market to see where the supply and rdemand levels are, and shaking the tree a little in the process. The costs of the exploration (if any) are probably well worth it for the data gathered (not to mention that some of the trading will be into their own bids and offers)
just a little bit of probing before the next move ...
Very astute observation, I concur. Although I think I would replace "person" with entity (IE organization).