meta issue: towards 300 tps

[lispc]

Our recent goal is to run a 300tps rollup test on testnet ( for 1 hour? ), including matching engine, witness generation, proving, contract verification.

here I list some must-to-do for this goal:

1. design bitwise tx encoding mechanism to save space and gas
2. sha the inputs and make all other circuit input private. Only the hash in public input.
3. rewrite global state manager in rust.
4. implement parallel merkle tree update
5. we may even need to use poseidon ( seems faster than rescue for offline cpu calculation?)

Better to do:

1. Reuse order tree slot
2. Encode big int, signficand + exponent

Depedency of other repo:

1. prover cluster
2. matchengine can generate rollup event

For all things above, we can support 'SpotTrade' first. Implement 'Withdraw/DepositToNew' etc later.

[lispc]

it may cost thousands of dollars EC2 cost (even for a very big proving cluster, for 1 hour) . Not too much.

[0xmountaintop]

At the moment, seems implementing "prover_cluster" and "rewrite global state manager in rust" is the most urgent.

[lispc]

We may write a series of article, like

1. Towards 300tps zk-rollup part 1: Parallel Merkle Tree
2. Towards 300tps zk-rollup part 2: Transaction Data Encoding
3. Towards 300tps zk-rollup part 3: Build a proving cluster
4. Towards 300tps zk-rollup part 3: High performance order matching engine

etc

[0xmountaintop]

w

Our recent goal is to run a 300tps rollup test on testnet ( for 1 hour? ), including matching engine, witness generation, proving, contract verification.

here I list some must-to-do for this goal:

1. design bitwise tx encoding mechanism to save space and gas
2. sha the inputs and make all other circuit input private. Only the hash in public input.
3. rewrite global state manager in rust.
4. implement parallel merkle tree update
5. we may even need to use poseidon ( seems faster than rescue for offline cpu calculation?)

Better to do:

1. Reuse order tree slot
2. Encode big int, signficand + exponent

Depedency of other repo:

1. prover cluster
2. matchengine can generate rollup event

For all things above, we can support 'SpotTrade' first. Implement 'Withdraw/DepositToNew' etc later.

We may wanna further remove ethAddr in circuits.