maxper @maxper__

cryptos, dev, research github.com/maxper4 Joined June 2017

Tweets

2K
Followers

315
Following

386
Likes

2K

maxper @maxper__

3 days ago

@iFeyz2 Une hirondelle (ou un autre oiseau) qui construit un nid

0 0 0 150 0

View Details

@yannvon @barnabemonnot @benjaminion_xyz I agree, right now DAG-based protocols are not mature enough: their advantage is that every message is an opportunity to broadcast a block, but it may make them too rigid to satisfy additional properties. I hope to explore this in the future!

0 0 2 55 0

View Details

maxper @maxper__

3 days ago

@xmal Seems cool! I can’t wait for a standard simulation framework to appear (currently, everyone is sort of doing its own tool)

0 0 1 17 0

View Details

maxper @maxper__

4 days ago

@barnabemonnot @benjaminion_xyz Thanks for the link! It is interesting that Ethereum is choosing a direction diametrically opposed to that of protocols from state of the art academic research (DAG-based, e.g., Mahi-Mahi or Mysticeti)

1 0 2 131 0

View Details

maxper @maxper__

2 weeks ago

@barnabemonnot @casparschwa @ethlabs_org Wish you the best!

0 0 0 81 0

View Details

maxper @maxper__

3 weeks ago

@MaxResnick Also, what is the point in reaching the full consensus in each parallel instance? You don’t need that all processes decide in each instance, just that there is a unique block

0 0 0 66 0

View Details

maxper @maxper__

3 weeks ago

@MaxResnick What is the difference with multi bft consensus? For instance this work: arxiv.org/html/2511.0584…

11 0 0 96 0

View Details

maxper @maxper__

3 weeks ago

@MaxResnick It seems fundamental to reference the previous leader in order to prevent the situation where another node committed the previous leader, and you commit the current leader while skipping the previous one

0 0 0 38 0

View Details

maxper @maxper__

3 weeks ago

@tony_fbr_invest Getaround est souvent moins cher @Getaround

0 0 0 34 0

View Details

sudo rm -rf --no-preserve-root / @pcaversaccio

a month ago

let's continue the technical insight posting today and i continue with something people still don't get: PoS or PoW (or DAGs) are NOT consensus protocols by themselves. they're _Sybil resistance mechanisms_ & block author selectors. it's this Sybil resistance mechanism combined with a chain selection rule (fork choice) that makes up a consensus mechanism. Ethereum currently runs _Gasper_: a consensus mechanism combining Casper FFG (finality gadget) with LMD-GHOST (fork choice rule), on top of PoS as the Sybil resistance mechanism & block author selector. some good references: - Casper: arxiv.org/pdf/1710.09437 - Gasper: arxiv.org/pdf/2003.03052 - ethereum.org/developers/doc… - github.com/ethereum/annot…

3 8 70 4K 26

View Details

maxper @maxper__

3 months ago

@xmal @IMDEA_Software @RennesUniv I like the wording "adversarial yet wellformed updates", but spamming is definitely not a byzantine behavior (which is defined as an arbitrary deviation from the *protocol*, not semantics). Also, adapting the difficulty from the causal past is not BFT.