Chainlink’s Sergey Nazarov Created BITCOIN! Satoshi Revealed!! - YouTube

Channel: Chico Crypto

[8]
Egggg yolk, howzit going with this channel’s faithful’s the Chico Army, and of course
[13]
any newbie who i like to call a viewer of the tube.
[15]
If you don’t know by now, my name is Tyler, the host of the only crypto channel, that
[20]
at first shocks, you & then brings the entire house down...you know, our zeus juice, it’s
[35]
time for Chico Crypto!
[39]
So did I shock you last week my video last week, which brought forward the evidence out
[43]
there that Elon Musk could be Satoshi Nakamoto.
[47]
Did you hear what I just said???
[49]
He could be, because there is sooo many different possible candidates out there besides Musk
[53]
which make some sense...Hal Finney, Wei Dai, Adam Back & even Dave Klieman….but there
[59]
is one more who makes my list as a contender, who hasn’t been discussed much & it ties
[64]
back to my #1 hodl, which is OHHHHH so stanky...that is Chainlink founder SN, Satoshi Nakamoto….or
[72]
Sergey Nazarov.
[74]
How, is the flan man himself, a candidate for Satoshi?
[78]
Chainlink was a 2017 ICO???
[80]
Didn’t Sergey create it around that time?.....
[82]
Well, actually no...chainlink has been in the works for a LOOOOONNNNN time, longer than
[87]
most people realize.
[88]
Which, relates back to the domain...smartcontract.com, which today is a landing page for Chainlink
[94]
smart contracts.
[96]
So, how does this website domain provide evidence, that Sergey could possibly be Satoshi??
[100]
Well, the first thing is when the domain was registered….using whois.net, a domain information
[106]
and lookup tool, we can see that smartcontract.com was officially registered, on October 25th,
[112]
2008.
[113]
2008?
[115]
Does that year ring a bell, for anything important, especially the month of October?
[119]
Well, the first email, Satoshi sent, announcing the release of the bitcoin whitepaper, was
[124]
done on October 31st, 2008.
[126]
So, just 6 days before the release of Bitcoin to the masses, Sergey Nazarov secured the
[132]
domain smartcontract.com, and the email he used to register it with, we can do a reverse
[137]
lookup of, and as we can see he has also registered a flurry of domain names, from 2008 on, names
[143]
which will become important.
[146]
All of that right there is weird, alone...but the fact that smartcontract was secured points
[151]
to something….as towards the end of Sathoshi’ “time” with Bitcoin, he started posting
[155]
more and more about “contracts” especially those smart ones...Here is a post, in 2010
[161]
about an escrow contract, Satoshi was coming up with for Bitcoin...then in December of
[166]
that same year, 2010 Satoshi announced the release of version 0.3.18 of bitcoin core,
[173]
and as we can see Satoshi said “ The main addition in this release is the Accounts-Based
[179]
JSON-RPC commands that Gavin's been working on...JSON RPC commands?
[183]
Well if we go to Ethereum, which is the grandaddy of smart contracts, we can see, from this
[189]
infographic, JSON RPC is an interface for the smart contract calling function….so
[194]
obviously, Satoshi was thinking smart just before leaving bitcoin...as just a few months
[201]
later, he sent this email to a group of core devs he was speaking with, some of his last
[205]
words when asked if he was stepping back from the limelight “I’ve moved on to other
[210]
things.
[211]
It’s in good hands with Gavin and Everyone”
[212]
Was that other things in relation to smart contracts….like smartcontract.com??
[218]
Well let’s dive deeper into that domain...and see what we can come up with.
[223]
Going a bit further, we can confirm once again, that yes it was registered 6 days before the
[227]
bitcoin whitepaper, but here it shows the Registrant was indeed Sergey Nazarov...but
[233]
there is also something special there, the registrant’s organization, which says QED
[238]
Global….and here is where things start to really pick up…rember that name QED Global...
[245]
So, the domain for smartcontract.com...it laid dormant from the time of registration,
[252]
until the launch of the actual website in the latter half of 2014.
[256]
I wonder what the original, smartcontract.com looked like?
[260]
We know what it looks like today, all spiked up with those Chainlinks...using web archive
[265]
for the 1st published version...oh shoot, that’s a ton of Bitcoin isn’t it...looks
[271]
like smart contracts for Bitcoin, including an escrow contract...which Sergey or Satoshi,
[276]
termed a conditional bitcoin escrow contract.
[280]
Smart contracts like this, from Sergey or Satoshi, were meant to happen with Bitcoin
[285]
one of the last things he posted in the forums was regarding the ability for smart contracts,
[291]
and JSON RPC calls.
[293]
But Bitcoin doesn’t use JSON RPC, it uses it’s own thing..called Bitcoin RPC and it
[300]
is used by authenticated clients and servers to connect to a running instance of bitcoin.
[305]
The clients issue commands to send transactions, get status, and a variety of other purposes.
[311]
Basically to call contract functions...but, BITCOIN RPC, is bitcoin specific, and not
[317]
friendly to the outside world of APIs and more...which causes major problems.
[322]
But, JSON RPC was implemented back then with Bitcoin, as we can see from the Bitcoin Wiki,
[329]
they have a whole section on JSON RPC...and in it we see, Bitcoin supports SSL (https)
[335]
JSON-RPC connections beginning with version 0.3.14 exactly when Satoshi was still around
[342]
But what the freak happened to it?
[344]
Well continuing, Allowing arbitrary machines to access the JSON-RPC port (using the rpcallowip
[349]
configuration option) is dangerous and strongly discouraged-- access should be strictly limited
[355]
to trusted machines.
[356]
Then, there was enabling SSL on the original client daemon, but that was removed an no
[362]
longer available on Bitcoin core, as of March 2019, and as we can see from the historical
[369]
comments, it says this no longer applies as RPC SSL was removed, and below it was JSON
[375]
RPC over SSL is strongly discouraged, even when it was around.
[380]
This doesn’t seem like what Satoshi wanted from Bitcoin, as he posted about it being
[384]
worked ON just before he left.
[386]
And it kind of looks, from Sergey’s own smart contract.com, that even in 2014, when
[392]
the website went live, he wanted BITCOIN too.
[395]
But, you remember just a bit ago, from the whois registration...it said the registrant’s
[401]
orginization was QED global, and I said that is important.
[405]
Now why?
[406]
Well let’s just go to their website today, and look who is still listed as the managing
[411]
director….a very young picture of Sergey Nazarov is right there.
[415]
So who is QED?
[418]
Well Sergey has them listed as part of his job experience...and it says “QED Capital
[423]
provided founder friendly venture capital to highly technical founding teams in Russia
[428]
and Eastern Europe...it then says “After the first Bitcoin price spike to $30+ (June
[435]
2011) QED Capital turned its attention towards cryptocurrency research and mining.
[441]
With the emergence of altcoins that offered the first smart contract functionality, we
[444]
refocused on applying blockchains beyond cryptocurrency and the real world applicability of smart
[450]
contracts….then it says “Through research, extensive technical due diligence and active
[455]
participation in multiple cryptocurrency communities, QED eventually led to the creation of an expert
[462]
technical team that would make the first blockchain-based webmail (CryptaMail), and one of the first
[467]
live/widely used decentralized applications that used smart contract to move real value
[473]
(Secure Asset Exchange)...which if we scroll, up of course Sergey was the co-founder and
[478]
CEO of each of these.
[480]
So why is this QED and all of this important?
[483]
Well QED, is russian, they have servers and their clients in Russia, and registered the
[491]
domain with Sergey.
[493]
Well, just this Month, Cointelegraph came out with an article, titled “Bitcoin Code
[499]
Reveals Satoshi Nakamoto Used a Russian Proxy” and the article states, as early as 2009,
[505]
Satoshi was relied on a russian proxy and the Telltale signs appear in the file “irc.cpp”
[512]
on line 212...though the details of it were hidden with a cipher, which they were able
[518]
to crack
[519]
The article continues “This cipher seems to work by removing all the zeros and then
[524]
converting the numbers from hexadecimal notation to decimal.
[528]
That produces what looks like an IP address: 87.251.146.
[531]
At the time, the proxy was provided by Anders Telecom.
[538]
It has apparently been defunct since 2016, but we can confirm here that yes, the Proxy
[544]
was indeed Russian..
[548]
Cointelgraph did a search of the IP used, for the proxy, 87.251.146 & you wouldn’t
[555]
guess what they found...they found that same IP proxy, posting hotel reviews in December,
[562]
2008...with the name...Sergey & then again in January 2009, Sergey posting from that
[569]
Proxy, in a thread about Russian speakers in Vietnam.
[571]
Now, that is some of the best who is Satoshi, I think we have come across.
[574]
The russian ties, to Satoshi, as if you didn’t know, BitcoinTalk, the forum Satoshi created,
[579]
Russian was the 1st non english non english section of it.
[582]
But I want to play you something to finish this episode off with, Sergey speaking at
[587]
a 2014 conference about blockchain smart contracts, even before Ethereum was released...let’s
[602]
begin...yes he says, the full potential of the blockchain…..
[615]
Now, let’s just go back to the a JSON RPC thread, from bitcoin talk in 2010 satoshi
[621]
was a part of..regarding JSON RPC, he sad this “as long as the interface is designed
[626]
for things like showing the user the last N transactions history, it's fine, now that
[632]
we have the Accounts feature making it easier to do payment detection the right way” Gavin,
[638]
could listtransactions have an option to list transactions for all accounts?
[642]
Which who was working on it Gavin Andresen, last replied that year, 2010...about it..Yes,
[650]
listtransactions "*" <count> is possible.
[651]
The other account routines could return a new "invalid account name" error if given
[656]
"*".I've got two issues with it, though: which he lists..and the next comment about this,
[662]
JSON RPC idea?
[663]
2013, a random user asks What is the new state of affairs regarding this issue, after 3 years?
[670]
Is there a way to poll or get notified when things happen on the network ?
[675]
No there wasn’t, development had failed to get the full potential, to solve some of
[680]
these problems Satoshi was last talking about.
[683]
Which Sergey was plainly saying at the conference with the release of Ethereum, as the crowdsale
[689]
for this was going on at the time... lets continue
[694]
Yes, BITCOIN was waiting, Sergey and Ethereum was not.
[729]
Cheer’s viewers I’ll see you next time!