Search the Community

Hello XRPChat, Our development team is working on a wallet/e-commerce app and hardware combo and would love some healthy and of course critical feedback from you. The app we are developing will allow users to store the top 5 cryptocurrencies with XRP being our prime focus. It can accommodate more cryptocurrencies but for now we'll start with the top 5. One of the main features of the app will be to transfer stored cryptocurrencies (value) to and from all users using the app, an equivalent to PayPal and Venmo but without the hosted mediary in between as we are not, nor do we wish to be an exchange as anything can be hacked. We are coding the app to interface with existing payment portals such as Apple Pay and Google, and stand-alone as we believe cryptocurrencies are the future of transactions and envision using the app to make common daily transactions once cryptocurrencies (xrp) become wildly accepted everywhere. So far there hasn't been any mention of consumers using XRP to trade and purchase goods just as credit and debit cards are now widely used and excepted and are wondering if anyone has seen or heard of such a thing not just the usage between the banks. Or is it that XRP will only be used for cross-border payment transfers and not directly for daily consumer usage? Again any feedback is greatly appreciated. If there doesn't exist such a platform what would you, the consumers and end users like to see in such an app? What features would add value for you? As mentioned, in addition to the software app, we are designing a totally offline hardware wallet for users to store the bulk of their cryptocurrencies and are projecting its cost to be lower than the Nano Ledger S. A wallet that's never connected to the internet. Our thinking is that "when" cryptocurrencies (xrp) become the mainstream store and transfer of value. Storing them will also become vitally important and as such, there needs to be an easy and highly secure way to house them, one which is always offline. The device we are designing will work in conjunction with our aforementioned software counterpart to move cryptocurrencies back and forth between one another. Again we welcome any and all feedback as we greatly value your insights and opinions. With your help, our primary focus will be to deliver a quality product. Thank you. Tony C. CEO - Phoenix Sequence

Get to know about arbitrage profit opportunities, realtime buy rate and sell rates from exchnges trading Ripple in all over the world. Arbitrage Opportunities are also shown for respective trading pairs. checkout: https://www.shufflup.org/

Created this platform so that people can compare buy rates, sell rates and fees for different exchanges offering Ripple Trading. Additionally, Arbitrage Opportunities are also shown for respective trading pairs. You can get notified whenever there is an arbitrage opportunity upon registration. As the increase in number of people investing in Ripple has increased and most of them are new to trading, thought this would be helpful. Checkout: https://www.shufflup.org

The crypto market is really on its peak and everybody wants to try their hands but due to very high demand many exchanges are closing new registration. Newbies are finding it difficult to find an exchange to invest. So, added the list of exchanges that support Ripple trading and whether they are open or closed for registration in https://www.shufflup.org/ex_status.php For those who haven't checked other functionalities that we provide, don't forget to explore. Many more things are coming up in the next few days. Ripple trading is easier like never before.

