Jump to content

Search the Community

Showing results for tags 'rippled'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Ripple
    • Please Read Before Posting
    • Press
    • General Discussion
    • Technical Discussion
    • Codius and Smart Contracts
    • Marketplace
  • Interledger Protocol
    • Interledger Protocol Discussion
  • Other Technology
    • Alt-Coins and General Fintech
  • More
    • Off-Topic
    • Meta
    • Languages
  • Canadian Zerpers's Topics
  • Vegemite Ripplers's Topics
  • 2 the Moon! For Real. The Club's Topics
  • NY Zerpers - aka bitlicense island's Topics
  • Brackish Waters Club's Topics
  • Trading Places's Topics
  • Anti-Club Club's Topics
  • The Irish Brigade's Topics
  • Saloon's Request
  • XRP Trading And Price Speculation's Topics
  • The Crypto Buffett's Topics
  • Alt-Coin Trading And Price Speculation's Topics
  • Super serious Ripple club's Topics
  • Making Millions!'s Topics
  • Ripple - India's Topics
  • SWELL's Topics
  • Gospel Hour's Topics
  • Korean XRP Holders's Topics
  • Strayans lovin your work XRP!!!'s Topics
  • Technical Analysis (TA) Area's Topics
  • BTC diving deep club's Topics
  • Ripple Enamel Pin Club's Topics
  • XRP Wave Surfers's Topics
  • FUDster's retreat's Topics
  • The Zerpening's Topics
  • Cooking with Snoopy's Topics
  • How it's all going to happen..'s Topics
  • Chocolate Fish's Topics
  • The Round Table's Topics
  • UK Hodlers's Topics
  • ˜”*°• Zerpmania •°*”˜'s Topics
  • XRP YouTube Videos's Topics

Calendars

  • Ripple Events
  • Vegemite Ripplers's Events
  • NY Zerpers - aka bitlicense island's Events
  • Brackish Waters Club's Events
  • Trading Places's Events
  • Anti-Club Club's Events
  • The Irish Brigade's Events
  • Saloon's Calendar
  • XRP Trading And Price Speculation's Events
  • The Crypto Buffett's Calendar
  • Alt-Coin Trading And Price Speculation's Events
  • Super serious Ripple club's Events
  • Making Millions!'s Events
  • Ripple - India's Events
  • SWELL's Events
  • Gospel Hour's Events
  • Korean XRP Holders's Events
  • Strayans lovin your work XRP!!!'s Events
  • Technical Analysis (TA) Area's Events
  • BTC diving deep club's Events
  • Ripple Enamel Pin Club's Events
  • XRP Wave Surfers's Events
  • FUDster's retreat's Events
  • The Zerpening's Events
  • Cooking with Snoopy's Events
  • Chocolate Fish's Events
  • The Round Table's Events
  • UK Hodlers's Events
  • XRP YouTube Videos's Events

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Interests


Location


Occupation


Country


Ripple Address


Biography


Location


Interests


Occupation

