MULTI WORD RESPONSE

github.com/smartcontractkit/chainlink/commit/7391acf38718659fb850f5b8c837f035a160b1f2

MULTI WORD RESPONSE

Attached: 1542386940988.jpg (1000x1000, 185.45K)

Other urls found in this thread:

github.com/smartcontractkit/chainlink/commit/7391acf38718659fb850f5b8c837f035a160b1f2
twitter.com/cryptodavid_/status/1304003681755553792
twitter.com/SFWRedditVideos

Please dumb it down for me

>github.com/smartcontractkit/chainlink/commit/7391acf38718659fb850f5b8c837f035a160b1f2
big if true

Attached: 1594089945581.jpg (729x954, 312.36K)

Attached: 1606826091720.jpg (1242x1322, 235.29K)

Thank you Steve

OH SHIT OH FUCK

Attached: 458-4584680_374-kb-png-pink-wojak-transpar2ent-png.png (840x704, 99.59K)

>MULTI WORD RESPONSE
what is that? pls respond

Please anoon explain us

Checked. This is big.

Attached: 1517591602383.jpg (775x837, 49.46K)

Holy shit usd, eur, jpy? Why they fuck do they keep implementing super use case specific shit to the node? Do these guys don't care about developing a general protocol at all? First they ditched their own protocol to use Synthetix's flux shit that only works with trusted nodes, now they are sinking faster and faster.

func assertPrices(t *testing.T, usd, eur, jpy []byte, consumer *multiwordconsumer_wrapper.MultiWordConsumer) {
var tmp [32]byte
copy(tmp[:], usd)
haveUsd, err := consumer.Usd(nil)
require.NoError(t, err)
assert.Equal(t, tmp[:], haveUsd[:])
copy(tmp[:], eur)
haveEur, err := consumer.Eur(nil)
require.NoError(t, err)
assert.Equal(t, tmp[:], haveEur[:])
copy(tmp[:], jpy)
haveJpy, err := consumer.Jpy(nil)
require.NoError(t, err)
assert.Equal(t, tmp[:], haveJpy[:])

// Simulate a consumer contract calling to obtain ETH quotes in 3 different currencies
// in a single callback.

There are people on this board that aren't all in on LINK

what does this mean in techlet words?

It's basically like multi-ball mode in pinball but with currency requests

/ The consumer contract needs to have link in it to be able to pay
// for the data request.

It means you just win.

There are only one billion LINK tokens on the entire planet to service this new system, and there will never be more.

user, I...

Attached: wef chainlink paper.png (846x687, 516.87K)

Must not be such a big achievement since it is still dumping

Attached: 1603301312870.jpg (675x380, 30.64K)

Who is laughing now?

Attached: A864F773-A747-4967-ADB9-D82AAC781F68.jpg (1180x1141, 116.48K)

>Why they fuck do they keep implementing super use case specific shit to the node?
Because they have very specific users.

>Do these guys don't care about developing a general protocol at all?
Ask WEF.

explanation here
twitter.com/cryptodavid_/status/1304003681755553792

>DECO is a use case within mixicles
I'm lost. My understanding was the Mixicles is a smart contract structure that cleverly obfuscates parties and payouts, whereas DECO was specifically about read-only access to TLS secured information that doesn't compromise that information.

Deco and mixicles have been intertwined from the very start over a year ago.

both are about preserving anonimity
you can use DECO signing for messages that are sent to mixicle oracles.

Does that not mean Link will become one of the more valuable commodities on the planet?

This + VRF + Threshold sigs = staking is essentailly live. Good god next year is gonna be insane, especially with Arbitrum coming online too and cucking eth

Attached: 1576893023175.png (2960x1770, 249.62K)

Your forgetting how many decimals it has

It sure does

Wait for idiots to find out.

Imagine all these hedge funds buying useless LTC,BCH,XRP

I have 5k link and don't even know what an oracle is - I am going to need smooth brain retard level quick run down on this one lads

>github.com/smartcontractkit/chainlink/commit/7391acf38718659fb850f5b8c837f035a160b1f2
it's going to take some time for normans to understand what this means
delete thread and stack

You're going to have 5 houses, each with super/ classic cars outside and a 10/10 high class lady waiting to greet you outside each one.
Thats the quick rundown

sweet!

Attached: wakey wakey.jpg (1500x1000, 337.38K)

While it's good long term, isn't that bad news for node operators income? They will be able to deliver more data in a single job, but they will only be paid for a single job. I wonder how this will play out