Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I don't understand tracking #100

Open
panicsteve opened this issue Mar 4, 2014 · 98 comments
Open

I don't understand tracking #100

panicsteve opened this issue Mar 4, 2014 · 98 comments

Comments

@panicsteve
Copy link

@panicsteve panicsteve commented Mar 4, 2014

This is more of a problem with me than a problem with Keybase. But I bring it up since you specifically asked us to file issues if we were unclear on anything.

Please forgive my naivety when it comes to signing and crypto matters. I understand, in a general way, the basic principles of signing and public key encryption, but I am no expert.

When I go to "track" someone on Keybase, here is the info that appears:

Tracking on Keybase is a big deal.

Tracking is sort of like "following" on other sites.

I'm with you so far.

However, when you "track" someone on Keybase, you are signing their key and identity proofs.

As far as signing someone else's key and identity proofs, I interpret that (possibly incorrectly) to mean I am vouching that this person's keybase identity is authentic. Like a "web of trust" sort of thing.

But that seems at odds with the word "tracking" -- to me, tracking/following evokes something that you can do frivolously on a whim. On the other hand, if I'm saying "yes, this person is really who they say they are", it seems like there should be more of a barrier to entry. Like I shouldn't "track" anyone I don't personally know.

This way you can request their username on any computer, and know you're getting the same answer from Keybase. This is especially useful in your terminal.

And now I'm really off in the weeds. What do you mean "when I request their username"? In what specific way is it useful in the terminal?

I guess what I'm fundamentally not understanding is what is the benefit (to me) of tracking someone? Is there a benefit to the other person?

Apologies again for cluelessness.

@copumpkin
Copy link

@copumpkin copumpkin commented Mar 5, 2014

As I understand it, your signature of their profile information is primarily for your own benefit. Say I track @malgorithms but don't trust his website not to get compromised. I plan on sending him a top-secret encrypted message in a week. I know his information is legit now, so I track him. If a week from now, the website gives me a different key for him (I can identify that it changed based on my signature), I'll certainly be suspicious of encrypting a message with that key.

If I indeed understand this correctly, a simple HMAC would be sufficient for this purpose, except for the fact that you might be sending that secret message from a different computer without your secret key, so you might know your public key fingerprint and nothing else. The public key signature scheme lets keybase tell you that you trusted that information at some point in the past.

Does that make sense? Please someone correct me if I'm missing the point.

@malgorithms
Copy link
Contributor

@malgorithms malgorithms commented Mar 5, 2014

hi @panicsteve - glad we're having this conversation, because it's something I've been struggling to explain on the site. And I need to do a better job. And yeah, it's confusing, because people think of "signing" someone's key in the WoT model, where you're making a statement that they are who they say there are.

Oh, and explaining things in a web form is tough because you pretty much have to get it down to 2 or 3 sentences or so, which is a constraint I don't have here.

So the problem, in a nutshell: when you first hear that there's some Keybase user you want to deal with, it's be nice if you could think of them in terms of a username, instead of some long fingerprint. That's probably what they told you or you read somewhere. Usernames are easier to remember and parse for errors that big fingerprints.

Our security model with Keybase is that the server isn't trusted. The client is (and you can write your own), but the server isn't. So when it replies with malgorithms' identity, there are two steps that have to happen:

  1. your trusted client has to make sure:
    • malgorithms' key is self-signed
    • each of the identities the server claims is verifiable by the key; this is done by scraping each of those sites, checking the statements, making sure the statements make the right claims, that they're signed by the key provided, etc.
  2. you, as a human have to review those identities and decide that's the person you want. it might be you're interested in a different twitter or github user, for example.

So now let's say you're on computer A and you encrypt a message for malgorithms. Then you go to computer B. Unfortunately you have to go through this process all over again. Because all you're typing in is "malgorithms" and once again, what if the server gives you the wrong info?

This is solved by you signing a statement of who malgorithms is and posting it on the server, for your own benefit. So when you perform a crypto action on malgorithms, you download that statement and know it hasn't been f'ed with, and you don't have to trust whether you got the right public key.

Does that make sense?

@panicsteve
Copy link
Author

@panicsteve panicsteve commented Mar 5, 2014

It does make sense. And I also don't know how you'd reduce that to a 3 or 4 sentence summary. :)

It seems like using a word other than "tracking" might help, but I'm not sure exactly what to suggest.

The first thing that came to mind is "snapshot". Like, snapshotting a person's identity at this point in time. This conveys that it's something that could change the road, but that you have a historical piece of evidence to compare those changes to.

Perhaps a new term along those lines, along with a link to a longer explanation from the web form for those who need the additional clarification?

It's a tough one!

@foozmeat
Copy link

@foozmeat foozmeat commented Mar 5, 2014

Tough problem indeed. Fundamentally you're protecting against a MitM attack correct?

Do you plan to expose to the user if someone you've tracked has tracked a user that you're interesting in communicating with? The key concept to convey to a novice is that if the stakes are greater than zero then they need to take an extra step to ensure that they're encrypting to the right key/ keybase identity. If, as a novice, I can see that my keybase social network has vouched for someone's identity then I'll feel more comfortable using them myself.

The rub I have with tracking is that it describes an active process. In other words if I'm tracking Steve then I expect to get notified about changes to Steve's account. That's not what happens. Steve's point about snapshotting is in the right direction in that it conveys you're recording the current state of someone's credentials and now you have something to compare to in the future.

If the site asked me if I wanted to "verify" (as opposed to track) Steve and then gave me his list of credentials to follow up on I think I'd know what my action accomplished and also understand that the action wasn't going to provide any further information to me in the future. You could also make clear that my vouching for him becomes a part of his public record. This has the potential side-effect of making the verifier feel a little more invested in the verification steps. I'd like to see when I verified him in the list currently labeled "Tracking".

Unfortunately this overloads the word Verify in a sense which is maybe not a problem.

@malgorithms
Copy link
Contributor

@malgorithms malgorithms commented Mar 5, 2014

Yes, MitM and coersion of our server; your satisfaction of Steve's identity is not portable without your signing it.

To clarify one thing about the future of tracking:

The rub I have with tracking is that it describes an active process. In other words if I'm tracking Steve then I expect to get notified about changes to Steve's account. That's not what happens.

Very soon, yes, if Steve's identity changes since you started tracking him, then a few things will happen:

  • in the CLI, if he adds an identity or something else making his new identity a superset, you'll receive a warning that he's added to his identity and you might want to review it
    • in the CLI, if something goes missing or he removes/revokes something, you'll get an error; how often this kind of thing is checked is subject to a couple controls
    • an email will be generated for you when his identity changes (which you can turn off)
    • on the website if you're tracking an out of date version of him, you'll be alerted when viewing his profile or trying to take some crypto action
    • and of course, if his key is deleted/revoked/replaced/whatever, you'll be notified too, in all these places

Obviously these things are not all implemented. But I just wanted to address the active/passive nature of it; "tracking" is intended to mean you have an ongoing interest in changes to his identity and key. They shouldn't be often.

Also, we chose "tracking" because we didn't want it to seem an endorsement of the accuracy of his identity. This seems to confuse people a lot. "Snapshot" is a good word, too, but we also want there to be a social element here, which will lend itself to future tools we may build (and others may, too), such as messaging platforms.

In summary: hmmmmmmmmm.

@CameronBanga
Copy link

@CameronBanga CameronBanga commented Mar 6, 2014

I'm not nearly as qualified to comment as you guys, but some thoughts from am extreme crypto novice. Like Steve, I was also a bit confused as to what tracking was at first. And while @malgorithms following me almost immediately on account creation felt neat and special, it did give me the sense that I should reciprocate or go out and find other users to track? I wasn't quite sure what the next step was.

I agree that this is difficult to do in one or two sentences, but maybe some sort of system could be written where users receive a signed encrypted message after account verification from @malgorithms? Is that even possible? I honestly have no idea, again I'm a complete novice and this is my first step into crypto. But maybe this message could include helpful links/long form information on next steps?

Thought being that if someone follows through far enough to this point, they will benefit from this information and not mind the longer explanation, and it won't cause friction during sign up, so won't be a 2-3 sentence limit?

@zigg
Copy link

@zigg zigg commented Mar 7, 2014

I think this is the right place to pitch in with my own thoughts on this. Thanks for the discussion so far.

@trenton42 is a good friend of mine, but we've never got around to actually verifying each other's fingerprints properly. (Later this month, I will do it.) But I thought, okay, I could track him.

$ keybase track trenton
info: ...checking identity proofs
✔ public key fingerprint: 7E3C FC83 D64E 2A7B C124 5AC9 191A 0473 89DD 2A77
✔ "trenton42" on twitter: https://twitter.com/trenton42/status/441778278521909248
✔ "trenton42" on github: https://gist.github.com/9404822
Is this the trenton you wanted? [y/N] y
Permanently track this user, and write proof to server? [Y/n]

This makes me a little uncomfortable, specifically the line about his fingerprint, and whoa, I'm writing a proof. I do rely on his Twitter handle already, but I feel like it's trust of the class that involves trusting a third-party, not direct trust. I get nervous asserting his fingerprint because I haven't actually been introduced to that via a trusted party.

I can certainly look at and verify his proofs myself without trusting the server, but that all reduces to a trust of Twitter, Github and Keybase, since if any of those are compromised or tricked, anyone can post a proof with any key they choose.

I guess what I'm trying to say is that I was all gung-ho to track until the above text popped up on my screen. 😆

@mdekstrand
Copy link

@mdekstrand mdekstrand commented Mar 15, 2014

To make sure that I understand what is going on with tracking: tracking a user writes a signed statement or object to the keybase.io server. This statement is a Keybase-specific concept, and is used to remember my verifications of the user's web-based identity, such as Twitter account.

Tracking a user does not create an actual PGP signature of their identity, such as is used in the Web of Trust.

Is that correct?

@malgorithms
Copy link
Contributor

@malgorithms malgorithms commented Mar 15, 2014

yes, that's correct.

@malgorithms
Copy link
Contributor

@malgorithms malgorithms commented Mar 15, 2014

and to be clear, you should feel a lot more comfortable tracking someone on Keybase than signing their identity in a WoT model. If you run the keybase client and id someone, it verifies the tweet, gist, etc., and makes sure both that it all exists, and also that the key is the correct one. It does the bulk of the work.

So all you have to do personally -- if you trust the client -- is make sure it is in fact the twitter or github username you want, and then you can reliably access their public key on any machine, without fear of the server lying.

Discovering who people track on Keybase is a fun thing, we hope, and it will help grow the service's popularity. (We'll do what we can to make crypto popular!) But note you can also track privately with --track-local.

I am frustrated trying to find an easy way to explain tracking. But it's very useful.

If you know someone on the site who only has a public key but hasn't proven their identity on any services, tracking is also helpful. Just make sure they tell you their fingerprint in person and you review it.

@mdekstrand
Copy link

@mdekstrand mdekstrand commented Mar 15, 2014

@malgorithms Thanks.

It seems there are at least 2 major difficulties in communicating tracking: communicating to new/unexperienced users what it is, and communicating it to experienced PGP users in a way that does not confuse or scare them with respect to existing trust and signature models.

@malgorithms
Copy link
Contributor

@malgorithms malgorithms commented Mar 15, 2014

yeah, well said. I feel sandwiched between the two. We'll definitely work on this.

@jeremy-w
Copy link

@jeremy-w jeremy-w commented Mar 18, 2014

After reading this, the prompt that comes to mind is, "Would you like to remember your judgment that this keybase user is so-and-so?" It's like notarizing for yourself that indeed this Keybase username with this quiver of social services is indeed the person your were hunting for.

Put antoher way, tracking seems to be adding a personal seal-of-approval on the identity for my own use, a seal that I can verify was written by myself and rely on in the future, but that no-one else need worry about. "Note to self" might be better as far as avoiding overloaded/stylized crypto terminology.

From that point of view, what's missing to me is a way to leave a private note for yourself along with the recorded judgment saying who that person is, in the event their social service/keybase names are not the first that come to mind for you when describing the person to yourself. For example, maybe you've always called the person "JW", even if their usernames happen to all be variants on "amigahaxx0r".

@timbray
Copy link

@timbray timbray commented Mar 19, 2014

OK, I just read this thread and the explanations I’ve seen still aren’t working for me. I’m confident enough in my own mainstream-ness that I'm pretty sure this means lots of others too. Let’s make it operational:

*** I do track "ericajoy". I say

keybase encrypt ericajoy -m whatever

It goes ahead and gives me the encrypted message

*** I don’t track “arlen”. I say

keybase encrypt arlen -m whatever

It goes and checks identity proofs right then and there, asks me whether this is the right arlen (and finally asks me if I want to track this person).

So...... this feels to me essentially like a caching/shortcutting operation. It uses a signature to protect the result of the checking computation. I suspect that if keybase ever takes off and needs to operate at scale, tracking is going to be a requirement, practically speaking, otherwise you’re gonna have twitter and github mad at you, among other things.

I assume that what you do is just sign the “user” object? With what, exactly?

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Mar 19, 2014

Here's the JSON object that I'm signing when I track Erica.

The relevant features are:

  • body.track.basics --- a summary of Erica's user object, so I can tell if she changes it later.
  • body.track.seq_tail --- the tail of Erica's hash chain, which summarizes everything that she's publicly signed
  • body.track.remote_proofs --- the remote proofs that I've OK'ed
  • body.track.key --- the details about Erica's key, used to verify the above proofs.
  • body.key --- My key, that I'm using to sign this tracking certificate.
{
   "ctime" : 1395242478,
   "body" : {
      "version" : 1,
      "track" : {
         "ctime" : 1395242478,
         "basics" : {
            "id_version" : 7,
            "last_id_change" : 1395122282,
            "username" : "ericajoy"
         },
         "seq_tail" : {
            "payload_hash" : "4d253e9de594dbc1926dad16dfe27c5a215387949e7c8e5e35b27659e77092db",
            "seqno" : 4,
            "sig_id" : "8d8a298b639867f6183edfee8a3c05654cb06b40bbc25662988fe9cec19bdf7f0f"
         },
         "remote_proofs" : [
            {
               "ctime" : 1395122257,
               "etime" : 1552802257,
               "seqno" : 2,
               "curr" : "7eb2fbac9d9cd608bb24b64302d0208a72100f28296f65f270d73b7c462760b6",
               "sig_type" : 2,
               "sig_id" : "f2ac76ac5c88b571396e26eed1993cefc246eba31b42a298e92c8951a370d8160f",
               "remote_key_proof" : {
                  "check_data_json" : {
                     "name" : "twitter",
                     "username" : "EricaJoy"
                  },
                  "proof_type" : 2,
                  "state" : 1
               }
            },
            {
               "ctime" : 1395122114,
               "etime" : 1552802114,
               "seqno" : 1,
               "curr" : "61a3f236bb5e2967b9450a471cb15d8829c6ece36353976ad3fec1f28715d63e",
               "sig_type" : 2,
               "sig_id" : "b23aeafe02e4dc04db71f49720045f88156bd282c12577de197858f6128c86080f",
               "remote_key_proof" : {
                  "check_data_json" : {
                     "name" : "github",
                     "username" : "EricaJoy"
                  },
                  "proof_type" : 3,
                  "state" : 1
               }
            }
         ],
         "id" : "cebe39978ac90f0db6ae3234b6aa1f00",
         "key" : {
            "kid" : "010182cb81f55dc659c245cc9c7ef6d9a7477caba8a3cf1df261bd595386c94b3d450a",
            "key_fingerprint" : "47cf5e0b8025ab6d5db9b75aa620b84340e9daa9"
         }
      },
      "type" : "track",
      "key" : {
         "uid" : "dbb165b7879fe7b1174df73bed0b9500",
         "key_id" : "6052B2AD31A6631C",
         "fingerprint" : "8efbe2e4dd56b35273634e8f6052b2ad31a6631c",
         "username" : "max",
         "host" : "keybase.io"
      }
   },
   "seqno" : 20,
   "prev" : "4ad325cfd0b724f5951c9ab779487a2e133a6863ac3027854e954d6c7d824507",
   "expire_in" : 157680000,
   "tag" : "signature"
}

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Mar 19, 2014

Btw, you're signing it with your public key. This captures the WoT component that PGP has, but with way more specifics. You can later verify your own signature on the tracking if you want to move between computers. You can also share these tracks with your friends, so they can base their trust on your signatures. That feature is still to come, but we thought we'd leave the option open.

@timbray
Copy link

@timbray timbray commented Mar 19, 2014

I'm thinking about the scenarios where the NSA drops by keybase with a National Security Letter, and it occurs to me that tracking might be a firewall against some of the bad things that they might be able to force you to do.

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Mar 19, 2014

An adversary who has full control of the server has three attacks that we can think of: (1) brute force secret keys stored on the server, for those users who have opted into this feature; (2) send malicious code to clients (which is why we recommend running the command-line program if possible); and (3) suppression of updates. The adversary can't forge tracking statements since they are all signed by the users.

@zigg
Copy link

@zigg zigg commented Mar 19, 2014

Wait, this is a trust thing now? I thought it wasn't. I thought it was effectively a personal seal.

