I wanted to plug in various currencies, or as it were permit various currencies to plug in by making gateways for various currencies, but so far that still is being put off seemingly indefinitely.
-MarkM-
Did you contact OpenCoin on that matter? Providing assistance for new gateways is among their highest priority tasks.
Only via forum posts basically. I am not looking to get some special foot in the door of a closed source system, what I had been about to do was to modify the gateway code per each of several coin types as free open source gateway code for a bunch of coins, based on the free open source gateway code already available in the samples collection.
However in addition to learning that people would not be able to use the gateway code due to unavailability of the rippled code, I also was told that actually the gateway code itself isn't suitable for real use, so all in all it seemed it was too early yet for people to start putting up gateways.
It also turned out that using other people's rippled means revealing your 'secret' to them, that was the biggest reason in fact for the absolute need to run a rippled of one's own.
So all in all it was a long way from being ready for people to start realistically using.
Before starting to adapt the gateway to more currencies for example, it needs to be robust enough for real production use.
Presumably the gateways online so far are either flaky code, not suitable for use, or had failed to submit pull requests of their fixes, or were straight-out proprietary systems from the get-go.
-MarkM-
You can sign transactions offline and never need to expose your secrets to a rippled instance. Running your own "signing" rippled locally only saves you from re-implementing
https://github.com/ripple/ripple-lib/blob/develop/bin/rsign.js, that's all. The way to construct and sign a transaction is outlined at
https://ripple.com/wiki/Constructing_a_transaction, how to get it to the network is outlined at
https://ripple.com/wiki/Robustly_submitting_a_transaction. You can take the fully signed transaction and submit it to any rippled out there that is networked, also the one operated by e.g. Bitstamp if you mistrust OpenCoin's public servers.
Gateways are Ripple clients basically, not servers. You can run a gateway just fine against any rippled out there, the upside to running your own is that you have a node under your control for sure, have a voice in the voting process and can be sure if something fails that it was most likely your fault, not a random server on the net suddenly failing.
The way to contact OpenCoin to get access to rippled sources is not via forum PMs, you need to send a mail to
[email protected], as outlined on
https://ripple.com/wiki/Rippled. Most gateways I know do develop their own codebase though to interface their systems with Ripple, the code that is published as example might really be more of an example than being used anywhere in the wild.