Hi everyone! I am brand new to Ripple in general, but a friend of mine studies it quite closely. He has tasked me with running our own rippled instance. Really, my goal at this point is to be able to connect to it from a local ripple-lib script over WSS and query account info -- that's all. I have rippled installed and as far as I can tell have a valid configuration, such that it does run, however the process is constantly being killed and restarted. The response from my script upon api.connect vacillates from garden-variety "NotConnectedError" (when the process is restarting) to "[RippledNotInitializedError(Rippled not initialized)]" (when it is briefly running). My environment is Ubuntu 16.04.1 on a very cheap Digitalocean droplet. I fully realize I will need a more powerful VPS if I want a working, live instance, but I would assume something basic is ok for testing. Please correct me if I am wrong on this. My config as of now is: [server] port_rpc_admin_local port_peer port_ws_admin_local port_ws_public [port_rpc_admin_local] port = 5006 ip = 127.0.0.1 admin = 127.0.0.1 protocol = http [port_peer] port = 51235 ip = 0.0.0.0 protocol = peer [port_ws_admin_local] port = 6006 ip = 127.0.0.1 admin = 127.0.0.1 protocol = ws [port_ws_public] port = 5005 ip = my.ip.addr protocol = wss ssl_key = /etc/opt/ripple/key.pem ssl_cert = /etc/opt/ripple/cert.pem #------------------------------------------------------------------------------- [node_size] medium [node_db] type=RocksDB path=/var/lib/rippled/db/rocksdb open_files=2000 filter_bits=12 cache_mb=256 file_size_mb=8 file_size_mult=2 online_delete=2000 advisory_delete=0 [database_path] /var/lib/rippled/db # This needs to be an absolute directory reference, not a relative one. # Modify this value as required. [debug_logfile] /var/log/rippled/debug.log [sntp_servers] time.windows.com time.apple.com time.nist.gov pool.ntp.org [sntp_servers] time.windows.com time.apple.com time.nist.gov pool.ntp.org # Where to find some other servers speaking the Ripple protocol. # [ips] r.ripple.com 51235 # File containing trusted validator keys or validator list publishers. # Unless an absolute path is specified, it will be considered relative to the # folder in which the rippled.cfg file is located. [validators_file] validators.txt # Turn down default logging to save disk space in the long run. # Valid values here are trace, debug, info, warning, error, and fatal [rpc_startup] { "command": "log_level", "severity": "info" } # If ssl_verify is 1, certificates will be validated. # To allow the use of self-signed certificates for development or internal use, # set to ssl_verify to 0. [ssl_verify] 0 A log of when I run rippled with "--fg --net" is below (it's long....sorry): 2018-Jan-08 00:45:04 JobQueue:NFO Auto-tuning to 3 validation/transaction/proposal threads. 2018-Jan-08 00:45:04 Amendments:DBG Amendment C6970A8B603D8778783B61C0D445C23D1633CCFAEF0D43E7DBCD1521D34BD7C3 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment C1B8D934087225F509BEB5A8EC24447854713EE447D277F69545ABFA0E0FD490 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 740352F2412A9909880C23A559FCECEDA3BE2126FED62FC7660D628A06927F11 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 1562511F573A19AE9BD103B5D6B9E01B3B46805AEC5D3C4805C902B514399146 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 532651B4FD58DF8922A49BA101AB3E996E5BFBF95A913B3E392504863E63B164 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment E2E6F2866106419B88C50045ACE96368558C345566AC8F2BDF5A5B5587F0E6FA is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 07D43DCE529B15A10827E5E04943B496762F9A88E3268269D69C44BE49E21104 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 86E83A7D2ECE3AD5FA87AB2195AE015C950469ABF0B72EAACED318F74886AE90 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 42EEA5E28A97824821D4EF97081FE36A54E9593C6E4F20CBAE098C69D2E072DC is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 3012E8230864E95A58C60FD61430D7E1B4D3353195F2981DC12B0C7C0950FFAC is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment CC5ABAE4F3EC92E94A59B1908C2BE82D2228B6485C00AFF8F22DF930D89C194E is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment B4D44CC3111ADD964E846FC57760C8B50FFCD5A82C86A72756F6B058DDDF96AD is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 6C92211186613F9647A89DFFBAB8F94C99D4C7E956D495270789128569177DA1 is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment B9E739B8296B4A1BB29BE990B17D66E21B62A300A909F25AC55C22D6C72E1F9D is supported. 2018-Jan-08 00:45:04 Amendments:DBG Amendment 1D3463A5891F9E589C5AE839FFAC4A917CE96197098A1EF22304E1BC5B98A454 is supported. 2018-Jan-08 00:45:04 OrderBookDB:DBG Advancing from 0 to 3 2018-Jan-08 00:45:04 OrderBookDB:DBG OrderBookDB::update> 2018-Jan-08 00:45:04 OrderBookDB:DBG OrderBookDB::update< 0 books found 2018-Jan-08 00:45:04 ValidatorList:DBG Loading configured trusted validator list publisher keys 2018-Jan-08 00:45:04 ValidatorList:DBG Loaded 0 keys 2018-Jan-08 00:45:04 ValidatorList:DBG Loading configured validator keys 2018-Jan-08 00:45:04 ValidatorList:DBG Loaded 5 entries 2018-Jan-08 00:45:04 ValidatorSite:DBG Loading configured validator list sites 2018-Jan-08 00:45:04 ValidatorSite:DBG Loaded 0 sites 2018-Jan-08 00:45:04 NodeObject:DBG NodeStore target size set to 131072 2018-Jan-08 00:45:04 NodeObject:DBG NodeStore target age set to 120000000000 2018-Jan-08 00:45:04 TaggedCache:DBG LedgerCache target size set to 256 2018-Jan-08 00:45:04 TaggedCache:DBG LedgerCache target age set to 180000000000 2018-Jan-08 00:45:04 TaggedCache:DBG TreeNodeCache target size set to 512000 2018-Jan-08 00:45:04 TaggedCache:DBG TreeNodeCache target age set to 90000000000 2018-Jan-08 00:45:04 NetworkOPs:NFO Consensus time for #3 with LCL 95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072 2018-Jan-08 00:45:04 ValidatorList:DBG 5 of 5 listed validators eligible for inclusion in the trusted set 2018-Jan-08 00:45:04 ValidatorList:DBG Using quorum of 3 for new set of 5 trusted validators 2018-Jan-08 00:45:04 LedgerConsensus:NFO Entering consensus process, watching, synced=no 2018-Jan-08 00:45:04 LedgerConsensus:NFO Consensus mode change before=observing, after=observing 2018-Jan-08 00:45:04 NetworkOPs:DBG Initiating consensus engine 2018-Jan-08 00:45:04 Server:NFO Opened 'port_rpc_admin_local' (ip=127.0.0.1:5006, admin IPs:127.0.0.1, http) 2018-Jan-08 00:45:04 Server:NFO Opened 'port_peer' (ip=0.0.0.0:51235, peer) 2018-Jan-08 00:45:04 Server:NFO Opened 'port_ws_admin_local' (ip=127.0.0.1:6006, admin IPs:127.0.0.1, ws) 2018-Jan-08 00:45:04 Server:NFO Opened 'port_ws_public' (ip=my.ip.addr:5005, wss) 2018-Jan-08 00:45:04 Application:FTL Startup RPC: { "command" : "log_level", "severity" : "info" } 2018-Jan-08 00:45:04 Application:FTL Result: {} 2018-Jan-08 00:45:04 PeerFinder:NFO Opening database at '/var/lib/rippled/db/peerfinder.sqlite' 2018-Jan-08 00:45:04 PeerFinder:NFO Opened version 4 database 2018-Jan-08 00:45:04 PeerFinder:NFO Bootcache loaded 187 addresses 2018-Jan-08 00:45:04 Application:NFO Application starting. Version is 0.80.2 2018-Jan-08 00:45:04 PeerFinder:NFO Logic added 0 new addresses from config: r.ripple.com 51235 2018-Jan-08 00:45:05 NetworkOPs:NFO STATE->connected 2018-Jan-08 00:45:05 NetworkOPs:NFO Node count (0) is sufficient. 2018-Jan-08 00:45:05 Peer:NFO [011] Public Key: n9KiJ4JHhajZ3mQ2k29ekz1ixnDYaQdF6bNi2hiKDhRM9nhwaLfW 2018-Jan-08 00:45:05 Peer:NFO [011] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.239.120.20:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [014] Public Key: n9MXY1xfS1VWmazwoYc98zvS28eVu1RQcYhWNKmzqxHd56oeRHQC 2018-Jan-08 00:45:05 Peer:NFO [014] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 52.55.102.204:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [010] Public Key: n9LGt2t1h1P76SnG86sEBTGdT6GrfxcT23KZ4nZX7xbGDYu3Y8Fc 2018-Jan-08 00:45:05 Peer:NFO [010] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.201.251.148:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [009] Public Key: n94KWZ9yJNJhaSqnn1S4K7Kna7ciaVBpjrqgHHyBM6g6NfgRAXT5 2018-Jan-08 00:45:05 Peer:NFO [009] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 184.72.137.59:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [019] Public Key: n9MqFgf89C1Q81rUXmunZjhFr1sZwaaQYoknVzTVwNC9ky9u2Mxb 2018-Jan-08 00:45:05 Peer:NFO [019] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.229.128.152:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [012] Public Key: n9Jt8awsPzWLjBCNKVEEDQnw4bQEPjezfcQ4gttD1UzbLT1FoG99 2018-Jan-08 00:45:05 Peer:NFO [012] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 52.90.42.69:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [013] Public Key: n94hKvqUffbA2cY49wz2Q7X2JoxtFW9o4dcWi6CSzUfXDTt3MWEi 2018-Jan-08 00:45:05 Peer:NFO [013] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 34.201.105.122:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [006] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:05 Peer:NFO [002] Public Key: n9KJb7NMxGySRcjCqh69xEPMUhwJx22qntYYXsnUqYgjsJhNoW7g 2018-Jan-08 00:45:05 Peer:NFO [002] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 54.84.21.230:51235 with 33 successes 2018-Jan-08 00:45:05 Peer:NFO [018] Public Key: n9LnqwvUxFBUdnS1JzbziohwVium9EkYL5i7TuTx2TvPSskPPcVs 2018-Jan-08 00:45:05 Peer:NFO [018] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 169.54.2.157:51235 with 1 success 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #1 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #2 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #3 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #4 2018-Jan-08 00:45:05 Protocol:NFO [010] Untrusted manifest #5 2018-Jan-08 00:45:05 Peer:NFO [008] Public Key: n94rE1SydpHTvJ4NyX9vC1cdeDmYP5nQSXTyeMnLh8jMJSRdcy9Q 2018-Jan-08 00:45:05 Peer:NFO [008] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 54.86.175.122:51235 with 33 successes 2018-Jan-08 00:45:05 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:05 Peer:NFO [017] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:05 Peer:NFO [005] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:05 Peer:NFO [001] Public Key: n9JAeNYjfb1Uzf5RHRpvDbYTvVNgPWiUfPUhdDtakQ1yXJ32n51c 2018-Jan-08 00:45:05 Peer:NFO [001] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 184.173.45.38:51235 with 33 successes 2018-Jan-08 00:45:05 Peer:NFO [020] Public Key: n9MGChK9EgiCBM6s15EwF9d6m4LWZHh1UnJcgr16kQr4xBpx71fS 2018-Jan-08 00:45:05 Peer:NFO [020] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 198.11.206.6:51235 with 1 success 2018-Jan-08 00:45:05 Peer:NFO [004] Public Key: n9LieQkojpM1wsqman9d8jxVXrLxRh8RAmwv5rDvC5ea3kxnEVUn 2018-Jan-08 00:45:05 Peer:NFO [004] Protocol: 1.2 2018-Jan-08 00:45:05 PeerFinder:NFO Bootcache connect 198.11.206.26:51235 with 33 successes 2018-Jan-08 00:45:05 Peer:NFO [016] HTTP Response: Service Unavailable Service Unavailable 2018-Jan-08 00:45:06 Peer:NFO [003] Public Key: n9MT5EjnV912KGuBUqPs4tpdhzMPGcnDBrTuWkD9sWQHJ1kDcUcz 2018-Jan-08 00:45:06 Peer:NFO [003] Protocol: 1.2 2018-Jan-08 00:45:06 PeerFinder:NFO Bootcache connect 54.186.248.91:51235 with 33 successes 2018-Jan-08 00:45:06 Peer:NFO [007] Public Key: n9JySgyBVcQKvyDoeRKg7s2Mm6ZcFHk22vUZb3o1HSosWxcj9xPt 2018-Jan-08 00:45:06 Peer:NFO [007] Protocol: 1.2 2018-Jan-08 00:45:06 PeerFinder:NFO Bootcache connect 54.186.73.52:51235 with 33 successes 2018-Jan-08 00:45:06 LedgerConsensus:WRN View of consensus changed during open status=open, mode=observing 2018-Jan-08 00:45:06 LedgerConsensus:WRN 95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072 to 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:06 LedgerConsensus:WRN { "accepted" : true, "account_hash" : "183D5235C7C1FB5AE67AD2F6CC3B28F5FB86E8C4F89DB50DD85641A96470534E", "close_flags" : 0, "close_time" : 568687500, "close_time_human" : "2018-Jan-08 00:45:00", "close_time_resolution" : 30, "closed" : true, "hash" : "95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072", "ledger_hash" : "95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072", "ledger_index" : "2", "parent_close_time" : 0, "parent_hash" : "AB868A6CFEEC779C2FF845C0AF00A642259986AF40C01976A7F842B6918936C7", "seqNum" : "2", "totalCoins" : "100000000000000000", "total_coins" : "100000000000000000", "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000" } 2018-Jan-08 00:45:06 LedgerConsensus:WRN Need consensus ledger 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:06 LedgerConsensus:NFO Consensus mode change before=observing, after=wrongLedger 2018-Jan-08 00:45:06 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:06 Peer:NFO [015] Public Key: n9KybMFrer7erpQDh58epdQkQga3pSaVYhD855h4gTkHtMUGVMx2 2018-Jan-08 00:45:06 Peer:NFO [015] Protocol: 1.2 2018-Jan-08 00:45:06 PeerFinder:NFO Bootcache connect 52.78.78.122:51235 with 1 success 2018-Jan-08 00:45:07 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:08 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:08 LedgerConsensus:NFO Proposers:5 nw:50 thrV:2 thrC:4 2018-Jan-08 00:45:08 LedgerConsensus:NFO Position change: CTime 568687501, tx 850CD9248733D95D8B3A79F452966CBCDFB4AAF01E48FCDD5B56EF9E943DF4A2 2018-Jan-08 00:45:08 LedgerConsensus:NFO Converge cutoff (5 participants) 2018-Jan-08 00:45:08 LedgerConsensus:NFO CNF buildLCL CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226 2018-Jan-08 00:45:08 NetworkOPs:WRN We are not running on the consensus ledger 2018-Jan-08 00:45:08 NetworkOPs:NFO Our LCL: { "accepted" : true, "account_hash" : "A0D5E308F7D3104D15CC4D73E6C0E88C17073FEF30F3AE9C09AB4A214A9390B4", "close_flags" : 0, "close_time" : 568687501, "close_time_human" : "2018-Jan-08 00:45:01", "close_time_resolution" : 30, "closed" : true, "hash" : "CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226", "ledger_hash" : "CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226", "ledger_index" : "3", "parent_close_time" : 568687500, "parent_hash" : "95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072", "seqNum" : "3", "totalCoins" : "100000000000000000", "total_coins" : "100000000000000000", "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000" } 2018-Jan-08 00:45:08 NetworkOPs:NFO Net LCL 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:08 NetworkOPs:NFO Consensus time for #4 with LCL CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226 2018-Jan-08 00:45:08 LedgerConsensus:NFO Entering consensus process, watching, synced=no 2018-Jan-08 00:45:08 LedgerConsensus:NFO Entering consensus with: 95A051FC5BC21820E6456FEB37C13AE530EE985A7A5C6837292DE961BEF73072 2018-Jan-08 00:45:08 LedgerConsensus:NFO Correct LCL is: 4ADAA6C071BBDF11BED45E907735449A944E1A7046D8487FF82DA9CA1B402D87 2018-Jan-08 00:45:08 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:08 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:09 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:09 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 NetworkOPs:NFO Not relaying trusted proposal 2018-Jan-08 00:45:10 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:10 LedgerConsensus:NFO Proposers:5 nw:50 thrV:2 thrC:4 2018-Jan-08 00:45:10 LedgerConsensus:NFO Position change: CTime 568687502, tx 850CD9248733D95D8B3A79F452966CBCDFB4AAF01E48FCDD5B56EF9E943DF4A2 2018-Jan-08 00:45:10 LedgerConsensus:NFO Converge cutoff (5 participants) 2018-Jan-08 00:45:10 LedgerConsensus:NFO CNF buildLCL 11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149 2018-Jan-08 00:45:10 NetworkOPs:WRN We are not running on the consensus ledger 2018-Jan-08 00:45:10 NetworkOPs:NFO Our LCL: { "accepted" : true, "account_hash" : "B0FD2544671D7B6FF68C11E316B61FAD2C00357D6B264835D28DB4AFD0596329", "close_flags" : 0, "close_time" : 568687502, "close_time_human" : "2018-Jan-08 00:45:02", "close_time_resolution" : 30, "closed" : true, "hash" : "11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149", "ledger_hash" : "11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149", "ledger_index" : "4", "parent_close_time" : 568687501, "parent_hash" : "CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226", "seqNum" : "4", "totalCoins" : "100000000000000000", "total_coins" : "100000000000000000", "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000" } 2018-Jan-08 00:45:10 NetworkOPs:NFO Net LCL BEC11E7A648417D571EEEB34AB5BB0AE79A0E2B94291F56E6B4B534A01677CA2 2018-Jan-08 00:45:10 NetworkOPs:NFO Consensus time for #5 with LCL 11FE35F315D026ED3141A105A5C4F8AD41B189E8E9D4481C53A6CDB1052EE149 2018-Jan-08 00:45:10 LedgerConsensus:NFO Entering consensus process, watching, synced=no 2018-Jan-08 00:45:10 LedgerConsensus:WRN Need consensus ledger BEC11E7A648417D571EEEB34AB5BB0AE79A0E2B94291F56E6B4B534A01677CA2 2018-Jan-08 00:45:10 LedgerConsensus:NFO Entering consensus with: CA17059A82993E7EF47DC1994476F2F60EB5B2C274B68FE2AB6656D5F55DC226 2018-Jan-08 00:45:10 LedgerConsensus:NFO Correct LCL is: BEC11E7A648417D571EEEB34AB5BB0AE79A0E2B94291F56E6B4B534A01677CA2 2018-Jan-08 00:45:10 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:10 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger 2018-Jan-08 00:45:10 LoadMonitor:WRN Job: processLedgerData run: 2058ms wait: 0ms 2018-Jan-08 00:45:11 LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger Killed If I run: ps -eo pid,comm,lstart,etime,time,args | grep rippled I can see: 22497 rippled: #142 Mon Jan 8 00:12:37 2018 30:29 00:00:00 /opt/ripple/bin/rippled --net 25235 rippled: main Mon Jan 8 00:43:02 2018 00:04 00:00:00 /opt/ripple/bin/rippled --net The duration of the main process never exceeds 0:15 or so, which strikes me as the root issue, however the numbered child process is fine. **It is also worth noting that if I run rippled in standalone mode, this issue doesn't occur, but then I am obviously unable to query any account info.** I've dug this forum and others for possible solutions as to why I would be seeing this, but I continue to hit dead ends. If anybody here has any ideas for what to look at, I would be incredibly grateful! Thank you! - Johnny

