Just wanted to let everyone know that I've discontinued Rippler command line client and won't support it any longer.
This decision was not easy for me as I've spend quite a bit of effort building this client, digging into Ripple(TM) API, server and client code as well as trying to understand the internal workings of this system in general. The more I learned about Ripple(TM) though the less satisfied I was about the system itself, the consequences of its possible widespread adoption and how OpenCoin chose to position and present it to the external world. Lately, I was also dissatisfied with the kind of people (https://bitcointalksearch.org/topic/m.2694725) Ripple is now associated with.
In all honesty, at this point I cannot support or endorse what Ripple(TM) stands for. As a result, I now decided to stop supporting Ripple(TM), OpenCoin or anything associated with OpenCoin in any way.
Topic: Ripple command line client (DISCONTINUED) (Read 2120 times)
So still no local signing then and no rippled source code. So you basically need a throwaway ripple account for this that will never be used with anything real.
I take it that signing is a pretty hard thing to implement eh?
-MarkM-
I take it that signing is a pretty hard thing to implement eh?
-MarkM-
Rippler works nicely--thanks
I'm trying to use it to make a payment from one ripple account to another.
It seems I have to use a command: sign secret tx_json [offline]
The tx_json needed for this is defined here https://ripple.com/wiki/Transaction_Format but looks complicated. Are there any examples?
I'm trying to use it to make a payment from one ripple account to another.
It seems I have to use a command: sign secret tx_json [offline]
The tx_json needed for this is defined here https://ripple.com/wiki/Transaction_Format but looks complicated. Are there any examples?
It is possible to use this API via Rippler, but you should understand that by using it with public server you're transmitting your secret over the wire. Proper use of it should be with a local server, but the server code is currently closed-source.
I have not seen any examples of transaction json on the Wiki but you can get some live samples from the ledger via Rippler, using for example tx_history and transaction_entry API.
Yeah, it occurred to me, I'd be able to see examples.
Rippler works nicely--thanks
I'm trying to use it to make a payment from one ripple account to another.
It seems I have to use a command: sign secret tx_json [offline]
The tx_json needed for this is defined here https://ripple.com/wiki/Transaction_Format but looks complicated. Are there any examples?
I'm trying to use it to make a payment from one ripple account to another.
It seems I have to use a command: sign secret tx_json [offline]
The tx_json needed for this is defined here https://ripple.com/wiki/Transaction_Format but looks complicated. Are there any examples?
sub
If you happen to do OTC deals with Ripple XRP (especially if you send BTC first), it is advisable to check the counter-party for red flags. Today, my command-line client saved me from being scammed for 2.5 BTC.
The party I've already done successful transactions with claimed to have 150K XRP for sale and asked that I send BTC first. I had no reason to distrust him, but as a precaution, I asked what Ripple account he is holding XRP at. Once I knew the account, it was easy to check if it has the XRP amount claimed:
$ rippler balances account:HIS_RIPPLE_ACCOUNT
It turned out, the account did not have anything close to XRP amount claimed, only 200XRP system reserve. When asked to explain this, my counter-party stopped responding.
Since a fully functional Ripple ledger browser is not available yet, you need to use Ripple API to check the counter-party in situations like this. Command-line line client offers an easy way to check any Ripple account for balances and history.
The party I've already done successful transactions with claimed to have 150K XRP for sale and asked that I send BTC first. I had no reason to distrust him, but as a precaution, I asked what Ripple account he is holding XRP at. Once I knew the account, it was easy to check if it has the XRP amount claimed:
$ rippler balances account:HIS_RIPPLE_ACCOUNT
It turned out, the account did not have anything close to XRP amount claimed, only 200XRP system reserve. When asked to explain this, my counter-party stopped responding.
Since a fully functional Ripple ledger browser is not available yet, you need to use Ripple API to check the counter-party in situations like this. Command-line line client offers an easy way to check any Ripple account for balances and history.
https://ripple.com/graph/
That can be used too. It's cool how you get to visualize so much stuff.
If you happen to do OTC deals with Ripple XRP (especially if you send BTC first), it is advisable to check the counter-party for red flags. Today, my command-line client saved me from being scammed for 2.5 BTC.
The party I've already done successful transactions with claimed to have 150K XRP for sale and asked that I send BTC first. I had no reason to distrust him, but as a precaution, I asked what Ripple account he is holding XRP at. Once I knew the account, it was easy to check if it has the XRP amount claimed:
$ rippler balances account:HIS_RIPPLE_ACCOUNT
It turned out, the account did not have anything close to XRP amount claimed, only 200XRP system reserve. When asked to explain this, my counter-party stopped responding.
Since a fully functional Ripple ledger browser is not available yet, you need to use Ripple API to check the counter-party in situations like this. Command-line line client offers an easy way to check any Ripple account for balances and history.
The party I've already done successful transactions with claimed to have 150K XRP for sale and asked that I send BTC first. I had no reason to distrust him, but as a precaution, I asked what Ripple account he is holding XRP at. Once I knew the account, it was easy to check if it has the XRP amount claimed:
$ rippler balances account:HIS_RIPPLE_ACCOUNT
It turned out, the account did not have anything close to XRP amount claimed, only 200XRP system reserve. When asked to explain this, my counter-party stopped responding.
Since a fully functional Ripple ledger browser is not available yet, you need to use Ripple API to check the counter-party in situations like this. Command-line line client offers an easy way to check any Ripple account for balances and history.
So this is the client I saw people discussing on IRC... Bravo, Arvicco, well done! Glad to know about it, I'll definitely be using it and contributing if I add any interesting features. And well-done on the MIT license. Generous move.
Does this sign stuff so that you do not need to send your "secret" to a rippled server?
(For example to flag an account as requiring destination tags?)
-MarkM-
(For example to flag an account as requiring destination tags?)
-MarkM-
I've created a command line client for Ripple. It is open source and can be found here:
https://github.com/arvicco/rippler
You can use the client in three ways:
1) Experiment with Ripple Websocket API without a browser. API reference is here: https://ripple.com/wiki/RPC_API, you need to use JSON format for commands.
2) Using bin/rippler is an example, you can create your own Ruby scripts using Ripple API.
3) Use it as part of your shell scripts to automate Ripple-related tasks.
Client is still beta, so use with caution.
https://github.com/arvicco/rippler
You can use the client in three ways:
1) Experiment with Ripple Websocket API without a browser. API reference is here: https://ripple.com/wiki/RPC_API, you need to use JSON format for commands.
2) Using bin/rippler is an example, you can create your own Ruby scripts using Ripple API.
3) Use it as part of your shell scripts to automate Ripple-related tasks.
Client is still beta, so use with caution.
Jump to: