I think the phrase down the rabbit hole is actually referring to Alice in Wonderland. But.

I would say the organism that tends to burrow the deepest into the Earth is humans. Average oil well depth appears to be around 5,964 feet (1818 meters), that’s pretty deep. The deepest hole we ever drilled is supposedly the Kola Superdeep Borehole dug by the Soviets, it was 40,230 feet (12.2km) deep.

Perhaps not answer your looking for though.

I don’t know anything specifically about KeePassXC but it’s my understanding that a transform round is some computationally expensive task that can be preformed as many times as desired, but must be preformed the same number of times to decrypt as well. The point being to slow down any attempts at brute forcing access to you database if someone gets a hold of your encrypted DB file. For example say it takes one second to derive the proper DB access key from the password you entered to unlock the app, that doesn’t really matter to you logging in as almost no one is going to notice a one second delay in logging in. But if some one else gets a hold of your encrypted password DB then they have to wait one second for every password they try, making brute forcing the DB file practically impossible given you’ve chosen an adequate password.

Ideally you’d choose something which gives a delay not too inconvenient for you when logging in, but enough to thwart the person who might try and brute force the password even if they’re using more powerful hardware.

I had a peek at the source code and although I don’t actually know Rust it looks like that error comes from a check for character length in the function “is_valid_body_field”. Strangely it does the same check twice against two variables “POST_BODY_MAX_LENGTH” and “BODY_MAX_LENGTH”.

The smaller of the two is BODY_MAX_LENGTH which is set at 10000, so I assume the max character limit is 10,000. There are no other checks in that function other than the character count and that’s the only place in the source code that the text “invalid_body_field” shows up so I assume it’s only sent as a response to too much text, but as I said I don’t actually know Rust so I could be wrong.

Here’s the github page for the program that’s at least partially responsible for that output.

From that page it appears detected means “Device is detected, driver is found, but not tested yet” and working means “Driver is found and operates properly (passed static or dynamic tests)”