Jump to content


  • Content Count

  • Joined

  • Last visited

1 Follower

About jargoman

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It's a good time to buy. After BTC rallied. Right after the XRP reversal pattern. Sure he didn't buy the bottom but maybe he's catching the beginning of a huge rally
  2. https://www.today.com/news/nasa-astronauts-weigh-canceled-all-female-spacewalk-t151306 Imagine if Ripple picked up the tab. Paying for the spacesuit and placed their logo on the suit. Ripple to the moon. again !
  3. You have to add Xrp Forum Troll Rcl ledger professional.
  4. Thank you I thought it didn't matter. json's white space is supposed to be irrelevant.
  5. Not having to provide your keys to every website you visit. It's the browsers version of a ledger nano.
  6. <script src="/Scripts/ripple-1.2.0.js" type="text/javascript"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.11/lodash.js" type="text/javascript"></script> <script type="text/javascript"> function SubmitTransaction() { const curr = document.getElementById("cur").innerHTML; document.getElementById("outcome").innerHTML += curr; const add = document.getElementById("ad").innerHTML; document.getElementById("outcome").innerHTML += add; const limit = document.getElementById("lim").innerHTML; document.getElementById("outcome").innerHTML += limit; const quin = document.getElementById("qin").innerHTML; document.getElementById("outcome").innerHTML += quin; const quout = document.getElementById("qout").innerHTML; document.getElementById("outcome").innerHTML += quout; const secr = document.getElementById("sec").value; document.getElementById("outcome").innerHTML += secr; const trustline = { currency: curr, counterparty: add, limit: limit, }; //const trustline = JSON.stringify(JSON.parse(t)); var api = new ripple.RippleAPI({ server: 'wss://s.altnet.rippletest.net:51233' }); var isValid = api.isValidSecret(secr); document.getElementById("outcome").innerHTML += "<br>IsValid " + isValid; var keypair = api.deriveKeypair(secr) document.getElementById("outcome").innerHTML += "<br>Public Key " + keypair.publicKey; var address = api.deriveAddress(keypair.publicKey); document.getElementById("outcome").innerHTML += "<br>Address " + address; const instructions = { maxFee: 0.000250, maxLedgerVersionOffset: 50 }; document.getElementById("outcome").innerHTML += "<br>Instructions " + JSON.stringify(instructions); api.connect().then(function () { document.getElementById("outcome").innerHTML += JSON.stringify(trustline); document.getElementById("outcome").innerHTML += "<br>Connected "; debugger; return api.prepareTrustline(address, trustline); }).then(function (prepared) { document.getElementById("outcome").innerHTML += "<br>prepared"; document.getElementById("outcome").innerHTML += "<br>" + JSON.stringify(prepared); const signedTransaction = api.sign(prepared.txJSON, secr); document.getElementById("outcome").innerHTML += "<br>signed = " + JSON.stringify(signedTransaction); api.submit(signedTransaction); }); } </script> the code halts when calling prepareTrustline and reports the following errors. instance.trustline.currency does not match pattern "^([a-zA-Z0-9<>(){}[\\]|?!@#$%^&*]{3}|[A-F0-9]{40}|drops)$", instance.trustline.counterparty does not conform to the "address" format,instance.trustline.counterparty does not match pattern "^r[1-9A-HJ-NP-Za-km-z]{25,34}$", instance.trustline.limit does not match pattern "^[0-9]*[.]?[0-9]+([eE][-+]?[0-9]+)?$" but the debugger reports trustline.currency as type string curr = "TST"; counterparty={valid ripple address string}; limit I've tried both int and string . is this a scope issue? I'm new to javascript but not programming
  7. A few weeks go, to my amazement ihilda's automated trading was settling @ 5 tx's per second. Also the bot has never snagged. Usually the only reason the bot will snag is if ripple's fee is higher than my maxfee for a prolonged period of time. Faster settlement translates to lower fee's because the network is less congested.
  8. there's two ripple's now. ripple > xrapid r3 > corda
  9. Mine has three interfaces for trading The depth chart The orderbook or the bot ui If these guys want to work together I'm down. edit* there is actually more interfaces for trading if you want to input the trades manually. Ihilda is about automation though
  10. I too am looking into creating a crypto based operating system. Possible base operating system candidates are debian/ubuntu/mint/, arch/manjaro or hardened bsd. I used to create my own distro called yahd. Arch linux with the zen-kernel. These guys seem to be making a command line environment. I'm talking full GUI. They might make a distributed exchange but I've already built one and it can run automatically and makes money automatically. It can run in command line mode if you want but in that mode only the bot runs. They might make a live image but mine will be better
  11. I read this again. You should save your secret key from within toast wallet. ANY software wallet is not a storage facility. It's a convenience wallet and it should be encrypted but you should have the secret key backed up. Software wallets can corrupt your wallet file, especially if it's encrypted. If the computer is saving to a file and the power goes out or the drive gets disconnected the file can be saved as blank or corrupted. There is no fix for this other than having your wallets backed up in a non corruptible form such as paper or wood or metal engraving. If you can't retrieve your secret see about setting a regular key for the account and backing that up. You'd have two keys. The master key on toast and the regular key you backed up.
  12. why do none of you guys save your secret key that's all you need.
  13. It's not something that is implemented server side. The user sets their regular key. If you reset their regular key. You'd have the key and they wouldn't.
  14. You can prevent replay attacks by setting a different regular key on each network. You'd only have to worry about the set regular key transactions being replayed. Replay attacks ARE possible. LastLedgerSequence was designed to stop an attacker from withholding a valid tx until it becomes profitable for them to submit it. Example a validator withholding a tx until it can be arbitraged against. People who sign tx's offline would sign a tx that would be valid later. So they would either not set a lastledger or they would set one that is farther in the future. I agree that replay attacks may be harder in practice but an attacker has public access to all the transactions submitted. A script could sniff and collect all susceptible transactions. Only accounts that were forked would be susceptible new accounts could have their tx's replayed but the systemd account would be unfunded.
  15. Yes you are right I saw all the numbers were exactly the same except the 11 turned to a 12. Weird it was exactly one month later
  • Create New...