• Add events to client / event sourcing to server.
• maybe use yarn workspaces(?) for local development

• move out merkle_tree into a separate crate
• in merkle_tree use parallel merkle_tree
• move out key_generator into a separate crate
• move out circuits into a separate crate
• move models and models/circuit into franklin/src/models crate

• remove switch network from explorer
• matter testnet => blockexplorer
• publish code of contract to rinkeby

• Move all crates to rust 2018
• Apply code format. (cargo fmt)
• Organize crates as a workspace (remove top level crate and move bins to server/prover crates)

EDIT:

• Apply clippy fixes
  After merge of all current work, another batch of fixes should be applied.

Since circuit implements all the feature it is time to clean it up and refactor

Create spec for current version of circuit

• Fee now takes 2 bytes
• Amount is not packed in deposit and partial_exit
• Partial_exit rename to withdraw
• Remove partial_exit 0 amount logic

• remove old client
• first approve then deposit

Multitoken MVP fixes

• Ubuntu 16.04
• Ubuntu 18.04
• Debian 9
• Centos 7
• Archlinux

Precision of amount and fee for transfer operation must be increased to 5 bytes and 2 bytes correspondingly, according to this spec:
https://github.com/matter-labs/franklin/wiki/Balance,-amount-and-fee-precision

Todo:

• adjust circuit
• adjust server
• adjust js lib to throw exception on an attempt to represent a number with unsupported precision

Make loadtest work with latest wallet

• parallelize

cache signatures?

• create k8s nodes for gitlab
• configure k8s (label, namespaces..)
• configure k8s plugins (nginx ingress controller, external-dns, certmon)
• set up a repository for docker containers
• set up a repository for helm charts
• configure vault / consul
• deploy gitlab
• configure gitlab
• configure gitlab backups
• import franklin repository
• create franklin helm chart
• configure ci

Constants on contract/dev.env/params.rs do not coincide

• Refactor api endpoints used by it.
• Improve UX (?)

Problem:

There are some parameters that make development hard on laptop.

• Block size chunks - size of Franklin block (denominated in chunks, 1 chunk is 8 bytes)
• Account tree depth - size of account tree.

Proposal:
I propose using environment to setup this constants in our project.

How this constants change code:

models::params -> circuit -> key generator -> solidity contract that verifies proofs.

How to pick up this constants from environment at compile time?
https://doc.rust-lang.org/1.2.0/std/macro.env!.html

How to ensure that constants in binary are consistent with environment?
You can create object in the same "models::params" module that is constructed with lazy_static! and in the construction you can verify that constants from current environment are the same as it was at compile time.
using https://doc.rust-lang.org/1.2.0/std/env/fn.var.html

Corresponds to the following part of roadmap.

• New data model
• Storage for the new model: strict db normalization

Specify API in wiki so that a parallel implementation is possible.

Full exit logic according to new spec

https://docs.google.com/document/d/1M1MnZwsOtt3nlZLJGWTsFz-1900bmvO6pnQmZnviIf8/edit#

Design and implement isolating the prover interface, so that the server and db can be run in a secured environment, while provers are running in the cloud.

new architetcture: https://docs.google.com/drawings/d/1ryKB9er9rJpuIASEnpWtj4HuBuygJe6ma016oBmg4Vo/edit

• make tests for single block generation
  • state must converge
  • prover must generate valid proof for the test block
• design and implement job queue
• create witness_generator actor (thread) in server, with its own state
• move witness generation and state rewinding from prover to witness_generator (via memory, not db)
• fix prover::rewind_state() to only load diff
• (optional) save witness to storage?
• provide witness for prover via REST API (with access control possible to allow prover only)

New deposit:

1. Deposit from from user -- one eth transaction.
2. Deposit funds locked forever (now correct block commit should not fail)
3. Since deposits are locked forever, now deposit cancel is part of the exodus mode.

• working example of new api

• spec
• priority queue
• exodus mode
• not lock balances
• separate governance
• fix contract known issues
• priority fee
• audit
• tests

• page for transactions
  • uniform type/from/to display
• page for accounts
  • paginated list of transactions
• all pages mutually interlinked from everywhere

We should add signature validation within circuit

Create page for franklin developers with issues/branching/review/code practices we tend to work within

• implement contracts
• test contracts

MVP for token transfers