boolafish
boolafish
Cool I got your point now. So the benefit would be shorter deposit confirmation time. Note the user still need to wait Rootchain to confirm, which would take an expected...
### DB data structure #### Structure 1 This is a simple structure that would do the work. The downside would be every time it would need to get all the...
DB interface and memory db implementation is done in #90. Remaining tasks: 1. whenever client get event update from operator should put into db. 2. Remove `block number` from client...
Thanks @mkchungs ! > It's natural to assume that plasma operator would be the primary provider for such services. I agree, and if even with a centralized operator providing all...
Currently it is hard to re-use the integration step code because those hard coded block numbers that client need. if our CI does not break too much might worth wait...
probably Piotr's idea is better: https://github.com/omisego/research/pull/106
I will note down the implication of this problem, this means we are at best RC without solving this.
[throw out some idea] Currently we got three possible proof, multi-sig, SGX, zk-snark. Alternative solution is to protect that on confirm sig. - With multi-sig, we can make the confirm...
[Pepesza's idea] Potentially use snark to prove the "chained txs" within a block is valid, so you can replace input with output.
We can probably solve this by decreasing challenge period, or just make sure challenge period is, for instance, half of the period of “exitable” waiting period. By doing so, trader...