An adversary can definitely create a tracking statement if nobody has bothered to check their (the adversary's) key in the first place. What's stopping the adversary from creating a key, compromising/tricking/coercing Twitter and/or GitHub into posting proofs signed with that key, and posing as a trusted party?

@CameronBanga
Copy link

@CameronBanga CameronBanga commented Mar 19, 2014

@zigg I'm not very well informed on this, so someone else can better describe, but I also thought that while keybase is Twitter/Github for now, personal server proofs were planned for the future as well, along with a handful of other potential services? But that Twitter/Github are the only two implemented now.

I assumed for the trust part, the idea being that if proofs are spread across enough locations, the difficulty compromising all would be more difficulty, thus making it much more likely that the key is true and not from an adversary.

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Mar 19, 2014

Sorry to be unclear. Right now, tracking is exactly as you say, a personal seal.

There's the potential for future features based on multiple hops, but as you correctly point out, it's a minefield, and we have to be extremely careful.

BTW @CameronBanga, we're nearly done with proofs for third-party domains names via HTTPS.

@timbray
Copy link

@timbray timbray commented Mar 19, 2014

@mattbehrens granting everything you say, if I track someone today, because
I know that person really is that twitter handle, and then the adversary
goes and slips in a new key, if I understand correctly, the tracking
signature will break, so tracking provides a useful defense against exactly
that. Or am I missing something?

On Wed, Mar 19, 2014 at 9:50 AM, Maxwell Krohn notifications@github.comwrote:

Sorry to be unclear. Right now, tracking is exactly as you say, a personal
seal.

There's the potential for future features based on multiple hops, but as
you correctly point out, it's a minefield, and we have to be extremely
careful.

BTW @CameronBanga https://github.com/CameronBanga, we're nearly done
with proofs for third-party domains names via HTTPS.


Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-38076505
.

@zigg
Copy link

@zigg zigg commented Mar 19, 2014

@timbray Slipping in a new key to an existing Keybase tracking relationship should indeed get noticed, but I bet some social engineering could convince the target that it's an actual new key because the old one was lost or compromised.

It is true that the more proofs you have, the harder the exploit becomes. I am concerned, though, that most proofs likely reduce to email, cf. the Mat Honan incident. This is why I think it's critical to both carefully check PGP fingerprints and keep private keys tightly held.

@timbray
Copy link

@timbray timbray commented Mar 19, 2014

Actually, there is a real live bug here. The web page at
https://keybase.io/timbray still asserts that I’m tracking paulehoffman but
in fact I no longer am, because he changed since I did so. So the
page-render logic should check that, right?

On Wed, Mar 19, 2014 at 10:09 AM, Matt Behrens notifications@github.comwrote:

@timbray https://github.com/timbray Slipping in a new key to an
existing Keybase tracking relationship should indeed get noticed, but I bet
some social engineering could convince the target that it's an actual new
key because the old one was lost or compromised.

It is true that the more proofs you have, the harder the exploit becomes.
I am concerned, though, that most proofs likely reduce to email, cf. the
Mat Honan incident. This is why I think it's critical to both carefully
check PGP fingerprints and keep private keys tightly held.


Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-38079232
.

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Mar 19, 2014

I think it's currently working as we originally intended, but we need better messaging here. We probably shouldn't break the tracking relationship if a proof was added. It should probably break if a proof is deleted (the Website doesn't currently do this). And it should probably break on public key update. Thanks for bringing this up, more work to do here (one of many reasons we're still in alpha).

@timbray
Copy link

@timbray timbray commented Mar 19, 2014

Mildly but not very sorry about hijacking this bug report into a discussion
of vulnerability models...

Upon reflection, it seems to me that the nastiest attack by far is the
combination of (2) and a stored private key. Because when I type my pass
phrase into malicious javascript, the attacker has my private key and it’s
100% game over. Right?

I wouldn’t mind trying out keybase-without-stored-private-key, but there
doesn’t seem to be an admin interface to remove the stored private key. Am
I missing it?

On Wed, Mar 19, 2014 at 9:31 AM, Maxwell Krohn notifications@github.comwrote:

An adversary who has full control of the server has three attacks that we
can think of: (1) brute force secret keys stored on the server, for those
users who have opted into this feature; (2) send malicious code to clients
(which is why we recommend running the command-line program if possible);
and (3) suppression of updates. The adversary can't forge tracking
statements since they are all signed by the users.


Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-38073345
.

@CameronBanga
Copy link

@CameronBanga CameronBanga commented Mar 19, 2014

@timbray My uninformed thought would be that in a situation where this scenario is a concern (and I hadn't thought about it personally, that does seem somewhat scary, good point), it'd be probably best to revoke the private key together and then go ahead with create a new private key and go through the verification process all together.

Inconvenient, but if a person has concern about something like a malicious person compromising the server, you probably also shouldn't trust that you haven't been compromised in the past, etc, and start fresh, as opposed to just trusting that when you hit "Delete private key from keybase", that the key has been deleted/handled properly?

@timbray
Copy link

@timbray timbray commented Mar 19, 2014

Well, the nice thing about keybase is that if you use the command-line
client and don’t store your private key, you're immune to that particular
attack. Which is a really powerful statement, and one of the things that
makes Keybase interesting to me.

On Wed, Mar 19, 2014 at 1:57 PM, Cameron Banga notifications@github.comwrote:

@timbray https://github.com/timbray My uninformed thought would be that
in a situation where this scenario is a concern (and I hadn't thought about
it personally, that does seem somewhat scary, good point), it'd be probably
best to revoke the private key together and then go ahead with create a new
private key and go through the verification process all together.

Inconvenient, but if a person has concern about something like a malicious
person compromising the server, you probably also shouldn't trust that you
haven't been compromised in the past, etc, and start fresh, as opposed to
just trusting that when you hit "Delete private key from keybase", that the
key has been deleted/handled properly?


Reply to this email directly or view it on GitHubhttps://github.com//issues/100#issuecomment-38105835
.

@CameronBanga
Copy link

@CameronBanga CameronBanga commented Mar 19, 2014

@tinbray Oh sure, get that and agree 100%. Maybe I'm misunderstanding, but I though that Keybase had this feature and that storing the private key was an optional decision that the user made on account setup, so if the user wanted to use Keybase without storing the private key, they would choose this option during set up and key would never be stored in the first place.

At least I thought I remembered that from setup, in that storing the private key was not required, but was recommended by Keybase (presumably for using things like the web encrypt/decrypt UI, etc). So my only thought was that if you set up your account initially with a stored private key, you'd first have to revoke the key and then go through setup process/verification again, without the "store private key" option.

@mlinton
Copy link

@mlinton mlinton commented Dec 9, 2014

One of the inherent risks in tracking is the meta-data regarding the people you track, or the people tracking you. This information establishes a relationship between two entities and erodes privacy, regardless of who stores it (on keybase or locally). Look to some of the issues with PGP clients updating keys within keychains. Intelligence actors would find this to be a very sought after source of connection data.

Establishing trustworthy private identities is probably the number one challenge in todays trust model.

@foozmeat
Copy link

@foozmeat foozmeat commented Dec 9, 2014

mlinton, I think your concerns on metadata tracking are valid however I don't believe that preventing this kind of tracking should be a goal of keybase. Keybase exists as a layer of trust above what PGP provides and will be easier for beginner/casual users to grasp (eventually).

If your threat modal includes actors who would be interested in who you're communicating with then Keybase is not the right tool for you.

Having said all of that I think it would be a cool thing for the keybase folks to explain metadata tracking on the site and why using keybase's modal might be a bad idea given certain circumstances.

@malgorithms
Copy link
Contributor

@malgorithms malgorithms commented Dec 9, 2014

Having said all of that I think it would be a cool thing for the keybase folks to explain metadata tracking on the site and why using keybase's modal might be a bad idea given certain circumstances.

We'll post more info on this in the future, when we exit alpha.

One thing to consider is that we've designed our data model so that it's easy to mirror Keybase's sig chain in its entirety, even with no fears of lies by omission. (See our server security docs and how we put our merkle tree root in the bitcoin blockchain.)

What this means for people who worry about the leakage associated with requesting someone's key: you can ask any server that mirrors keybase. You can also implement a mirror easily, and prove to a client that they're getting up to date info.

You could even run a small program which mirrors every user's key and proof chain. Or even a "random" seeming subset. There are a number of solutions for those who fear key lookup metadata leakage. You can also visit Keybase and Keybase proofs over Tor.

Outside of Keybase, checking the proofs themselves is arguably metadata leakage. If you visit someone's tweet where they say "this is my fingerprint", someone could have infiltrated twitter and noticed this. This is true outside Keybase, too: if you're getting someone's key anywhere on the Internet or reviewing statements about that key, you're leaking info.

But yeah, public tracking does/will have metadata leakage - we figure this is abundantly clear when we publish trackers on the website and use the word "public" in the client. The idea is that you've posted a public statement that on date X someone's proof looked like P...and this strengthens the audit of their key.

cc

@thedod
Copy link

@thedod thedod commented Jan 17, 2015

I'd like to suggest yet another alternative for the word "tracking": "recognizing".
The essence of the action is this:

you, as a human have to review those identities and decide that's the person you want. it might be you're interested in a different twitter or github user, for example.

The rest (including the crypto) is just plumbing.

Also: the sentence "@thedod has recognized @malgorithms" is a past event (i.e. a snapshot), while "@thedod is tracking @malgorithms" sounds as if I'm regularly verifying stuff. It's true I may "recognize" you again once my "recognition" expire (or your proof does), but once again — this would be a snapshot and not an ongoing process (and there's no guarantee I'll "recognize" you again: e.g. if you change your avatar and start speaking a different language 😉).

@DigitalBrains1
Copy link

@DigitalBrains1 DigitalBrains1 commented Feb 1, 2015

I hope you'll excuse me for not reading the whole discussion (I skimmed through it), but I wanted to report a little mistake:

The PGP web of trust has existed for over 20 years. However it is very difficult to use [...]

Yes, it is very hard to use, as is apparent from the fact the information in that very footnote is inaccurate, or wrong, in an important aspect! :)

It says you trust John, but you'd also need to trust Carla if you wish to be able to get key validity for Maria. If you don't assign ownertrust to Carla, the PGP Web-of-Trust model will not assign any validity to Maria through Carla's signature. This makes sense because trust is not transitive. I've signed a good number of keys of people I don't know at keysigning parties. But I'm making a statement about their identity, not their trustworthiness. If it were to work as it is explained in the footnote, somebody who trusts me would also suddenly trust signatures made by people I only met once on a keysigning party and don't know in any other capacity.

And since Carla apparently signs keys while drunk (XKCD fan?), I would not trust her signatures ;).

<edit>
The final paragraph might very well be referring to you needing to assign trust to Carla as well, but I think as it stands this is not apparent from the text. As it stands, it seems to confirm a frequent misunderstanding of the Web-of-Trust, namely that trust is somehow transitive in the WoT.
</edit>

@vext01
Copy link

@vext01 vext01 commented Aug 2, 2015

Sorry to dig up an old thread.

Am I right in thinking that "tracking" somebody on keybase, is entirely separate from signing someone's public key? I notice that the contacts keybase has imported into my keychain are both untrusted and unverified in the eyes of the command line gpg tools. This means that when I send an encrypted email in mutt, I get a warning. Should we also sign each others keys int the traditional manner (i.e. external to keybase)?

@chigh
Copy link

@chigh chigh commented Aug 2, 2015

For what it's worth, I do.

@quinot
Copy link

@quinot quinot commented Aug 28, 2015

Hi,
Unless I'm much mistaken, there's a fundamental difference in the tracking instructions between using the command line client (which will locally verify bindings, and then sign an object describing the bindings it has verified), and the "bash+GPG+CURL" instructions, where the object to sign is provided by Keybase. In the latter case, this means that the user has to trust the Keybase server as to which proofs have been verified, which essentially kills the notion that the server needs not be trusted. This seems quite fundamental.

@oconnor663
Copy link

@oconnor663 oconnor663 commented Aug 28, 2015

@DigitalBrains1 I think you're right. I've filed a ticket for us to fix the footnote.

@quinot you're right, the local tracking instructions don't automatically verify proofs for you. It's expected that you'll do this to your satisfaction by hand. A couple reasons:

  1. It's actually too complicated. Each website has different logic for scraping a proof out of the DOM (or the hash of a proof in Twitter's case, which then has to be compared to the full text fetched from the server), and all of that would have to be translated into bash. We use a whole JS library to do this in the client and in the browser.
  2. Because you're pasting code that you got from the server, you're essentially trusting the server anyway. The difference between the local client and the web page in this respect is that you can install the local client in a way that makes it more difficult for the server to single you out and ship you bad code. With JS in the browser you have to worry that the server's snooping on you in a way that nobody else will see, and the same ends up being true of bash pasted from the browser.

@mitar
Copy link

@mitar mitar commented Dec 11, 2015

To my understanding, "tracking" is more like "pinning". You pin a key of somebody else and remember it.

@patcon
Copy link

@patcon patcon commented Dec 11, 2015

As someone just about to finally unsub from this long-running thread, that is imho a much better term @mitar!

@mitar
Copy link

@mitar mitar commented Dec 11, 2015

I opened a ticket: #1913

@sull
Copy link

@sull sull commented Dec 19, 2015

If Pinning, then why not use MONITOR as a base crypto verb?

"observe and check the progress or quality of (something) over a period of time; keep under systematic > review."

If monitoring is the first action taken by a user upon another user, then many other sub-actions could fall beneath it. Such as FOLLOW (receive alerts, quick access to activity in client UIs etc), VOUCH (periodically vouch for someone after meetings, projects and other associations, loose or tight, that warrant this social gesture), CERTIFY (voluntary occasional assessment of the users identity chain), MESSAGE, etc etc....

Now as I type this, MONITOR could be akin to Facebook Friend, however on FB you don't have to FOLLOW a friend or even interact with them. It has become the initial thread of tethering people together.
Likewise, MONITOR in Keybase could work in a similar manner. It is the beginning of a connection. The thread between users gets more robust and durable as deeper actions are performed. MONITOR, like pinning, means you are just putting the user on your radar. They are a blip. But they are there. Pinning is a bit less accurate because it is often used to describe putting something at the top of a bunch of other things. Pin a tweet, Pin a forum post, Pin an email etc. Its not bad. But not the best especially when you are pinning many, it starts to break down. In the physical world, pinning stuff up on a board is a closer resemblance to Keygen tracking (visualize a crime case investigation scene for example). But it's messy feeling right? MONITOR does not really bring in such visualizations or pre-conceptions I dont think.

MONITOR is also like a cousin to TRACK. It is less agressive, however. Tracking makes me thing of sniffing and pursuing and hunting. All aggressive actions to find someone or keep them close to watch every move etc. Monitoring to me is just more passive and easy-going. It seems that's the more proper vibe of this Keybase usage pattern.

So, there is my input after reading this entire thread on a Friday night and Sat morning :)

@rvs
Copy link

@rvs rvs commented Jan 3, 2016

I've been keeping an eye on Keybase for more than a year now and so far it seems promising. Just like everybody else on this thread I got super confused by the notion of "tracking" but I am better now ;-)

For anybody (like myself) coming from hardcore PGP background it would've been much easier to get what Keybase is doing if the notion of sigchain was explicitly exposed and discussed from the get go.

Speaking of which, are there any plans to allow CLI-driven inspection of sigchain for a given user? Is there an issue for an extension like this or should I file a new issue?

@zQueal
Copy link

@zQueal zQueal commented Jan 3, 2016

As it stands, the keybase id command supposedly checks the sig chain, so I'm sure it would be trivial to simply display it for self inspection if that's what you're getting at;

NAME:
   keybase id - Identify a user and check their signature chain

USAGE:
   keybase id [command options] [username]

DESCRIPTION:
   Identify a user and check their signature chain.  Don't specify a username to identify yourself.  You     can also specify proof assertions like user@twitter.

OPTIONS:
   -t, --track-statement        Output a tracking statement (in JSON format).

Perhaps you can already view what you need if you add the debug string (-d);

