chainlink VS sourcegraph

Chainlink (LINK) – The Blockchain Oracle Giant

Chainlink allows smart contract developers to receive a wide variety of off-chain data, with the most commonly used features being receiving off-chain randomness and off-chain pricing data. Integrating your smart contracts with Chainlink provides a unique set of potential security vulnerabilities that attackers can exploit; here are the common vulnerabilities that smart contract developers & auditors need to look out for.

In some way, I'd also put Chainlink in that category since they allow to access open world data on-chain and making dapps more relevant as a result.

Smart contracts have revolutionized various industries by enabling the automation of agreements and transactions in a secure and decentralized manner. However, for smart contracts to reach their full potential, they need access to real-world data and external systems. This is where Chainlink comes into play.

I would suggest the use of an oracle like chainlink. Link: https://chain.link - I don't know exactly what your specific requirements are since I cannot review your code but a thirdparty oracle sounds like it could offer you at least some direction.

🥁 Introducing Co:OPERATE @ EthCC by Celo with Co:HOST Chainlink!

Etherisc has built a platform (Generic Insurance Framework) for decentralized insurance applications. We use blockchain technology to help make the purchase and sale of insurance more efficient, enable lower operational costs, provide greater transparency into the industry and democratize access to reinsurance. We’ve been around since 2016, have many high-profile collaborators (including Chainlink) and are proud of the innovative applications of the parametric insurance products built on our platform, including travel delay, crop and carbon credit protection.

As well as feeding real-world data to smart contracts, oracles can be used to monitor other blockchains and pass information about them between networks. Chainlink has made progress in this direction, with their Cross-Chain Interoperability Protocol (CCIP). This enables the creation of multi-chain apps. The protocol is maintained by a decentralized network of nodes. However, this is unlikely to be as secure as the chains between which messages are being sent.

Chainlink is not a blockchain - it's a "heterogeneous network", i.e. an open-source protocol for building oracle networks. Chainlink is 'blockchain-agnostic', aimed at connecting any chain to any API/external system and supporting interoperability between chains. Besides ETH, it has existing or planned integrations with: ONE, ADA, XTZ, MATIC, HBAR, DOT, BSC, ATOM, LUNA, etc.

Sourcegraph | REMOTE | Full-Time | Machine Learning Engineer, Developer Advocate, Enterprise Product Manager, Technical Advisor | https://sourcegraph.com

Sourcegraph is a code AI platform that makes it easy to read, write, and fix code–even in big, complex codebases.

We are building Cody, an AI coding assistant that uses code search and code intelligence to help devs quickly understand what's happening in code and generate new code that matches the best practices in your codebase. Cody supports AI-enabled autocompletion, fixing bugs, refactoring, test generation, code explanation, and answering high-level questions. You can read Steve Yegge's post on why Cody's code context engine differentiates it from the fast-moving field of AI dev tools: https://about.sourcegraph.com/blog/cheating-is-all-you-need.

Apply here: https://grnh.se/0572f98b4us

That's pretty much what https://sourcegraph.com/ are selling, is it not?

Despite their shitty rug-pull <https://github.com/sourcegraph/sourcegraph/pull/53345>, I do really like Sourcegraph and one doesn't (currently?!) need to be logged in to use it: https://sourcegraph.com/search and they have a handy rewrite pattern such that one can just plug the repo path into the URL for quick searching e.g. https://sourcegraph.com/github.com/JetBrains/intellij-commun...

- https://sourcegraph.com is pivoting and building a copilot application (named Cody). This is pretty good, since sourcegraph is great at understanding your code

While a readable Dockerfile can work as documentation, there are a few caveats:

* the application needs to be designed to work outside containers (so, no hardcoded URLs, ports, or paths). Also, not directly related to containers, but it's nice if it can be easily compiled in most environments and not just on the base image.

* I still need a way to notify me of updates; if the Dockerfile just wgets a binary, this doesn't help me.

* The Dockerfiles need to be easy to find. Sourcegraph's don't seem to be referenced from the documentation, I had to look through their Github repos to find https://github.com/sourcegraph/sourcegraph/tree/main/docker-... (though most are bazel scripts instead of Dockerfiles, but serve the same purpose)

We use Sourcegraph, which is a tool that searches through code in repositories. We leverage this tool in order to understand the adoption curve of our components across all of Reddit. We have a dashboard for each of the platforms to compare the inclusion of RPL components over legacy components. These insights are helpful for us to make informed decisions on how we continue to drive RPL adoption. We love seeing the green line go up and the red line go down!

SourceGraph: https://github.com/sourcegraph/sourcegraph/pulls?q=is%3Apr+a...