Found 31 results
Minimum search term is 4 characters long. Can't find what you want? Click here for the custom google search instead.

  1. https://ripple.com/dev-blog/rippled-version-0-90-1/ Hotfix release that patches some crash bugs (including several reported by Guido Vranken, whose work is impressive). No new features or other changes. Along with the release itself, Ripple is starting to vote in favor of the Checks, DepositAuth, and fix1513 amendments, so expect those to turn on in 2 weeks. (Note to self: update the "Known Amendments" page with the updated expected time)
  2. Hi everyone! First off, let me apologize for cross-posting. I know this is a major faux pas, but realize now that "Problem Solving" was the wrong place. Anyhow... I am brand new to Ripple in general, but a friend of mine has watched 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
  3. When running rippled on Centos 6 using the yum package, you may encounter this error: Or something to the effect that 1024 file descriptors are available and 4096 were requested from rippled, so it shut down. To fix this error, open /etc/security/limits.conf and at the bottom of the file add: Next, open /etc/sysctl.conf and at the bottom of the file add: Run ulimit -Ha to check if open files has been updated to 10240, such as: Execute service rippled start and it should operate correctly.
  4. Hello! I usually don't post into technical, because I don't know much of the technicals. I bumped into this on Ripple's website and just wanted to ask what it means. Someone who knows can give a sort of ELI5 kind of answer https://ripple.com/build/build-run-rippled-ubuntu/ Lose money in the sense of losing the transactions to hackers with wrong kind of data or just lose money in the sense of "your validator is outdated and does not any bring anything to the network, thus you're wasting resources while running it". Thanks.
  5. Last night we added several new pieces of documentation to the XRP Ledger in preparation for the upcoming release of rippled 0.90.0: Deposit Authorization is a new feature for compliance with regulations such as the New York Bitlicense. In addition to the concept page, the flag has been added in appropriate places such as the AccountSet transaction reference. Checks documentation has been added to the transaction reference and ledger reference. Checks are a feature originally conceived back in, like, 2012 or something, which got new life recently when we realized they'd solve one of the challenges with Deposit Authorization. We also added specific instructions for how to build and run rippled 0.90.0 and higher on Ubuntu Linux. That's important, because rippled 0.90.0 must be compiled against the latest version of Boost, which now includes Vinnie Falco's Beast library (originally developed to use in rippled). There'll be more coming out in the coming days, including an article on another key 0.90.0 feature, history sharding. I can't give a specific release date for 0.90.0, but the feature set is final, as we're just now polishing up the details and ironing out the bugs. As per usual, it'll be out soon—when it's ready—and no sooner. P.S. if you want to try out Checks and Deposit Auth leading up to the release, they're already available for use on the Test Net.
  6. I am trying to send a payment using ripple-lib, and I am getting this error: Here is my code: Thanks so much!
  7. https://ripple.com/dev-blog/rippled-version-0-81-0/ This is a big step towards decentralizing control of the XRP Ledger! Update your validator settings!
  8. i am trying to start an private ripple blockchain with one validator but when i check the status it gives me error root@admin1-OptiPlex-9020:~# sudo systemctl status rippled.service ● rippled.service - Ripple Daemon Loaded: loaded (/usr/lib/systemd/system/rippled.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/rippled.service.d └─nofile_limit.conf Active: inactive (dead) since Wed 2017-07-19 13:58:15 IST; 3min 36s ago Process: 4254 ExecStart=/opt/ripple/bin/rippled --net --silent --conf /etc/opt/ripple/rippled.cfg (code=exited, status=0/SUCCESS) Main PID: 4254 (code=exited, status=0/SUCCESS) Jul 19 13:57:25 admin1-OptiPlex-9020 rippled[4254]: Watchdog: Launching child 1 Jul 19 13:57:25 admin1-OptiPlex-9020 rippled[4254]: Terminating thread rippled: main: unhandled N4soci18sqlite3_soci_errorE 'Cannot establish c Jul 19 13:57:35 admin1-OptiPlex-9020 rippled[4254]: Watchdog: Launching child 2 Jul 19 13:57:35 admin1-OptiPlex-9020 rippled[4254]: Terminating thread rippled: main: unhandled N4soci18sqlite3_soci_errorE 'Cannot establish c Jul 19 13:57:45 admin1-OptiPlex-9020 rippled[4254]: Watchdog: Launching child 3 Jul 19 13:57:45 admin1-OptiPlex-9020 rippled[4254]: Terminating thread rippled: main: unhandled N4soci18sqlite3_soci_errorE 'Cannot establish c Jul 19 13:57:55 admin1-OptiPlex-9020 rippled[4254]: Watchdog: Launching child 4 Jul 19 13:57:55 admin1-OptiPlex-9020 rippled[4254]: Terminating thread rippled: main: unhandled N4soci18sqlite3_soci_errorE 'Cannot establish c Jul 19 13:58:05 admin1-OptiPlex-9020 rippled[4254]: Watchdog: Launching child 5 My rippled.cfg -- [server] port_rpc_admin_local port_peer port_ws_admin_local #port_ws_public #ssl_key = /etc/ssl/private/server.key #ssl_cert = /etc/ssl/certs/server.crt [port_rpc_admin_local] port = 5005 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 = 127.0.0.1 #protocol = wss #------------------------------------------------------------------------------- [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 # Where to find some other servers speaking the Ripple protocol. # [ips] #r.ripple.com 51235 [validator_token] ey-------------------------------------token # 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": "warning" } # 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] 1 Please help me to resolve it
  9. Wow guys, what a horrible day. It only seems like its going to get worse. Looks like there is absolutely no buy support as the bears are demolishing the price of XRP. It may even end up cheaper than when the AMEX partnership was announced. Crazy right? I really don't get it. What I do get is that lots of people are probably losing money at this point on this trade if they bought on the way up. This is another pump and dump. Sickening. I'm tired of Ripple doing this every single time. I have made so much more money with Stellar Lumens. I'll keepp Holding because you don't realize a loss until you sell, but my God this is frustrating. Not to mention the opportunity cost since you are basically stuck in a trade. Will we ever catch a real break with XRP? God help us!
  10. TiffanyHayden

    Routing attacks

    I have been reading about Bitcoin routing attacks and I'm wondering how things differ with Ripple. Quick summary of what I read: Bitcoin uses a general gossip protocol which broadcasts all transactions to the network. Internet routing infrastructure is insecure and can easily be manipulated by attackers to intercept Bitcoin traffic. Bitcoin messages are exchanged in clear text and without integrity checks, any (malicious) third-party on the forwarding path can eavesdrop, drop, modify, inject, or delay Bitcoin messages. Bitcoin is extremely centralized from an Internet routing perspective. (Only 13 ASes host 30% of the entire network, while 50 ASes host 50% of the Bitcoin network.) Any malicious ISP with access to the Internet routing infrastructure can perform a routing attack by partitioning the Bitcoin network and isolating 50% of its mining power. Any ISP transiting Bitcoin traffic can delay the propagation of mined blocks (for up to 20 minutes), in a stealth way. Many examples of actual routing attacks that ended up diverting Bitcoin traffic have been found. So, how does Ripple differ? How are transactions broadcast? I'm assuming end-to-end encryption isn't used, because then validators wouldn't be able to see what they're validating?
  11. Hi, I am running two servers locally (ledger fork), it seems to be working. So far I've created two new accounts and sent XRP to both from the genesis acct. I then created trust-lines from the new accounts to the genesis acct and issued IOU currency from the genesis to the other two accounts. I've preformed multiple transfer operations via API and sent IOU back and forth. Rippling worked well, all transfers were completed and I was able to verify balances via API. Now I'd like to view the transaction details for each account, but not getting the desired result. to view account_lines on the genesis account: /opt/ripple/bin/rippled account_lines rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh { "id" : 1, "result" : { "account" : "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh", "ledger_current_index" : 158533, "lines" : [ { "account" : "rhBwgZf5dA5HbWJKnrztePviUQmWTf4kwh", "balance" : "-1120", "currency" : "USD", "limit" : "0", "limit_peer" : "91500", "quality_in" : 0, "quality_out" : 0 }, { "account" : "rHfx7bE1USYJE5Vmh9VbVFrJbc4a76tu4s", "balance" : "-10000", "currency" : "USD", "limit" : "0", "limit_peer" : "86500", "quality_in" : 0, "quality_out" : 0 } ], "status" : "success", "validated" : false } } seems to be correct. The same information is displayed after I stop both servers, meaning they are in sync and persistence is working? /opt/ripple/bin/rippled account_info rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh validated: { "id" : 1, "result" : { "account_data" : { "Account" : "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh", "Balance" : "99997649999448428", "Flags" : 8388608, "LedgerEntryType" : "AccountRoot", "OwnerCount" : 0, "PreviousTxnID" : "C86538FAED7912EFE185B322907B0FEED47C870ED612D6519F726E98AAFEA8F7", "PreviousTxnLgrSeq" : 128917, "Sequence" : 132, "index" : "2B6AC232AA4C4BE41BF49D2459FA4A0347E1B543A4C92FCEE0821C0201E2E9A8" }, "ledger_hash" : "9B697B5B93794270C837464A5ABA757066B9646D5DB1BF588BC7DE548A051E60", "ledger_index" : 158492, "status" : "success", "validated" : true } } I'd like to see transaction details for the PreviousTxnID: /opt/ripple/bin/rippled tx C86538FAED7912EFE185B322907B0FEED47C870ED612D6519F726E98AAFEA8F7 { "id" : 1, "result" : { "error" : "txnNotFound", "error_code" : 28, "error_message" : "Transaction not found.", "request" : { "command" : "tx", "transaction" : "C86538FAED7912EFE185B322907B0FEED47C870ED612D6519F726E98AAFEA8F7" }, "status" : "error" } } Transaction not found, why? I've read this article about this error but not sure what to do to fix this: https://ripple.com/build/reliable-transaction-submission/ how can I check/test both cases? also not getting any luck if I try to view all transactions for the genesis account: /opt/ripple/bin/rippled account_tx rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh { "id" : 1, "result" : { "error" : "lgrNotValidated", "error_code" : 21, "error_message" : "Ledger not validated.", "request" : { "account" : "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh", "command" : "account_tx" }, "status" : "error" } } further troubleshooting, viewing account_object, not sure what to pay attention to here: /opt/ripple/bin/rippled account_objects rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh { "id" : 1, "result" : { "account" : "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh", "account_objects" : [ { "Balance" : { "currency" : "USD", "issuer" : "rrrrrrrrrrrrrrrrrrrrBZbvji", "value" : "1120" }, "Flags" : 65536, "HighLimit" : { "currency" : "USD", "issuer" : "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh", "value" : "0" }, "HighNode" : "0000000000000000", "LedgerEntryType" : "RippleState", "LowLimit" : { "currency" : "USD", "issuer" : "rhBwgZf5dA5HbWJKnrztePviUQmWTf4kwh", "value" : "91500" }, "LowNode" : "0000000000000000", "PreviousTxnID" : "4409963786C92939C3220E9C2E0D46A418D9D4E14C88969F0A132130173BF411", "PreviousTxnLgrSeq" : 151601, "index" : "B13A9EC73431FC0B319389ABA44DE1FBBFD849FFBE27816C7A4B9DD826B503C0" }, { "Balance" : { "currency" : "USD", "issuer" : "rrrrrrrrrrrrrrrrrrrrBZbvji", "value" : "10000" }, "Flags" : 65536, "HighLimit" : { "currency" : "USD", "issuer" : "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh", "value" : "0" }, "HighNode" : "0000000000000000", "LedgerEntryType" : "RippleState", "LowLimit" : { "currency" : "USD", "issuer" : "rHfx7bE1USYJE5Vmh9VbVFrJbc4a76tu4s", "value" : "86500" }, "LowNode" : "0000000000000000", "PreviousTxnID" : "4409963786C92939C3220E9C2E0D46A418D9D4E14C88969F0A132130173BF411", "PreviousTxnLgrSeq" : 151601, "index" : "C29A2B914AF8B5B5C1C18235AC96D22B090D02E1F593ABC7DD537C2BE8D8A398" } ], "ledger_current_index" : 158646, "status" : "success", "validated" : false } } here's my server_state: { "id" : 1, "result" : { "state" : { "build_version" : "0.70.1", "complete_ledgers" : "156002-158575", "io_latency_ms" : 1, "last_close" : { "converge_time" : 2000, "proposers" : 1 }, "load" : { "job_types" : [ { "in_progress" : 1, "job_type" : "clientCommand" }, { "job_type" : "peerCommand", "per_second" : 1 } ], "threads" : 8 }, "load_base" : 256, "load_factor" : 256, "peers" : 1, "pubkey_node" : "n9KHec9cJXXgaHT4nYCQQgCq3Miaz4tXab9HPNAVPUfCkZiThmfy", "pubkey_validator" : "none", "server_state" : "full", "state_accounting" : { "connected" : { "duration_us" : "3003948", "transitions" : 1 }, "disconnected" : { "duration_us" : "1238259", "transitions" : 1 }, "full" : { "duration_us" : "2191436885", "transitions" : 1 }, "syncing" : { "duration_us" : "2001013", "transitions" : 1 }, "tracking" : { "duration_us" : "7", "transitions" : 1 } }, "uptime" : 2198, "validated_ledger" : { "base_fee" : 10, "close_time" : 556986221, "hash" : "3F8EB07A93F31F8E83589E7377819C559D85EAFD2568F87ABB574F95C1A452B1", "reserve_base" : 20000000, "reserve_inc" : 5000000, "seq" : 158575 }, "validation_quorum" : 1 }, "status" : "success" } } and server_info: { "id" : 1, "result" : { "info" : { "build_version" : "0.70.1", "complete_ledgers" : "156002-158582", "hostid" : "osboxes", "io_latency_ms" : 1, "last_close" : { "converge_time_s" : 1.999, "proposers" : 1 }, "load" : { "job_types" : [ { "in_progress" : 1, "job_type" : "clientCommand" } ], "threads" : 8 }, "load_factor" : 1, "peers" : 1, "pubkey_node" : "n9KHec9cJXXgaHT4nYCQQgCq3Miaz4tXab9HPNAVPUfCkZiThmfy", "pubkey_validator" : "none", "server_state" : "full", "state_accounting" : { "connected" : { "duration_us" : "3003948", "transitions" : 1 }, "disconnected" : { "duration_us" : "1238259", "transitions" : 1 }, "full" : { "duration_us" : "2211203188", "transitions" : 1 }, "syncing" : { "duration_us" : "2001013", "transitions" : 1 }, "tracking" : { "duration_us" : "7", "transitions" : 1 } }, "uptime" : 2218, "validated_ledger" : { "age" : 2, "base_fee_xrp" : 1e-05, "hash" : "FFFEFFE38B65DE96DD5E4108114B5B68306574D97D3C082B8234D985F42C6028", "reserve_base_xrp" : 20, "reserve_inc_xrp" : 5, "seq" : 158582 }, "validation_quorum" : 1 }, "status" : "success" } } any help would be greatly appreciated!
  12. I am wondering about the implications of opening port 51235 on a rippled validator or node (running in front of a validator). I assume doing so would carry a risk of DDoS attacks, however, it also provides other nodes with access to the ledger. In other words, it seems like there is a minor security risk and a reasonable benefit for the community. From what I understand, rippled nodes will connect to any peer to get the ledger. Is this so, or do they only connect to trusted peers? Finally, is there any reason to include my IP in the [ips] section on my ripple.txt, if port 51235 is closed? Thanks so much!
  13. Hi, I am running two VMs with rippled servers, one as stock and another as validator. I started the stock server with -a, then I stopped and restarted it with --start. The config of the stock server is pointing to the validator. Then I started validator and both servers seem to be connected. I then submitted a transaction to send XRP from genesis address to a newly generated address. The transaction went through and XRP balances got updated. I can confirm this on both servers with "rippled account_info #ADDR#" for each account. Great, however then I stop the validator and restart it, expecting to see the same balances as they were prior to restart, however the ledger gets reset. The genesis account has an original amount in it and the newly created account to which I've transferred XRP in the previous session is no longer found. How come this is happening and what am I doing wrong with my setup? stock server log: 2017-Aug-16 13:13:16 NetworkOPs:NFO Consensus time for #1664 with LCL 7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236 2017-Aug-16 13:13:16 LedgerConsensus:NFO Entering consensus process, watching 2017-Aug-16 13:13:18 Peer:WRN [022] onReadMessage: short read 2017-Aug-16 13:13:19 LedgerConsensus:NFO Proposers:1 nw:50 thrV:1 thrC:1 2017-Aug-16 13:13:19 LedgerConsensus:NFO Converge cutoff (1 participants) 2017-Aug-16 13:13:19 LedgerConsensus:NFO CNF buildLCL F6C117EC8731DC304A4B8DC7143D557840EA82B2B44F23DED11216F3882C2372 2017-Aug-16 13:13:19 LedgerConsensus:NFO We closed at 556204397 2017-Aug-16 13:13:19 LedgerConsensus:NFO 1 time votes for 556204397 2017-Aug-16 13:13:19 LedgerConsensus:NFO Our close offset is estimated at 0 (2) 2017-Aug-16 13:13:19 NetworkOPs:NFO Consensus time for #1665 with LCL F6C117EC8731DC304A4B8DC7143D557840EA82B2B44F23DED11216F3882C2372 2017-Aug-16 13:13:19 LedgerConsensus:NFO Entering consensus process, watching 2017-Aug-16 13:13:42 LedgerConsensus:NFO Converge cutoff (0 participants) 2017-Aug-16 13:13:42 LedgerConsensus:NFO CNF buildLCL 7F988A5EDDF16EBB0202FB879295DB3A2C8BCC722685F04162813841EFECCC17 2017-Aug-16 13:13:42 LedgerConsensus:NFO We closed at 556204420 2017-Aug-16 13:13:42 LedgerConsensus:NFO Our close offset is estimated at 0 (1) 2017-Aug-16 13:13:42 NetworkOPs:WRN We are not running on the consensus ledger 2017-Aug-16 13:13:42 NetworkOPs:NFO Our LCL: { "accepted" : true, "account_hash" : "1ECEF6EA6F3959C7A9A55A848F0D176261722E1009360965A5D00A5A3953D1A2", "close_flags" : 0, "close_time" : 556204420, "close_time_human" : "2017-Aug-16 13:13:40", "close_time_resolution" : 10, "closed" : true, "hash" : "7F988A5EDDF16EBB0202FB879295DB3A2C8BCC722685F04162813841EFECCC17", "ledger_hash" : "7F988A5EDDF16EBB0202FB879295DB3A2C8BCC722685F04162813841EFECCC17", "ledger_index" : "1665", "parent_close_time" : 556204400, "parent_hash" : "F6C117EC8731DC304A4B8DC7143D557840EA82B2B44F23DED11216F3882C2372", "seqNum" : "1665", "totalCoins" : "99999999999999988", "total_coins" : "99999999999999988", "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000" } 2017-Aug-16 13:13:42 NetworkOPs:NFO Net LCL 7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236 2017-Aug-16 13:13:42 NetworkOPs:NFO STATE->syncing 2017-Aug-16 13:13:42 NetworkOPs:ERR JUMP last closed ledger to 7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236 2017-Aug-16 13:13:42 NetworkOPs:NFO Consensus time for #1664 with LCL 7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236 2017-Aug-16 13:13:42 LedgerConsensus:NFO Entering consensus process, watching 2017-Aug-16 13:13:44 LedgerConsensus:WRN Removing stale proposal from BABF6A89E9113E8298A959982C186000CA11AB7F 2017-Aug-16 13:13:44 LedgerConsensus:NFO Converge cutoff (0 participants) 2017-Aug-16 13:13:44 LedgerConsensus:NFO CNF buildLCL 40F90A131285E06DCE0735A409C231E33300B02E806BC4FCBACB938109B541F4 2017-Aug-16 13:13:44 LedgerConsensus:NFO We closed at 556204422 2017-Aug-16 13:13:44 LedgerConsensus:NFO 1 time votes for 556204397 2017-Aug-16 13:13:44 LedgerConsensus:NFO Our close offset is estimated at -12 (2) 2017-Aug-16 13:13:44 TimeKeeper:NFO TimeKeeper: Close time offset now -3 2017-Aug-16 13:13:44 NetworkOPs:NFO STATE->tracking 2017-Aug-16 13:13:44 NetworkOPs:NFO STATE->full 2017-Aug-16 13:13:44 NetworkOPs:NFO Consensus time for #1665 with LCL 40F90A131285E06DCE0735A409C231E33300B02E806BC4FCBACB938109B541F4 2017-Aug-16 13:13:44 LedgerConsensus:NFO Entering consensus process, watching 2017-Aug-16 13:14:05 LedgerConsensus:NFO Converge cutoff (0 participants) 2017-Aug-16 13:14:05 LedgerConsensus:NFO CNF buildLCL 7E23BB3A1B11B01F223AEAB5553D3891673730A840509814DF607B4848C6EF32 2017-Aug-16 13:14:05 LedgerConsensus:NFO We closed at 556204440 2017-Aug-16 13:14:05 LedgerConsensus:NFO Our close offset is estimated at 0 (1) 2017-Aug-16 13:14:05 TimeKeeper:NFO TimeKeeper: Close time offset now -2 2017-Aug-16 13:14:05 NetworkOPs:WRN We are not running on the consensus ledger validator log: 2017-Aug-16 13:13:06 Resource:DBG Inactive "127.0.0.1" 2017-Aug-16 13:13:07 LedgerConsensus:DBG Checking for TX consensus: agree=0, disagree=0 2017-Aug-16 13:13:07 LedgerConsensus:DBG normal consensus 2017-Aug-16 13:13:07 LedgerConsensus:NFO Converge cutoff (0 participants) 2017-Aug-16 13:13:07 LedgerConsensus:DBG Report: Prop=yes val=yes corLCL=yes fail=no 2017-Aug-16 13:13:07 LedgerConsensus:DBG Report: Prev = 05111C39A3B43A640F9945C32633CBD5FC3A49556E000C3EF9DDE8F504AFD9E1:1659 2017-Aug-16 13:13:07 LedgerConsensus:DBG Report: TxSt = 0000000000000000000000000000000000000000000000000000000000000000, close 556204390 2017-Aug-16 13:13:07 LedgerConsensus:DBG Applying consensus set transactions to the last closed ledger 2017-Aug-16 13:13:07 LedgerConsensus:DBG Pass: 0 Txns: 0 retriable 2017-Aug-16 13:13:07 LedgerConsensus:DBG Pass: 0 finished 0 changes 2017-Aug-16 13:13:07 LedgerConsensus:DBG Pass: 1 Txns: 0 final 2017-Aug-16 13:13:07 LedgerConsensus:DBG Pass: 1 finished 0 changes 2017-Aug-16 13:13:07 LedgerConsensus:DBG Flushed 2 accounts and 1 transaction nodes 2017-Aug-16 13:13:07 LedgerConsensus:DBG Consensus built new ledger 2017-Aug-16 13:13:07 LedgerConsensus:DBG Report: NewL = 9B7DDDE79742F17F777AF38B050A482EB4BEAD43BB5AEC3E226D7934784E8F39:1660 2017-Aug-16 13:13:07 Validations:DBG Val for 9B7DDDE79742F17F777AF38B050A482EB4BEAD43BB5AEC3E226D7934784E8F39 from n9MX1GQr8jaH99jD5efJVQ8MaEbYrNxtwdE8opufGYd9Ww4GaMxK added trusted/current 2017-Aug-16 13:13:07 LedgerConsensus:NFO CNF Val 9B7DDDE79742F17F777AF38B050A482EB4BEAD43BB5AEC3E226D7934784E8F39 2017-Aug-16 13:13:07 LedgerMaster:NFO Advancing accepted ledger to 1660 with >= 1 validations 2017-Aug-16 13:13:07 LedgerHistory:DBG MATCH: seq=1660 2017-Aug-16 13:13:07 LedgerConsensus:DBG Consensus ledger fully validated 2017-Aug-16 13:13:07 LedgerConsensus:NFO We closed at 556204385 2017-Aug-16 13:13:07 LedgerConsensus:NFO Our close offset is estimated at 0 (1) 2017-Aug-16 13:13:07 NetworkOPs:DBG L: 9B7DDDE79742F17F777AF38B050A482EB4BEAD43BB5AEC3E226D7934784E8F39 t=1, n=1 2017-Aug-16 13:13:07 NetworkOPs:NFO Consensus time for #1661 with LCL 9B7DDDE79742F17F777AF38B050A482EB4BEAD43BB5AEC3E226D7934784E8F39 2017-Aug-16 13:13:07 ValidatorList:DBG 1 of 1 listed validators eligible for inclusion in the trusted set 2017-Aug-16 13:13:07 ValidatorList:DBG Using quorum of 1 for new set of 1 trusted validators 2017-Aug-16 13:13:07 LedgerConsensus:NFO Entering consensus process, validating 2017-Aug-16 13:13:07 LedgerMaster:DBG tryAdvance publishing seq 1660 2017-Aug-16 13:13:07 LedgerMaster:DBG Ledger 1660 accepted :9B7DDDE79742F17F777AF38B050A482EB4BEAD43BB5AEC3E226D7934784E8F39 2017-Aug-16 13:13:07 PathRequest:DBG updateAll complete: 0 processed and 0 removed 2017-Aug-16 13:13:07 NetworkOPs:DBG Initiating consensus engine 2017-Aug-16 13:13:07 NetworkOPs:DBG recvValidation 9B7DDDE79742F17F777AF38B050A482EB4BEAD43BB5AEC3E226D7934784E8F39 from 2 2017-Aug-16 13:13:07 Resource:DBG Expired "127.0.0.1" 2017-Aug-16 13:13:10 LedgerConsensus:DBG Checking for TX consensus: agree=0, disagree=0 2017-Aug-16 13:13:10 LedgerConsensus:DBG normal consensus 2017-Aug-16 13:13:10 LedgerConsensus:NFO Converge cutoff (0 participants) 2017-Aug-16 13:13:10 LedgerConsensus:DBG Report: Prop=yes val=yes corLCL=yes fail=no 2017-Aug-16 13:13:10 LedgerConsensus:DBG Report: Prev = 9B7DDDE79742F17F777AF38B050A482EB4BEAD43BB5AEC3E226D7934784E8F39:1660 2017-Aug-16 13:13:10 LedgerConsensus:DBG Report: TxSt = 0000000000000000000000000000000000000000000000000000000000000000, close 556204391 2017-Aug-16 13:13:10 LedgerConsensus:DBG Applying consensus set transactions to the last closed ledger 2017-Aug-16 13:13:10 LedgerConsensus:DBG Pass: 0 Txns: 0 retriable 2017-Aug-16 13:13:10 LedgerConsensus:DBG Pass: 0 finished 0 changes 2017-Aug-16 13:13:10 LedgerConsensus:DBG Pass: 1 Txns: 0 final 2017-Aug-16 13:13:10 LedgerConsensus:DBG Pass: 1 finished 0 changes 2017-Aug-16 13:13:10 LedgerConsensus:DBG Flushed 2 accounts and 1 transaction nodes 2017-Aug-16 13:13:10 LedgerConsensus:DBG Consensus built new ledger 2017-Aug-16 13:13:10 LedgerConsensus:DBG Report: NewL = 2384B44945FAD5E0C9929484C1FDCF699B3FC1AA63124434DA77E5D32AB29ABE:1661 2017-Aug-16 13:13:10 Validations:DBG Val for 2384B44945FAD5E0C9929484C1FDCF699B3FC1AA63124434DA77E5D32AB29ABE from n9MX1GQr8jaH99jD5efJVQ8MaEbYrNxtwdE8opufGYd9Ww4GaMxK added trusted/current 2017-Aug-16 13:13:10 LedgerConsensus:NFO CNF Val 2384B44945FAD5E0C9929484C1FDCF699B3FC1AA63124434DA77E5D32AB29ABE 2017-Aug-16 13:13:10 LedgerMaster:NFO Advancing accepted ledger to 1661 with >= 1 validations 2017-Aug-16 13:13:10 LedgerHistory:DBG MATCH: seq=1661 2017-Aug-16 13:13:10 LedgerConsensus:DBG Consensus ledger fully validated 2017-Aug-16 13:13:10 LedgerConsensus:NFO We closed at 556204388 2017-Aug-16 13:13:10 LedgerConsensus:NFO Our close offset is estimated at 0 (1) 2017-Aug-16 13:13:10 LedgerMaster:DBG tryAdvance publishing seq 1661 2017-Aug-16 13:13:10 LedgerMaster:DBG Ledger 1661 accepted :2384B44945FAD5E0C9929484C1FDCF699B3FC1AA63124434DA77E5D32AB29ABE 2017-Aug-16 13:13:10 NetworkOPs:DBG L: 2384B44945FAD5E0C9929484C1FDCF699B3FC1AA63124434DA77E5D32AB29ABE t=1, n=1 2017-Aug-16 13:13:10 NetworkOPs:NFO Consensus time for #1662 with LCL 2384B44945FAD5E0C9929484C1FDCF699B3FC1AA63124434DA77E5D32AB29ABE 2017-Aug-16 13:13:10 ValidatorList:DBG 1 of 1 listed validators eligible for inclusion in the trusted set 2017-Aug-16 13:13:10 ValidatorList:DBG Using quorum of 1 for new set of 1 trusted validators 2017-Aug-16 13:13:10 LedgerConsensus:NFO Entering consensus process, validating 2017-Aug-16 13:13:10 NetworkOPs:DBG Initiating consensus engine 2017-Aug-16 13:13:10 PathRequest:DBG updateAll complete: 0 processed and 0 removed 2017-Aug-16 13:13:10 NetworkOPs:DBG recvValidation 2384B44945FAD5E0C9929484C1FDCF699B3FC1AA63124434DA77E5D32AB29ABE from 2 2017-Aug-16 13:13:13 LedgerConsensus:DBG Checking for TX consensus: agree=0, disagree=0 2017-Aug-16 13:13:13 LedgerConsensus:DBG normal consensus 2017-Aug-16 13:13:13 LedgerConsensus:NFO Converge cutoff (0 participants) 2017-Aug-16 13:13:13 LedgerConsensus:DBG Report: Prop=yes val=yes corLCL=yes fail=no 2017-Aug-16 13:13:13 LedgerConsensus:DBG Report: Prev = 2384B44945FAD5E0C9929484C1FDCF699B3FC1AA63124434DA77E5D32AB29ABE:1661 2017-Aug-16 13:13:13 LedgerConsensus:DBG Report: TxSt = 0000000000000000000000000000000000000000000000000000000000000000, close 556204392 2017-Aug-16 13:13:13 LedgerConsensus:DBG Applying consensus set transactions to the last closed ledger 2017-Aug-16 13:13:13 LedgerConsensus:DBG Pass: 0 Txns: 0 retriable 2017-Aug-16 13:13:13 LedgerConsensus:DBG Pass: 0 finished 0 changes 2017-Aug-16 13:13:13 LedgerConsensus:DBG Pass: 1 Txns: 0 final 2017-Aug-16 13:13:13 LedgerConsensus:DBG Pass: 1 finished 0 changes 2017-Aug-16 13:13:13 LedgerConsensus:DBG Flushed 2 accounts and 1 transaction nodes 2017-Aug-16 13:13:13 LedgerConsensus:DBG Consensus built new ledger 2017-Aug-16 13:13:13 LedgerConsensus:DBG Report: NewL = 1CB109D4BF0933B7A6AC6E59D51CF910D3601AE5D1964C580609153A7663363D:1662 2017-Aug-16 13:13:13 Validations:DBG Val for 1CB109D4BF0933B7A6AC6E59D51CF910D3601AE5D1964C580609153A7663363D from n9MX1GQr8jaH99jD5efJVQ8MaEbYrNxtwdE8opufGYd9Ww4GaMxK added trusted/current 2017-Aug-16 13:13:13 LedgerConsensus:NFO CNF Val 1CB109D4BF0933B7A6AC6E59D51CF910D3601AE5D1964C580609153A7663363D 2017-Aug-16 13:13:13 LedgerMaster:NFO Advancing accepted ledger to 1662 with >= 1 validations 2017-Aug-16 13:13:13 LedgerHistory:DBG MATCH: seq=1662 2017-Aug-16 13:13:13 LedgerConsensus:DBG Consensus ledger fully validated 2017-Aug-16 13:13:13 LedgerConsensus:NFO We closed at 556204391 2017-Aug-16 13:13:13 LedgerConsensus:NFO Our close offset is estimated at 0 (1) 2017-Aug-16 13:13:13 NetworkOPs:DBG L: 1CB109D4BF0933B7A6AC6E59D51CF910D3601AE5D1964C580609153A7663363D t=1, n=1 2017-Aug-16 13:13:13 NetworkOPs:NFO Consensus time for #1663 with LCL 1CB109D4BF0933B7A6AC6E59D51CF910D3601AE5D1964C580609153A7663363D 2017-Aug-16 13:13:13 ValidatorList:DBG 1 of 1 listed validators eligible for inclusion in the trusted set 2017-Aug-16 13:13:13 ValidatorList:DBG Using quorum of 1 for new set of 1 trusted validators 2017-Aug-16 13:13:13 LedgerConsensus:NFO Entering consensus process, validating 2017-Aug-16 13:13:13 NetworkOPs:DBG Initiating consensus engine 2017-Aug-16 13:13:13 LedgerMaster:DBG tryAdvance publishing seq 1662 2017-Aug-16 13:13:13 LedgerMaster:DBG Ledger 1662 accepted :1CB109D4BF0933B7A6AC6E59D51CF910D3601AE5D1964C580609153A7663363D 2017-Aug-16 13:13:13 PathRequest:DBG updateAll complete: 0 processed and 0 removed 2017-Aug-16 13:13:13 NetworkOPs:DBG recvValidation 1CB109D4BF0933B7A6AC6E59D51CF910D3601AE5D1964C580609153A7663363D from 2 2017-Aug-16 13:13:14 InboundLedger:DBG Swept 0 out of 0 inbound ledgers. 2017-Aug-16 13:13:16 LedgerConsensus:DBG Checking for TX consensus: agree=0, disagree=0 2017-Aug-16 13:13:16 LedgerConsensus:DBG normal consensus 2017-Aug-16 13:13:16 LedgerConsensus:NFO Converge cutoff (0 participants) 2017-Aug-16 13:13:16 LedgerConsensus:DBG Report: Prop=yes val=yes corLCL=yes fail=no 2017-Aug-16 13:13:16 LedgerConsensus:DBG Report: Prev = 1CB109D4BF0933B7A6AC6E59D51CF910D3601AE5D1964C580609153A7663363D:1662 2017-Aug-16 13:13:16 LedgerConsensus:DBG Report: TxSt = 0000000000000000000000000000000000000000000000000000000000000000, close 556204393 2017-Aug-16 13:13:16 LedgerConsensus:DBG Applying consensus set transactions to the last closed ledger 2017-Aug-16 13:13:16 LedgerConsensus:DBG Pass: 0 Txns: 0 retriable 2017-Aug-16 13:13:16 LedgerConsensus:DBG Pass: 0 finished 0 changes 2017-Aug-16 13:13:16 LedgerConsensus:DBG Pass: 1 Txns: 0 final 2017-Aug-16 13:13:16 LedgerConsensus:DBG Pass: 1 finished 0 changes 2017-Aug-16 13:13:16 LedgerConsensus:DBG Flushed 2 accounts and 1 transaction nodes 2017-Aug-16 13:13:16 LedgerConsensus:DBG Consensus built new ledger 2017-Aug-16 13:13:16 LedgerConsensus:DBG Report: NewL = 7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236:1663 2017-Aug-16 13:13:16 Validations:DBG Val for 7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236 from n9MX1GQr8jaH99jD5efJVQ8MaEbYrNxtwdE8opufGYd9Ww4GaMxK added trusted/current 2017-Aug-16 13:13:16 LedgerConsensus:NFO CNF Val 7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236 2017-Aug-16 13:13:16 LedgerMaster:NFO Advancing accepted ledger to 1663 with >= 1 validations 2017-Aug-16 13:13:16 LedgerHistory:DBG MATCH: seq=1663 2017-Aug-16 13:13:16 LedgerConsensus:DBG Consensus ledger fully validated 2017-Aug-16 13:13:16 LedgerConsensus:NFO We closed at 556204394 2017-Aug-16 13:13:16 LedgerConsensus:NFO Our close offset is estimated at 0 (1) 2017-Aug-16 13:13:16 NetworkOPs:DBG L: 7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236 t=1, n=1 2017-Aug-16 13:13:16 LedgerMaster:DBG tryAdvance publishing seq 1663 2017-Aug-16 13:13:16 LedgerMaster:DBG Ledger 1663 accepted :7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236 2017-Aug-16 13:13:16 NetworkOPs:NFO Consensus time for #1664 with LCL 7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236 2017-Aug-16 13:13:16 ValidatorList:DBG 1 of 1 listed validators eligible for inclusion in the trusted set 2017-Aug-16 13:13:16 ValidatorList:DBG Using quorum of 1 for new set of 1 trusted validators 2017-Aug-16 13:13:16 LedgerConsensus:NFO Entering consensus process, validating 2017-Aug-16 13:13:16 NetworkOPs:DBG Initiating consensus engine 2017-Aug-16 13:13:16 PathRequest:DBG updateAll complete: 0 processed and 0 removed 2017-Aug-16 13:13:16 NetworkOPs:DBG recvValidation 7C6899F29DEABCC62AC4E85DD131AEC85F6EE1F058631B13412296C7C5B2C236 from 2 2017-Aug-16 13:13:18 Resource:DBG New unlimited endpoint "127.0.0.1" Thanks
  14. Hello all, I am trying to learn how Ripple works by setting up a local stock and validator servers. It seems that the communication has been established. At first I started 1st server with "-a" to generate genesis transaction and later started the same server pointing to the validator. These are my "server_info" responses, first the stock server: /opt/ripple/bin/rippled server_info Loading: "/etc/opt/ripple/rippled.cfg" 2017-Aug-14 08:41:56 HTTPClient:NFO Connecting to 127.0.0.1:5005 { "id" : 1, "result" : { "info" : { "build_version" : "0.70.1", "complete_ledgers" : "76002-78765", "hostid" : "xx1", "io_latency_ms" : 1, "last_close" : { "converge_time_s" : 2, "proposers" : 1 }, "load" : { "job_types" : [ { "in_progress" : 1, "job_type" : "clientCommand" }, { "job_type" : "peerCommand", "per_second" : 1 } ], "threads" : 8 }, "load_factor" : 1, "peers" : 1, "pubkey_node" : "n94UTpr9W4p5aakm8ZipXsrwm5MUgonNk45wWXs2w3DNMvqKGzHh", "pubkey_validator" : "none", "server_state" : "full", "state_accounting" : { "connected" : { "duration_us" : "1000491", "transitions" : 1 }, "disconnected" : { "duration_us" : "1150974", "transitions" : 1 }, "full" : { "duration_us" : "235832998577", "transitions" : 1 }, "syncing" : { "duration_us" : "2001010", "transitions" : 1 }, "tracking" : { "duration_us" : "6", "transitions" : 1 } }, "uptime" : 235837, "validated_ledger" : { "age" : 4, "base_fee_xrp" : 1e-05, "hash" : "80943FEE03E58456BCAFF97A4E294AE8EEA2AE04C0AF78EE50EFB868B39BE25E", "reserve_base_xrp" : 20, "reserve_inc_xrp" : 5, "seq" : 78765 }, "validation_quorum" : 1 }, "status" : "success" } } validator: /opt/ripple/bin/rippled server_info Loading: "/etc/opt/ripple/rippled.cfg" 2017-Aug-14 08:43:40 HTTPClient:NFO Connecting to 127.0.0.1:5005 { "id" : 1, "result" : { "info" : { "build_version" : "0.70.1", "complete_ledgers" : "76010-78800", "hostid" : "xx2", "io_latency_ms" : 1, "last_close" : { "converge_time_s" : 1.999, "proposers" : 0 }, "load" : { "job_types" : [ { "in_progress" : 1, "job_type" : "clientCommand" }, { "job_type" : "writeObjects", "per_second" : 1 }, { "job_type" : "peerCommand", "per_second" : 1 }, { "job_type" : "WriteNode", "per_second" : 1 } ], "threads" : 6 }, "load_factor" : 1, "peers" : 1, "pubkey_node" : "n9Mv6Ci6rVt3Ka47i2Z5YNpy4qLGs4f1PCG1qeZfsF6FF7mtDwdj", "pubkey_validator" : "nHUuVACwNCYzKPUTE6V5VYab76aqP7gWN8sDuLWwSSUUdbB2w6Xc", "server_state" : "proposing", "state_accounting" : { "connected" : { "duration_us" : "58039595", "transitions" : 1 }, "disconnected" : { "duration_us" : "1060053", "transitions" : 1 }, "full" : { "duration_us" : "236587737319", "transitions" : 1 }, "syncing" : { "duration_us" : "0", "transitions" : 0 }, "tracking" : { "duration_us" : "5", "transitions" : 1 } }, "uptime" : 236647, "validated_ledger" : { "base_fee_xrp" : 1e-05, "hash" : "62E7AD5CEDA13589969A2F04F50949C53E512DE6EA569608ECECBFCCD9A29763", "reserve_base_xrp" : 20, "reserve_inc_xrp" : 5, "seq" : 78800 }, "validation_quorum" : 1 }, "status" : "success" } } I created a new address and used RippleAPI JS to send XRP from genesis acct to the new account. The payment JS has the following code: const instructions = {maxLedgerVersionOffset: 5}; const payment = { source: { address: 'rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh', maxAmount: { value: '1000.55', currency: 'XRP' } }, destination: { address: 'rPTHuXH4ZMwXu4oHw8YUWAX7gqr7phfCfv', amount: { value: '1000.55', currency: 'XRP' } } }; Transaction went through and balances got updated: /opt/ripple/bin/rippled account_info rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh Loading: "/etc/opt/ripple/rippled.cfg" 2017-Aug-14 08:32:56 HTTPClient:NFO Connecting to 127.0.0.1:5005 { "id" : 1, "result" : { "account_data" : { "Account" : "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh", "Balance" : "99999998999449988", "Flags" : 0, "LedgerEntryType" : "AccountRoot", "OwnerCount" : 0, "PreviousTxnID" : "DB733040C1D76163C9765CC40CB7DBCA78D4F0A7D426F75F381D51C347F34DF6", "PreviousTxnLgrSeq" : 18, "Sequence" : 2, "index" : "2B6AC232AA4C4BE41BF49D2459FA4A0347E1B543A4C92FCEE0821C0201E2E9A8" }, "ledger_current_index" : 78586, "status" : "success", "validated" : false } } 2nd wallet: /opt/ripple/bin/rippled account_info rPTHuXH4ZMwXu4oHw8YUWAX7gqr7phfCfv Loading: "/etc/opt/ripple/rippled.cfg" 2017-Aug-14 08:33:56 HTTPClient:NFO Connecting to 127.0.0.1:5005 { "id" : 1, "result" : { "account_data" : { "Account" : "rPTHuXH4ZMwXu4oHw8YUWAX7gqr7phfCfv", "Balance" : "1000550000", "Flags" : 0, "LedgerEntryType" : "AccountRoot", "OwnerCount" : 0, "PreviousTxnID" : "DB733040C1D76163C9765CC40CB7DBCA78D4F0A7D426F75F381D51C347F34DF6", "PreviousTxnLgrSeq" : 18, "Sequence" : 1, "index" : "2CBCDEC9A21E72F1D30D90B5D504307044B7BF03C2EAF2740CCA896705AD3E97" }, "ledger_current_index" : 78606, "status" : "success", "validated" : false } } Are these results normal and is there a way to verify that my setup is running correctly? How come both of them have "validated" set to false? I've attempted to install ripplecharts but when I follow instructions and start the app, it's not connecting. What are the settings that need to be added to "deployment.environments.json"? The example file contains this: { "development": { "ga_account" : "", "ga_id" : "", "api" : "REPLACEME", "maintenance" : false }, "staging": { "ga_account" : "", "ga_id" : "", "api" : "REPLACEME", "maintenance" : false }, "production": { "ga_account" : "", "ga_id" : "", "api" : "REPLACEME", "maintenance" : false } } what should I enter for the ga_account, ga_id and API settings?
  15. Hello , I try to make the trustline between two account using this JSON-rpc api { "method": "submit", "params": [ { "secret": "Secret-key", "tx_json": { "Account": "rcWB6PobWkr2hAWRAFGxpAxPUpxnWNtiA", "Fee": "15000", "TransactionType": "TrustSet", "LimitAmount": { "currency": "SOM", "issuer": "rUfWPdSpQVHkAxarYTPU3uHX47n6L78guM", "value": 0 }, "Flags": 65536, "Sequence": 9 } } ] } but when i check tx_blob in return using request { "method": "submit", "params": [ { "tx_blob": "120014220001000024000000036380000000000000000000000000000000000000004442530000000000E1F55708CB67B2DB45E8A7E06FDEE81D88F02B01684000000000003A987321022CBD94ACD2BCAD62720AFD1AE0462B917CA6CA6F8503F52053ACEB3B6F0C3A92744730450221009BDF94DEE456B792B717636B0AB9B0F671456101FBEF95719BEAE923C8B70FF80220333C86E0EF845F863CDF12376B00F780E469A620407B3D051AF2A82823B352588114119ED18567D6A1045821AF158EB10FC4B1676B26" } ] } Response - { "result": { "engine_result": "tefALREADY", "engine_result_code": -198, "engine_result_message": "The exact transaction was already in this ledger.", "status": "success", "tx_blob": "120014220001000024000000036380000000000000000000000000000000000000004442530000000000E1F55708CB67B2DB45E8A7E06FDEE81D88F02B01684000000000003A987321022CBD94ACD2BCAD62720AFD1AE0462B917CA6CA6F8503F52053ACEB3B6F0C3A92744730450221009BDF94DEE456B792B717636B0AB9B0F671456101FBEF95719BEAE923C8B70FF80220333C86E0EF845F863CDF12376B00F780E469A620407B3D051AF2A82823B352588114119ED18567D6A1045821AF158EB10FC4B1676B26", "tx_json": { "Account": "rpcwkwGA8u8k2nxEGc1837tGeH7QWvi4qQ", "Fee": "15000", "Flags": 65536, "LimitAmount": { "currency": "DBS", "issuer": "rMbkAg2T9biQ1Ax7r2juNGXRfTeN8j6wLk", "value": "0" }, "Sequence": 3, "SigningPubKey": "022CBD94ACD2BCAD62720AFD1AE0462B917CA6CA6F8503F52053ACEB3B6F0C3A92", "TransactionType": "TrustSet", "TxnSignature": "30450221009BDF94DEE456B792B717636B0AB9B0F671456101FBEF95719BEAE923C8B70FF80220333C86E0EF845F863CDF12376B00F780E469A620407B3D051AF2A82823B35258", "hash": "CDEC1C858F20A2E046031743904AEF86C9DFAC6391E46891072E82F9CB2A5F11" } } } And when i check the gatway_balance request - { "method": "gateway_balances", "params": [ { "account": "rpcwkwGA8u8k2nxEGc1837tGeH7QWvi4qQ", "hotwallet": [ "rMbkAg2T9biQ1Ax7r2juNGXRfTeN8j6wLk" ] } ] } Response - { "result": { "account": "rpcwkwGA8u8k2nxEGc1837tGeH7QWvi4qQ", "ledger_current_index": 3, "status": "success", "validated": false } } Please help me to solve it .
  16. Hi, I am stuck at one Problem when trying to setup a simple Docker-rippled + ripple-lib app, I have rippled installed in a docker conainer with the following Config (irrelevant parts omited) : http://paste.ubuntu.com/25075264/ This Forum removes all my newlines from code i copy from my IDE for some reason, have to use pastebin, sorry. and i try to connect to the deamon with the ripple-lib javascript library and the following code: 'use strict'; const {RippleAPI} = require('ripple-lib') const api = new RippleAPI({ server: 'wss://172.17.0.7:51235', // docker ip authorization: 'username:password' }); and i always get the response: [NotConnectedError(unexpected server response (401))] no idea why, cant find any logs, someone has any ideas?
  17. I overlaid the RCL validator map from https://charts.ripple.com/#/topology to a map of the US showing major cities and thought it might be fun for everyone to do some speculation. It got more interesting than I anticipated. I know IP mapping isn't 100% accurate but I think this gives some insights and I'm sure others can come up with more. Also, keep in mind the size of the dot indicates the number of connections for that validator. Using Ripple as a control you can see a few validators in the SF area that would represent their connections. The giant dot in Southern Kansas seems to be due to this: http://fusion.net/story/287592/internet-mapping-glitch-kansas-farm/ The giant dots in southern WA are maybe another IP mapping issue, but I believe there are server farms in that area. The small validator in Boston seems to offer another control as it seems that would be MIT. Seems to be a bit of dedicated processing power near Seattle. Microsoft maybe? Curious about all the power in Dallas/Houston. Look at Washington DC. If there are any positive indicators that Ripple may be the first crypto approved for interbank settlement in addition to the tweets, extensive compliance team, Faster Payments situation, etc. @papa Pointed out that Washington DC has the most connections. I count 6 validators with what looks like more than 2x the connections in the Silicon Valley area. This is obviously the headquarters for the Federal Reserve (I only mention that because of #8). The validators in Dallas/Houston are what sparked my interest in this, but as I fell down the rabbit hole the most interesting thing I've found as I've dug in a bit is that of the 12 Federal Reserve Banks throughout the country, seven of them have validators (SF, KC, DAL, NY, CHI, ATL, BOS). The exceptions are Minneapolis, Philadelphia, Richmond, Cleveland, and St. Louis. Philadelphia does have a validator in PA not too far away, but it wasn't right on the dot. Not trying to make outlandish assertions, but that's interesting! #8 makes me believe there is a decent chance the fed is already watching these tests. How would banks have the confidence to use XRP in live trials if the Fed wasn't watching. Seems to make sense. Also make sense that they would run a validator so they can audit the transactions. You know they want that kind of control and visibility. Also makes sense as to why DC would have more connections by far than any other city. Still curious about Houston, Southern WA and those validators defaulting to Kansas. Any Ripple partners in Houston? That's all I got. Didn't expect to go so crazy, but hopefully you guys enjoy.
  18. Looking at ripple network topology, one can see that there are some nodes whose IPs are not know (i.e. location not know). How did they manage to hide their IP and how to go about doing this for myself? Tried setting peer_private=1 in rippled.cfg file but what it did is made the server respond with "InsufficientNetworkMode", perhaps suggesting that it is not syncing up any more. It would be nice to be able to hide IP from topology page, since there is no need for that if it's only for you. Noticed that straight after setting up a rippled server, there where almost immediately failed attempts to ssh log in from China. Do not have to be a genius to deduce where they got my server IP from...
  19. Closingbell2012

    Rippled Commands

    Hi Folks. I have installed Rippled on my Ubuntu distro AWS m3.2xlarge (26 ECUs, 8 vCPUs, 2.5 GHz, Intel Xeon E5-2670v2, 30 GiB memory, 2 x SSD 80 GiB Storage Capacity) instances. I am just experimenting with Rippled and have limited experience with node.js and C++. What I am doing now is testing the basic rippled commands using $ /opt/ripple/bin/rippled <COMMAND> After I executed the first command using $ /opt/ripple/bin/rippled account_currencies I got the following message "Loading: "/home/ubuntu/rippled.cfg" and nothing happens. I have also updated the rippled.cfg (using vim) with the following command: { "command": "account_currencies", "account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59", "strict": true, "ledger_index": "validated" } - source: https://ripple.com/build/rippled-apis/#account-currencies No results. Am I doing something wrong? Any help would be greatly appreciated. PS: anyone has a the source code to generate public and secret keys for paper wallet storage? Thanks guys, Closingbell2012
  20. Which type of AWS instance is suitable for rippled (only home research purpose) - getting mixed opinions: 1. t2.2xlarge (Variable ECUs, 8 vCPUs, 2.4 GHz, Intel Xeon Family, 32 GiB memory, EBS only) 2. m4.2xlarge (26 ECUs, 8 vCPUs, 2.4 GHz, Intel Xeon E5-2676v3, 32 GiB memory, EBS only) 3. m3.large (6.5 ECUs, 2 vCPUs, 2.5 GHz, Intel Xeon E5-2670v2, 7.5 GiB memory, 1 x 32 GiB Storage Capacity) 4. g2.2xlarge (26 ECUs, 8 vCPUs, 2.6 GHz, Intel Xeon E5-2670, 15 GiB memory, 1 x 60 GiB Storage Capacity) Thanks folks.
  21. Hello guys, looks like the orderbooks are not being built with offer autobridging. I just validated it at https://ripple.com/build/websocket-tool/# REQUEST: { "id": 4, "command": "book_offers", "taker": "rDb6qVhDdAybg9ARF2Yy64AAdk17Bi4M2q", "taker_gets": { "currency": "BTC", "issuer": "rKxKhXZCeSDsbkyB8DVgxpjy5AHubFkMFe" }, "taker_pays": { "currency": "BRL", "issuer": "rfNZPxoZ5Uaamdp339U9dCLWz2T73nZJZH" }, "limit": 3 } RESPONSE { "id": 4, "status": "success", "type": "response", "result": { "ledger_current_index": 29005704, "offers": [ { "Account": "rwSrs1WCfRZPaPx7tqHToQFqyjobMPrgkJ", "BookDirectory": "A183825144B5D679B197CDCDA3E44DDF14F55F3591AF0C58580DBB55D3F68000", "BookNode": "0000000000000000", "Flags": 131072, "LedgerEntryType": "Offer", "OwnerNode": "0000000000000001", "PreviousTxnID": "9744DED4BB1833AAC463D8CC3BD29D028097A7738AE4F925A416186F6660D743", "PreviousTxnLgrSeq": 29005673, "Sequence": 34535, "TakerGets": { "currency": "BTC", "issuer": "rKxKhXZCeSDsbkyB8DVgxpjy5AHubFkMFe", "value": "0.512" }, "TakerPays": { "currency": "BRL", "issuer": "rfNZPxoZ5Uaamdp339U9dCLWz2T73nZJZH", "value": "1978.957824" }, "index": "0D60320194196138FC5D16723DF35AD1628ECA57B9C99C8051502DB39FE36C14", "owner_funds": "1.327867740457333", "quality": "3865.152" } ], "validated": false } } Charts:
  22. HI there! I'm trying to build a stock RippleD Server on CentOs 7 and I'm facing some issues. RippleD is up and running as a Linux Service, but strangely I'm unable to connect via the WSS interface... I receive a 403 error! Please note that when using WS it works perfectly but I would like to use WSS for security reasons. RippleD Config: validators.txt RippleD Log: NodeJS program that is trying to connect to RippleD: NodeJS Log: Do you guys have any clue what I'm doing wrong? Why the hell am I receiving a 403? Thanks a lot for your help!!!
  23. https://ripple.com/dev-blog/rippled-0-50-0/ And we're planning on voting for TickSize and SusPay so that both get enabled on Feb 21.
  24. Background Originally, the FlowV2 amendment was planned to replace rippled’s payment processing engine with a more robust and efficient implementation. It was previously expected to become active on Wednesday, 2016-08-24. FlowV2 Was Vetoed The rippled team found a flaw in FlowV2 while testing. As a result, the Ripple network has vetoed the new payment engine amendment. A corrected version of the payment processing engine has been created and is now undergoing further testing. It is scheduled to be included in a future version of rippled as an amendment called Flow. This demonstrates the robustness of Ripple’s amendment process. The review period and governance code with vetoing work as intended. Action Recommended No action is currently required. However, Ripple recommends that validator operators also veto the FlowV2 amendment to ensure it does not regain a majority. To veto the amendment, add the following, single line, under the [veto_amendments] stanza to the rippled.cfg file on validators: 5CC22CFF2864B020BD79E0E1F048F63EF3594F95E650E43B3F837EF1DF5F4B26 FlowV2 Learn, Ask Questions, and Discuss Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing: https://ripple.com/build/ Other resources: The Ripple Forum: https://forum.ripple.com/ The Ripple Dev Blog: https://ripple.com/category/dev-blog/ Ripple Technical Services: support@ripple.com
  25. The FlowV2 Amendment is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the FlowV2 engine. The new version of the payment processing engine is intended to follow the same rules as the old engine. However, the new engine occasionally produces different results due to floating point rounding. The FlowV2 Engine also makes it easier to improve and expand the payment engine with further Amendments. Ripple’s validators will vote in favor of the FlowV2 amendment. We expect the new feature to become active on Wednesday, 2016-08-24. Actions Required If you operate a `rippled` server, you should upgrade to version 0.32.1 by Wednesday, 2016-08-24 for the best performance. Note: A previous version of this post incorrectly stated that backend software must be updated to construct transactions for the new payment processing engine. The process of creating and submitting transactions for the FlowV2 payment engine is the same as for the previous payment engine. Impact of Not Upgrading If you operate a `rippled` server but don’t upgrade to version 0.32.1 by Wednesday, 2016-08-24 (when FlowV2 is expected to become available via Amendment) then: Your server will become "amendment blocked" and unable to process transactions or evaluate the validity of ledgers. For instruction on updating `rippled` on supported platforms, see: https://ripple.com/build/rippled-setup/#updating-rippled For other platforms, please compile version 0.32.1 from source. For details, see https://wiki.ripple.com/Rippled_build_instructions Learn, Ask Questions, and Discuss Related documentation is available in the Ripple Developer Portal, including detailed example API calls and web tools for API testing: https://ripple.com/build/ Other Resources * The Ripple Forum: https://forum.ripple.com/ * The Ripple Dev Blog: https://ripple.com/category/dev-blog/ * Ripple Technical Services: support@ripple.com
×