If you are using the package on one market only, or at least build a logic per market, you should not see any difference, as you can, and probably want to, use market.api.query (it returns full results from market's API). If you are going to build market independent logic than, yes, you might be interested of market.api.process.I'm not sure if required packages will be loaded automatically when loading Rbitcoin, be aware of require/library them (RCurl, RJSONIO, digest, data.table).I think I will stick with the cran for now (updates there allowed each 1-2 months). The only changes which I'm currently planning to do till v1.0 is to extend the api.dict for all common API methods + more error catching, so it affect market.api.process only.
Unfortunately I'm currently focus on other project, Rbitcoin will be updated, but because of that other project I will stick with cran and monthly updates.
I don't plan to release further versions to CRAN repo. I already settled using locally per-package repositories hosted on github.io or gitlab.io (installation is seamless from package source directly). Besides there isn't much development ongoing now, and no plans for any. Package is working fine, and I already moved to other non-cryptocurrency related projects.
Current version of Rbitcoin is 0.9.5.1 (2015-10-04).
Last release to CRAN was 0.9.2 (2014-09-01).