# Summa sync

## Discussion items
- Brain dump from Barry: https://hackmd.io/@OFccBlU5TNCiRhpIyT1m7g/B1oVXYEkR
- What is/was the devious plan
- Summa pivot?
- CEX's are L2's?
- Bank proof of reserves?
- Tax payment proof?
- Latest plans from Ryan: https://www.notion.so/pse-team/Q1-DevRel-Plan-816ce0318f694481bedfbc54c683a3f2?pvs=4

## Notes
- Summa
- project 6 months in when Ryan joined / became team lead
- Context
- Started after FTX. Makes sure exchanges can pay back liabilities
- EF strategically, could be a good project to build something valuable for CEX, for ecosystem
- Vision to have exchanges become L2s
- Using Summa to do this. spectrum of being CEX, from becomming full L2. 1st step Pushes them along this spectrum
- eventually CEXs having same trust assumptions & guarentees that L2s do
- Becomming validiums? Signatures from users in order to tranfer money out
- Is this something worth exploring? Publish "what if"? Pushing out vision/thought experiment?
- Not sure. Barry has this idea. V talked about it in his post as well. Would need to know more of security guarantees to know if it's a substantial step along the way. What is CEX tied/enforced into? But research post e.g. on ethresearch could be useful
- Eventually becoming rollups. Same guarantees that L2 does
- Seems like it will default happen (will happen without us doing it)
- CEX being an intermediary. Onboarding users. Basically have to go through them (& legacy financial system - need bank account, need KYC). Dangerous point of power gathering that exixts
- How can we make it easy to help people onboard to crypto (TLSN, ZKP2P, ZKEmail helps). helping people trustlessly onboard
- More ways we can diminish that power: prevent them from stealing money

**Vision?**

- Move away from proofs of on-chain assets
- Move towards proofs of off-chain assets
- Start to prepare to prove solvency for non-CEX (banks & others)

Move into explorations/PoC to build proofs of off-chain stuff (proofs of solvency). Combining with TLSN to do this. e.g. I have this much income. There's gonna be something there. ZK tools for financial data.

ZK as an interoperability tool.
e.g. take all emails. or export from TSLN. wrap in a proof.

Experimenting with TLSN. ZK profile. Import some financial data from TLSN. Making proofs about this.
Pre-processing step (ZPK). take all this e.g. bank data. parse this from difficult to consume JSON to easier to consume merkle tree
Put all this stuff in an Accumulator.
Why?
- it's easier to work with
- make difficult proof once, then make lots of little proofs a lot

Making the interopability, then proving it to do something.

Explore & see what's interesting.

Long term goals?
- Having financial services sign this data. Would be easier than TLSN. Signed data is usable & valuable. Signing data makes it portable

Is this a team identifying use cases for TLSN?
Wouldn't say that. This should be separate from TLSN. Maybe do some market research, choose a specific data source. Ownership of exporting that data into a format that makes sense, is usable, can make proofs about that data.
- So then task it to find that data source that matches strategic priorities
- Export that data, make some proofs about it

**So what's the highest priority data source?**

But thinking through what people would actually care about
Chance to make friends with regulators? Maybe their consumers of this financial data. Not sure how to go about that. Maybe presenting at a financial conference.

Ryan's take
- Mission has been to build product/service for CEX for PoR
- How to make an out-of-the-box product for CEX?
- Barry: this will happen by default. even if it doesn't less upside than other areas. PoC for off-chain asset
- Thinking we should shift to "custodians" more broadly. Widening who the user might be
- Not sure where this project is going. We should wrap it up, put it on the shelf

**Current Summa**

As is, kind of in a reasonable stopping place.
Market research to explore this? Not sure that's useful (people want a faster horse)

Is what Summa is now workable for this?
There's a commitment proof, then inclusion proofs that are based off that on large scale

Barry: probably needs to change
Now based on ECDSA
Probably current architecture won't be super applicable

**Moving forward**

Do we call this Summa? Or leave behind as is?

Seems it could be something new. Could stick with current plan to "wrap up Summa"

Operational aspects
- Power/autonomy as team lead?
- Barry: from my PoV, if you & Sam are happy about going about something, that's great. Don't need explicit signoff
- Ryan & Sam can jam on strategy from here
- Check in after some time? Share our ideas. Async into TG
- Ryan meeting regularly with Wanseob (advising)
- Continue to meet? Bring him up to speed?
- Wanseob has been super useful for technical direction. working with team directly
- To avoid confusion, get Wanseob up to speed. Jam with him on his reactions
- Resource / personnel resources
- Exploring use cases. Do we have the people we need?
- Current team: Ryan, Alex, Jin
- Resources. e.g. Zoey helping with research. Utilizing those resources? Or externally or hiring? Is this available?
- Broadly: Barry could support additional people/resources

## Action items
- [ ] Bar