blakemscurr

e2e-zk-ecdsa @privacyscaling
Building a safe validium

[blakemscurr @BlakeMScurr]

@bennhoffman @noworkfunction @eigenrobot Yup, it'd be great if there were a timestamping service as widely used as, say, https://t.co/zgqwrEMD78. Could at least limit the scope of discussion. Second solution feels flimsy, but I believe there are protocols in the works for it. https://t.co/L5ZNZizuRj

[blakemscurr @BlakeMScurr]

@dystopiabreaker Didn't this already happen like last year?

[blakemscurr @BlakeMScurr]

@Jeyffre Yeah, and these vary hugely in how fast you can get up to speed. I think for an average interested developer it's something like:

Type 4: days
Type 3: weeks
Type 2: months
Type 1: years

[blakemscurr @BlakeMScurr]

@portport255 @p_tsanev @pashov @code4rena @zksync Makes sense, can you say anything about the language/proving stack?

[blakemscurr @BlakeMScurr]

@odysseas_eth @ProofOfZk @ameensol With plume I think you could take a snapshot of key holders at the time of poll creation, and the proof would show that you own an address in that list. That should solve the registration time issues🤞

[blakemscurr @BlakeMScurr]

@odysseas_eth @ProofOfZk @ameensol I think you could replace semaphore with plume and you wouldn't have to interactively create nullifiers. A plume signature is unique for a given user and message (in this case poll id), and it's still unlinkable. Wallet support is an issue though. https://t.co/095NWlvZX3

[blakemscurr @BlakeMScurr]

@dystopiabreaker Huh, seems about right. 2 people is a model 3 is ~2000lbs of vehicle weight per person, and a R32 (subway car) is ~1500lbs/person with all seats full and no one standing.

Still, cars bad: noise, killing people, concrete wasteland.

[blakemscurr @BlakeMScurr]

@justanowlet Beethoven's 7th symphony 2nd movement.
Tannhäuser overture.
Mozart requiem in D minor (the lacrimosa part is particularly epic).
Grieg, Åse's Death.

[blakemscurr @BlakeMScurr]

@aryehazan What has changed lately that makes the wet market more likely? In mid 2020 I was pretty convinced that it was a lab leak for the reasons you stated, and the lack of evidence for the wet market hypothesis at the time and I haven't updated much since.

[blakemscurr @BlakeMScurr]

@nullity00 I think there might be a small mistake though. Instead of `g^{s+hash(msg)}`, I think you need `g^{hash(s+hash(msg))}` or something. Otherwise you could just pick a new message and change `s` accordingly.

[blakemscurr @BlakeMScurr]

@nullity00 Oh nice, I feel like it could be a good game mechanic. Secretly burn eth (as an offering?) to make a move in the fog of war.

Curious to see if there are more practical defi/protocol use cases though.

[blakemscurr @BlakeMScurr]

@HamishDoodles The lonely lonely water hemisphere

[blakemscurr @BlakeMScurr]

@DrugGovoruna @orthonormalist Yeah, @orthonormalist, if they happen to have studied IPs or PCPs they should be able to get a cryptography-ish position working on ZKPs at an Ethereum L2 like @Starknet @aztecnetwork @zksync @Scroll_ZKP and many others

[blakemscurr @BlakeMScurr]

@levs57 go to. That's not a uniquely attributable fault - I don't think mainnet can tell who is withholding data from whom. If we can't tell which successor is acting badly, I don't know if we can do a cascade like you describe.

[blakemscurr @BlakeMScurr]

@levs57 Hey, sorry for the late response! So how is failure defined here?

My main confusion is that if there are two successor validia that are trying to claim from the same predecessor, they might claim the same specific coins, but withhold the proofs that show who the coins should...

[blakemscurr @BlakeMScurr]

@donnoh_eth @kobigurk favour doing things offchain where the throughput is practically onbounded.

[blakemscurr @BlakeMScurr]

@donnoh_eth @kobigurk @donnoh_eth in ArcPay we're not actually trying to determine who's at fault for a DA problem, we're just using L1 as a fallback to post data in case someone wants to forcibly get the data. That means we're limited to L1 level *forced* data throughput, but the game theory should..

[blakemscurr @BlakeMScurr]

@bkiepuszewski @optimismFND Is there a good post explaining why they had to rebuild their whole stack? Looks like a little discrepancy between the L1 simulation contracts vs what the sequencer was running - I'd have thought those bugs could be squashed more incrementally.

[blakemscurr @BlakeMScurr]

@eth_call I love reading this without knowing hoon, it's like a Lewis Carroll poem. A contract is a door with two arms?