Jump to content


  • Content Count

  • Joined

  • Last visited


About segra

  • Rank

Recent Profile Visitors

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

  1. Tip: Dont play games with the ATO. History has shown they will not go after big companies and their various tactics for extracting money from the country without tax, But they will hunt down small time individuals, even for a $100 miscalculation. And the pentalty for getting it wrong, very heavily outweighs any benefit you gain from avoiding tax ( tax * 2 + interest -- basically setup to ensure you end up owing more than your profit )
  2. a 'someone' may not have coverage, but if Ripple gets behind it, its not that unreasonable to assume others will follow
  3. Not exactly true. *someone* started the symbol project, but given the short time frame it would appear that Ripple already had a new symbol in the works, possibly due for launch at the XRP commnunity night... hence why they had all lthe merchandise ready. @lucky
  4. had previously been using these; STTx, OrderBookDB, Book, Ledger, LedgerInfo, STValidation, AcceptedLedger, AcceptedLedgerTx, STObject, ReadView, SLE (Not entire sure if i actually needed all these or not) use cases might be easier for the other parts (Not sure all the specific classes which are required to do this) I would like to be able to fire up a module, connect to a few running validators and receive everything as normal, having the module use callbacks for published ledgers or new transactions, and be able to grab order books. eg. Previously I had hacked things up so that this was possible (callback implementation makes use of shared/weak ptrs, with the calling side (QT Widget/window) holding a shared_ptr, and the caller (rippled side) holding a weak_ptr... so if the GUI/window is destroyed, the callback token will become invalid) using tCallbackToken = std::shared_ptr<void> using tPubLedger = std::shared_ptr<ripple::AcceptedLedger>; using tSubmitTrans = std::shared_ptr<ripple::STTx const>; using tSubmitTxCallbackTarget = std::function<bool(tPubLedger, tSubmitTrans, bool)>; tCallbackToken cRipplePP::SubmitTransaction(tSubmitTrans const iTrans, tSubmitTxCallbackTarget pCallback) { ripple::gRippleD->getOPs().submitTransaction(iTrans); return LedgerAttach( [this, iTrans, pCallback](tPubLedger pLedger) -> bool { auto TxID = iTrans->getTransactionID(); // Transaction didn't make it? if (!pLedger->getLedger()->txExists(TxID)) { // TODO: Check max ledgers past? // Keep waiting return true; } // The attached callback can decide if this should continue running return pCallback(pLedger, iTrans, true); }); } Appologies @tulo; i feel i hijacked your thread
  5. Speaking of tooling, is there any future plans to 'modularise' rippled (or parts of it) at all? While I have nothing against using APIs, having the node built-in with callbacks is more preferred (for me anyway - and how screenshot above was implemented)... it was problematic though, as it requires one to copy a couple of core files and make alternations (Application.cpp / NetworkOps.cpp). In hindsight, the time is probably now to implement a trading tool (im not a trader either, it was more just for fun)
  6. Yeah, this is a tool for finding new seeds... but it should be enough to work with xrp-vanity is essentially an unrolled version of the code Nik is pointing to (thats how it was built anyway, some replacements made for simplicity)
  7. was working on a C++/QT trading app mid last year, but interest seemed low...
  8. Its not an error, The first 32 bytes of the SHA512 (of the seed) are used as the Root Deterministic Key https://github.com/segrax/xrp-vanity/blob/master/Source/main.cpp#L130
  9. You could argue that Firefox is a descendant of Netscape, doubtful that any of the original code base is in Firefox though You could also pickup a copy off eBay https://www.ebay.com/itm/Netscape-Navigator-Gold-Personal-Edition-Windows-95/173156225992?hash=item2850ea53c8:g:3hAAAOSwB09YJl7b
  10. @Hodor xrp-wallet https://github.com/segrax/xrp-wallet
  11. One of the best languages around, who wouldn't want to know it!
  12. I think the problem may actually lay with the C++ QR Code generator its using, I just tested the blob below with http://www.qr-code-generator.com/ and the QR Code reader on binz.io can read it no problem everytime... I'll put some time into xrp-wallet this weekend and see what can be done... seems the library creates unnecessarily large QR Codes, as the one generated on that page is very small incomparision But,this is a 4 signature escrow create transaction { "command" : "submit", "tx_blob" : "12000122800000002400000002202521781E656140000000000F42406840000000000000647300701127A0258020EB1C5A011A527EF1688C20E8ED62F0F2E47E0B39BCFB67341C3463C2F9FECB7B81010B8114545E7EE45DFDC53A00F2F7864149D758BF817306831496E710669EBFB208551FF7876B731B82BCFC19A7F3E01073210248F2D519093E5F43C34B8B7537E47F4CD2AF01EDEC896ACA7C9C78782F5838DE744730450221009B21F841D7B7BB915482D00152BAE6769A22E2532113AE6B18E2A7646B11289902200FD2F3EE4AF53F9E34E13330BC596EE56F4BFE2F1BE1EEBB9E2C1CFAE65407CB811496E710669EBFB208551FF7876B731B82BCFC19A7E1E01073210291BA662409D7EAED6408D99807B3E5232CF97B9C0CA0C628CD1B9A8EFA10CA7F74473045022100E6364C3A43B06AAD47E1D71239A3538F87BB9310742B300A4A5D275BDCDD15DB022041910977175DB82E2766AEA742194FE56C41CA61A3BE78169200D0C8D12A79418114C348C105F4A2533057CBD5C75FA85EE7E190FFAAE1E010732103C2522275697EE070F40F8A7F248B80643FF5EB0BDAEE88B8B651A2F48DC9B49D74463044022023B9304C0190ABA04995545D6DD7A2BA6731F71D2D70E491BF06AA160271F21602201EEDA767BFAC05CD2B41F689290E270C548D34D99A20FEFF31B7B0F1A403C0D48114C3A483614BEC94A745ACBD762DD4079080D96902E1E010732103DBFFE72E435600CDBDFC5A0FD3CFFDB22B67DC58CBC15AB7628A59F41C2E51A27446304402206431D4DE6BF1586E0482A347A871100D38B96225CBFCFECB07C2D837B5FC68B30220721BE2D9F79E99A53DE1E5FF3703B456E8D4E0B86CA4F16A13F9592677C0C8BA8114DE0D53849C16F712C96688FBDCEDF24A5B432E21E1F1" }
  13. That was my pain point when originally setting up a cold wallet, the copying of a signed tx blob onto a USB and then submitting it. That’s what led to the QR code scanner, if anyone has suggestions on improving it, would love to hear them, I know it has some issues on phone, occasionally it does take a few goes ( photos ) before it can successfully read it, moving closer/away from the screen usually fixes it ( I had trouble finding a resolution to resize the capture image, which worked for all situations ). A good example is a multi signed transaction, they’re really pushing the boundaries of QR code sizes ( infact, a lot of phone apps won’t even recognise large qr codes ) - in saying all that, I probably didn’t dedicate as much time to it as it deserves, but if there is demand, I’ll do what I can to improve it, am also happy to accept Pull Requests on github and push them out to binz.io
  14. Just the standard Ripple websocket format, so a signed ready to submit transaction such as { "command": "submit", "tx_blob": "1200002280000000240000001E61D4838D7EA4C6800000000000000000000000000055534400000000004B4E9C06F24296074F7BC48F92A97916C6DC5EA968400000000000000B732103AB40A0490F9B7ED8DF29D246BF2D6269820A0EE7742ACDD457BEA7C7D0931EDB7447304502210095D23D8AF107DF50651F266259CC7139D0CD0C64ABBA3A958156352A0D95A21E02207FCF9B77D7510380E49FF250C21B57169E14E9B4ACFD314CEDC79DDD0A38B8A681144B4E9C06F24296074F7BC48F92A97916C6DC5EA983143E9D4A2B8AA0780F682D136F7A56D6724EF53754" } Put through a QR Code generator will be submitted to the ledger as is. PNG should be fine (generally i use my mobile phone, and take a photo of the screen) but; you should be able to do the same with software on your pc... Nah, but it wouldnt be hard to modify it to include this support (the page is just using basic HTML5 features)
  • Create New...