I have some explaining to do.

The past couple of days were challenging when it comes to the @XummWallet / XRP Ledger infrastructure I'm responsible for.

The amount of XUMM users & clients connected to xrplcluster.com has been rising and rising. Scaling was required.
A couple of weeks back we scaled the XUMM platform, confident that we'd be able to handle the user growth for some time to come. We also made sure that future scaling would be easier.

Right after scaling, our cloud provider had multiple outages. That never happened before.
The communication of our cloud provider and the amount of sudden issues resulted in an emergency migration. This came with one hour of downtime. I personally kept you all posted on our status page: status.xrpl-labs.com.

Our status page had been a boring, green page for years.
After our cloud migration, yet again we were confident that the worst was behind us. However, as Murphy's law states: "Anything that can go wrong will go wrong."

After the XUMM platform was scaled for growth (500 » » 2000 » 5000 new users per day!) we ran into new problems.
XUMM, just like many other ecosystem participants (like @Ledger, websites, platforms, tools, exchanges) needs to connect to XRP Ledger nodes. "rippled" is the software that powers the XRP Ledger. Responsible for consensus, history, transactions: "the blockchain".
The XRP Ledger software, "rippled" has been tested with high amounts of transactions (throughput tests). During these tests it became clear that the XRP Ledger can handle a significant amount of transactions submitted by a client.
Today's production workload is different: instead of one client submitting many transactions, there are many clients submitting a small amount of transactions. The many clients do, however, read a lot of data from the "rippled" nodes: Trust Line balances, offers, order books.
To handle the amount of requests for the high amount of users (clients), more scaling was required. This time not the XUMM platform, but "xrplcluster.com": the cluster that provides access to the XRP Ledger for XUMM and many other companies, developers & tools.
Scaling blockchain nodes is harder though. A lot of testing, tuning & coding was required. Thanks to some of the well known & bright minds in our ecosystem, working behind the scenes day and night for days, the situation seems to be under control again.
The cluster was upgraded:
- From 8 full history nodes to 12 nodes
- 9 new dedicated non full history nodes were added
- 2 transaction submission nodes were added

On top of adding capacity, I wrote code to automatically orchestrate seamless client handover between nodes.
New code is monitoring the entire cluster on a per host per host type basis, and if a host is too busy, misbehaving (overloaded) or simply down, clients will immediately be routed to another node. Also: anomaly detection, transaction offloading (e.g. if full history isn't needed)
The first results are promising, and after many stressful days I am hopeful that I can finally get some good night's sleep again, knowing that the cluster will take care of itself now.

While this scaling and "patchwork" (or automation, if you like) may solve things now, (...)
(...) it will take a lot of effort, testing, profiling, searching, discussing and coding to optimize many components powering our ecosystem to keep up with the growth we're currently seeing. I'm confident that the bright minds amongst us will join forces & make this happen.
After very very stressful weeks I feel the worst is behind us. I am very sorry for the horrible user experience some of you have had the past days using XUMM or other XRPL tools. Sorry. Really. 😚
I have to remind myself (and you?) that this is all happening because of growth we could have only dreamed of just months ago.

Please take a moment while using XUMM, the XRPL, transacting, using the DEX to realize there are many geeks working day and night to make it possible.
And now: onwards 🚀
😚 @bharathchari @nbougalis @XRPL_rabbit and many others for providing node capacity, offering to help, debugging & fixing alongside of me & sending kind words my way. @XummWallet users, community: you are awesome. Thank you for keeping my spirits up & being so understanding.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with WietseWind - 🛠 XUMM @ XRPL Labs

WietseWind - 🛠 XUMM @ XRPL Labs Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @WietseWind

29 Sep 20
@Hopiumhater @aspingos22 @XRPLF @Ripple @Coil @GateHub I think the XRPL is not unattractive to devs: the technology, connectivity, speed, tools are all very attractive. The reason the XRPL isn't the go-to tech for the development you're aiming at has multiple causes, like:
(1/...)
@Hopiumhater @aspingos22 @XRPLF @Ripple @Coil @GateHub (2/...)
- The account reserve, limiting the amount of users one can reach (as they should be willing to pay the reserve to use the XRPL) (Disclaimer: I believe the reserve is a good thing, but let's face it: it limits the user base)
@Hopiumhater @aspingos22 @XRPLF @Ripple @Coil @GateHub (3/...)
For some devs:
- Misplaced "it can't be mined so it's bad" sentiment
- The lack of layer one smart contracts (Disclaimer: they are not smart and not really contracts, imo, but that's just terminology)
Read 6 tweets
31 Aug 20
After receiving a significant amount of questions about XUMM being in beta & the amount of XRP that's safe to store, this is me answering that question publicly 😊

ℹ️ Your XRP is "stored" on the XRP ledger, not "in" XUMM. XUMM is non custodial. Keys lost? No recovery ⚠️
We are confident that security, encryption, storing, sending & receiving **XRP** in XUMM has been thoroughly tested.

We're improving the user interface here and there, adding features & translations & sending, receiving & trading IOU's (non-XRP currencies) are work in progress.
This means we trust XUMM can handle larger XRP balances today, at version 0.5.1 (the version you can get from or upgrade to using the Apple App/ Google Play store). However, and I can't stress this enough: KEEP YOUR KEYS SAFE. WRITE THEM DOWN & STORE THEM @ MULTIPLE SECURE PLACES
Read 8 tweets
28 Aug 20
Automated #XUMM testing 🎉 @baltazar223 working on fully automated testing, of the XUMM user interface, interaction & encryption 😎 Image
Onboard. Generate account. Confirm secret numbers. Check account. Compose a transaction. Sign transaction. Confirm signature. Fully automated, pre-release.

(Yes, closing in on version 1.0)
Read 4 tweets
21 Aug 20
Tutorial, instructions & a tool to prepare for claiming your @FlareNetworks Spark tokens 🎉

While the Flare network *isn't live yet* and the Spark token distribution *hasn't started* you can already prepare your accounts

For #XUMM & @xrptoolkit users

coil.com/p/wietse/Prepa…
Image
Please note: I am *not* part of the Flare team, *don't* have more details / information (like timelines, etc.) and have *no financial incentive* to promote the Flare network and/or Spark token.
Read 4 tweets
15 Jul 20
Last tests & fixes for a massive XUMM update. The next 1~2 days: last internal testing & fixes. Next week: community dev. testing. Estimated public release: end of next week.
Over 60 changes, additions, improvements & fixes, mostly developed by Ali @baltazar223 & @ThisIsTRISS 🤗
Don't let the version number (0.5.1, just a .1 on the end) fool you: it doesn't honour the amount of work & improvements at all, but we decided to stick with it.

After this update we take a bit of time for @baltazar223 to work on automated internal testing procedures, etc.
After this, there will probably be one more beta release (0.6.0) with a little less changes & updates, after which we'll remove the Beta label and launch V1. As we're adding some things I'm really excited about (think: XUMM Pro, opt in KYC, hosted PayID & more) expect mid Q4.
Read 7 tweets
18 Jun 20
Checks feature on the XRPL: so let's say you want to pay Netflix on the XRPL (who knows, maybe one day they'll accept XRPL payments). You don't want to pay the entire year in advance, and you don't want to lock up (escrow) the entire year in payments: (1/2)
(2/2) You generate 12 Checks for the monthly amount each, and every month Netflix will try to cash one of your checks on the XRPL. If they can't because you are out of funds, the service simply gets terminated.
Want to terminate < 12 months? Cancel the remaining Checks.
(Just a random example of where on ledger Checks can come in handy)
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(