[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance

View post   
File: 227 KB, 635x661, 1561966530823.png [View same] [iqdb] [saucenao] [google]
14516848 No.14516848 [Reply] [Original]

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 if 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

>> No.14516898
File: 43 KB, 600x600, 1472624530127.jpg [View same] [iqdb] [saucenao] [google]
14516898

$1,000 EOY

>> No.14516913

>>14516898
more like 1.000 eoy faggot

>> No.14516951
File: 204 KB, 851x884, eurobabel_2.gif [View same] [iqdb] [saucenao] [google]
14516951

>>14516913
Fine by me

>> No.14516966

>>14516848
ooga booga explain simpler terms in

>> No.14516968

>>14516848
Thanks just dumped my bags

>> No.14517343
File: 245 KB, 346x427, 1561880264870.png [View same] [iqdb] [saucenao] [google]
14517343

>>14516848
>tcp ip developer

>> No.14517392

>>14516848
That reads like every ' whitepaper

>> No.14517438
File: 388 KB, 840x840, fortune.png [View same] [iqdb] [saucenao] [google]
14517438

>> No.14517486

>>14516848
>e 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 clo
>we
>know
t. bsv believer

>> No.14517592

>>14516848
As a ddos developer i can confirm this

> internetword + developer = credability

>> No.14517851
File: 207 KB, 937x528, 2019-03.mueller-russia_0.jpg [View same] [iqdb] [saucenao] [google]
14517851

>tcp ip developer

>> No.14517877

>>14516848
i am unironically a real tcp ip developer and this schizo is garbage

>> No.14517887

>>14516913
That's how you write 1000 in europe faggot