-
## Motivation
For security, we are enforcing a 32 byte address system. While this increases security, this sized address and even the Ethereum 20 byte address format is quite large for normal day-to-…
-
customer:
performer:
deadline:
estimated:
started:
actual:
completed:
confirmed:
dependencies:
- [x] anoma/green#715
supersedes:
-
---
Essentially, the commitments, nullifiers, and roots should be…
-
Instead of storing the whitelisted accounts in on-chain, it is stored in off-chain as a Merkle tree by the specific asset maintainer.
In order to ensure the validity for the lists, they need to comm…
-
## Description
We should support the full node side of the light client protocol.
The components we need for this are:
### Groundwork
- [x] Light client types in `consensus/types`. This in…
-
The tutorial seems to work very well up to part 2. At part 3 right after the `next_fri_polynomial` function is created, the test of `sha256(','.join([str(i) for i in next_p.poly]).encode()).hexdigest(…
-
### Description
The idea of this issue is to try to optimize the step that computes the state root. Indeed, the longest part of this step is the multiple Keccak calculations and t…
matkt updated
1 month ago
-
Issues with Size of circuit
I tried to experiment with size of circuit both sides (large and small) and below are the observations:
**I tried some large size of circuit (K=25) and could observe …
-
BEP: 299
Title: Token Migration after BC Fusion
Status: Draft
Type: Standards
Created: 2023-10-16
# BEP-299: Token Migration after BC Fusion
- [BEP-299: Token Migration after BC …
-
# Lines of code
https://github.com/code-423n4/2022-12-caviar/blob/main/src/Pair.sol#L463-L472
# Vulnerability details
## Impact
`_validateTokenIds()` does not check the length of the incoming `t…
-
Looks like the server accepts a merkle_root set to None.
// Response from the server
Block hash verified: False
Difficulty check: True
Merkle tree check: True