Search the Community

I am using ripple-lib for connecting Ripple. To create Trustline I am using api.prepareTrustline(address, trustline); which method needs to use to create TrustSet in ripple-lib.

Just looking for some devs or advanced users to chime in on some best practices for general private key security while using RippleAPI on a local server. Was going through xrpl.org docs and it's in there that commandline is less secure than, say, JSON-RPC because of things like shell histories and maybe process logging, etc., which I agree with generally. Trying to avoid things like cutting and pasting private keys into commandline scripts to mitigate things like keyboard/clipboard/history loggers, even if just a little. I've been using Linux bash and piping things into jq to process JSON in order to sign and submit transactions; are devs hardcoding private keys into JavaScripts and then just encrypting those files? Pretty sure hard-coding private keys in anything like a script is a no-no, but I could be missing something. In terms of eventually automating my transactions, I could think of a couple ways, like referencing decrypted private key files, running your scripts then deleting/re-encrypting your private keys. I'm picking up javascript at the moment and guess I'll end up switching over to node.js to do transactions instead of through bash and bash scripts; seems like the Ripple API was designed with that in mind. I'm just using Linux command-line now cause I'm already familiar with bash and jq. Generally speaking, how are y'all managing private keys while using commandline/JSON-RPC/Websocket?

Hi folks, I'm using RippleAPI (the NodeJS library) to write a quick proof-of-concept for an idea I have. Basically what I'm trying to do is store some data in the Memo field. I can do it easily enough with some plain text (e.g., "Here is text" below): const preparedTx = await api.prepareTransaction( { TransactionType: "Payment", Account: ADDRESS, Amount: api.xrpToDrops("22"), // Same as "Amount": "22000000" Destination: "rUCzEr6jrEyMpjhs4wSdQdz4g8Y382NxfM", Memos: [ Memo: { MemoData: Buffer.from("Here is text", "utf8") .toString("hex") .toUpperCase() } } ] }, { // Expire this transaction if it doesn't execute within ~5 minutes: maxLedgerVersionOffset: 5 } ); After submitting the tx I just do this to get the text: let data = tx.specification.memos[0].data; console.log(Buffer.from(data, "hex").toString("utf-8")); // => "Here is text" What I'm having difficulty doing is submitting encrypted data in the memo field, e.g.: const preparedTx = await api.prepareTransaction( { TransactionType: "Payment", Account: ADDRESS, Amount: api.xrpToDrops("22"), // Same as "Amount": "22000000" Destination: "rUCzEr6jrEyMpjhs4wSdQdz4g8Y382NxfM", Memos: [ { Memo: { MemoData: encrypted.toUpperCase() } } ] }, { // Expire this transaction if it doesn't execute within ~5 minutes: maxLedgerVersionOffset: 5 } ); console.log(preparedTx); // => {"TransactionType":"Payment","Account":"rHVQntm23skDRzDrrjtFjr7iWkZvwTPvYd","Amount":"22000000","Destination":"rUCzEr6jrEyMpjhs4wSdQdz4g8Y382NxfM","Memos":[{"Memo":{"MemoData":"EB8C1317FBD61EBF271022486402753A4373E80A6ED498DEB437B27E44E07DB9AC4A8B5BF635E10232A236CE784DCBFC"}}],"Flags":2147483648,"LastLedgerSequence":2617395,"Fee":"12","Sequence":2614128} It looks like the memo field is properly in hex format, but when I print `tx.specification.memos` after submitting the tx, the memo data field looks unrecognizable: [ { data: `�\u0013\u0017��\u001e�'\u0010"Hd\u0002u:Cs�\nnԘ޴7�~D�}��J�[�5�\u00022�6�xM��` } ] How do I fix this to show the hex memo data? (I'm not good with encodings, please forgive me if I'm not using the right terms) Without going too much into the specifics, here is the encryption function: function encrypt(text, secret) { const IV_LENGTH = 16; let iv = crypto.randomBytes(IV_LENGTH); console.log("SECRET_LENGTH", secret.length * 4); let cipher = crypto.createCipheriv( "aes-" + secret.length * 4 + "-cbc", Buffer.from(secret, "hex"), iv ); let encrypted = cipher.update(text); encrypted = Buffer.concat([encrypted, cipher.final()]); return iv.toString("hex") + encrypted.toString("hex"); }

I use the getTransactions method in the rippleApi to get transaction data, so how do I get it over time?There is no time parameter option in this method parameter

I may be misinterpreting how the fillOrKill flag works but I have had multiple orders now that are coming through as successful but that are not filling? I am getting tesSUCCESS as the final result yet my balances do not change. How is this possible? Doesn't fillOrKill ensure that the balances change or the order is cancelled?

I was just looking through this topic by tulo: https://www.xrpchat.com/topic/8223-rippleapi-orderbooks-order-is-by-string-quality/?tab=comments#comment-78458 and decided to reproduce the problem he was having. When I started playing around with limit option I noticed something odd. Looking up the XRP / CNY rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y book with the option.limit set to 1 would not always return a result for both the bid and ask. When I up the limit to 5 or 10 it always returned for both. Any ideas on why this might be happening? I can think of a lot of use cases for wanting a limit of 1 since it should return the top bid and ask quality. This coupled with the string sorting brought up in tulo's post means that you need to return the entire orderbook, re-sort, then take the top quality to ensure that you are getting it. Seems like a lot of work.

We've created a new mailing list for ripple-lib (RippleAPI) release announcements. I expect to send about 1 email per week: https://groups.google.com/forum/#!forum/ripple-lib-announce Similar to the ripple server list for rippled, we will send updates to this list when important changes or releases are made. We'll also notify this list if any bugs or issues are discovered. If you use ripple-lib in any capacity, I highly recommend subscribing. The list is public, but you need to join/subscribe before you can view its messages. The list is intended for announcements only; to communicate questions and feedback to our team, please use GitHub issues. Again, here's that link to the new list: https://groups.google.com/forum/#!forum/ripple-lib-announce Thanks!

I have node ripple on server Amazon. Before 1 days, when I sign transaction with ripple api on this node by RPC api: (sign), response of api sign have error "highFee" (fee execute transaction very high ), but fee execute normal transaction that is 10 drops. Todays, I also test with api sign but fee execute normal transaction that is "10". Does anyone know about problem ? Thanks very much.

Hi all, We will participate in a conference about blockchain and made an introductory guide to start playing with ripple consensus ledger (testnet). We chose some basic transactions like creating and activating accounts, creating trustlines and making atomic cross-currency payments. Feel free to use it for whatever you want. https://github.com/rippex/ripple-node-examples

It's probably no surprise to the people here, since RippleAPI has been available for a little while, but here's the official announcement about the release of RippleAPI: https://ripple.com/dev-blog/introducing-rippleapi/ tl;dr RippleAPI is the merger of Ripple-REST and ripple-lib, it's way better than those two were, we're not supporting the old stuff anymore, and you should check out the brand-new Beginners Guide in case you're not sure how to get started with RippleAPI.