Jump to content


  • Content Count

  • Joined

  • Last visited

About xrpscan

  • Rank

Contact Methods

  • Website URL

Recent Profile Visitors

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

  1. That's a fair point, and I agree that better wording could be used here.
  2. All I could find is this article: https://www.blocktempo.com/taiwan-exchange-bitopro-got-hacked-xrp-lost/
  3. Looking at the transaction pattern, here's my take: The attacker at rERfHy4YmDbKxsuFmzPBhMQCGyFrAGvbra has a small USD balance at gatehub that they use to probe exchanges. I scrolled till page 4 and almost every popular exchange that has XRP listed has been probed. The list even includes XRP Tip Bot! As a corollary, I believe the unlabelled destination addresses may be unknown exchanges. The pattern seems to be first a test amount (7K XRP) and if it works, a large transfer (of 3M XRP, to be withdrawn/traded until the exchange wallet runs dry). BitoPro's case looks to be a bit curious though. They've never held 7M XRP in either of their known wallets, which makes me think if the attacker traded the XRP for other coins and withdrew funds that way.
  4. It looks like a partially fulfilled offer from Gatehub for 0.001 USD. Sorry, this doesn't seem intuitive - we'll try and see if we can add more details to offer fulfilment transactions.
  5. As per those who're familiar with Coinbase's listing pattern, a Coinbase Pro listing is usually followed by Coinbase listing after a few weeks.
  6. In case someone wants to look up, their deposit account is here: https://xrpscan.com/account/rw2ciyaNshpHe7bCHo4bRWq6pqqynnWKQg
  7. Thank you for the vote of confidence CB. This means a lot, coming from folks who've been around for a while. I would recuse myself from commenting on the topic due to conflict of interest, but I'll say this - Ripple's Data API has been a big help in keeping xrpscan.com operations sustainable. By consuming Data API's transactions and payments endpoints, we keep our storage costs low. There may be a point in future where we cache all ledgers and generate transaction listing locally, but for now considering our traffic and query pattern, we're happy with the architectural trade-offs we've made. There are also bits like exchange data, node/validator analytics that isn't available on-ledger and is difficult to acquire by external means. Whatever the future of xrpcharts is, its the Ripple Data API that is more precious.
  8. (emphasis mine) Well said. People come from diverse backgrounds and everyone has a different taste and preference. Giving more choice to users benefits everyone in the ecosystem!
  9. This looks like a great initiative! You are correct in your assertion that xrpscan.com doesn't do deep ledger analytics. That, in fact, is our current goal - to provide great UX for shallow XRPL queries and aim to be the fastest ledger explorer. We use Ripple's Data API in 3 places: Historical transactions Historical payments Validator analytics Everything else is powered by our own rippled instance. Ours isn't configured as a full history server, but it's great to see other projects setting up full history servers. That said, if you're interested we can contribute our cache of RippleTrade username mappings. Let me know what you think!
  10. Evidence collected by "triggering XRP people" - does that even count as evidence? Not sure what kind of law school he's attending.
  11. I believe this can go well with the Transaction statistics widget at the bottom. The widget can link to an advanced view on a separate page and show ledger transaction volume on a time series chart. Thank you, this is a great tip! I should be able to select these data points, including Destroyed XRP and Payment Channel activity, and draw them on the time series charts. Thanks for the feedback, these are great suggestions. Thank you for your encouragement all along, Hodor! With the huge uptake Coil has seen in the recent months, our plan is to monetize it via Coil after the service stabilizes. At the moment there's no monetization because we want to finish the full version roadmap and improve the stability of the service (A large portion of making this service stable involves moving away from Ripple Data APIs, which is a huge bottleneck, and leveraging the services provided by our rippled instance). A big thank you to everyone for sharing your feedback. We really appreciate it.
  12. Summary The XRPSCAN Project is now available for beta testing. XRPSCAN is an explorer for the Ripple ledger that aims to provide you with an easy to use account and transaction explorer. URL: https://xrpscan.com If you've transacted in other leading cryptocurrencies like Bitcoin, you may have undoubtedly used their Blockchain explorers to look up the status of your transactions and check your account balance. You may also have felt the need for a Ledger explorer for Ripple that provides similar levels of ease of use and granularity of information. The XRPSCAN project aims to bridge that gap and provide you with a clean and simple way to look up your accounts and transactions. While on the homepage, you can track the ledger close events in real time and watch the diminishing XRP supply. Ledgers The ledger page tells you about all the transactions that were included in the given ledger. We support all transaction types that are supported by the XRP Ledger. Accounts Accounts page tells you at a glance about the current state and balance available. It also contains detailed information about Payments made, Currency balances, Orders, Trustlines, Account settings, Activated accounts and the Transactions this account was involved in. XRP is treated like every other currency issued by the counterparties and is displayed seamlessly without treating it as a special snowflake. Validators The validator registry lists all validator nodes and displays their verified domain names, UNL status, ledger chain and agreement rates. Search Ledger objects like Accounts, Ledgers, Transaction hashes and Validators are searchable from the search box at the top. The objects are directly addressable from the URL too, so you may simply use the address bar to look up: Ledger - https://xrpscan.com/ledger/[ledger-number] Account - https://xrpscan.com/account/[account] Transaction - https://xrpscan.com/tx/[tx-hash] Validator - https://xrpscan.com/validator/[node-public-key] Closing notes We hope you find this project useful and use it in your daily interaction with XRP. There are several items that we're working on to make XRPSCAN more useful and accessible for you. We'll continuously roll out these changes as and when they are complete. We run a verified Ripple validator, are committed to the success of XRP and absolutely ❤ the #xrpcommunity. We hope you give us a try and spread the word. Feedback XRPSCAN is in beta testing. Should you find a bug, please report it here: https://github.com/xrpscan/xrpscan.com/issues Follow us: We're active on Twitter, give us a follow: @xrpscan
  13. Hi Sukrim, we had implemented and announced the availability of new validator pages just a week after Ripple announced changes in their data API, back in 23rd October 😁.
  14. Shameless plug: you may also want to bookmark alternate validator registries, such as ours - https://xrpscan.com/validators
  15. Hi @mDuo13, will the webfinger based api have data from the older api?
  • Create New...