[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]

/biz/ - Business & Finance

Search:


View post   

>> No.14542298 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14542298

>>14542100
Bingo.

>> No.14538408 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14538408

Poor linkies

>> No.14537402 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14537402

>>14537374
Almost a millionare tier

>> No.14534774 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14534774

Based, and dare I say it... Fantom pilled!

>> No.14531108 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14531108

I'm a tcp ip developer at a fortune 50 big data company with 25 years experience in database infosec, I've looked into chainlink and all I can tell you is that the cryptographic measures implemented in regards to the decentralized security paradigm in the API and IoT structure of chainlink's github code is fundamentally flawed after the Pivotal tracker server crashed due to the core attacks on the network enabled by its corrupt data inputs and outputs, what this really means is that by attempting to solve the oracle sybil resistance issue it instead allows customers to bypass the encrypted hardware and even hack into the smart contract Intel SGX mainframe, unless they manage to increase the signatures and scalable nodes, which isn't likely considering the Google backend isn't compatible with the legacy JSON systems and Solidity language from the EVM in the Truffle stacks, that's why the ic3 and SWIFT engineering teams developed the ISO 20220 standards but it's centralized and susceptible to the 51% front running program so yeah basically Sergey didn't foresee that the enterprise customers and cloud blockchain dapps would never allow their protocols to rely on these permissioned host mechanisms thus rendering the LINK ERC 677 token obsolete and no serious developer would consider DLT technology in these conditions, sorry linkies I'm just telling it how it is, personally I sold everything after learning about this.

>> No.14530656 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14530656

And finally

I'm a tcp ip developer at a fortune 50 big data company with 25 years experience in database infosec, I've looked into chainlink and all I can tell you is that the cryptographic measures implemented in regards to the decentralized security paradigm in the API and IoT structure of chainlink's github code is fundamentally flawed after the Pivotal tracker server crashed due to the core attacks on the network enabled by its corrupt data inputs and outputs, what this really means is that by attempting to solve the oracle sybil resistance issue it instead allows customers to bypass the encrypted hardware and even hack into the smart contract Intel SGX mainframe, unless they manage to increase the signatures and scalable nodes, which isn't likely considering the Google backend isn't compatible with the legacy JSON systems and Solidity language from the EVM in the Truffle stacks, that's why the ic3 and SWIFT engineering teams developed the ISO 20220 standards but it's centralized and susceptible to the 51% front running program so yeah basically Sergey didn't foresee that the enterprise customers and cloud blockchain dapps would never allow their protocols to rely on these permissioned host mechanisms thus rendering the LINK ERC 677 token obsolete and no serious developer would consider DLT technology in these conditions, sorry linkies I'm just telling it how it is, personally I sold everything after learning about this

>> No.14529517 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14529517

Unironically balls deep. 10x minimum.

>> No.14529442 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14529442

Imagine not being balls deep

>> No.14528385 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14528385

>> No.14523027 [View]
File: 349 KB, 840x840, 1548565250538.png [View same] [iqdb] [saucenao] [google]
14523027

>>14522891
I AM SORRY FOR DOUBTING YOU WHALE ANON

>> No.14522828 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14522828

All in.

>> No.14522246 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14522246

Balls deep in FTM. it won't be an instant moon but it's destined.

>> No.14522079 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14522079

>> No.14519659 [View]
File: 349 KB, 840x840, 1547308754003.png [View same] [iqdb] [saucenao] [google]
14519659

>>14519638
scamcoin desu

>> No.14517723 [View]
File: 349 KB, 840x840, 1544973429811.png [View same] [iqdb] [saucenao] [google]
14517723

>>14517290
die pajeet

>> No.14517530 [View]
File: 349 KB, 840x840, 1562024719083.png [View same] [iqdb] [saucenao] [google]
14517530

FTM unironically

>> No.14517418 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14517418

FTM

>> No.14517013 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14517013

FTM is a good medium hold anon

>> No.14516706 [View]
File: 349 KB, 840x840, 1562023159947.png [View same] [iqdb] [saucenao] [google]
14516706

Pump eet.

>> No.14516475 [View]
File: 349 KB, 840x840, 1549899953558.png [View same] [iqdb] [saucenao] [google]
14516475

>>14516450
die linkie

Navigation
View posts[+24][+48][+96]