05:19:07.399793 - [DEBU keybase json.go:48] 001 + loading config file: C:\Users\zqueal\AppData\Roaming\Keybase\config.json
05:19:07.400793 - [DEBU keybase json.go:76] 002 - successfully loaded config file
05:19:07.400793 - [DEBU keybase config.go:114] 003 Config: mapping server ->
05:19:07.401793 - [DEBU keybase config.go:114] 004 Config: mapping socket_file ->
05:19:07.401793 - [DEBU keybase config.go:114] 005 Config: mapping home ->
05:19:07.402793 - [DEBU keybase ui.go:434] 006 Can't set GPG_TTY; discover failed
05:19:07.402793 - [DEBU keybase config.go:114] 007 Config: mapping timers ->
05:19:07.403793 - [DEBU keybase globals.go:193] 008 Keybase CLI 1.0.6-1
05:19:07.403793 - [DEBU keybase globals.go:193] 009 - Built with go1.5.1
05:19:07.403793 - [DEBU keybase globals.go:193] 00a - Visit https://keybase.io for more details
05:19:07.404794 - [DEBU keybase main.go:101] 00b + configureProcesses
05:19:07.404794 - [DEBU keybase fork_server.go:47] 00c Getting flock
05:19:07.405794 - [DEBU keybase config.go:114] 00d Config: mapping home ->
05:19:07.405794 - [DEBU keybase config.go:114] 00e Config: mapping pid_file ->
05:19:07.406794 - [DEBU keybase config.go:114] 00f Config: mapping home ->
05:19:07.406794 - [DEBU keybase fork_server.go:64] 010 The server is still up
05:19:07.407794 - [DEBU keybase main.go:158] 011 | After forks; newProc=false
05:19:07.407794 - [DEBU keybase main.go:179] 012 + configureLogging
05:19:07.408794 - [DEBU keybase config.go:114] 013 Config: mapping local_rpc_debug ->
05:19:07.408794 - [DEBU keybase config.go:114] 014 Config: mapping local_rpc_debug ->
05:19:07.408794 - [DEBU keybase main.go:215] 015 Setting remote log level: 1
05:19:07.410794 - [DEBU keybase main.go:181] 016 - configureLogging
05:19:07.410794 - [DEBU keybase versionfix.go:21] 017 + FixVersionClash
05:19:07.413794 - [DEBU keybase log.go:30] 018 Config: mapping server ->
05:19:07.413794 - [DEBU keybase log.go:30] 019 Config: mapping socket_file ->
05:19:07.413794 - [DEBU keybase log.go:30] 01a Config: mapping home ->
05:19:07.417794 - [DEBU keybase log.go:30] 01b | configured GPG w/ path: C:\Program Files (x86)\GNU\GnuPG\pub\gpg2.exe
05:19:07.420794 - [DEBU keybase versionfix.go:33] 01c | Contacted service; got version: 1.0.6-1
05:19:07.421795 - [DEBU keybase versionfix.go:55] 020 | version check 1.0.6-1 v 1.0.6-1
05:19:07.421795 - [DEBU keybase versionfix.go:57] 021 | versions check out
05:19:07.422795 - [DEBU keybase versionfix.go:23] 022 - FixVersionClash -> <nil>
05:19:07.422795 - [DEBU keybase main.go:103] 023 - configureProcesses -> <nil>
05:19:07.421795 - [DEBU keybase log.go:30] 01f Config: mapping home ->
05:19:07.421795 - [DEBU keybase log.go:30] 01d Config: mapping config_file ->
05:19:07.421795 - [DEBU keybase log.go:30] 01e | configured GPG w/ path: C:\Program Files (x86)\GNU\GnuPG\pub\gpg2.exe
05:19:07.425795 - [DEBU keybase log.go:30] 024 + LoadUser(uid=, name=keybase://zqueal)
05:19:07.425795 - [DEBU keybase log.go:30] 025 - makeContext -> <nil>
05:19:07.426795 - [DEBU keybase log.go:30] 026 | using a remote UI as normal
05:19:07.426795 - [DEBU keybase log.go:30] 027 - Account "G - GetMyUID - GetUID"
05:19:07.427795 - [DEBU keybase log.go:30] 030 LoadUser: {UID: Name:keybase://zqueal PublicKeyOptional:true NoCacheResult:false Self:false ForceReload:false AllKeys:false LoginContext:<nil> AbortIfSigchainUnchanged:false Contextified:{g:0x2023c620}}
05:19:07.426795 - [DEBU keybase log.go:30] 029 + Account "G - GetMyUID - GetUID"
05:19:07.426795 - [DEBU keybase log.go:30] 02a + loadUserFromLocalStorage(15b4292135d94eba7afb70290fdcc900)
05:19:07.426795 - [DEBU keybase log.go:30] 02b + RunEngine(Identify)
05:19:07.426795 - [DEBU keybase log.go:30] 02c | resolved to 15b4292135d94eba7afb70290fdcc900
05:19:07.426795 - [DEBU keybase log.go:30] 02d + RunEngine(Id)
05:19:07.426795 - [DEBU keybase log.go:30] 02e + makeContext(0, {0 zqueal false false false {CLI id command} 0})
05:19:07.426795 - [DEBU keybase log.go:30] 02f + LevelDb.open
05:19:07.427795 - [DEBU keybase log.go:30] 031 - LevelDb.open -> ok
05:19:07.426795 - [DEBU keybase log.go:30] 028 + Resolving username keybase://zqueal
05:19:07.429795 - [DEBU keybase log.go:30] 032 | Loaded successfully
05:19:07.430795 - [DEBU keybase log.go:30] 033 + ParseKeyFamily
05:19:07.521800 - [DEBU keybase log.go:30] 034 - ParseKeyFamily -> ok
05:19:07.521800 - [DEBU keybase log.go:30] 035 | Loaded username zqueal (uid=15b4292135d94eba7afb70290fdcc900)
05:19:07.522800 - [DEBU keybase log.go:30] 036 + LevelDb.open
05:19:07.522800 - [DEBU keybase log.go:30] 037 - LevelDb.open -> ok
05:19:07.522800 - [DEBU keybase log.go:30] 038 + LevelDb.open
05:19:07.522800 - [DEBU keybase log.go:30] 039 | LookupPath
05:19:07.522800 - [DEBU keybase log.go:30] 03a + MerkleClient.LoadRoot()
05:19:07.522800 - [DEBU keybase log.go:30] 03b - LevelDb.open -> ok
05:19:07.522800 - [DEBU keybase log.go:30] 03c - loadUserFromLocalStorage(zqueal,15b4292135d94eba7afb70290fdcc900)
05:19:07.522800 - [DEBU keybase log.go:30] 03d + API GET request to https://keybase.io/_/api/1.0/merkle/path.json?poll=10&uid=15b4292135d94eba7afb70290fdcc900
05:19:07.523800 - [DEBU keybase log.go:30] 03e + MerkleClient.LookupUser(map[uid:15b4292135d94eba7afb70290fdcc900 poll:10])
05:19:07.523800 - [DEBU keybase log.go:30] 03f - MerkleClient.LoadRoot() -> &{{0x2023c620} 341526 [3 225 70 205 175 129 54 104 10 213 102 145 42 50 52 12 236 140 148 146] 0x206063c0 {"body":{"key":{"fingerprint":"03e146cdaf8136680ad566912a32340cec8c9492","key_id":"2A32340CEC8C9492"},"legacy_uid_root":"d3450288d233fe9125d0b6f8196dbc93447bca2630300898781a637a44752032","prev":"41000d2fa051c61c2650941c2cebd53943db6b90e4df2636f1ef63c664d343023666783d2f7f0a564a603d2dcd1b670db1d4af548521968059c1d2a62c3ff1dd","root":"94ba53b88427ae895b69eb10e76bea8eb572ac911113b495eaa6e616d731052701e6b245f6d24320f749f11c5ad212657f988ced6ce5f2dae2ea55aa72eea57c","seqno":341526,"txid":"1b41c295eb22981170418c9aa1fed715","type":"merkle_root","version":1},"ctime":1451815873,"tag":"signature"} 0x20606580 [148 186 83 184 132 39 174 137 91 105 235 16 231 107 234 142 181 114 172 145 17 19 180 149 234 166 230 22 215 49 5 39 1 230 178 69 246 210 67 32 247 73 241 28 90 210 18 101 127 152 140 237 108 229 242 218 226 234 85 170 114 238 165 124] [211 69 2 136 210 51 254 145 37 208 182 248 25 109 188 147 68 123 202 38 48 48 8 152 120 26 99 122 68 117 32 50] 1451815873}
05:19:07.576803 - [DEBU keybase log.go:30] 040 | Result is: 200 OK
05:19:07.601805 - [DEBU keybase log.go:30] 041 | VerifyRoot
05:19:07.601805 - [DEBU keybase log.go:30] 042 - successful API call
05:19:07.601805 - [DEBU keybase log.go:30] 043 | Merkle root: got back 341526, >= cached 341526
05:19:07.602805 - [DEBU keybase log.go:30] 044 | VerifyUser
05:19:07.616806 - [DEBU keybase log.go:30] 045 - ParsingMerkleUserLeaf -> ok
05:19:07.616806 - [DEBU keybase log.go:30] 046 + ParsingMerkleUserLeaf
05:19:07.617806 - [DEBU keybase log.go:30] 047 | VerifyUsername
05:19:07.617806 - [DEBU keybase log.go:30] 048 | Failed to map Username zqueal -> UID 15b4292135d94eba7afb70290fdcc900 via direct hash
05:19:07.617806 - [DEBU keybase log.go:30] 049 | Local basics version is up-to-date @ version 130
05:19:07.617806 - [DEBU keybase log.go:30] 04a + LevelDb.open
05:19:07.617806 - [DEBU keybase log.go:30] 04b | Preload failed
05:19:07.620806 - [DEBU keybase log.go:30] 05e | loading link; curr=aa2c03d7e83c28b21edef77812d62213eafdde59a4af4d5bbf8fa2544fef1e71
05:19:07.617806 - [DEBU keybase log.go:30] 04d | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) LoadLinksFromStorage
05:19:07.617806 - [DEBU keybase log.go:30] 04e | Freshness: basics=true; for 15b4292135d94eba7afb70290fdcc900
05:19:07.617806 - [DEBU keybase log.go:30] 04f + SigChainLoader.LoadFromStorage(15b4292135d94eba7afb70290fdcc900)
05:19:07.617806 - [DEBU keybase log.go:30] 050 + SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900)
05:19:07.617806 - [DEBU keybase log.go:30] 051 | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) GetFingerprint
05:19:07.617806 - [DEBU keybase log.go:30] 052 | Username zqueal mapped to 15b4292135d94eba7afb70290fdcc900 via Merkle lookup
05:19:07.618806 - [DEBU keybase log.go:30] 053 + LevelDb.open
05:19:07.618806 - [DEBU keybase log.go:30] 054 | Checking cased username difference: zqueal v zQueal
05:19:07.618806 - [DEBU keybase log.go:30] 055 - LevelDb.open -> ok
05:19:07.619806 - [DEBU keybase log.go:30] 056 - MerkleClient.LookupUser(map[uid:15b4292135d94eba7afb70290fdcc900 poll:10]) -> OK
05:19:07.626806 - [DEBU keybase log.go:30] 07b | loading link; curr=1919fc94d51940c62fb7f20cb6cd0e9df2bac1861b1eb5c2c696ebaabe9b55e5
05:19:07.626806 - [DEBU keybase log.go:30] 07c | Unpacked Link 49c7ad82c74ee985251296e8a529377548b1b5c1216629a245458f016b081e5f
05:19:07.620806 - [DEBU keybase log.go:30] 059 + LevelDb.open
05:19:07.620806 - [DEBU keybase log.go:30] 05a | Setting loadKID=01010373e851fecad178051f4af74acd9dbcbe73cd4ba0fca976a3135d72b064ffee0a
05:19:07.628806 - [DEBU keybase log.go:30] 08b - LevelDb.open -> ok
05:19:07.620806 - [DEBU keybase log.go:30] 05c | Unpacked Link 8e81da8b9232c844c5fff2c15945456f0c7791d0d7ea782ef67c636b54ecc67c
05:19:07.620806 - [DEBU keybase log.go:30] 05d - LevelDb.open -> ok
05:19:07.617806 - [DEBU keybase log.go:30] 04c | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) AccessPreload
05:19:07.620806 - [DEBU keybase log.go:30] 05f | loading link; curr=f7518cbdf60680e70e1033f8b4e475bab78f92741a283cd9ee448e8547b8ae76
05:19:07.631807 - [DEBU keybase log.go:30] 0a8 | loading link; curr=bfc0083eff47fdc5b538f5ec1224188b274ed8d1ea9d5e89571e8d16a36f0838
05:19:07.631807 - [DEBU keybase log.go:30] 0a9 | Unpacked Link 96cff4ecc55454caf0cfda2efbaa31c82ac34bba11d87ed1cce0a07f6c0b3868
05:19:07.620806 - [DEBU keybase log.go:30] 062 | Link is marked as 'sig_verified'
05:19:07.622806 - [DEBU keybase log.go:30] 063 + LevelDb.open
05:19:07.622806 - [DEBU keybase log.go:30] 064 | Unpacked Link f7518cbdf60680e70e1033f8b4e475bab78f92741a283cd9ee448e8547b8ae76
05:19:07.634807 - [DEBU keybase log.go:30] 0c6 | loading link; curr=da9751d314c6e4d7f95c5b774e1551c40162dd283c8a215063213596276047cc
05:19:07.623806 - [DEBU keybase log.go:30] 066 - LevelDb.open -> ok
05:19:07.623806 - [DEBU keybase log.go:30] 067 | Link is marked as 'sig_verified'
05:19:07.624806 - [DEBU keybase log.go:30] 068 + LevelDb.open
05:19:07.624806 - [DEBU keybase log.go:30] 069 | loading link; curr=8810b3a08f411c698197da2ae2de9940d03684a92747f9a6b7835c9cf10998c1
05:19:07.636807 - [DEBU keybase log.go:30] 0dd | Unpacked Link df0ce4cdc596541db52f5ac62427838a6d3bf702a144bd1040eda442a9bb5613
05:19:07.636807 - [DEBU keybase log.go:30] 0de | Unpacked Link b048295f72dde311fb352b91202dd398dde89262b23b1c38a62af67da660c0b2
05:19:07.624806 - [DEBU keybase log.go:30] 06c + LevelDb.open
05:19:07.625806 - [DEBU keybase log.go:30] 06d | loading link; curr=512ee3afc25e34d708108325baae7b338b2e798aad3d33d362e5fc36cadf1958
05:19:07.625806 - [DEBU keybase log.go:30] 06e | Link is marked as 'sig_verified'
05:19:07.625806 - [DEBU keybase log.go:30] 06f - LevelDb.open -> ok
05:19:07.625806 - [DEBU keybase log.go:30] 070 | Unpacked Link 8810b3a08f411c698197da2ae2de9940d03684a92747f9a6b7835c9cf10998c1
05:19:07.625806 - [DEBU keybase log.go:30] 071 - LevelDb.open -> ok
05:19:07.625806 - [DEBU keybase log.go:30] 072 | Unpacked Link 1919fc94d51940c62fb7f20cb6cd0e9df2bac1861b1eb5c2c696ebaabe9b55e5
05:19:07.640807 - [DEBU keybase log.go:30] 0f3 - LevelDb.open -> ok
05:19:07.625806 - [DEBU keybase log.go:30] 074 + LevelDb.open
05:19:07.641807 - [DEBU keybase log.go:30] 0fe | loading link; curr=36d1285a0194aec54a8dbe2f1a047e5869a2775e1d2d82d9d25b78c4f628429b
05:19:07.642807 - [DEBU keybase log.go:30] 101 | loading link; curr=a7bdae9a8cc5367c9ce49dd853175bcd2c05d28963963053f71296b2563b18d5
05:19:07.642807 - [DEBU keybase log.go:30] 10c | Unpacked Link af25b0f3e0cb647676d969c47fc2c4f32c6ef5a4f053cbfc03736d94b9e032b9
05:19:07.626806 - [DEBU keybase log.go:30] 078 | loading link; curr=49c7ad82c74ee985251296e8a529377548b1b5c1216629a245458f016b081e5f
05:19:07.626806 - [DEBU keybase log.go:30] 079 + LevelDb.open
05:19:07.626806 - [DEBU keybase log.go:30] 07a | loading link; curr=fb4eb5ab067c52b7037d7460d1e4b0126665d236673c614b06f3edbd54900bde
05:19:07.619806 - [DEBU keybase log.go:30] 058 - LevelDb.open -> ok
05:19:07.619806 - [DEBU keybase log.go:30] 057 | loading link; curr=8e81da8b9232c844c5fff2c15945456f0c7791d0d7ea782ef67c636b54ecc67c
05:19:07.627806 - [DEBU keybase log.go:30] 07d + LevelDb.open
05:19:07.627806 - [DEBU keybase log.go:30] 07e - LevelDb.open -> ok
05:19:07.627806 - [DEBU keybase log.go:30] 07f + LevelDb.open
05:19:07.627806 - [DEBU keybase log.go:30] 080 | Link is marked as 'sig_verified'
05:19:07.627806 - [DEBU keybase log.go:30] 081 | loading link; curr=d162d91056d8496010f2062b5d59162f623bd73652a3db80c6bba168724618b6
05:19:07.627806 - [DEBU keybase log.go:30] 082 - LevelDb.open -> ok
05:19:07.647807 - [DEBU keybase log.go:30] 12c + LevelDb.open
05:19:07.647807 - [DEBU keybase log.go:30] 132 + LevelDb.open
05:19:07.628806 - [DEBU keybase log.go:30] 085 | Unpacked Link 403e2fcc6eab83f4b37925e07eed988f163e80729cc259060d7d3e15d6fdecca
05:19:07.628806 - [DEBU keybase log.go:30] 086 | loading link; curr=403e2fcc6eab83f4b37925e07eed988f163e80729cc259060d7d3e15d6fdecca
05:19:07.628806 - [DEBU keybase log.go:30] 087 | Unpacked Link d162d91056d8496010f2062b5d59162f623bd73652a3db80c6bba168724618b6
05:19:07.628806 - [DEBU keybase log.go:30] 088 - LevelDb.open -> ok
05:19:07.628806 - [DEBU keybase log.go:30] 089 + LevelDb.open
05:19:07.628806 - [DEBU keybase log.go:30] 08a | loading link; curr=02c314d82e6cbd2cb2a90ebb429b1cf19d4338c2077e3eef2cad93b294a454c8
05:19:07.628806 - [DEBU keybase log.go:30] 08c - LevelDb.open -> ok
05:19:07.628806 - [DEBU keybase log.go:30] 08d + LevelDb.open
05:19:07.620806 - [DEBU keybase log.go:30] 05b | Link is marked as 'sig_verified'
05:19:07.651808 - [DEBU keybase log.go:30] 14d + LevelDb.open
05:19:07.651808 - [DEBU keybase log.go:30] 14e | loading link; curr=968c4bb8056dd87f689e455013cde3a83cac3f06ecb2aa9415da4f6d20fad18f
05:19:07.628806 - [DEBU keybase log.go:30] 090 + LevelDb.open
05:19:07.628806 - [DEBU keybase log.go:30] 091 - LevelDb.open -> ok
05:19:07.653808 - [DEBU keybase log.go:30] 15f + LevelDb.open
05:19:07.628806 - [DEBU keybase log.go:30] 093 | Unpacked Link 9fdc4a1617c474ace33c1e40da8f26e4d4acf25f6de542fca37f520f807d5665
05:19:07.628806 - [DEBU keybase log.go:30] 094 | loading link; curr=5ed83ebfe9048369a0e0c8f5d8466649fb26f9b8151b6fdbdad2276192f14d5d
05:19:07.654808 - [DEBU keybase log.go:30] 16f - LevelDb.open -> ok
05:19:07.654808 - [DEBU keybase log.go:30] 170 | Unpacked Link 97ba80437fa597b6b619ae66fd284cb5066eb8dde02a761bc60042cd0aaa83e5
05:19:07.655808 - [DEBU keybase log.go:30] 175 - SigChainLoader.LoadFromStorage(15b4292135d94eba7afb70290fdcc900) -> ok
05:19:07.630806 - [DEBU keybase log.go:30] 097 - LevelDb.open -> ok
05:19:07.630806 - [DEBU keybase log.go:30] 099 | Unpacked Link 5ed83ebfe9048369a0e0c8f5d8466649fb26f9b8151b6fdbdad2276192f14d5d
05:19:07.630806 - [DEBU keybase log.go:30] 09a + LevelDb.open
05:19:07.630806 - [DEBU keybase log.go:30] 09b | Unpacked Link 8bbc9c2aa2c581a43d7af7cd24b429984d807fa621ac297b5652b7de6063a3f3
05:19:07.630806 - [DEBU keybase log.go:30] 09c + LevelDb.open
05:19:07.630806 - [DEBU keybase log.go:30] 09d + LevelDb.open
05:19:07.630806 - [DEBU keybase log.go:30] 09e | loading link; curr=96cff4ecc55454caf0cfda2efbaa31c82ac34bba11d87ed1cce0a07f6c0b3868
05:19:07.630806 - [DEBU keybase log.go:30] 09f - LevelDb.open -> ok
05:19:07.630806 - [DEBU keybase log.go:30] 0a0 | Unpacked Link 3b3c803ee610f9fd6dec42a119afd5a512c1a1cec0a3869c79b2aed3dfbce9a8
05:19:07.631807 - [DEBU keybase log.go:30] 0a1 - LevelDb.open -> ok
05:19:07.631807 - [DEBU keybase log.go:30] 0a3 - LevelDb.open -> ok
05:19:07.631807 - [DEBU keybase log.go:30] 0a2 | Unpacked Link 7aec28d20c82d761a55f9bd0762420544c8137fccae80bfb1fc5765ff644fc59
05:19:07.631807 - [DEBU keybase log.go:30] 0a5 | loading link; curr=145cf68cab3e6033b4f5c2114c04437b8933b333c95af1eae9807a6a2770a3cb
05:19:07.631807 - [DEBU keybase log.go:30] 0a4 | Unpacked Link 2c422a72f7126616f7326c466738acb7c5e6191dffeedb61c6d53f925745f82f
05:19:07.631807 - [DEBU keybase log.go:30] 0a6 - LevelDb.open -> ok
05:19:07.631807 - [DEBU keybase log.go:30] 0a7 | loading link; curr=7aec28d20c82d761a55f9bd0762420544c8137fccae80bfb1fc5765ff644fc59
05:19:07.620806 - [DEBU keybase log.go:30] 060 + LevelDb.open
05:19:07.620806 - [DEBU keybase log.go:30] 061 | Unpacked Link aa2c03d7e83c28b21edef77812d62213eafdde59a4af4d5bbf8fa2544fef1e71
05:19:07.632807 - [DEBU keybase log.go:30] 0aa + LevelDb.open
05:19:07.632807 - [DEBU keybase log.go:30] 0ab | Unpacked Link 145cf68cab3e6033b4f5c2114c04437b8933b333c95af1eae9807a6a2770a3cb
05:19:07.632807 - [DEBU keybase log.go:30] 0ac + LevelDb.open
05:19:07.632807 - [DEBU keybase log.go:30] 0ad - LevelDb.open -> ok
05:19:07.632807 - [DEBU keybase log.go:30] 0ae + LevelDb.open
05:19:07.632807 - [DEBU keybase log.go:30] 0af | loading link; curr=2c422a72f7126616f7326c466738acb7c5e6191dffeedb61c6d53f925745f82f
05:19:07.632807 - [DEBU keybase log.go:30] 0b0 - LevelDb.open -> ok
05:19:07.632807 - [DEBU keybase log.go:30] 0b1 - LevelDb.open -> ok
05:19:07.632807 - [DEBU keybase log.go:30] 0b2 + LevelDb.open
05:19:07.633807 - [DEBU keybase log.go:30] 0b3 | Unpacked Link bfc0083eff47fdc5b538f5ec1224188b274ed8d1ea9d5e89571e8d16a36f0838
05:19:07.633807 - [DEBU keybase log.go:30] 0b4 + LevelDb.open
05:19:07.633807 - [DEBU keybase log.go:30] 0b5 | Unpacked Link 7253f6f02c876462c5216b0b113551bc653f114486680880864a525205b98959
05:19:07.633807 - [DEBU keybase log.go:30] 0b6 | loading link; curr=74b4a7bb4ee639991d9232982c4ab913352146c386465e4475cd3d136450e870
05:19:07.633807 - [DEBU keybase log.go:30] 0b7 + LevelDb.open
05:19:07.633807 - [DEBU keybase log.go:30] 0b8 | Unpacked Link a54f1ac862db006527541f1db26fd2f530d8ca6e44e651dea50fcbd742f4273c
05:19:07.633807 - [DEBU keybase log.go:30] 0b9 - LevelDb.open -> ok
05:19:07.633807 - [DEBU keybase log.go:30] 0ba - LevelDb.open -> ok
05:19:07.633807 - [DEBU keybase log.go:30] 0bb | loading link; curr=0e96959d0bd39d957eadd3679b426116c973cb9715ebdc95ea8d9b3a7f5330b2
05:19:07.633807 - [DEBU keybase log.go:30] 0bc | Unpacked Link 74b4a7bb4ee639991d9232982c4ab913352146c386465e4475cd3d136450e870
05:19:07.633807 - [DEBU keybase log.go:30] 0bd + LevelDb.open
05:19:07.633807 - [DEBU keybase log.go:30] 0be | loading link; curr=a54f1ac862db006527541f1db26fd2f530d8ca6e44e651dea50fcbd742f4273c
05:19:07.634807 - [DEBU keybase log.go:30] 0bf | Unpacked Link 72bd83a1548a78fdcc2badf1e5784685420864a26409fbe44b6ed89145e70b31
05:19:07.634807 - [DEBU keybase log.go:30] 0c0 + LevelDb.open
05:19:07.634807 - [DEBU keybase log.go:30] 0c1 - LevelDb.open -> ok
05:19:07.634807 - [DEBU keybase log.go:30] 0c2 | Unpacked Link 0e96959d0bd39d957eadd3679b426116c973cb9715ebdc95ea8d9b3a7f5330b2
05:19:07.634807 - [DEBU keybase log.go:30] 0c3 | loading link; curr=f457b410b453f22f688a248f06b6b09b560302670fbe2415124981a6be2235f4
05:19:07.634807 - [DEBU keybase log.go:30] 0c4 | loading link; curr=1becc2e57393d93845441c7586eee98922883eb14f654a0868c73fea193f6ce4
05:19:07.634807 - [DEBU keybase log.go:30] 0c5 - LevelDb.open -> ok
05:19:07.622806 - [DEBU keybase log.go:30] 065 | loading link; curr=418baa132aaa9cae85d4875f5fed0c1cf07bfcd4d073c471e8763518580a8cea
05:19:07.634807 - [DEBU keybase log.go:30] 0c7 + LevelDb.open
05:19:07.634807 - [DEBU keybase log.go:30] 0c8 | Unpacked Link da9751d314c6e4d7f95c5b774e1551c40162dd283c8a215063213596276047cc
05:19:07.634807 - [DEBU keybase log.go:30] 0c9 + LevelDb.open
05:19:07.634807 - [DEBU keybase log.go:30] 0ca | loading link; curr=72bd83a1548a78fdcc2badf1e5784685420864a26409fbe44b6ed89145e70b31
05:19:07.634807 - [DEBU keybase log.go:30] 0cb - LevelDb.open -> ok
05:19:07.634807 - [DEBU keybase log.go:30] 0cc - LevelDb.open -> ok
05:19:07.634807 - [DEBU keybase log.go:30] 0cd | Unpacked Link 1becc2e57393d93845441c7586eee98922883eb14f654a0868c73fea193f6ce4
05:19:07.634807 - [DEBU keybase log.go:30] 0ce | Unpacked Link f457b410b453f22f688a248f06b6b09b560302670fbe2415124981a6be2235f4
05:19:07.634807 - [DEBU keybase log.go:30] 0cf + LevelDb.open
05:19:07.634807 - [DEBU keybase log.go:30] 0d0 - LevelDb.open -> ok
05:19:07.635807 - [DEBU keybase log.go:30] 0d1 | loading link; curr=82725bda8d615f82a87588779be13074f332215109075d9e8d430571d2215d0f
05:19:07.678809 - [DEBU keybase log.go:30] 17e + CheckFreshness
05:19:07.678809 - [DEBU keybase log.go:30] 183 - SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) -> (true, ok)
05:19:07.635807 - [DEBU keybase log.go:30] 0d4 | loading link; curr=b048295f72dde311fb352b91202dd398dde89262b23b1c38a62af67da660c0b2
05:19:07.635807 - [DEBU keybase log.go:30] 0d5 - LevelDb.open -> ok
05:19:07.635807 - [DEBU keybase log.go:30] 0d6 + LevelDb.open
05:19:07.635807 - [DEBU keybase log.go:30] 0d7 + LevelDb.open
05:19:07.635807 - [DEBU keybase log.go:30] 0d8 + LevelDb.open
05:19:07.635807 - [DEBU keybase log.go:30] 0d9 - LevelDb.open -> ok
05:19:07.636807 - [DEBU keybase log.go:30] 0da - LevelDb.open -> ok
05:19:07.636807 - [DEBU keybase log.go:30] 0db - LevelDb.open -> ok
05:19:07.636807 - [DEBU keybase log.go:30] 0dc | Unpacked Link 55136c844eb18642f38ef9588dc2b6d5d56b31b934c789f88224923e8a8ded47
05:19:07.624806 - [DEBU keybase log.go:30] 06a - LevelDb.open -> ok
05:19:07.624806 - [DEBU keybase log.go:30] 06b | Unpacked Link 418baa132aaa9cae85d4875f5fed0c1cf07bfcd4d073c471e8763518580a8cea
05:19:07.637807 - [DEBU keybase log.go:30] 0df - LevelDb.open -> ok
05:19:07.637807 - [DEBU keybase log.go:30] 0e0 | loading link; curr=55136c844eb18642f38ef9588dc2b6d5d56b31b934c789f88224923e8a8ded47
05:19:07.637807 - [DEBU keybase log.go:30] 0e1 | Unpacked Link a277fcfddcbf2d0fde3b35ef9a08f74aa1575949bdea91019d8e2c26bad3da29
05:19:07.637807 - [DEBU keybase log.go:30] 0e2 | loading link; curr=a277fcfddcbf2d0fde3b35ef9a08f74aa1575949bdea91019d8e2c26bad3da29
05:19:07.638807 - [DEBU keybase log.go:30] 0e3 | loading link; curr=2a7206e1c8b9f9e7ab7d9c19ee2b518cd618ebd8a625af7ed2c48e95faaa8032
05:19:07.638807 - [DEBU keybase log.go:30] 0e4 + LevelDb.open
05:19:07.638807 - [DEBU keybase log.go:30] 0e5 | loading link; curr=df0ce4cdc596541db52f5ac62427838a6d3bf702a144bd1040eda442a9bb5613
05:19:07.638807 - [DEBU keybase log.go:30] 0e6 + LevelDb.open
05:19:07.638807 - [DEBU keybase log.go:30] 0e7 | Unpacked Link 91749ecda774599097ab4505f9a01abc9568b51a4f70b64cb57d6a2e4b651826
05:19:07.638807 - [DEBU keybase log.go:30] 0e8 | loading link; curr=91749ecda774599097ab4505f9a01abc9568b51a4f70b64cb57d6a2e4b651826
05:19:07.638807 - [DEBU keybase log.go:30] 0e9 + LevelDb.open
05:19:07.638807 - [DEBU keybase log.go:30] 0ea - LevelDb.open -> ok
05:19:07.639807 - [DEBU keybase log.go:30] 0eb - LevelDb.open -> ok
05:19:07.639807 - [DEBU keybase log.go:30] 0ec - LevelDb.open -> ok
05:19:07.639807 - [DEBU keybase log.go:30] 0ed | Unpacked Link 2a7206e1c8b9f9e7ab7d9c19ee2b518cd618ebd8a625af7ed2c48e95faaa8032
05:19:07.639807 - [DEBU keybase log.go:30] 0ee | loading link; curr=ffb98903f25819ee3e9a1883744d6784c0b9a437e5219b9ccf24fda5879bb5e8
05:19:07.639807 - [DEBU keybase log.go:30] 0ef + LevelDb.open
05:19:07.639807 - [DEBU keybase log.go:30] 0f0 + LevelDb.open
05:19:07.639807 - [DEBU keybase log.go:30] 0f1 | Unpacked Link ffb98903f25819ee3e9a1883744d6784c0b9a437e5219b9ccf24fda5879bb5e8
05:19:07.639807 - [DEBU keybase log.go:30] 0f2 | loading link; curr=5a8b9b2cb072fde29f5494ff84add742ca2319be4e8ed19df92902a786d76a11
05:19:07.625806 - [DEBU keybase log.go:30] 073 | Link is marked as 'sig_verified'
05:19:07.640807 - [DEBU keybase log.go:30] 0f4 + LevelDb.open
05:19:07.640807 - [DEBU keybase log.go:30] 0f5 | Unpacked Link a7bdae9a8cc5367c9ce49dd853175bcd2c05d28963963053f71296b2563b18d5
05:19:07.641807 - [DEBU keybase log.go:30] 0f6 | loading link; curr=09a1bb4b489bb772b0cfa15c60d64049179929c8938e9d00e3ff3605932e0610
05:19:07.641807 - [DEBU keybase log.go:30] 0f8 | Unpacked Link 09a1bb4b489bb772b0cfa15c60d64049179929c8938e9d00e3ff3605932e0610
05:19:07.641807 - [DEBU keybase log.go:30] 0f7 + LevelDb.open
05:19:07.641807 - [DEBU keybase log.go:30] 0f9 | loading link; curr=be1d3cf2c7215c0a2351f74615327df9e29f84c9e91346dd1be162435f1c45d7
05:19:07.641807 - [DEBU keybase log.go:30] 0fa - LevelDb.open -> ok
05:19:07.641807 - [DEBU keybase log.go:30] 0fb + LevelDb.open
05:19:07.641807 - [DEBU keybase log.go:30] 0fc - LevelDb.open -> ok
05:19:07.641807 - [DEBU keybase log.go:30] 0fd | Unpacked Link 5a8b9b2cb072fde29f5494ff84add742ca2319be4e8ed19df92902a786d76a11
05:19:07.625806 - [DEBU keybase log.go:30] 075 | Unpacked Link 512ee3afc25e34d708108325baae7b338b2e798aad3d33d362e5fc36cadf1958
05:19:07.642807 - [DEBU keybase log.go:30] 0ff - LevelDb.open -> ok
05:19:07.642807 - [DEBU keybase log.go:30] 100 | Unpacked Link 36d1285a0194aec54a8dbe2f1a047e5869a2775e1d2d82d9d25b78c4f628429b
05:19:07.625806 - [DEBU keybase log.go:30] 076 - LevelDb.open -> ok
05:19:07.642807 - [DEBU keybase log.go:30] 102 + LevelDb.open
05:19:07.642807 - [DEBU keybase log.go:30] 103 - LevelDb.open -> ok
05:19:07.642807 - [DEBU keybase log.go:30] 104 | Unpacked Link 7454692a0dca02bc92f88c3cd4fef0b584aa72f5879893e569442a0797e65a8f
05:19:07.642807 - [DEBU keybase log.go:30] 105 - LevelDb.open -> ok
05:19:07.642807 - [DEBU keybase log.go:30] 106 | loading link; curr=af25b0f3e0cb647676d969c47fc2c4f32c6ef5a4f053cbfc03736d94b9e032b9
05:19:07.642807 - [DEBU keybase log.go:30] 107 | Unpacked Link 232ce82837300501d30d761e5e60400dd8b029d2b752ebf486ff9936685c142e
05:19:07.642807 - [DEBU keybase log.go:30] 108 + LevelDb.open
05:19:07.642807 - [DEBU keybase log.go:30] 109 + LevelDb.open
05:19:07.642807 - [DEBU keybase log.go:30] 10a - LevelDb.open -> ok
05:19:07.642807 - [DEBU keybase log.go:30] 10b | loading link; curr=7454692a0dca02bc92f88c3cd4fef0b584aa72f5879893e569442a0797e65a8f
05:19:07.626806 - [DEBU keybase log.go:30] 077 - LevelDb.open -> ok
05:19:07.642807 - [DEBU keybase log.go:30] 10d + LevelDb.open
05:19:07.642807 - [DEBU keybase log.go:30] 10e | loading link; curr=7f8bc8d9ec96fcabd7aa39d9d3e9eaa6542bc5a4e220f0970e4b5364eebd2e3e
05:19:07.643807 - [DEBU keybase log.go:30] 10f - LevelDb.open -> ok
05:19:07.643807 - [DEBU keybase log.go:30] 110 | Unpacked Link ad4532503587e8230612fdc316adc018d76a0d65abcffd6a28ce5707ac085437
05:19:07.643807 - [DEBU keybase log.go:30] 111 | loading link; curr=579f067318333c05ba325064ab2ec718f4bac2331adc2c173d9be6f5030290a5
05:19:07.643807 - [DEBU keybase log.go:30] 112 - LevelDb.open -> ok
05:19:07.643807 - [DEBU keybase log.go:30] 113 + LevelDb.open
05:19:07.643807 - [DEBU keybase log.go:30] 114 + LevelDb.open
05:19:07.643807 - [DEBU keybase log.go:30] 115 | Unpacked Link be1d3cf2c7215c0a2351f74615327df9e29f84c9e91346dd1be162435f1c45d7
05:19:07.643807 - [DEBU keybase log.go:30] 116 - LevelDb.open -> ok
05:19:07.644807 - [DEBU keybase log.go:30] 117 | loading link; curr=ad4532503587e8230612fdc316adc018d76a0d65abcffd6a28ce5707ac085437
05:19:07.644807 - [DEBU keybase log.go:30] 118 | Unpacked Link 579f067318333c05ba325064ab2ec718f4bac2331adc2c173d9be6f5030290a5
05:19:07.644807 - [DEBU keybase log.go:30] 119 | loading link; curr=232ce82837300501d30d761e5e60400dd8b029d2b752ebf486ff9936685c142e
05:19:07.644807 - [DEBU keybase log.go:30] 11a + LevelDb.open
05:19:07.644807 - [DEBU keybase log.go:30] 11b + LevelDb.open
05:19:07.644807 - [DEBU keybase log.go:30] 11c - LevelDb.open -> ok
05:19:07.645807 - [DEBU keybase log.go:30] 11d - LevelDb.open -> ok
05:19:07.645807 - [DEBU keybase log.go:30] 11e | Unpacked Link f97c6138afda17bbc5c806768b9e1e2c555719ca77cda533a0cb3d2b60059391
05:19:07.645807 - [DEBU keybase log.go:30] 11f | loading link; curr=b975280bfc0cd503c5396509d77107b725718f5118db54af879e4235cbde6ac0
05:19:07.645807 - [DEBU keybase log.go:30] 120 | Unpacked Link 6e177cc5402e52f5b35cfb8e979c804e2edb890886e3487cc9db7bd1a7ede5ae
05:19:07.645807 - [DEBU keybase log.go:30] 121 | loading link; curr=7a635c45762e63944f71f7d30b348674595f9562ed18c8074cbb6b6cfa4403c5
05:19:07.645807 - [DEBU keybase log.go:30] 122 - LevelDb.open -> ok
05:19:07.645807 - [DEBU keybase log.go:30] 123 + LevelDb.open
05:19:07.646807 - [DEBU keybase log.go:30] 124 + LevelDb.open
05:19:07.646807 - [DEBU keybase log.go:30] 125 | Unpacked Link 7f8bc8d9ec96fcabd7aa39d9d3e9eaa6542bc5a4e220f0970e4b5364eebd2e3e
05:19:07.646807 - [DEBU keybase log.go:30] 126 | Unpacked Link df7b8faca3c29c3c6d79b1c36f630403f388b56d877aa517a7902f0d36bb7af0
05:19:07.646807 - [DEBU keybase log.go:30] 127 - LevelDb.open -> ok
05:19:07.646807 - [DEBU keybase log.go:30] 128 | loading link; curr=6e177cc5402e52f5b35cfb8e979c804e2edb890886e3487cc9db7bd1a7ede5ae
05:19:07.646807 - [DEBU keybase log.go:30] 129 | Unpacked Link b975280bfc0cd503c5396509d77107b725718f5118db54af879e4235cbde6ac0
05:19:07.647807 - [DEBU keybase log.go:30] 12a | loading link; curr=f97c6138afda17bbc5c806768b9e1e2c555719ca77cda533a0cb3d2b60059391
05:19:07.647807 - [DEBU keybase log.go:30] 12b + LevelDb.open
05:19:07.627806 - [DEBU keybase log.go:30] 083 | Unpacked Link fb4eb5ab067c52b7037d7460d1e4b0126665d236673c614b06f3edbd54900bde
05:19:07.647807 - [DEBU keybase log.go:30] 12d | loading link; curr=df7b8faca3c29c3c6d79b1c36f630403f388b56d877aa517a7902f0d36bb7af0
05:19:07.647807 - [DEBU keybase log.go:30] 12e - LevelDb.open -> ok
05:19:07.647807 - [DEBU keybase log.go:30] 12f + LevelDb.open
05:19:07.647807 - [DEBU keybase log.go:30] 130 | Unpacked Link 7a635c45762e63944f71f7d30b348674595f9562ed18c8074cbb6b6cfa4403c5
05:19:07.647807 - [DEBU keybase log.go:30] 131 | loading link; curr=3522c4011d95679041af76fa5cbd25a49b98ee7e3c84f76237bb7bf22da8520e
05:19:07.647807 - [DEBU keybase log.go:30] 133 - LevelDb.open -> ok
05:19:07.628806 - [DEBU keybase log.go:30] 084 + LevelDb.open
05:19:07.647807 - [DEBU keybase log.go:30] 134 - LevelDb.open -> ok
05:19:07.647807 - [DEBU keybase log.go:30] 135 + LevelDb.open
05:19:07.648808 - [DEBU keybase log.go:30] 136 - LevelDb.open -> ok
05:19:07.648808 - [DEBU keybase log.go:30] 137 | Unpacked Link b1724f56848acdaefaa6f6c28af0bc41fcf018f3696c4f22c74ad5caf2bd39f9
05:19:07.649808 - [DEBU keybase log.go:30] 138 + LevelDb.open
05:19:07.649808 - [DEBU keybase log.go:30] 13a | Unpacked Link 3522c4011d95679041af76fa5cbd25a49b98ee7e3c84f76237bb7bf22da8520e
05:19:07.649808 - [DEBU keybase log.go:30] 13b - LevelDb.open -> ok
05:19:07.649808 - [DEBU keybase log.go:30] 13c | loading link; curr=b1724f56848acdaefaa6f6c28af0bc41fcf018f3696c4f22c74ad5caf2bd39f9
05:19:07.649808 - [DEBU keybase log.go:30] 13d | Unpacked Link 3a340b1d22aebc9b84ce0a22c0fade8cf827ee6e440c298c2a0f6704e9c1bce5
05:19:07.649808 - [DEBU keybase log.go:30] 13e | loading link; curr=19445c7e1443f593d0bcd968087c3042edbcade8495be3a4e8fda83434a8cb5e
05:19:07.649808 - [DEBU keybase log.go:30] 13f | Unpacked Link 19445c7e1443f593d0bcd968087c3042edbcade8495be3a4e8fda83434a8cb5e
05:19:07.649808 - [DEBU keybase log.go:30] 139 | loading link; curr=3a340b1d22aebc9b84ce0a22c0fade8cf827ee6e440c298c2a0f6704e9c1bce5
05:19:07.650808 - [DEBU keybase log.go:30] 141 | loading link; curr=5c8e49936e8bf0ecb9805ccd212e3ca4625a50527156bb6b8299c4ba02891943
05:19:07.650808 - [DEBU keybase log.go:30] 142 + LevelDb.open
05:19:07.650808 - [DEBU keybase log.go:30] 143 | loading link; curr=c356d46d362f68a369f9e90eefa33399b26824b5e1142f365547b55489b53f27
05:19:07.650808 - [DEBU keybase log.go:30] 144 + LevelDb.open
05:19:07.650808 - [DEBU keybase log.go:30] 145 | Unpacked Link 968c4bb8056dd87f689e455013cde3a83cac3f06ecb2aa9415da4f6d20fad18f
05:19:07.651808 - [DEBU keybase log.go:30] 146 - LevelDb.open -> ok
05:19:07.650808 - [DEBU keybase log.go:30] 140 - LevelDb.open -> ok
05:19:07.651808 - [DEBU keybase log.go:30] 147 - LevelDb.open -> ok
05:19:07.651808 - [DEBU keybase log.go:30] 148 - LevelDb.open -> ok
05:19:07.651808 - [DEBU keybase log.go:30] 149 | Unpacked Link 5c8e49936e8bf0ecb9805ccd212e3ca4625a50527156bb6b8299c4ba02891943
05:19:07.651808 - [DEBU keybase log.go:30] 14a | Unpacked Link c356d46d362f68a369f9e90eefa33399b26824b5e1142f365547b55489b53f27
05:19:07.651808 - [DEBU keybase log.go:30] 14b | loading link; curr=6cf3b96586b075d01dd87717ced9e5bf632eb2ec6a051af7169a683b0c144962
05:19:07.651808 - [DEBU keybase log.go:30] 14c | loading link; curr=fb7b09db240ab40a80176c1118b996ac81d3fc96f1728c0ee7f55bd59f29cb5a
05:19:07.628806 - [DEBU keybase log.go:30] 08e | loading link; curr=8bbc9c2aa2c581a43d7af7cd24b429984d807fa621ac297b5652b7de6063a3f3
05:19:07.651808 - [DEBU keybase log.go:30] 14f + LevelDb.open
05:19:07.651808 - [DEBU keybase log.go:30] 150 + LevelDb.open
05:19:07.628806 - [DEBU keybase log.go:30] 08f | loading link; curr=7253f6f02c876462c5216b0b113551bc653f114486680880864a525205b98959
05:19:07.652808 - [DEBU keybase log.go:30] 151 | loading link; curr=8bbaba0f6e5688f9be0f2b27cae0af4be44bd4d4d24690a42ec2653fb9632682
05:19:07.652808 - [DEBU keybase log.go:30] 152 - LevelDb.open -> ok
05:19:07.652808 - [DEBU keybase log.go:30] 153 - LevelDb.open -> ok
05:19:07.652808 - [DEBU keybase log.go:30] 154 | Unpacked Link fb7b09db240ab40a80176c1118b996ac81d3fc96f1728c0ee7f55bd59f29cb5a
05:19:07.652808 - [DEBU keybase log.go:30] 155 | Unpacked Link 8bbaba0f6e5688f9be0f2b27cae0af4be44bd4d4d24690a42ec2653fb9632682
05:19:07.652808 - [DEBU keybase log.go:30] 156 + LevelDb.open
05:19:07.652808 - [DEBU keybase log.go:30] 157 + LevelDb.open
05:19:07.652808 - [DEBU keybase log.go:30] 158 | Unpacked Link 25122bcb9c7110bd29269ad31f8f3e523f308e89c426ff8dd2e123dbeff35d2a
05:19:07.652808 - [DEBU keybase log.go:30] 159 - LevelDb.open -> ok
05:19:07.652808 - [DEBU keybase log.go:30] 15a + LevelDb.open
05:19:07.652808 - [DEBU keybase log.go:30] 15b | loading link; curr=25122bcb9c7110bd29269ad31f8f3e523f308e89c426ff8dd2e123dbeff35d2a
05:19:07.652808 - [DEBU keybase log.go:30] 15c + LevelDb.open
05:19:07.652808 - [DEBU keybase log.go:30] 15d - LevelDb.open -> ok
05:19:07.652808 - [DEBU keybase log.go:30] 15e | Unpacked Link 6cf3b96586b075d01dd87717ced9e5bf632eb2ec6a051af7169a683b0c144962
05:19:07.628806 - [DEBU keybase log.go:30] 092 | Unpacked Link 02c314d82e6cbd2cb2a90ebb429b1cf19d4338c2077e3eef2cad93b294a454c8
05:19:07.653808 - [DEBU keybase log.go:30] 160 | loading link; curr=97ba80437fa597b6b619ae66fd284cb5066eb8dde02a761bc60042cd0aaa83e5
05:19:07.653808 - [DEBU keybase log.go:30] 162 - LevelDb.open -> ok
05:19:07.653808 - [DEBU keybase log.go:30] 161 + LevelDb.open
05:19:07.653808 - [DEBU keybase log.go:30] 163 | loading link; curr=d36934dfe37c1e2b593804fd471b62c910263452bfada32bf63755a8d4d29434
05:19:07.653808 - [DEBU keybase log.go:30] 164 | loading link; curr=40f54fdf70948ed59a9d23aedd3aedeb09e3ee1e44885ef4d6e5ba5e384263c7
05:19:07.653808 - [DEBU keybase log.go:30] 165 - LevelDb.open -> ok
05:19:07.653808 - [DEBU keybase log.go:30] 166 | Unpacked Link f470eaeef51d4a00590596f2ca316a01bdfc78f1ff41ec03e0885d3de467804e
05:19:07.653808 - [DEBU keybase log.go:30] 167 | Unpacked Link d36934dfe37c1e2b593804fd471b62c910263452bfada32bf63755a8d4d29434
05:19:07.653808 - [DEBU keybase log.go:30] 168 | Unpacked Link 40f54fdf70948ed59a9d23aedd3aedeb09e3ee1e44885ef4d6e5ba5e384263c7
05:19:07.653808 - [DEBU keybase log.go:30] 169 | loading link; curr=f470eaeef51d4a00590596f2ca316a01bdfc78f1ff41ec03e0885d3de467804e
05:19:07.653808 - [DEBU keybase log.go:30] 16a + LevelDb.open
05:19:07.653808 - [DEBU keybase log.go:30] 16b | loading link; curr=f4990fc2d1400773f39d6365e4505e0dbfa1044061f1500e5e41998bd3e225d9
05:19:07.654808 - [DEBU keybase log.go:30] 16c - LevelDb.open -> ok
05:19:07.654808 - [DEBU keybase log.go:30] 16d | loading link; curr=ab2d83393c3ee1d4136e1a3502d9f8f9ee19199bea2af28a0eb01353adae38cb
05:19:07.654808 - [DEBU keybase log.go:30] 16e - LevelDb.open -> ok
05:19:07.628806 - [DEBU keybase log.go:30] 095 | loading link; curr=3b3c803ee610f9fd6dec42a119afd5a512c1a1cec0a3869c79b2aed3dfbce9a8
05:19:07.630806 - [DEBU keybase log.go:30] 096 | loading link; curr=9fdc4a1617c474ace33c1e40da8f26e4d4acf25f6de542fca37f520f807d5665
05:19:07.655808 - [DEBU keybase log.go:30] 171 | loading link; curr=504752c98dec7e2f42eac6caf25ab52b6665709ffe6b7569d66d89395780c53e
05:19:07.655808 - [DEBU keybase log.go:30] 172 | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) MakeSigChain
05:19:07.655808 - [DEBU keybase log.go:30] 174 - LevelDb.open -> ok
05:19:07.655808 - [DEBU keybase log.go:30] 173 + LevelDb.open
05:19:07.630806 - [DEBU keybase log.go:30] 098 + LevelDb.open
05:19:07.655808 - [DEBU keybase log.go:30] 176 | Unpacked Link 504752c98dec7e2f42eac6caf25ab52b6665709ffe6b7569d66d89395780c53e
05:19:07.655808 - [DEBU keybase log.go:30] 177 - LevelDb.open -> ok
05:19:07.655808 - [DEBU keybase log.go:30] 178 + LevelDb.open
05:19:07.655808 - [DEBU keybase log.go:30] 179 | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) VerifyChain
05:19:07.655808 - [DEBU keybase log.go:30] 17a | Unpacked Link ab2d83393c3ee1d4136e1a3502d9f8f9ee19199bea2af28a0eb01353adae38cb
05:19:07.656808 - [DEBU keybase log.go:30] 17b | Unpacked Link f4990fc2d1400773f39d6365e4505e0dbfa1044061f1500e5e41998bd3e225d9
05:19:07.656808 - [DEBU keybase log.go:30] 17c | Stop loading at KID=01010373e851fecad178051f4af74acd9dbcbe73cd4ba0fca976a3135d72b064ffee0a (!= KID=0101b835f2748fe5c7faec0853db8881b5b2dfb5162d8745ae2c977b803bd71694830a)
05:19:07.656808 - [DEBU keybase log.go:30] 17d + SigChain::VerifyChain()
05:19:07.635807 - [DEBU keybase log.go:30] 0d2 + LevelDb.open
05:19:07.678809 - [DEBU keybase log.go:30] 17f | Future triple=nil
05:19:07.678809 - [DEBU keybase log.go:30] 180 | Sigchain was fully cached. Short-circuiting verification.
05:19:07.678809 - [DEBU keybase log.go:30] 181 + LoadSigHints(15b4292135d94eba7afb70290fdcc900)
05:19:07.678809 - [DEBU keybase log.go:30] 182 | Server triple: &{84 8e81da8b9232c844c5fff2c15945456f0c7791d0d7ea782ef67c636b54ecc67c 471bea416f5a5da354216aad3f78337ba45f8e89b785fe6c6ce808c090e3ba7b0f}
05:19:07.678809 - [DEBU keybase log.go:30] 184 - SigChain::VerifyChain() -> ok
05:19:07.635807 - [DEBU keybase log.go:30] 0d3 | Unpacked Link 82725bda8d615f82a87588779be13074f332215109075d9e8d430571d2215d0f
05:19:07.679809 - [DEBU keybase log.go:30] 186 + LevelDb.open
05:19:07.679809 - [DEBU keybase log.go:30] 187 | Local chain version is up-to-date @ version 84
05:19:07.679809 - [DEBU keybase log.go:30] 185 - CheckFreshness (15b4292135d94eba7afb70290fdcc900) -> (false,ok)
05:19:07.679809 - [DEBU keybase log.go:30] 188 | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) CheckFreshness
05:19:07.679809 - [DEBU keybase log.go:30] 189 | Client triple: &{84 8e81da8b9232c844c5fff2c15945456f0c7791d0d7ea782ef67c636b54ecc67c 471bea416f5a5da354216aad3f78337ba45f8e89b785fe6c6ce808c090e3ba7b0f}
05:19:07.679809 - [DEBU keybase log.go:30] 18a - LevelDb.open -> ok
05:19:07.679809 - [DEBU keybase log.go:30] 18b | SigHints loaded @v4
05:19:07.679809 - [DEBU keybase log.go:30] 18c - LoadSigHints(15b4292135d94eba7afb70290fdcc900)
05:19:07.680809 - [DEBU keybase log.go:30] 18d + API GET request to https://keybase.io/_/api/1.0/sig/hints.json?low=4&uid=15b4292135d94eba7afb70290fdcc900
05:19:07.680809 - [DEBU keybase log.go:30] 18e + Refresh SigHints() for uid=15b4292135d94eba7afb70290fdcc900
05:19:07.778815 - [DEBU keybase log.go:30] 18f + SigHints.Store() for uid=15b4292135d94eba7afb70290fdcc900
05:19:07.778815 - [DEBU keybase log.go:30] 190 - Store for zqueal skipped; user wasn't dirty
05:19:07.779815 - [DEBU keybase log.go:30] 191 | SigHints.Store() skipped; wasn't dirty
05:19:07.779815 - [DEBU keybase log.go:30] 192 - SigHints.Store() for uid=15b4292135d94eba7afb70290fdcc900 -> ok
05:19:07.779815 - [DEBU keybase log.go:30] 193 | Checking user's ComputedKeyFamily
05:19:07.779815 - [DEBU keybase log.go:30] 195 - successful API call
05:19:07.779815 - [DEBU keybase log.go:30] 196 - HasActiveKey -> true
05:19:07.779815 - [DEBU keybase log.go:30] 197 - Refresh SigHints() for uid=15b4292135d94eba7afb70290fdcc900
05:19:07.779815 - [DEBU keybase log.go:30] 198 + Store user zqueal
05:19:07.779815 - [DEBU keybase log.go:30] 199 + Checking session
05:19:07.780815 - [DEBU keybase log.go:30] 19a + Populate ID Table
05:19:07.780815 - [DEBU keybase log.go:30] 19b - Account "G - GetMyUID - GetUID"
05:19:07.780815 - [DEBU keybase log.go:30] 19c + HasActiveKey
05:19:07.779815 - [DEBU keybase log.go:30] 194 | No changes; version 4 was up-to-date
05:19:07.780815 - [DEBU keybase log.go:30] 19d - Populate ID Table
05:19:07.781815 - [DEBU keybase log.go:30] 19e + VerifySelfSig for user zqueal
05:19:07.781815 - [DEBU keybase log.go:30] 19f - session is recent, short-circuiting
05:19:07.781815 - [DEBU keybase log.go:30] 1a0 - Account "LoggedInLoad"
05:19:07.781815 - [DEBU keybase log.go:30] 1a1 | Found self-signature for zqueal @uid=15b4292135d94eba7afb70290fdcc900, seq=84, link=8e81da8b9232c844c5fff2c15945456f0c7791d0d7ea782ef67c636b54ecc67c
05:19:07.781815 - [DEBU keybase log.go:30] 1a2 - VerifySelfSig via SigChain
05:19:07.781815 - [DEBU keybase log.go:30] 1a3 | resolved to 15b4292135d94eba7afb70290fdcc900
05:19:07.781815 - [DEBU keybase log.go:30] 1a4 + Account "LoggedInLoad"
05:19:07.781815 - [DEBU keybase log.go:30] 1a5 + LoadUser(uid=15b4292135d94eba7afb70290fdcc900, name=)
05:19:07.781815 - [DEBU keybase log.go:30] 1a6 + Loading session
05:19:07.781815 - [DEBU keybase log.go:30] 1a7 - Skipped; already loaded
05:19:07.781815 - [DEBU keybase log.go:30] 1a8 + Account "G - GetMyUID - GetUID"
05:19:07.781815 - [DEBU keybase log.go:30] 1a9 + loadUserFromLocalStorage(15b4292135d94eba7afb70290fdcc900)
05:19:07.781815 - [DEBU keybase log.go:30] 1aa + LevelDb.open
05:19:07.782815 - [DEBU keybase log.go:30] 1ab LoadUser: {UID: Name: PublicKeyOptional:false NoCacheResult:false Self:true ForceReload:false AllKeys:false LoginContext:<nil> AbortIfSigchainUnchanged:false Contextified:{g:0x2023c620}}
05:19:07.782815 - [DEBU keybase log.go:30] 1ac - LevelDb.open -> ok
05:19:07.782815 - [DEBU keybase log.go:30] 1ad | Result is: 200 OK
05:19:07.784815 - [DEBU keybase log.go:30] 1ae | Loaded successfully
05:19:07.785815 - [DEBU keybase log.go:30] 1af + ParseKeyFamily
05:19:07.880821 - [DEBU keybase log.go:30] 1b0 - ParseKeyFamily -> ok
05:19:07.880821 - [DEBU keybase log.go:30] 1b1 | Loaded username zqueal (uid=15b4292135d94eba7afb70290fdcc900)
05:19:07.880821 - [DEBU keybase log.go:30] 1b2 - loadUserFromLocalStorage(zqueal,15b4292135d94eba7afb70290fdcc900)
05:19:07.880821 - [DEBU keybase log.go:30] 1b3 + MerkleClient.LookupUser(map[uid:15b4292135d94eba7afb70290fdcc900 poll:10])
05:19:07.880821 - [DEBU keybase log.go:30] 1b4 + MerkleClient.LoadRoot()
05:19:07.880821 - [DEBU keybase log.go:30] 1b5 + LevelDb.open
05:19:07.880821 - [DEBU keybase log.go:30] 1b6 - LevelDb.open -> ok
05:19:07.880821 - [DEBU keybase log.go:30] 1b7 | LookupPath
05:19:07.880821 - [DEBU keybase log.go:30] 1b8 + LevelDb.open
05:19:07.880821 - [DEBU keybase log.go:30] 1b9 + API GET request to https://keybase.io/_/api/1.0/merkle/path.json?poll=10&uid=15b4292135d94eba7afb70290fdcc900
05:19:07.881821 - [DEBU keybase log.go:30] 1ba - LevelDb.open -> ok
05:19:07.881821 - [DEBU keybase log.go:30] 1bb - MerkleClient.LoadRoot() -> &{{0x2023c620} 341526 [3 225 70 205 175 129 54 104 10 213 102 145 42 50 52 12 236 140 148 146] 0x21f06840 {"body":{"key":{"fingerprint":"03e146cdaf8136680ad566912a32340cec8c9492","key_id":"2A32340CEC8C9492"},"legacy_uid_root":"d3450288d233fe9125d0b6f8196dbc93447bca2630300898781a637a44752032","prev":"41000d2fa051c61c2650941c2cebd53943db6b90e4df2636f1ef63c664d343023666783d2f7f0a564a603d2dcd1b670db1d4af548521968059c1d2a62c3ff1dd","root":"94ba53b88427ae895b69eb10e76bea8eb572ac911113b495eaa6e616d731052701e6b245f6d24320f749f11c5ad212657f988ced6ce5f2dae2ea55aa72eea57c","seqno":341526,"txid":"1b41c295eb22981170418c9aa1fed715","type":"merkle_root","version":1},"ctime":1451815873,"tag":"signature"} 0x21f06a60 [148 186 83 184 132 39 174 137 91 105 235 16 231 107 234 142 181 114 172 145 17 19 180 149 234 166 230 22 215 49 5 39 1 230 178 69 246 210 67 32 247 73 241 28 90 210 18 101 127 152 140 237 108 229 242 218 226 234 85 170 114 238 165 124] [211 69 2 136 210 51 254 145 37 208 182 248 25 109 188 147 68 123 202 38 48 48 8 152 120 26 99 122 68 117 32 50] 1451815873}
05:19:07.941824 - [DEBU keybase log.go:30] 1bc | Result is: 200 OK
05:19:07.969826 - [DEBU keybase log.go:30] 1bd | VerifyRoot
05:19:07.969826 - [DEBU keybase log.go:30] 1be - successful API call
05:19:07.969826 - [DEBU keybase log.go:30] 1bf | Merkle root: got back 341526, >= cached 341526
05:19:07.970826 - [DEBU keybase log.go:30] 1c0 | VerifyUser
05:19:07.975826 - [DEBU keybase log.go:30] 1c1 | VerifyUsername
05:19:07.975826 - [DEBU keybase log.go:30] 1c2 - ParsingMerkleUserLeaf -> ok
05:19:07.976826 - [DEBU keybase log.go:30] 1c3 + ParsingMerkleUserLeaf
05:19:07.976826 - [DEBU keybase log.go:30] 1c4 | Failed to map Username zqueal -> UID 15b4292135d94eba7afb70290fdcc900 via direct hash
05:19:07.976826 - [DEBU keybase log.go:30] 1c5 + LevelDb.open
05:19:07.977826 - [DEBU keybase log.go:30] 1c7 | Local basics version is up-to-date @ version 130
05:19:07.977826 - [DEBU keybase log.go:30] 1c6 | Checking cased username difference: zqueal v zQueal
05:19:07.977826 - [DEBU keybase log.go:30] 1c8 | loading link; curr=8e81da8b9232c844c5fff2c15945456f0c7791d0d7ea782ef67c636b54ecc67c
05:19:07.977826 - [DEBU keybase log.go:30] 1c9 | Username zqueal mapped to 15b4292135d94eba7afb70290fdcc900 via Merkle lookup
05:19:07.977826 - [DEBU keybase log.go:30] 1ca - LevelDb.open -> ok
05:19:07.977826 - [DEBU keybase log.go:30] 1cb | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) LoadLinksFromStorage
05:19:07.977826 - [DEBU keybase log.go:30] 1cc | Preload failed
05:19:07.980826 - [DEBU keybase log.go:30] 1dd | Unpacked Link aa2c03d7e83c28b21edef77812d62213eafdde59a4af4d5bbf8fa2544fef1e71
05:19:07.977826 - [DEBU keybase log.go:30] 1ce + SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900)
05:19:07.977826 - [DEBU keybase log.go:30] 1cf | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) GetFingerprint
05:19:07.977826 - [DEBU keybase log.go:30] 1d0 | Freshness: basics=true; for 15b4292135d94eba7afb70290fdcc900
05:19:07.977826 - [DEBU keybase log.go:30] 1d1 + LevelDb.open
05:19:07.977826 - [DEBU keybase log.go:30] 1d2 + SigChainLoader.LoadFromStorage(15b4292135d94eba7afb70290fdcc900)
05:19:07.983827 - [DEBU keybase log.go:30] 1f9 + LevelDb.open
05:19:07.978826 - [DEBU keybase log.go:30] 1d4 - MerkleClient.LookupUser(map[uid:15b4292135d94eba7afb70290fdcc900 poll:10]) -> OK
05:19:07.978826 - [DEBU keybase log.go:30] 1d5 - LevelDb.open -> ok
05:19:07.978826 - [DEBU keybase log.go:30] 1d6 | Link is marked as 'sig_verified'
05:19:07.978826 - [DEBU keybase log.go:30] 1d7 | loading link; curr=aa2c03d7e83c28b21edef77812d62213eafdde59a4af4d5bbf8fa2544fef1e71
05:19:07.979826 - [DEBU keybase log.go:30] 1d8 + LevelDb.open
05:19:07.979826 - [DEBU keybase log.go:30] 1d9 | Setting loadKID=01010373e851fecad178051f4af74acd9dbcbe73cd4ba0fca976a3135d72b064ffee0a
05:19:07.979826 - [DEBU keybase log.go:30] 1da - LevelDb.open -> ok
05:19:07.979826 - [DEBU keybase log.go:30] 1db + LevelDb.open
05:19:07.979826 - [DEBU keybase log.go:30] 1dc - LevelDb.open -> ok
05:19:07.977826 - [DEBU keybase log.go:30] 1cd | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) AccessPreload
05:19:07.980826 - [DEBU keybase log.go:30] 1de | Link is marked as 'sig_verified'
05:19:07.980826 - [DEBU keybase log.go:30] 1df | loading link; curr=f7518cbdf60680e70e1033f8b4e475bab78f92741a283cd9ee448e8547b8ae76
05:19:07.980826 - [DEBU keybase log.go:30] 1e0 | Unpacked Link f7518cbdf60680e70e1033f8b4e475bab78f92741a283cd9ee448e8547b8ae76
05:19:07.980826 - [DEBU keybase log.go:30] 1e1 | loading link; curr=418baa132aaa9cae85d4875f5fed0c1cf07bfcd4d073c471e8763518580a8cea
05:19:07.981827 - [DEBU keybase log.go:30] 1e2 + LevelDb.open
05:19:07.981827 - [DEBU keybase log.go:30] 1e3 | Link is marked as 'sig_verified'
05:19:07.981827 - [DEBU keybase log.go:30] 1e4 - LevelDb.open -> ok
05:19:07.981827 - [DEBU keybase log.go:30] 1e5 + LevelDb.open
05:19:07.982827 - [DEBU keybase log.go:30] 1e6 - LevelDb.open -> ok
05:19:07.982827 - [DEBU keybase log.go:30] 1e7 | loading link; curr=8810b3a08f411c698197da2ae2de9940d03684a92747f9a6b7835c9cf10998c1
05:19:07.982827 - [DEBU keybase log.go:30] 1e8 | Unpacked Link 418baa132aaa9cae85d4875f5fed0c1cf07bfcd4d073c471e8763518580a8cea
05:19:07.983827 - [DEBU keybase log.go:30] 1e9 + LevelDb.open
05:19:07.983827 - [DEBU keybase log.go:30] 1ea | Link is marked as 'sig_verified'
05:19:07.994827 - [DEBU keybase log.go:30] 251 + LevelDb.open
05:19:07.983827 - [DEBU keybase log.go:30] 1ec - LevelDb.open -> ok
05:19:07.983827 - [DEBU keybase log.go:30] 1ed + LevelDb.open
05:19:07.983827 - [DEBU keybase log.go:30] 1ee + LevelDb.open
05:19:07.983827 - [DEBU keybase log.go:30] 1ef | Link is marked as 'sig_verified'
05:19:07.983827 - [DEBU keybase log.go:30] 1f0 - LevelDb.open -> ok
05:19:07.983827 - [DEBU keybase log.go:30] 1f1 | loading link; curr=403e2fcc6eab83f4b37925e07eed988f163e80729cc259060d7d3e15d6fdecca
05:19:07.996827 - [DEBU keybase log.go:30] 259 - LevelDb.open -> ok
05:19:07.997827 - [DEBU keybase log.go:30] 25a - LevelDb.open -> ok
05:19:07.983827 - [DEBU keybase log.go:30] 1f4 - LevelDb.open -> ok
05:19:07.983827 - [DEBU keybase log.go:30] 1f5 - LevelDb.open -> ok
05:19:07.998828 - [DEBU keybase log.go:30] 269 | Unpacked Link ffb98903f25819ee3e9a1883744d6784c0b9a437e5219b9ccf24fda5879bb5e8
05:19:07.998828 - [DEBU keybase log.go:30] 26e | loading link; curr=ffb98903f25819ee3e9a1883744d6784c0b9a437e5219b9ccf24fda5879bb5e8
05:19:07.983827 - [DEBU keybase log.go:30] 1f8 - LevelDb.open -> ok
05:19:07.978826 - [DEBU keybase log.go:30] 1d3 | Unpacked Link 8e81da8b9232c844c5fff2c15945456f0c7791d0d7ea782ef67c636b54ecc67c
05:19:08.000828 - [DEBU keybase log.go:30] 27a + LevelDb.open
05:19:07.984827 - [DEBU keybase log.go:30] 1fb | loading link; curr=fb4eb5ab067c52b7037d7460d1e4b0126665d236673c614b06f3edbd54900bde
05:19:07.984827 - [DEBU keybase log.go:30] 1fc | loading link; curr=512ee3afc25e34d708108325baae7b338b2e798aad3d33d362e5fc36cadf1958
05:19:08.001828 - [DEBU keybase log.go:30] 282 - LevelDb.open -> ok
05:19:08.001828 - [DEBU keybase log.go:30] 288 + LevelDb.open
05:19:08.002828 - [DEBU keybase log.go:30] 28e + LevelDb.open
05:19:07.985827 - [DEBU keybase log.go:30] 200 | loading link; curr=3b3c803ee610f9fd6dec42a119afd5a512c1a1cec0a3869c79b2aed3dfbce9a8
05:19:07.985827 - [DEBU keybase log.go:30] 201 - LevelDb.open -> ok
05:19:07.985827 - [DEBU keybase log.go:30] 202 | Unpacked Link 3b3c803ee610f9fd6dec42a119afd5a512c1a1cec0a3869c79b2aed3dfbce9a8
05:19:07.985827 - [DEBU keybase log.go:30] 203 + LevelDb.open
05:19:07.985827 - [DEBU keybase log.go:30] 204 - LevelDb.open -> ok
05:19:07.985827 - [DEBU keybase log.go:30] 205 | Link is marked as 'sig_verified'
05:19:07.986827 - [DEBU keybase log.go:30] 206 | loading link; curr=02c314d82e6cbd2cb2a90ebb429b1cf19d4338c2077e3eef2cad93b294a454c8
05:19:07.986827 - [DEBU keybase log.go:30] 207 | Unpacked Link 403e2fcc6eab83f4b37925e07eed988f163e80729cc259060d7d3e15d6fdecca
05:19:08.005828 - [DEBU keybase log.go:30] 2a1 - LevelDb.open -> ok
05:19:08.005828 - [DEBU keybase log.go:30] 2a7 | loading link; curr=b1724f56848acdaefaa6f6c28af0bc41fcf018f3696c4f22c74ad5caf2bd39f9
05:19:07.986827 - [DEBU keybase log.go:30] 20a | loading link; curr=d162d91056d8496010f2062b5d59162f623bd73652a3db80c6bba168724618b6
05:19:07.986827 - [DEBU keybase log.go:30] 20b + LevelDb.open
05:19:07.987827 - [DEBU keybase log.go:30] 20c | Unpacked Link 7253f6f02c876462c5216b0b113551bc653f114486680880864a525205b98959
05:19:07.987827 - [DEBU keybase log.go:30] 20d + LevelDb.open
05:19:07.987827 - [DEBU keybase log.go:30] 20e - LevelDb.open -> ok
05:19:07.988827 - [DEBU keybase log.go:30] 20f + LevelDb.open
05:19:07.988827 - [DEBU keybase log.go:30] 210 | loading link; curr=9fdc4a1617c474ace33c1e40da8f26e4d4acf25f6de542fca37f520f807d5665
05:19:07.988827 - [DEBU keybase log.go:30] 211 - LevelDb.open -> ok
05:19:07.988827 - [DEBU keybase log.go:30] 212 + LevelDb.open
05:19:07.988827 - [DEBU keybase log.go:30] 213 + LevelDb.open
05:19:08.010828 - [DEBU keybase log.go:30] 2c5 + LevelDb.open
05:19:08.010828 - [DEBU keybase log.go:30] 2ca | loading link; curr=968c4bb8056dd87f689e455013cde3a83cac3f06ecb2aa9415da4f6d20fad18f
05:19:08.011828 - [DEBU keybase log.go:30] 2d0 + LevelDb.open
05:19:07.988827 - [DEBU keybase log.go:30] 216 - LevelDb.open -> ok
05:19:07.989827 - [DEBU keybase log.go:30] 219 + LevelDb.open
05:19:07.989827 - [DEBU keybase log.go:30] 218 | Unpacked Link 9fdc4a1617c474ace33c1e40da8f26e4d4acf25f6de542fca37f520f807d5665
05:19:08.013828 - [DEBU keybase log.go:30] 2f7 | Stop loading at KID=01010373e851fecad178051f4af74acd9dbcbe73cd4ba0fca976a3135d72b064ffee0a (!= KID=0101b835f2748fe5c7faec0853db8881b5b2dfb5162d8745ae2c977b803bd71694830a)
05:19:07.989827 - [DEBU keybase log.go:30] 21b | loading link; curr=96cff4ecc55454caf0cfda2efbaa31c82ac34bba11d87ed1cce0a07f6c0b3868
05:19:07.989827 - [DEBU keybase log.go:30] 21c - LevelDb.open -> ok
05:19:07.989827 - [DEBU keybase log.go:30] 21d | Unpacked Link 96cff4ecc55454caf0cfda2efbaa31c82ac34bba11d87ed1cce0a07f6c0b3868
05:19:07.989827 - [DEBU keybase log.go:30] 21e | loading link; curr=2c422a72f7126616f7326c466738acb7c5e6191dffeedb61c6d53f925745f82f
05:19:07.989827 - [DEBU keybase log.go:30] 21f - LevelDb.open -> ok
05:19:07.989827 - [DEBU keybase log.go:30] 220 | loading link; curr=8bbc9c2aa2c581a43d7af7cd24b429984d807fa621ac297b5652b7de6063a3f3
05:19:07.989827 - [DEBU keybase log.go:30] 221 + LevelDb.open
05:19:07.989827 - [DEBU keybase log.go:30] 222 | Unpacked Link 8bbc9c2aa2c581a43d7af7cd24b429984d807fa621ac297b5652b7de6063a3f3
05:19:07.989827 - [DEBU keybase log.go:30] 223 + LevelDb.open
05:19:07.989827 - [DEBU keybase log.go:30] 224 + LevelDb.open
05:19:07.989827 - [DEBU keybase log.go:30] 225 - LevelDb.open -> ok
05:19:07.990827 - [DEBU keybase log.go:30] 226 | Unpacked Link 7aec28d20c82d761a55f9bd0762420544c8137fccae80bfb1fc5765ff644fc59
05:19:07.990827 - [DEBU keybase log.go:30] 227 - LevelDb.open -> ok
05:19:07.990827 - [DEBU keybase log.go:30] 228 | loading link; curr=7aec28d20c82d761a55f9bd0762420544c8137fccae80bfb1fc5765ff644fc59
05:19:07.991827 - [DEBU keybase log.go:30] 229 | loading link; curr=bfc0083eff47fdc5b538f5ec1224188b274ed8d1ea9d5e89571e8d16a36f0838
05:19:07.991827 - [DEBU keybase log.go:30] 22a + LevelDb.open
05:19:07.991827 - [DEBU keybase log.go:30] 22b | Unpacked Link 2c422a72f7126616f7326c466738acb7c5e6191dffeedb61c6d53f925745f82f
05:19:07.991827 - [DEBU keybase log.go:30] 22c - LevelDb.open -> ok
05:19:07.991827 - [DEBU keybase log.go:30] 22d | Unpacked Link 145cf68cab3e6033b4f5c2114c04437b8933b333c95af1eae9807a6a2770a3cb
05:19:07.991827 - [DEBU keybase log.go:30] 22e - LevelDb.open -> ok
05:19:07.991827 - [DEBU keybase log.go:30] 22f | Unpacked Link bfc0083eff47fdc5b538f5ec1224188b274ed8d1ea9d5e89571e8d16a36f0838
05:19:07.991827 - [DEBU keybase log.go:30] 230 | loading link; curr=145cf68cab3e6033b4f5c2114c04437b8933b333c95af1eae9807a6a2770a3cb
05:19:07.991827 - [DEBU keybase log.go:30] 231 + LevelDb.open
05:19:07.991827 - [DEBU keybase log.go:30] 232 | loading link; curr=74b4a7bb4ee639991d9232982c4ab913352146c386465e4475cd3d136450e870
05:19:07.991827 - [DEBU keybase log.go:30] 233 + LevelDb.open
05:19:07.991827 - [DEBU keybase log.go:30] 234 | loading link; curr=a54f1ac862db006527541f1db26fd2f530d8ca6e44e651dea50fcbd742f4273c
05:19:07.991827 - [DEBU keybase log.go:30] 235 | Unpacked Link 74b4a7bb4ee639991d9232982c4ab913352146c386465e4475cd3d136450e870
05:19:07.991827 - [DEBU keybase log.go:30] 236 | Unpacked Link a54f1ac862db006527541f1db26fd2f530d8ca6e44e651dea50fcbd742f4273c
05:19:07.991827 - [DEBU keybase log.go:30] 237 - LevelDb.open -> ok
05:19:07.991827 - [DEBU keybase log.go:30] 238 - LevelDb.open -> ok
05:19:07.992827 - [DEBU keybase log.go:30] 239 + LevelDb.open
05:19:07.992827 - [DEBU keybase log.go:30] 23a | loading link; curr=0e96959d0bd39d957eadd3679b426116c973cb9715ebdc95ea8d9b3a7f5330b2
05:19:07.993827 - [DEBU keybase log.go:30] 23b | Unpacked Link 1becc2e57393d93845441c7586eee98922883eb14f654a0868c73fea193f6ce4
05:19:07.993827 - [DEBU keybase log.go:30] 23c + LevelDb.open
05:19:07.993827 - [DEBU keybase log.go:30] 23d | loading link; curr=72bd83a1548a78fdcc2badf1e5784685420864a26409fbe44b6ed89145e70b31
05:19:07.993827 - [DEBU keybase log.go:30] 23e - LevelDb.open -> ok
05:19:07.993827 - [DEBU keybase log.go:30] 23f - LevelDb.open -> ok
05:19:07.993827 - [DEBU keybase log.go:30] 240 | Unpacked Link 72bd83a1548a78fdcc2badf1e5784685420864a26409fbe44b6ed89145e70b31
05:19:07.993827 - [DEBU keybase log.go:30] 241 | Unpacked Link 0e96959d0bd39d957eadd3679b426116c973cb9715ebdc95ea8d9b3a7f5330b2
05:19:07.993827 - [DEBU keybase log.go:30] 242 + LevelDb.open
05:19:07.993827 - [DEBU keybase log.go:30] 243 | loading link; curr=da9751d314c6e4d7f95c5b774e1551c40162dd283c8a215063213596276047cc
05:19:07.993827 - [DEBU keybase log.go:30] 244 | loading link; curr=1becc2e57393d93845441c7586eee98922883eb14f654a0868c73fea193f6ce4
05:19:07.993827 - [DEBU keybase log.go:30] 245 + LevelDb.open
05:19:07.993827 - [DEBU keybase log.go:30] 246 - LevelDb.open -> ok
05:19:07.993827 - [DEBU keybase log.go:30] 247 | loading link; curr=82725bda8d615f82a87588779be13074f332215109075d9e8d430571d2215d0f
05:19:07.993827 - [DEBU keybase log.go:30] 248 - LevelDb.open -> ok
05:19:07.993827 - [DEBU keybase log.go:30] 249 | loading link; curr=f457b410b453f22f688a248f06b6b09b560302670fbe2415124981a6be2235f4
05:19:07.993827 - [DEBU keybase log.go:30] 24a + LevelDb.open
05:19:07.993827 - [DEBU keybase log.go:30] 24b + LevelDb.open
05:19:07.994827 - [DEBU keybase log.go:30] 24c - LevelDb.open -> ok
05:19:07.994827 - [DEBU keybase log.go:30] 24d - LevelDb.open -> ok
05:19:07.994827 - [DEBU keybase log.go:30] 24e | Unpacked Link f457b410b453f22f688a248f06b6b09b560302670fbe2415124981a6be2235f4
05:19:07.994827 - [DEBU keybase log.go:30] 24f | Unpacked Link da9751d314c6e4d7f95c5b774e1551c40162dd283c8a215063213596276047cc
05:19:07.994827 - [DEBU keybase log.go:30] 250 - LevelDb.open -> ok
05:19:07.983827 - [DEBU keybase log.go:30] 1eb | Unpacked Link 8810b3a08f411c698197da2ae2de9940d03684a92747f9a6b7835c9cf10998c1
05:19:07.996827 - [DEBU keybase log.go:30] 252 | loading link; curr=b048295f72dde311fb352b91202dd398dde89262b23b1c38a62af67da660c0b2
05:19:07.996827 - [DEBU keybase log.go:30] 253 | Unpacked Link b048295f72dde311fb352b91202dd398dde89262b23b1c38a62af67da660c0b2
05:19:07.996827 - [DEBU keybase log.go:30] 254 | loading link; curr=a277fcfddcbf2d0fde3b35ef9a08f74aa1575949bdea91019d8e2c26bad3da29
05:19:07.996827 - [DEBU keybase log.go:30] 255 | Unpacked Link 82725bda8d615f82a87588779be13074f332215109075d9e8d430571d2215d0f
05:19:08.035830 - [DEBU keybase log.go:30] 2fc + CheckFreshness
05:19:08.035830 - [DEBU keybase log.go:30] 301 | Local chain version is up-to-date @ version 84
05:19:07.996827 - [DEBU keybase log.go:30] 258 + LevelDb.open
05:19:07.983827 - [DEBU keybase log.go:30] 1f2 | Unpacked Link fb4eb5ab067c52b7037d7460d1e4b0126665d236673c614b06f3edbd54900bde
05:19:07.983827 - [DEBU keybase log.go:30] 1f3 | Unpacked Link 512ee3afc25e34d708108325baae7b338b2e798aad3d33d362e5fc36cadf1958
05:19:07.997827 - [DEBU keybase log.go:30] 25b - LevelDb.open -> ok
05:19:07.997827 - [DEBU keybase log.go:30] 25c | Unpacked Link df0ce4cdc596541db52f5ac62427838a6d3bf702a144bd1040eda442a9bb5613
05:19:07.997827 - [DEBU keybase log.go:30] 25d | Unpacked Link 2a7206e1c8b9f9e7ab7d9c19ee2b518cd618ebd8a625af7ed2c48e95faaa8032
05:19:07.997827 - [DEBU keybase log.go:30] 25e | Unpacked Link a277fcfddcbf2d0fde3b35ef9a08f74aa1575949bdea91019d8e2c26bad3da29
05:19:07.997827 - [DEBU keybase log.go:30] 25f | Unpacked Link 55136c844eb18642f38ef9588dc2b6d5d56b31b934c789f88224923e8a8ded47
05:19:07.997827 - [DEBU keybase log.go:30] 260 | loading link; curr=55136c844eb18642f38ef9588dc2b6d5d56b31b934c789f88224923e8a8ded47
05:19:07.997827 - [DEBU keybase log.go:30] 261 - LevelDb.open -> ok
05:19:07.997827 - [DEBU keybase log.go:30] 262 | loading link; curr=df0ce4cdc596541db52f5ac62427838a6d3bf702a144bd1040eda442a9bb5613
05:19:07.997827 - [DEBU keybase log.go:30] 263 | loading link; curr=2a7206e1c8b9f9e7ab7d9c19ee2b518cd618ebd8a625af7ed2c48e95faaa8032
05:19:07.997827 - [DEBU keybase log.go:30] 264 + LevelDb.open
05:19:07.997827 - [DEBU keybase log.go:30] 265 + LevelDb.open
05:19:07.998828 - [DEBU keybase log.go:30] 266 + LevelDb.open
05:19:07.998828 - [DEBU keybase log.go:30] 267 | loading link; curr=91749ecda774599097ab4505f9a01abc9568b51a4f70b64cb57d6a2e4b651826
05:19:07.998828 - [DEBU keybase log.go:30] 268 | Unpacked Link 91749ecda774599097ab4505f9a01abc9568b51a4f70b64cb57d6a2e4b651826
05:19:07.983827 - [DEBU keybase log.go:30] 1f6 | Unpacked Link 49c7ad82c74ee985251296e8a529377548b1b5c1216629a245458f016b081e5f
05:19:07.998828 - [DEBU keybase log.go:30] 26a - LevelDb.open -> ok
05:19:07.998828 - [DEBU keybase log.go:30] 26b - LevelDb.open -> ok
05:19:07.998828 - [DEBU keybase log.go:30] 26c + LevelDb.open
05:19:07.998828 - [DEBU keybase log.go:30] 26d | loading link; curr=5a8b9b2cb072fde29f5494ff84add742ca2319be4e8ed19df92902a786d76a11
05:19:07.983827 - [DEBU keybase log.go:30] 1f7 | Unpacked Link 1919fc94d51940c62fb7f20cb6cd0e9df2bac1861b1eb5c2c696ebaabe9b55e5
05:19:07.999828 - [DEBU keybase log.go:30] 26f - LevelDb.open -> ok
05:19:07.999828 - [DEBU keybase log.go:30] 270 | loading link; curr=be1d3cf2c7215c0a2351f74615327df9e29f84c9e91346dd1be162435f1c45d7
05:19:07.999828 - [DEBU keybase log.go:30] 271 | Unpacked Link a7bdae9a8cc5367c9ce49dd853175bcd2c05d28963963053f71296b2563b18d5
05:19:07.999828 - [DEBU keybase log.go:30] 272 | Unpacked Link 36d1285a0194aec54a8dbe2f1a047e5869a2775e1d2d82d9d25b78c4f628429b
05:19:07.999828 - [DEBU keybase log.go:30] 273 | loading link; curr=09a1bb4b489bb772b0cfa15c60d64049179929c8938e9d00e3ff3605932e0610
05:19:07.999828 - [DEBU keybase log.go:30] 274 + LevelDb.open
05:19:07.999828 - [DEBU keybase log.go:30] 275 | loading link; curr=a7bdae9a8cc5367c9ce49dd853175bcd2c05d28963963053f71296b2563b18d5
05:19:07.999828 - [DEBU keybase log.go:30] 276 - LevelDb.open -> ok
05:19:07.999828 - [DEBU keybase log.go:30] 277 + LevelDb.open
05:19:08.000828 - [DEBU keybase log.go:30] 278 | Unpacked Link 09a1bb4b489bb772b0cfa15c60d64049179929c8938e9d00e3ff3605932e0610
05:19:07.984827 - [DEBU keybase log.go:30] 1fa | loading link; curr=49c7ad82c74ee985251296e8a529377548b1b5c1216629a245458f016b081e5f
05:19:08.000828 - [DEBU keybase log.go:30] 27b | Unpacked Link be1d3cf2c7215c0a2351f74615327df9e29f84c9e91346dd1be162435f1c45d7
05:19:08.000828 - [DEBU keybase log.go:30] 27c | loading link; curr=36d1285a0194aec54a8dbe2f1a047e5869a2775e1d2d82d9d25b78c4f628429b
05:19:08.000828 - [DEBU keybase log.go:30] 27d + LevelDb.open
05:19:08.000828 - [DEBU keybase log.go:30] 27e - LevelDb.open -> ok
05:19:08.000828 - [DEBU keybase log.go:30] 27f | Unpacked Link 5a8b9b2cb072fde29f5494ff84add742ca2319be4e8ed19df92902a786d76a11
05:19:08.000828 - [DEBU keybase log.go:30] 279 - LevelDb.open -> ok
05:19:08.001828 - [DEBU keybase log.go:30] 280 + LevelDb.open
05:19:08.001828 - [DEBU keybase log.go:30] 281 | loading link; curr=ad4532503587e8230612fdc316adc018d76a0d65abcffd6a28ce5707ac085437
05:19:07.985827 - [DEBU keybase log.go:30] 1fd | loading link; curr=1919fc94d51940c62fb7f20cb6cd0e9df2bac1861b1eb5c2c696ebaabe9b55e5
05:19:08.001828 - [DEBU keybase log.go:30] 283 | Unpacked Link 232ce82837300501d30d761e5e60400dd8b029d2b752ebf486ff9936685c142e
05:19:08.001828 - [DEBU keybase log.go:30] 284 - LevelDb.open -> ok
05:19:08.001828 - [DEBU keybase log.go:30] 285 + LevelDb.open
05:19:08.001828 - [DEBU keybase log.go:30] 286 | loading link; curr=7454692a0dca02bc92f88c3cd4fef0b584aa72f5879893e569442a0797e65a8f
05:19:08.001828 - [DEBU keybase log.go:30] 287 | Unpacked Link ad4532503587e8230612fdc316adc018d76a0d65abcffd6a28ce5707ac085437
05:19:08.001828 - [DEBU keybase log.go:30] 289 | loading link; curr=af25b0f3e0cb647676d969c47fc2c4f32c6ef5a4f053cbfc03736d94b9e032b9
05:19:07.985827 - [DEBU keybase log.go:30] 1fe | loading link; curr=7253f6f02c876462c5216b0b113551bc653f114486680880864a525205b98959
05:19:08.001828 - [DEBU keybase log.go:30] 28a | loading link; curr=579f067318333c05ba325064ab2ec718f4bac2331adc2c173d9be6f5030290a5
05:19:08.001828 - [DEBU keybase log.go:30] 28b - LevelDb.open -> ok
05:19:08.001828 - [DEBU keybase log.go:30] 28c - LevelDb.open -> ok
05:19:08.002828 - [DEBU keybase log.go:30] 28d + LevelDb.open
05:19:07.985827 - [DEBU keybase log.go:30] 1ff + LevelDb.open
05:19:08.002828 - [DEBU keybase log.go:30] 28f | Unpacked Link 7454692a0dca02bc92f88c3cd4fef0b584aa72f5879893e569442a0797e65a8f
05:19:08.002828 - [DEBU keybase log.go:30] 290 - LevelDb.open -> ok
05:19:08.002828 - [DEBU keybase log.go:30] 291 + LevelDb.open
05:19:08.002828 - [DEBU keybase log.go:30] 292 | loading link; curr=232ce82837300501d30d761e5e60400dd8b029d2b752ebf486ff9936685c142e
05:19:08.003828 - [DEBU keybase log.go:30] 294 | Unpacked Link 579f067318333c05ba325064ab2ec718f4bac2331adc2c173d9be6f5030290a5
05:19:08.003828 - [DEBU keybase log.go:30] 293 - LevelDb.open -> ok
05:19:08.003828 - [DEBU keybase log.go:30] 296 + LevelDb.open
05:19:08.003828 - [DEBU keybase log.go:30] 297 | loading link; curr=6e177cc5402e52f5b35cfb8e979c804e2edb890886e3487cc9db7bd1a7ede5ae
05:19:08.003828 - [DEBU keybase log.go:30] 295 - LevelDb.open -> ok
05:19:08.004828 - [DEBU keybase log.go:30] 299 | loading link; curr=7f8bc8d9ec96fcabd7aa39d9d3e9eaa6542bc5a4e220f0970e4b5364eebd2e3e
05:19:08.004828 - [DEBU keybase log.go:30] 298 | Unpacked Link 7f8bc8d9ec96fcabd7aa39d9d3e9eaa6542bc5a4e220f0970e4b5364eebd2e3e
05:19:08.004828 - [DEBU keybase log.go:30] 29a | Unpacked Link af25b0f3e0cb647676d969c47fc2c4f32c6ef5a4f053cbfc03736d94b9e032b9
05:19:08.004828 - [DEBU keybase log.go:30] 29b + LevelDb.open
05:19:08.004828 - [DEBU keybase log.go:30] 29c | Unpacked Link 7a635c45762e63944f71f7d30b348674595f9562ed18c8074cbb6b6cfa4403c5
05:19:08.004828 - [DEBU keybase log.go:30] 29d - LevelDb.open -> ok
05:19:08.005828 - [DEBU keybase log.go:30] 29e - LevelDb.open -> ok
05:19:08.005828 - [DEBU keybase log.go:30] 29f | Unpacked Link 6e177cc5402e52f5b35cfb8e979c804e2edb890886e3487cc9db7bd1a7ede5ae
05:19:08.005828 - [DEBU keybase log.go:30] 2a0 | Unpacked Link f97c6138afda17bbc5c806768b9e1e2c555719ca77cda533a0cb3d2b60059391
05:19:07.986827 - [DEBU keybase log.go:30] 208 | Unpacked Link 02c314d82e6cbd2cb2a90ebb429b1cf19d4338c2077e3eef2cad93b294a454c8
05:19:08.005828 - [DEBU keybase log.go:30] 2a2 | loading link; curr=b975280bfc0cd503c5396509d77107b725718f5118db54af879e4235cbde6ac0
05:19:08.005828 - [DEBU keybase log.go:30] 2a3 | loading link; curr=7a635c45762e63944f71f7d30b348674595f9562ed18c8074cbb6b6cfa4403c5
05:19:08.005828 - [DEBU keybase log.go:30] 2a4 + LevelDb.open
05:19:08.005828 - [DEBU keybase log.go:30] 2a5 | Unpacked Link 3522c4011d95679041af76fa5cbd25a49b98ee7e3c84f76237bb7bf22da8520e
05:19:08.005828 - [DEBU keybase log.go:30] 2a6 + LevelDb.open
05:19:08.005828 - [DEBU keybase log.go:30] 2a8 - LevelDb.open -> ok
05:19:08.005828 - [DEBU keybase log.go:30] 2a9 - LevelDb.open -> ok
05:19:07.986827 - [DEBU keybase log.go:30] 209 | Unpacked Link d162d91056d8496010f2062b5d59162f623bd73652a3db80c6bba168724618b6
05:19:08.006828 - [DEBU keybase log.go:30] 2aa + LevelDb.open
05:19:08.006828 - [DEBU keybase log.go:30] 2ab - LevelDb.open -> ok
05:19:08.006828 - [DEBU keybase log.go:30] 2ac | loading link; curr=3522c4011d95679041af76fa5cbd25a49b98ee7e3c84f76237bb7bf22da8520e
05:19:08.006828 - [DEBU keybase log.go:30] 2ad | loading link; curr=df7b8faca3c29c3c6d79b1c36f630403f388b56d877aa517a7902f0d36bb7af0
05:19:08.006828 - [DEBU keybase log.go:30] 2ae + LevelDb.open
05:19:08.006828 - [DEBU keybase log.go:30] 2af + LevelDb.open
05:19:08.007828 - [DEBU keybase log.go:30] 2b0 | loading link; curr=f97c6138afda17bbc5c806768b9e1e2c555719ca77cda533a0cb3d2b60059391
05:19:08.007828 - [DEBU keybase log.go:30] 2b1 | Unpacked Link b975280bfc0cd503c5396509d77107b725718f5118db54af879e4235cbde6ac0
05:19:08.007828 - [DEBU keybase log.go:30] 2b2 | Unpacked Link df7b8faca3c29c3c6d79b1c36f630403f388b56d877aa517a7902f0d36bb7af0
05:19:08.007828 - [DEBU keybase log.go:30] 2b3 + LevelDb.open
05:19:08.007828 - [DEBU keybase log.go:30] 2b4 + LevelDb.open
05:19:08.007828 - [DEBU keybase log.go:30] 2b5 | Unpacked Link 5c8e49936e8bf0ecb9805ccd212e3ca4625a50527156bb6b8299c4ba02891943
05:19:08.007828 - [DEBU keybase log.go:30] 2b6 - LevelDb.open -> ok
05:19:08.007828 - [DEBU keybase log.go:30] 2b7 - LevelDb.open -> ok
05:19:08.008828 - [DEBU keybase log.go:30] 2b8 - LevelDb.open -> ok
05:19:08.008828 - [DEBU keybase log.go:30] 2b9 | loading link; curr=5c8e49936e8bf0ecb9805ccd212e3ca4625a50527156bb6b8299c4ba02891943
05:19:08.008828 - [DEBU keybase log.go:30] 2ba | Unpacked Link 3a340b1d22aebc9b84ce0a22c0fade8cf827ee6e440c298c2a0f6704e9c1bce5
05:19:08.008828 - [DEBU keybase log.go:30] 2bb | Unpacked Link b1724f56848acdaefaa6f6c28af0bc41fcf018f3696c4f22c74ad5caf2bd39f9
05:19:08.008828 - [DEBU keybase log.go:30] 2bc - LevelDb.open -> ok
05:19:08.008828 - [DEBU keybase log.go:30] 2bd | loading link; curr=19445c7e1443f593d0bcd968087c3042edbcade8495be3a4e8fda83434a8cb5e
05:19:08.008828 - [DEBU keybase log.go:30] 2be | loading link; curr=3a340b1d22aebc9b84ce0a22c0fade8cf827ee6e440c298c2a0f6704e9c1bce5
05:19:08.009828 - [DEBU keybase log.go:30] 2bf | loading link; curr=8bbaba0f6e5688f9be0f2b27cae0af4be44bd4d4d24690a42ec2653fb9632682
05:19:08.009828 - [DEBU keybase log.go:30] 2c0 | Unpacked Link fb7b09db240ab40a80176c1118b996ac81d3fc96f1728c0ee7f55bd59f29cb5a
05:19:08.009828 - [DEBU keybase log.go:30] 2c1 + LevelDb.open
05:19:08.010828 - [DEBU keybase log.go:30] 2c2 + LevelDb.open
05:19:08.010828 - [DEBU keybase log.go:30] 2c3 | loading link; curr=fb7b09db240ab40a80176c1118b996ac81d3fc96f1728c0ee7f55bd59f29cb5a
05:19:08.010828 - [DEBU keybase log.go:30] 2c4 - LevelDb.open -> ok
05:19:07.988827 - [DEBU keybase log.go:30] 214 + LevelDb.open
05:19:08.010828 - [DEBU keybase log.go:30] 2c6 + LevelDb.open
05:19:08.010828 - [DEBU keybase log.go:30] 2c7 + LevelDb.open
05:19:08.010828 - [DEBU keybase log.go:30] 2c8 - LevelDb.open -> ok
05:19:08.010828 - [DEBU keybase log.go:30] 2c9 | loading link; curr=c356d46d362f68a369f9e90eefa33399b26824b5e1142f365547b55489b53f27
05:19:08.010828 - [DEBU keybase log.go:30] 2cb | Unpacked Link c356d46d362f68a369f9e90eefa33399b26824b5e1142f365547b55489b53f27
05:19:07.988827 - [DEBU keybase log.go:30] 215 - LevelDb.open -> ok
05:19:08.010828 - [DEBU keybase log.go:30] 2cc | Unpacked Link 8bbaba0f6e5688f9be0f2b27cae0af4be44bd4d4d24690a42ec2653fb9632682
05:19:08.010828 - [DEBU keybase log.go:30] 2cd | Unpacked Link 19445c7e1443f593d0bcd968087c3042edbcade8495be3a4e8fda83434a8cb5e
05:19:08.010828 - [DEBU keybase log.go:30] 2ce | Unpacked Link 968c4bb8056dd87f689e455013cde3a83cac3f06ecb2aa9415da4f6d20fad18f
05:19:08.010828 - [DEBU keybase log.go:30] 2cf | loading link; curr=6cf3b96586b075d01dd87717ced9e5bf632eb2ec6a051af7169a683b0c144962
05:19:08.011828 - [DEBU keybase log.go:30] 2d2 + LevelDb.open
05:19:08.011828 - [DEBU keybase log.go:30] 2d1 - LevelDb.open -> ok
05:19:07.989827 - [DEBU keybase log.go:30] 217 | Unpacked Link 5ed83ebfe9048369a0e0c8f5d8466649fb26f9b8151b6fdbdad2276192f14d5d
05:19:08.011828 - [DEBU keybase log.go:30] 2d3 - LevelDb.open -> ok
05:19:08.011828 - [DEBU keybase log.go:30] 2d4 | loading link; curr=40f54fdf70948ed59a9d23aedd3aedeb09e3ee1e44885ef4d6e5ba5e384263c7
05:19:08.011828 - [DEBU keybase log.go:30] 2d5 + LevelDb.open
05:19:08.011828 - [DEBU keybase log.go:30] 2d6 - LevelDb.open -> ok
05:19:08.011828 - [DEBU keybase log.go:30] 2d7 - LevelDb.open -> ok
05:19:08.011828 - [DEBU keybase log.go:30] 2d8 - LevelDb.open -> ok
05:19:08.011828 - [DEBU keybase log.go:30] 2d9 | Unpacked Link 6cf3b96586b075d01dd87717ced9e5bf632eb2ec6a051af7169a683b0c144962
05:19:08.011828 - [DEBU keybase log.go:30] 2da | loading link; curr=97ba80437fa597b6b619ae66fd284cb5066eb8dde02a761bc60042cd0aaa83e5
05:19:08.011828 - [DEBU keybase log.go:30] 2db | loading link; curr=504752c98dec7e2f42eac6caf25ab52b6665709ffe6b7569d66d89395780c53e
05:19:08.011828 - [DEBU keybase log.go:30] 2dc | Unpacked Link 40f54fdf70948ed59a9d23aedd3aedeb09e3ee1e44885ef4d6e5ba5e384263c7
05:19:08.011828 - [DEBU keybase log.go:30] 2dd + LevelDb.open
05:19:08.011828 - [DEBU keybase log.go:30] 2de | Unpacked Link 97ba80437fa597b6b619ae66fd284cb5066eb8dde02a761bc60042cd0aaa83e5
05:19:08.011828 - [DEBU keybase log.go:30] 2df | loading link; curr=f4990fc2d1400773f39d6365e4505e0dbfa1044061f1500e5e41998bd3e225d9
05:19:08.011828 - [DEBU keybase log.go:30] 2e0 | loading link; curr=d36934dfe37c1e2b593804fd471b62c910263452bfada32bf63755a8d4d29434
05:19:08.011828 - [DEBU keybase log.go:30] 2e1 - LevelDb.open -> ok
05:19:08.011828 - [DEBU keybase log.go:30] 2e2 + LevelDb.open
05:19:08.012828 - [DEBU keybase log.go:30] 2e3 | Unpacked Link 25122bcb9c7110bd29269ad31f8f3e523f308e89c426ff8dd2e123dbeff35d2a
05:19:08.012828 - [DEBU keybase log.go:30] 2e5 + LevelDb.open
05:19:08.012828 - [DEBU keybase log.go:30] 2e4 - LevelDb.open -> ok
05:19:08.012828 - [DEBU keybase log.go:30] 2e6 | Unpacked Link d36934dfe37c1e2b593804fd471b62c910263452bfada32bf63755a8d4d29434
05:19:08.012828 - [DEBU keybase log.go:30] 2e7 + LevelDb.open
05:19:08.012828 - [DEBU keybase log.go:30] 2e8 | Unpacked Link f470eaeef51d4a00590596f2ca316a01bdfc78f1ff41ec03e0885d3de467804e
05:19:08.012828 - [DEBU keybase log.go:30] 2e9 - LevelDb.open -> ok
05:19:08.012828 - [DEBU keybase log.go:30] 2ea | loading link; curr=25122bcb9c7110bd29269ad31f8f3e523f308e89c426ff8dd2e123dbeff35d2a
05:19:08.012828 - [DEBU keybase log.go:30] 2eb - LevelDb.open -> ok
05:19:08.012828 - [DEBU keybase log.go:30] 2ec | loading link; curr=f470eaeef51d4a00590596f2ca316a01bdfc78f1ff41ec03e0885d3de467804e
05:19:08.012828 - [DEBU keybase log.go:30] 2ed - LevelDb.open -> ok
05:19:08.012828 - [DEBU keybase log.go:30] 2ee - LevelDb.open -> ok
05:19:08.012828 - [DEBU keybase log.go:30] 2ef - SigChainLoader.LoadFromStorage(15b4292135d94eba7afb70290fdcc900) -> ok
05:19:08.012828 - [DEBU keybase log.go:30] 2f0 | Unpacked Link 504752c98dec7e2f42eac6caf25ab52b6665709ffe6b7569d66d89395780c53e
05:19:08.013828 - [DEBU keybase log.go:30] 2f1 | Unpacked Link ab2d83393c3ee1d4136e1a3502d9f8f9ee19199bea2af28a0eb01353adae38cb
05:19:08.013828 - [DEBU keybase log.go:30] 2f2 + LevelDb.open
05:19:08.013828 - [DEBU keybase log.go:30] 2f3 | loading link; curr=ab2d83393c3ee1d4136e1a3502d9f8f9ee19199bea2af28a0eb01353adae38cb
05:19:08.013828 - [DEBU keybase log.go:30] 2f4 | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) MakeSigChain
05:19:08.013828 - [DEBU keybase log.go:30] 2f5 | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) VerifyChain
05:19:08.013828 - [DEBU keybase log.go:30] 2f6 | Unpacked Link f4990fc2d1400773f39d6365e4505e0dbfa1044061f1500e5e41998bd3e225d9
05:19:07.989827 - [DEBU keybase log.go:30] 21a | loading link; curr=5ed83ebfe9048369a0e0c8f5d8466649fb26f9b8151b6fdbdad2276192f14d5d
05:19:08.014828 - [DEBU keybase log.go:30] 2f9 + LevelDb.open
05:19:08.014828 - [DEBU keybase log.go:30] 2f8 + SigChain::VerifyChain()
05:19:08.035830 - [DEBU keybase log.go:30] 2fa | Future triple=nil
05:19:08.035830 - [DEBU keybase log.go:30] 2fb | Sigchain was fully cached. Short-circuiting verification.
05:19:07.996827 - [DEBU keybase log.go:30] 256 + LevelDb.open
05:19:08.035830 - [DEBU keybase log.go:30] 2fd - SigChain::VerifyChain() -> ok
05:19:08.035830 - [DEBU keybase log.go:30] 2fe | SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) CheckFreshness
05:19:08.035830 - [DEBU keybase log.go:30] 2ff - SigChainLoader.Load(15b4292135d94eba7afb70290fdcc900) -> (true, ok)
05:19:08.035830 - [DEBU keybase log.go:30] 300 + LevelDb.open
05:19:08.035830 - [DEBU keybase log.go:30] 302 + LoadSigHints(15b4292135d94eba7afb70290fdcc900)
05:19:07.996827 - [DEBU keybase log.go:30] 257 + LevelDb.open
05:19:08.036830 - [DEBU keybase log.go:30] 303 - CheckFreshness (15b4292135d94eba7afb70290fdcc900) -> (false,ok)
05:19:08.036830 - [DEBU keybase log.go:30] 305 | Server triple: &{84 8e81da8b9232c844c5fff2c15945456f0c7791d0d7ea782ef67c636b54ecc67c 471bea416f5a5da354216aad3f78337ba45f8e89b785fe6c6ce808c090e3ba7b0f}
05:19:08.036830 - [DEBU keybase log.go:30] 304 | Client triple: &{84 8e81da8b9232c844c5fff2c15945456f0c7791d0d7ea782ef67c636b54ecc67c 471bea416f5a5da354216aad3f78337ba45f8e89b785fe6c6ce808c090e3ba7b0f}
05:19:08.036830 - [DEBU keybase log.go:30] 306 + Refresh SigHints() for uid=15b4292135d94eba7afb70290fdcc900
05:19:08.036830 - [DEBU keybase log.go:30] 307 - LoadSigHints(15b4292135d94eba7afb70290fdcc900)
05:19:08.037830 - [DEBU keybase log.go:30] 309 | SigHints loaded @v4
05:19:08.037830 - [DEBU keybase log.go:30] 308 + API GET request to https://keybase.io/_/api/1.0/sig/hints.json?low=4&uid=15b4292135d94eba7afb70290fdcc900
05:19:08.037830 - [DEBU keybase log.go:30] 30a - LevelDb.open -> ok
05:19:08.132835 - [DEBU keybase log.go:30] 30b + SigHints.Store() for uid=15b4292135d94eba7afb70290fdcc900
05:19:08.132835 - [DEBU keybase log.go:30] 30c - Store for zqueal skipped; user wasn't dirty
05:19:08.133835 - [DEBU keybase log.go:30] 30d | SigHints.Store() skipped; wasn't dirty
05:19:08.133835 - [DEBU keybase log.go:30] 30e | Result is: 200 OK
05:19:08.133835 - [DEBU keybase log.go:30] 30f | Checking user's ComputedKeyFamily
05:19:08.133835 - [DEBU keybase log.go:30] 310 - SigHints.Store() for uid=15b4292135d94eba7afb70290fdcc900 -> ok
05:19:08.133835 - [DEBU keybase log.go:30] 311 + HasActiveKey
05:19:08.133835 - [DEBU keybase log.go:30] 312 - successful API call
05:19:08.133835 - [DEBU keybase log.go:30] 313 - HasActiveKey -> true
05:19:08.134835 - [DEBU keybase log.go:30] 314 + Store user zqueal
05:19:08.134835 - [DEBU keybase log.go:30] 315 + Populate ID Table
05:19:08.134835 - [DEBU keybase log.go:30] 316 | No changes; version 4 was up-to-date
05:19:08.134835 - [DEBU keybase log.go:30] 317 - Refresh SigHints() for uid=15b4292135d94eba7afb70290fdcc900
05:19:08.134835 - [DEBU keybase config.go:114] 318 Config: mapping log_format ->
05:19:08.137835 - [INFO keybase ui.go:55] 31d Identifying zqueal
05:19:08.134835 - [DEBU keybase log.go:30] 319 - VerifySelfSig via SigChain
05:19:08.134835 - [DEBU keybase log.go:30] 31a - Populate ID Table
05:19:08.135835 - [DEBU keybase log.go:30] 31b + VerifySelfSig for user zqueal
05:19:08.135835 - [DEBU keybase log.go:30] 31c | Found self-signature for zqueal @uid=15b4292135d94eba7afb70290fdcc900, seq=84, link=8e81da8b9232c844c5fff2c15945456f0c7791d0d7ea782ef67c636b54ecc67c
05:19:08.139836 - [DEBU keybase log.go:30] 31e + HasActiveKey
05:19:08.140836 - [DEBU keybase log.go:30] 31f - HasActiveKey -> true
05:19:08.140836 - [DEBU keybase log.go:30] 320 | Checking user's ComputedKeyFamily
05:19:08.140836 - [DEBU keybase config.go:114] 321 Config: mapping log_format ->
OK public key fingerprint: 7B5A C030 0E2C 74FD 355C CC81 B1DA 56DC B73E 8516
05:19:08.141836 - [DEBU keybase log.go:30] 322 + Identify(zqueal)
05:19:08.144836 - [DEBU keybase config.go:114] 323 Config: mapping log_format ->
BTC bitcoin 12csNifta955YUAT7kBC9Dh47bW1Ueieo7
05:19:08.145836 - [DEBU keybase log.go:30] 324 + RemoteCheckProof uid=15b4292135d94eba7afb70290fdcc900, seq=57, link=da9751d314c6e4d7f95c5b774e1551c40162dd283c8a215063213596276047cc
05:19:08.145836 - [DEBU keybase log.go:30] 325 + RemoteCheckProof uid=15b4292135d94eba7afb70290fdcc900, seq=73, link=02c314d82e6cbd2cb2a90ebb429b1cf19d4338c2077e3eef2cad93b294a454c8
05:19:08.145836 - [DEBU keybase log.go:30] 326 + RemoteCheckProof uid=15b4292135d94eba7afb70290fdcc900, seq=69, link=5ed83ebfe9048369a0e0c8f5d8466649fb26f9b8151b6fdbdad2276192f14d5d
05:19:08.145836 - [DEBU keybase log.go:30] 327 + API GET request to https://keybase.io/_/api/1.0/user/card.json?uid=15b4292135d94eba7afb70290fdcc900
05:19:08.147836 - [DEBU keybase log.go:30] 335 - Account "sessionArgs"
05:19:08.145836 - [DEBU keybase log.go:30] 328 + RemoteCheckProof uid=15b4292135d94eba7afb70290fdcc900, seq=65, link=7aec28d20c82d761a55f9bd0762420544c8137fccae80bfb1fc5765ff644fc59
05:19:08.145836 - [DEBU keybase config.go:114] 329 Config: mapping log_format ->
05:19:08.148836 - [DEBU keybase config.go:114] 336 Config: mapping log_format ->
OK "zqueal" on twitter: https://twitter.com/zqueal/status/449697262059663360 [cached 2016-01-03 05:11:39 EST]
05:19:08.145836 - [DEBU keybase log.go:30] 32a + RemoteCheckProof uid=15b4292135d94eba7afb70290fdcc900, seq=16, link=97ba80437fa597b6b619ae66fd284cb5066eb8dde02a761bc60042cd0aaa83e5
05:19:08.145836 - [DEBU keybase log.go:30] 32b - RemoteCheckProof uid=15b4292135d94eba7afb70290fdcc900, seq=16, link=97ba80437fa597b6b619ae66fd284cb5066eb8dde02a761bc60042cd0aaa83e5
05:19:08.145836 - [DEBU keybase log.go:30] 32c + Account "sessionArgs"
05:19:08.145836 - [DEBU keybase config.go:114] 32d Config: mapping log_format ->
05:19:08.150836 - [DEBU keybase config.go:114] 337 Config: mapping log_format ->
OK "Xanza" on hackernews: https://news.ycombinator.com/user?id=Xanza [cached 2016-01-03 05:11:39 EST]
05:19:08.145836 - [DEBU keybase log.go:30] 32e - RemoteCheckProof uid=15b4292135d94eba7afb70290fdcc900, seq=57, link=da9751d314c6e4d7f95c5b774e1551c40162dd283c8a215063213596276047cc
05:19:08.145836 - [DEBU keybase config.go:114] 32f Config: mapping log_format ->
05:19:08.152836 - [DEBU keybase config.go:114] 338 Config: mapping log_format ->
OK "zqueal" on coinbase: https://coinbase.com/zqueal/public-key [cached 2016-01-03 05:11:39 EST]
05:19:08.145836 - [DEBU keybase log.go:30] 330 - RemoteCheckProof uid=15b4292135d94eba7afb70290fdcc900, seq=73, link=02c314d82e6cbd2cb2a90ebb429b1cf19d4338c2077e3eef2cad93b294a454c8
05:19:08.145836 - [DEBU keybase config.go:114] 331 Config: mapping log_format ->
05:19:08.154836 - [DEBU keybase config.go:114] 339 Config: mapping log_format ->
05:19:08.154836 - [DEBU keybase config.go:114] 33a Config: mapping log_format ->
OK admin of DNS zone queal.net: found TXT entry keybase-site-verification=ckK1iVirIRJjyVZ7JU5Fzb94AF1peZCpTFBZJhJ8MAQ [cached 2016-01-03 05:11:39 EST]
05:19:08.146836 - [DEBU keybase log.go:30] 333 - RemoteCheckProof uid=15b4292135d94eba7afb70290fdcc900, seq=69, link=5ed83ebfe9048369a0e0c8f5d8466649fb26f9b8151b6fdbdad2276192f14d5d
05:19:08.146836 - [DEBU keybase config.go:114] 334 Config: mapping log_format ->
05:19:08.157837 - [DEBU keybase config.go:114] 33b Config: mapping log_format ->
OK "zQueal" on github: https://gist.github.com/1fa438d29795ac9476ea [cached 2016-01-03 05:11:39 EST]
05:19:08.146836 - [DEBU keybase log.go:30] 332 - RemoteCheckProof uid=15b4292135d94eba7afb70290fdcc900, seq=65, link=7aec28d20c82d761a55f9bd0762420544c8137fccae80bfb1fc5765ff644fc59
05:19:08.196839 - [DEBU keybase log.go:30] 33c | Result is: 200 OK
05:19:08.196839 - [DEBU keybase log.go:30] 33d user card: {FollowSummary:{Following:7 Followers:10} Profile:{FullName:Zach Queal Location:New York, New York Bio:Developer, CEH v7, I love the Cloud and all things tech. Website: Twitter:} YouFollowThem:false TheyFollowYou:false}
05:19:08.197839 - [DEBU keybase log.go:30] 33e - Identify(zqueal)
05:19:08.198839 - [DEBU keybase log.go:30] 33f inserting identify outcome for "zqueal" in TrackCache
05:19:08.198839 - [DEBU keybase log.go:30] 340 - RunEngine(Identify) -> ok
05:19:08.198839 - [DEBU keybase log.go:30] 341 TrackCache key: "9ed4b611be55b10ed1628c194da6b0aa"
05:19:08.202839 - [DEBU keybase log.go:30] 342 - RunEngine(Id) -> ok
05:19:08.202839 - [DEBU keybase globals.go:238] 343 Calling shutdown first time through
05:19:08.207839 - [DEBU keybase login_state.go:887] 345 + Account "LoginState - Shutdown"
05:19:08.207839 - [DEBU keybase login_state.go:889] 346 - Account "LoginState - Shutdown"
05:19:08.202839 - [DEBU keybase log.go:30] 344 Identify: storing result for "zqueal" in result cache
05:19:08.208840 - [DEBU keybase globals.go:278] 347 exiting shutdown code=0; err=<nil>

