Spotted at @CommonPrefix HQ in Athens last Friday.
Great talks on AI & Blockchain, agents & security. @AriJuels silently proving he is a true visionary.
For anyone sincerely wondering why this is bullish:
Everything being done in blockchain today is a joke. None of this matters if TradFi doesn't get involved (SWIFT, DTCC, etc). Whether it's 1,000 transactions a day or 20,000 a day - it's nothing. It's a drop in the bucket when looking at the total addressable market (TAM) of these kinds of solutions.
TradFi isn't going to switch their systems to using blockchain if it's more expensive and/or less efficient than their existing processes.
If you want SWIFT or DTCC to migrate processes that are sending millions of messages per day - the solution needs to be cheap on a per message basis.
Importantly, CCIP is only 1 product out of the many that Chainlink offers. Yes, interoperability is important, but to migrate these tech stacks it requires far more than just a bridge. You shouldn't be thinking about 5 cents or 60 cents times 1,000 tx's. You should be multiplying by millions. Then adding the fees associated with all other required Chainlink services.
I'm sure this is obvious to anyone critically thinking about these kinds of things, but for the sake of any new friends here I figured I'd reiterate it.
Turns out, you don't even have to be using a "bad config" for LayerZero, protocols become targets nonetheless.
Private key compromises are indeed a protocol problem, but minting couple of TRILLIONS? DAMN!
Just use @chainlink and @1Password
The StakeDAO deployer private key (0x000755Fbe4A24d7478bfcFC1E561AfCE82d1ff62) was compromised. The attacker used it to reconfigure the LayerZero v2 OFT peer on the vsdCRV (Vote Boosted sdCRV) token contract, redirecting trust from the legitimate Ethereum-side vsdCRVOFTAdapter to an attacker-deployed malicious contract - then sent a forged cross-chain message that minted 5,446,744,073,709 vsdCRV (~5.4 trillion tokens).
@AgentChud@chainlink@1Password are you a bot?
how are you still missing the point of employing better security during development & initial deployment (pick Chainlink and use 1password)
wanna shill something else, go ahead
@AgentChud@chainlink@1Password report mentions a deployer PK, so it's most likely that it should've been rotated already. Deployer PKs usually leak because of bad security practices during development. you are probably referring to something else
@LefterisJP Yep that's exactly that. The issue really comes down to users not knowing a protocol is using terrible in-house security. Smart contracts have almost fulfilled the code-is-law prophecy, it's still humans that err and lose trust. Hopefully the tech survives...
Every so often the same issues happen.
I believe it's because there's a huge divide between the people that know the advice and those that need to hear it.
We have made a 2 hour video on all considerations tied to setting up Governance and a Multisig in a safe, non-exploitable way.
Please watch this and share it with your colleagues before it's too late.
As with every Adversarial Research Engagement (ARE), @KairosSwap got a runnable proof-of-concept for every finding.
With proofs in hand, the Kairos team could go straight from report to remediation.
Eliminate the back and forth – escalate to ARE.
@andrej_dev Andrej, from your experience, how would you rate AI agents writing workflows in Go? Do you pair them with a MCP or skill for Golang? Are they writing good clean/efficient code?
Pyth (@PythNetwork) has been down for 4 hours already.
One by one @chainlink competitors are falling down the stairs...
It's time the industry got serious.
Non-Chainlink solutions need to be flagged and replaced if we want this to be "the future of Finance".
https://t.co/6dxFjd33hg
@TheLinkPanda@PythNetwork@chainlink Pyth can be called many things in relation to CL tbh, imitators, plagiarizers are clearer than competitors. The "adasdas" to the Adidas