Read on Twitter
1/N
Some highlights from Thomas Hodges ( #Chainlink Integration Engineer) AMA from yesterday:
1) Currently Chainlink is able to provide 32 byte responses, which is a bit limited (enough for prices and few other usecases) BUT since $LINK is designed to provide any kind
-->
Some highlights from Thomas Hodges ( #Chainlink Integration Engineer) AMA from yesterday:
1) Currently Chainlink is able to provide 32 byte responses, which is a bit limited (enough for prices and few other usecases) BUT since $LINK is designed to provide any kind
-->
2/N
--> of response. They are working in "Multiword responses" where the size of the answer can be any size, enabling any use case responses.
Simply if you need bigger responses you will pay more for it.
(continues)
--> of response. They are working in "Multiword responses" where the size of the answer can be any size, enabling any use case responses.
Simply if you need bigger responses you will pay more for it.
(continues)
3/N
2) When asked about "When threshold sigs" , response:
"Definitely, this year"
2) When asked about "When threshold sigs" , response:
"Definitely, this year"
4/N
3) Q: "Is DECO technically linked to Mixicles"?
"Yes, absolutely. DECO is a use case within Mixicles,..."
My personal opinion is that mixicles was put on hold in order to do a future release with DECO + Mixicles together. Would make sense to me in order to code+audit it
3) Q: "Is DECO technically linked to Mixicles"?
"Yes, absolutely. DECO is a use case within Mixicles,..."
My personal opinion is that mixicles was put on hold in order to do a future release with DECO + Mixicles together. Would make sense to me in order to code+audit it
5/N
When asked about "When staking":
Answer: "Staking is let's say 10% of the work".
The real hardwork is to make the consensus mechanism. And of course make everything work fine with other techs involved (mixicles, t. sigs, etc), study all caveats and corner cases, etc.
When asked about "When staking":
Answer: "Staking is let's say 10% of the work".
The real hardwork is to make the consensus mechanism. And of course make everything work fine with other techs involved (mixicles, t. sigs, etc), study all caveats and corner cases, etc.
Anyone who saw that AMA video ( )
FEEL FREE TO ADD extra things said in it in this thread.
There was lots of mini-things said, I just put in this thread some of the most "commented" things in twitter but there was much more
FEEL FREE TO ADD extra things said in it in this thread.
There was lots of mini-things said, I just put in this thread some of the most "commented" things in twitter but there was much more