Hi, I really would like to know if and if yes, where solutions are available (specific XRP) in order to make it easy for businesses to accept XRP from consumers. Next to that also information about possible solutions for banks so they can hold XRP for consumers and consumers to be able to pay directly from their accounts with online banking. Asking banks to do this with BTC or whatever other crypto currency is naturally useless, but XRP of all crypto currencies is just the one in place to pull this off. I understand Ripple having a focus on the institutional side of this, but they could easily set up a spin-off company that solely focuses on adoption by consumer banks and their customers and businesses. This way general presence and market adoption would be pushed like hell. The fact that it is still volatile nowadays is less of a problem because the market has begun to accept that having had the previous experience with BTC already. So it is to be expected that as more market acceptance and use are generated the price will go up (with a correction from time to time). So please inform about possible available solutions and/or how you all think this is going to be played.

Are there any Ripple developers here that have built anything cool? Please share what you''ve made. Thx.

This thread is to ask if anyone else has noticed software bugs on the exchanges. Good programmers understand the importance of writing good code, but nevertheless, in my experience this seems to be the exception, rather than the rule. This evening, I sent a customer support ticket to Poloniex. In order to do so, I had to create a new account, because there was an apparent software bug in the system that would not allow me to enter the support system with my other account. Here is what I wrote: "Hi, I'm a newer user of your exchanged, but I've noticed a number of apparent bugs in your system. First, when I try to access the support center email system from my other account email and password, stopbeingsoedgarallanpolish@yahoo.com and XXXXXXXX, your system gives me an error, saying it's the incorrect password, and I am currently down to two more tries, before I am locked out of the system. Yet, I am able to log in and out for trading, with no problem. This error occurs whether I am already logged in, or not. Second, last night, as well as on other occasions, I tried to close PART of a margin position an enumerable number of times, and each time that I tried to do so, I received no message, and NO ORDER WAS PLACED. Unless you don't allow users to close partial positions, and you're not telling your users, this appears to be an major bug. Third, and slightly similar to the issue above, in wanting to close a partial margin position at market, I've noticed there appears to be no way of doing so. Trying to set a stop-limit order in a fast moving market is nearly impossible. Yet, that's the way your exchange appears to be set up. Is that correct? If so, is that by intent? I hope you will look at these issues, and provide some feedback as to what is going on, especially on how one can close close at market part of an open margin or exchange position, instead of the whole position, at once. Trying to use a market order, which is apparently the case when the close all button is selected to suddenly close out what amounts to a large number of bitcoins, can disadvantageously move a thinly traded market. The system might not work right, but if you fix or include one thing, this one would be most appreciated. Thanks," Nutcake Ok, that's been my experience, which doesn't speak well of the Polo SW developers. And you've got to remember, for every mouse you see in the house... Perhaps there is something I haven't been doing correctly, and their customer service people will set me straight. But software defects are usually pretty obvious to programmers, and bugs in financial software should be non-existent, or at least not very noticeable. Has anyone else seen apparent problems that lead to questions about the quality of an exchange's software?

I started this topic because I am tired of waiting for someone else to furnish a hardware wallet to the Ripple/XRP community. I'm a former product developer, with hardware and software experience. This project will need skill-sets in hardware development, micro-computer coding, internet coding, testing, and manufacturing. I feel that with the right group of people we can make a world class HW Wallet that will enhance the value of XRP (besides giving everyone a convenient and safe place to store their XRP). Beyond that, we can leverage the knowledge gained, with our experience, to go on to bigger and better things with Ripple. This project should be considered a commercial project, and sales profits of the wallet will be distributed to the team. In other words, this is a serious development project for experienced people, willing and able to put in the time and effort. If you are interested, please post here, talking about your skill set and how this could proceed.