Jeff Burdges

If you've an outer envelop anyways then yeah you might as well do batch verification. We're limited in doing batch verification for gossip because if we've a bad message then...

We do first upgrade all nodes to understand both v1 and v2 assignments, right? It's no problem if some nodes use v1 and some use v2 in principle. It simply...

At a network level, we kinda expect fetching all data from fewer sources to be somehow cheaper, but how much does this mater? At least bittorrent really does not impose...

I'd conjecture that utilizing more connections would cost us little _if_ our networking code was done properly. This opinion is based upon my belief that libtorrent is quite efficient, but...

We've this security implication: If we permit validators to claim less than all their assignments then the list of what they actually claim should really be signed by the extra...

We have this bitfield/list now as `claimed_core_indices: Vec` since @rphmeier did it this way the first time (and you wrote it into https://github.com/paritytech/polkadot/pull/6782 too), but do we want to permit...

I'll try to do a proper write up of incentivization but just fyi some notes exist at https://github.com/w3f/research-security-issues/issues/30#issuecomment-768593265 so message me on element if you do not have access.

Anyone cleaver regression tests done yet? If it's slower in niche cases, then maybe one should've a `no_unsafe` default feature doing this, so then basically everyone benefits but in theory...

We're asking pairing based stuff to run in pure wasm right now. In fact, pairings could run native on a substrate fork, which works fine for polkadot collators, but polkadot...

Related: https://polkadot.polkassembly.io/post/167