@rvs
Copy link

@rvs rvs commented Jan 4, 2016

@zQueal thanks for pointing out -t this is super useful! (like I said I really think keybase should advertise this more especially during the time when the whole thing is trying to boostrap and gain trust).

Anyway, this definitely gives me a point at which to look for doing my hacks. As far the CLI goes it still has a few annoying limitations:

  • not providing and option for a full traversal of a sigchain (it just gives me the current one)
  • this: WARNING can't generate track statement on yourself

@zQueal
Copy link

@zQueal zQueal commented Jan 4, 2016

like I said I really think keybase should advertise this more especially during the time when the whole thing is trying to bootstrap and gain trust

One of the biggest issues with keybase is documentation. But qute honestly, the Go build isn't even finished to the point of being pushed to the general public. But once that's done, you can expect documentation to be scrubbed and amended.

not providing an option for a full traversal of a sig chain (it just gives me the current one)

This would probably be best in its own ticket. For posterity and because it's a really great feature. (assuming it's not already a planned feature)

@dghubble
Copy link

@dghubble dghubble commented Feb 28, 2016

@mitar I too think a verb change would be an improvement.

It is important to distinguish "tracking" from an actual signature of someone's public key, which occurs only when their identity can be confirmed in real life. Tracking seems to be a Keybase-specific and user-specific signed snapshot meant to save me from repeatedly checking Github, Twitter, etc proofs for a frequent contact. I'd call that "pinning", "memoizing", "sealing", etc before calling it "tracking".

