Thread by @dao_kassandra

API3 vs Chainlink - KassandraDAO's answer.

We got a lot of questions about this. I think it's time we set the record straight.

TL;DR: Kassandra is oracle failing resistant and needs way more data feeds than what Chainlink has.

🧵1/8

#AVAX #Avalanche #API3 $LINK

🍎🍊Apples and oranges. Comparing price oracle solutions to AMM-set prices didn't make a lot of sense.

We've said this many times, but we don't use any oracle to update our price feeds; each investment fund is it's own AMM.

🧵2/8

While we do recognize @chainlink as the leading and most secure oracle provider, using their oracles would be justified only when you use one of it's already existing data feeds, or when your application critically relies on the data.

None of those fit the bill for us.

🧵3/8

This means that even if @API3DAO gets compromised, the very worst that can happen is a small amount of our portfolio being misallocated in pre-approved assets.

This is not critical, and we can always pause the strategy as soon as its detected.

🧵4/8

Furthermore, to allow investors to customize and build investment strategies, we need a LOT of data feeds.

While Chainlink makes it easy for you to use their natively integrated data feeds, you'd need to sponsor infrastructure for each and every one that it doesn't have.

🧵5/8

This would cost a high amount each year for each data feed. Simply put, it'd be a lot of money to spend on a system with a whole suite of features that we wouldn't use fully, just for data feed integration.

We'd go broke before $aHYPE got a chance to be released.

🧵6/8

However, this doesn't mean we're not in talks with them about using a certain part of their solutions...

I'm talking too much about it on the open though.

You'll find out more about it on the coming weeks and months, or on the next protocol update... Probably nothing.

🧵7/8

With this being said, $LINK marines, please don't tear us apart.

We'll hire you to train the Kassandra Phalanx as a peace treaty, deal?

🧵8/8 - END.