Don't say I called someone a pedophile when I haven't.
I sent it to you in a PM - you made it public. :/
Understandably .. PMs blocked after allegation.
Marco tried to put my public GPG key into his key base account, presumably to try to impersonate me.
I did no such thing. "Presumably" was me. See how many unknowns there are here, anyone could have meddled with my account (it's even possible it was compromised before I deleted it, I never used it).
Hey, where is your proof, scammer?
I KNOW you don't care about the accuracy of YOUR statements.
Go ahead and talk to yourself some more.
A keybase account is a huge point of failure. I don't think I verified identities on there let alone set it up entirely. Neither ever signed my keybase-PGP with my Bitcoin Address (if this happened and I had signed it, tell me, because then THAT would have been a problem and I need to investigate much further). I don't think I ever used my keybase-PGP with link to this forum (again, please correct me if wrong). Much like if someone creates an email account with "marcotheminer@...) and messages people, is that me? No.. The nearest thing to 'confirming original identity' that we have are BTC signatures (and is the only thing I've ever used for this purpose). Still, that said
PGP/Signed BTC addresses can only be relied on if we are certain that keys were not compromised, nor shared.Edit:
Vod, if you make a statement like that - back it up full force. Please find the post.
That's fair - I will give QS due diligence even though he doesn't offer the same. :/
Third Fourth post down: PGP key duplicated.
http://archive.is/fjdwR#selection-2601.0-3059.23Thanks for the reference, I will finally get around to reading the bs. I don't know if anything will change your mind Vod, but yeah big misunderstanding, I have no relation to QS.. And please stop referring to me as QS..
--
Edited some typos + added some info.
I just found this too:
https://github.com/keybase/keybase-issues/issues/2762A good quote I found from user "malgorithms":
Also, just to be clear in case there's any speculation on bitcointalk.org : there's no proof that marcotheminer ever had the private key associated with that public key, since they never signed anything to prove it was theirs. This really was a website bug.
This is a case of jumping to a conclusion from a past jumped-to-conclusion event. We're kind of all in the wrong, but still I am not QS..
My post for the staked address:
Address:
12hYBWiPqfwdveGzpbRdGxeqnoMcNvGNSq
PGP: Should I set one up with keybase.io? Isn't it just another potential point of failure? (if someone manages to gain access to my keybase.io?)
It's interesting I wrote that, and it's what could have happened.. Again, no business was ever done with Keybase. A scammer (let's assume accessing a compromised keybase) could have only fooled someone not double checking / verifying identities best they could (which for now means signed message from staked BTC address)