Zellic — Research Blog

What if a node rejects a malicious block but still remembers too much about it?

During our review of Relay Protocol’s Settlement Protocol, we spent some time around the Bitcoin sweep path, the small piece of machinery that moves a confirmed BTC deposit from a per-order address into Relay’s depository.

Formal verification provides mathematical guarantees that constraints correctly enforce their intended computation.

We discovered a type-confusion vulnerability in Chrome’s V8 engine that can be exploited to achieve remote code execution.

This article is for security research and auditing: we start by locating controllable inputs and verification boundaries in the program lifecycle, then break down the interpreter and JIT execution paths, and finally use two real vulnerabilities to show how

Imagine that we’re making a crypto wallet.

I designed a new ZK-friendly hash function: Polocolo↗.

Boneh-Lynn-Shacham (BLS) multi-signatures are a powerful cryptographic tool that enable multiple participants to jointly produce a single, compact signature.

For the forseeable future, Code4rena will run all of its audit competitions for zero platform fee.

While building the EVM trackooor↗, we had the idea of scanning for uninitialized contracts on Ethereum to find potentially vulnerable contracts.

Have you heard of TON?

Last summer, we acquired Code4rena↗, the leading audit competitions platform.

It’s well-known that Bitcoin has a more constrained scripting system than other blockchains like Ethereum or Solana, which more directly support running smart contracts.

Numerous rug pulls and hacks have made choosing a decentralized finance (DeFi) protocol seem risky and overwhelming.

Members of the Zellic cryptography team (Malte Leip and Avi Weinstock) participated in the most recent ZK Hack competition, ZK Hack V↗, consisting of three puzzles overall.

Zellic is proud to announce the EVM trackooor, a framework for tracking and processing arbitrary data on blockchains.

What happens when developers accidentally pick a predictable source of randomness, and that source happens to be significantly weaker than reasonable developers would expect?

Curating relevant security information is challenging, especially when there’s an overwhelming amount of available data.

When on the topic of Web3 security, smart contract vulnerabilities are the first things that come to mind.

gnark↗ is a popular zkSNARK library written in Go.