The way tracking/trackers are prominently displayed on a user's profile seems misleading to newcomers, even dangerous. The fact that I "track" person A just says at one point I checked a few social proofs (enough that I was somewhat comfortable) and created a snapshot of their key and signed it for my own personal use/convenience later. I'm not sure I see value in the trackers/tracking list being public - nobody else should make decisions based on it imo.

@malgorithms
Copy link
Contributor

@malgorithms malgorithms commented Aug 10, 2016

Update here : we've renamed "tracking" "following". There were lots of proposals in this thread from early on, and lots of considerations pointed out and good ideas proposed.

Ultimately "tracking" gave too many people the creeps and we wanted to teach people it's a casual decision (as in not an attestation) and a public decision (you can look at the people that someone follows). People have learned the term "follow" from other sites, and it achieves those goals well.

we'd been talking about this for a few months - it wasn't an abrupt decision.

happy to keep this thread open for further discussion of what it means.

The latest app and website should have this wording. The keyase [un]track command is now keybase [un]follow and the old command will work as an alias for a while.

@mitar
Copy link

@mitar mitar commented Aug 10, 2016

@malgorithms: Why not pinning?

@malgorithms
Copy link
Contributor

@malgorithms malgorithms commented Aug 10, 2016

It's a good word...I think for non-technical users who haven't learned the underlying meaning, it's less universal as a social action. people will still be left wondering:

  • is this public?
  • will they know I "pinned" them?
  • why would I do this?

