---
# System prepended metadata

title: Weekly Knowledge Exchange

---

# Weekly Knowledge Exchange

## Notes

### Voting transaction
- When vote (tx to aggregator), voter have to provide the following info:
    - He has registered his public key with rollup contract (proof of membership)
    - He has the private key corresponding to registered public key (signature)
    - Vote

## Questions
### eKYC
- Read info with phone => how ?


### Verify Certificate Chain 
- Where to get certs?

### Scope of the system
- **General purpose or for specific application only?**
- Can policies be changed? (change which parameters?)

### Privacy preservence (?)
- How should voter submit info to aggregator?
    - Which field is in clear text?
    - Which field is not in clear text? If not, encrypted or replaced with zk proof?

### Registration transaction
- Send to L2 aggregator or L1 rollup contract?
    - L1 => very slow
    - L2 => censored then what to do?
- **If current aggregator went down, what would we do?**
    - Same with Ethereum PoS?

## TODO
### eKYC
- Get private key, public key to sign transaction
- Get CVCA
- Verify CVCA

## Concerns
### Batch size
- How many txs in a batch is too much? (If too many => proof too big)


### Demo
- Fork Ethereum and run on our nodes or run on test net?