Jump to content

Kakoyla

Member
  • Content Count

    261
  • Joined

  • Last visited

  1. { "TransactionType": "AccountSet", "Account" : "rABCDEF... ", "Fee": "12", "Sequence": 5, "ClearFlag": 4, }
  2. Yep, by using either the regular key or multisig, both worked for me. This was on testnet but i can't see why this wouldn't work on live XRPL as well.
  3. You can re-enable the masterkey if you can gather the required number of signers for multisigning. Assuming you are able to submit a multisign transaction with the required signing weight, you would then submit a accountset transaction with the clearflag field set to 4.
  4. @zach There is an optional SourceTag field you could check for, (Optional) Arbitrary integer used to identify the reason for this payment, or a sender on whose behalf this transaction is made. Conventionally, a refund should specify the initial payment's SourceTag as the refund payment's DestinationTag. https://developers.ripple.com/transaction-common-fields.html
  5. I made a few minor updates ( added back buttons, fixed typos, fixed the deposit auth transaction, etc)... But also wanted to add I shared this for people to use on TESTNET to try out different transaction types. I will use on the live XRPL, BUT if you do PLEASE be sure to double check the signed transaction JSON prior to submitting, and make sure your amounts (fees or amount sent) are correct first. I am just a rookie and while everything seems to be working as intended, i do not have experience with the edge cases of dealing with large numbers and JS. Also, the part I really wanted to show was how much easier and less stressful it can be using qr codes rather than typing in the address/secret, the paper wallet is going to still take up the same amount of physical space, why not take a short cut and include the QR? If interested I added a testnet account option to Bithomp's awesome paperwallet, which includes qr codes so you can print out a few and play around. The modified paperwallet can be found here: https://kakoyla.github.io/xrp-paper-wallet/
  6. Kakoyla

    Saudi/UAE Digital Currency Goes Live in Q1

    Everyone has been trained to doubt everything thanks to the bear market. This is incredible news, being totally undervalued by the community, wait until this spreads.
  7. This graphic is a little off, $98m direct is huge but the 2018 Q2 and Q3 are showing total sales while the rest of the list is showing direct.
  8. I will work on it, thanks for the input! yes, that's the only place i know where you can send the JSON without submitting it yourself via your own code. If you leave it as a tx_blob, you can submit it at any of these, there are probably more that I don't know about: https://kyteapp.co/ <-- click on send air gapped transaction https://bithomp.com/submit/ http://ripplerm.github.io/ripple-wallet/ <-- go click the tools tab, then submit sub-tab padanaram.digital <-- click XRPL then submit transaction for live xrpl or click testnet then submit transaction for testnet (I do not know of any other easy testnet submit sites) I was thinking this exact same thing. If you can see the tx_JSON matches what you expect, since this will never be run online, does the rest of the code even matter or is the end result all you need to worry about? If you want to see the tx_blob deconverted back to JSON you can drop the tx_blob into a decoder i made, padanaram.digital then click quick tools then decode tx_blob, it will give you the JSON. Assuming a simple payment....besides the destination and transaction type, I think the amount and fee are the most important fields to check. Amount is shown in drops so you would divide that by 1,000,000 to see it in XRP. Fee is also shown in drops but most people think of fees in drops already anyway, ie a fee of 12 would be 0.000012 XRP If the reason you want to check this is because of trust, you probably won't want to trust something else I provided, so you can do it yourself. deconvert the blob yourself: assuming you have node installed on your pc, install ripple binary codec (https://github.com/ripple/ripple-binary-codec) npm i ripple-binary-codec save this code as decodeTx.js: const binary = require('ripple-binary-codec') const signedTX ='ENTER YOUR tx_blob HERE' var decoded = (binary.decode(signedTX)) console.log(decoded) Then update const signedTX with your tx_blob and save Run it on the command line with node decodeTx.js The decoded tx_blob will be shown and you can now review to make sure the fields present match your expected transaction.
  9. Abducted by aliens with tig ol bitties please ?
  10. I needed a simple wallet interface that my wife or non-tech savvy friends could use if something were to happen to me...( ? / ? ). @ripplerm made my favorite wallet by far, and I got addicted to the convenience of using qr code when transferring the tx_blob to an online computer, but even though that wallet is pretty straight forward to me, it wasn't for the people i want to be able to use it. Also, the QR option isn't on all the fields I would like (typing in an address takes a long time when you need to be 100% correct) Wietse had made the kyte app and it was pretty easy to use, but as it currently stands, needs an online connection or a server on localhost, which is too complicated for what I am looking for. So I made this: kakoyla.github.io -----This was made for desktop, and intended for offline use. I tried to make it as dummy proof as possible, the simple XRP payment should be able to be completed by anyone as long as they know the keys. After I had the payment working easily i kept going and added all the options that I wanted to play with. All that being said, I have read this forum for a long time and realize NO ONE will trust this and use it on the live net, but that's not the goal of this post. I was thinking maybe someone non-technical will find this useful for learning about the options available on the XRPL by trying things out on the testnet. If interested you can generate pre-funded testnet accounts here. You can submit any tx_blobs for the testnet transactions here (click the testnet option then submit transaction). I also have a qr generator under the tools option, open it on a phone and enter in an account address or anything else you wouldn't want to type in manually, then you can just hold the phone up to the webcam of the (simulated) offline pc. I haven't done extensive testing so please PM me if you find something wrong or buggy so i can fix it. The code can be found here. If you have suggestions for improvements i'm all ears. edit: if you want to check it out, you can use snyFoZt6fJeAYfAxjBVt3qGXKyKcC edit #2: you can submit tx blobs here: https://kyteapp.co/ <-- click on send air gapped transaction https://bithomp.com/submit/ http://ripplerm.github.io/ripple-wallet/ <-- go click the tools tab, then submit sub-tab TESTNET submission: padanaram.digital <-- click testnet then submit transaction for TESTNET (I do not know of any other easy testnet submit sites) edit #3: If interested I added a testnet account option to Bithomp's awesome paperwallet, which includes qr codes so you can print out a few and play around. The modified paperwallet can be found here: https://kakoyla.github.io/xrp-paper-wallet/
  11. Sorry for the confusion, I didn't mean rippleAPI was the work around, I meant with rippleAPI you still need another step of combining the signatures and of course i was doing it wrong (AKA manually instead of using combine). I admit it is a very small extra step and not a big deal at all, i was just wondering why the combine step isn't included in the rippleAPI signAs process like it is for Rippled's signFor. Again, not a big deal I was just wondering.
  12. Kakoyla

    Ripple Names API

    I believe this is depreciated but: https://id.ripple.com//v1/user/acct # Example https://id.ripple.com//v1/user/rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B Will give u bitstamp info
  13. I am wondering if it's possible to sign for a multisign transaction with the ripple binary codec because I see this file within the code: https://github.com/ripple/ripple-binary-codec/blob/master/src/signing.js And more specifically this particular function within signing.js : function signFor(tx_json_, keyPair, signingAccount = null) {... But I am not sure how to call this function, or if it's even possible. I want to sign the transaction in the same way as the Rippled command signFor but based on my understanding ripple api doesn't seem to use this and would rather have you collect the signatures and combine them at the end. I think the rippled signFor process makes a lot more sense. I have made a work around using ripple api way, but I would rather do it the clean way than my way if possible. Thanks in advance
  14. I realize CFTC isn't the same as SEC, but I also don't think it's unreasonable to read between the lines here.
  15. What do you have the server set to? Did you include the wss:// before the address? Should be similar to this: const api = new RippleAPI({ server: 'wss://s1.ripple.com' // Public rippled server hosted by Ripple, Inc. });
×