For "follow" the UX is pretty clearly expected because of many sites. Pinning is obviously used elsewhere (notably pinterest), but it brings up more questions about what it means to pin a person.

All that said, "pin" could still be a bit better word for describing what's going on underneath it all.

@mitar
Copy link

@mitar mitar commented Aug 10, 2016

I think pinning might be more familiar now because of Pinterest. From Pinterest they would know:

  • it is public
  • they know you pinned them
  • this is the only one where we would have to explain the difference from Pinterest (it is not your favorite - despite I think many people are using tracking/following on favorite people)

But I just wanted to make sure you considered it as well. I do not want to reopen the discussion. Following is much better than tracking. It just does not mean anything technically. But it is easier to explain to technical people what you are really doing than vice-versa. :-)

@Avamander
Copy link

@Avamander Avamander commented Oct 6, 2017

I agree, "Pin" makes more sense compared to other options, it also doesn't confuse people thinking they're actually doing something like key signing.

@gene1wood
Copy link

@gene1wood gene1wood commented Jan 30, 2018

For what it's worth, I read the doc page on "following", didn't understand what I was asserting by following someone, came to the linked bug and saw the body of the bug itself saying

But that seems at odds with the word "tracking" -- to me, tracking/following evokes something that you can do frivolously on a whim. On the other hand, if I'm saying "yes, this person is really who they say they are", it seems like there should be more of a barrier to entry. Like I shouldn't "track" anyone I don't personally know.

This is exactly my question (which at least for me isn't clear on this page).

What am I asserting by following a user? I'll (selfishly) neglect to read the 94 comments on this issue to better understand it and just hold off on following anyone for the time being. I'll try checking back to the doc page another time and see if it makes any more sense about what I'm saying publicly by following someone (that I'm confident their accounts haven't been taken over at this point in time, that I trust keybases assertion that the listed accounts are linked because I've verified the account assertions client side, something I'm not thinking of, etc)

Update

@nealmcb pointed me below to comment #100 (comment) above by Chris Coyne which explains this well. Thanks @nealmcb

@IpsmLorem
Copy link

@IpsmLorem IpsmLorem commented Feb 17, 2019

What about hiding followed and followed by people ?

@satorutakada
Copy link

@satorutakada satorutakada commented Aug 4, 2020

ここでいいですか。お互いもう一度信頼するためにしておくべきなのでしょう。信じてるけどね。大事なことでしょう

@nealmcb
Copy link

@nealmcb nealmcb commented Aug 4, 2020

Following people is a good thing for you to do so you can easily keep track of your own verifications.
@gene1wood: Just read the third post in this thread to understand the actual meaning and utility of following: #100 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests