E.g. Travis/Coveralls or CircleCI

doesn't fit through startExit function since moreVM

Bounty 8: Plasma exit with priority queue

Currently there are only exits by proving a burn. Add exits using the priority queue.

Scope:

• exits using the priority queue as described in resources

Resources:

• 0 confirmation exists: https://github.com/omisego/research/blob/master/plasma/plasma-mvp/specifications/no-confirmations.md
• limbo exits: https://ethresear.ch/t/reliable-exits-of-withheld-in-flight-transactions-limbo-exits/1901/2

Deliverables:

• function implementation
• tests

Gain for Circle:

• Full MVP support.

Bounties: https://github.com/parsec-labs/PIPs/wiki/Bounties

wasn't able to apply upgradeability because it used callbacks.

• how to distribute exactly 1 reward per slot per period?
• how to make sure that if a validator is not online, another guy submits the period? which one?

Bounty 34:

Scope

implement the confidence vote process as described in:
https://docs.google.com/document/d/1fC7YFgJB2QQbqbyJuU1AVqleLQPf6hEp0qNgj9-L_dM

Deliverables

• Contract
• Tests

Gain for the project

• Ability to govern chain updates.

Roles:

bounty gardener: @johannbarbie / 10%
bounty worker: open / 80%
bounty reviewer: open / 10%

• package.json scripts
• dependencies
• scripts, test helpers etc

Bounty 19: Exit Market Maker

Reference: https://ethresear.ch/t/simple-fast-withdrawals/2128/29

Prerequisites

• Bounty 18 - Tokenized NFT exits

Scope

• create a smart contract which buys exit tokens with a discount

Deliverables

• market maker smart contract deployed on a Rinkeby network

Bounties: https://github.com/parsec-labs/PIPs/wiki/Bounties

Bounty

Full(ish) test coverage.

Scope

• Achieve 90 % test coverage

Deliverables

More tests.

Gain for the project

Confidence in code.

Roles

bounty gardener: @TheReturnOfJan / 5%
bounty worker: @TheReturnOfJan / 80%
bounty reviewer: name / 15%

use the solEVM enforcer 💪

now:

• follows the auction/logout flow

expected:

• just update balance

currently:

• only transfer utxos can be exited

expected:

• deposit and transfer utxos can be exited

Bounty 18: Tokenized NFT exits

Reference: https://ethresear.ch/t/simple-fast-withdrawals/2128

Scope

• startExit should create an ERC721 exit token for the user
• funds from matured exits should be sent only to the corresponding token owners

Bounties: https://github.com/parsec-labs/PIPs/wiki/Bounties

as described in token economics 5% of each block reward should go to multisig Address.

add a function where a validator can be slashed for including a transaction with less than the min-gas fee.

it is readonly now

getTip() returns blockHeight -1 for some reason

Bounty 27 : Refactor LeapBridge into Bridge and Operator

We want to separate POS logic into it's own contract to enable later upgrades.

Scope

• split bridge into core and operator contract
• have all tests pass with PoS operator contract
• have all tests pass with single operator contract

Deliverables

Branch is pushed to GitHub that solves the above.

Gain for the project

Helps us incrementally launch on a network.

Bounties: https://github.com/parsec-labs/PIPs/wiki/Bounties

• double-spend
• coinbase with output > 0
• non-existing utxo
• invalid tx formats

we want to be able to upgrade the contract with protocol changes of the Plasma chain. But the community should have the ability to veto each upgrade. Process envisioned like this:

1. new contract code is deployed and registered for upgrade.
2. timer runs down over x days.
3. if no majority of token holders veto'ed the upgrade, new contract code is enabled.

as described in token economics

first x years: 50%
after that: 10%

currently there is some absurd formula that doesn't work: https://github.com/leapdao/leap-contracts/blob/master/contracts/LeapBridge.sol#L400-L406

Architecture proposal: https://hackmd.io/s/B11xSoaEm

• Register ERC721 tokens
• Deposit ERC721 tokens
• Change TxLib to work with 32-byte values
• Limit Plasma exit game to ERC20-color tokens only. Create separate exit procedure without priority queue for ERC721-color tokens.

Related: leapdao/leap-node#60

• allow to submit fraud proof that operator has created 2 blocks at same hight
• depends on #5

now all proofs only work for transactions with 1 input and output.

desired:

• enable proofs and slashing for second output in tx
• add unit tests

keep track of gas price used for exits and increase challenge period in case gas price increases

• analyze different grieving attacks during consensus window
• add clipping if possible.

Add uint256[50] private ______gap; into inherited contracts to accommodate possible changes/resizings during upgrades (see openzeppelin-eth lib for example)

objective is to rationalize the need of 2-phase prepare commit transactions on the child chain (or other mitigations, like the expiration time proposed by @DavidKnott in last plasma call).

assumptions: child chain works without any signed confirmations(as in MVP spec):

Deposit not credited Attack

• alice deposits funds into plasma contract
• Validator creates UTXO in next plasma block
• Validator censors all future transactions by Alice to spend the UTXO
• Alice initiates exit from plasma
  => all good?

Frustration Attack

• Alice sends tx with output to Bob
• Validator withholds tx
• Alice gets frustrated and initiated exit with value of tx
• Validator includes tx in next block and challenges Alice's exit

Block Withholding Attack

• Validator constructs a block with invalid txns (0 input, or wrong sigs)
• Validator submits block hash
• Aalidator starts exit of funds
  => no-one can challenge validator, because block data missing

Double Spend by Exit Attack

• Alice sends tx1 to bob
• Bob spends from tx1 with tx2
• Alice initiates an exit with value of tx1
• Bob challenges Alice's exit with tx2

Valueless UTXO Attack

• Alice deposits x into plasma
• Validator includes UTXO with x in next block
• Alice initiates an exit of x
• Alice waits 14 days and receives x back
• Alice starts using UTXO on childchain

Bounty : MoreVP Episode 2

Implement MoreVP for better UX.

Scope

• implement an ExitHandler contract the conforms to MoreVP on refactoring branch
• unit tests

Deliverables

Branch is pushed to GitHub that solves the above.

Gain for the project

It's good design.

https://github.com/omisego/research/blob/master/plasma/plasma-mvp/delegated-exits.md

chose a variant that will work for transactions to smart contracts as well

gardener: @johannbarbie 10%
worker: @nanspro 70%
reviewer: 20%

Especially, for contract and governance upgrades

Scope:

• add an npm script to measure Solidity test coverage with solcover (or alternative). It should be made to run separately from regular npm test.
• add codecov.io integration to travis config. Do not add codecov dependency — it will be used on Travis CI only and Travis already have codecov globally

Deliverables:

• test coverage can be run locally with a separate command
• test coverage is being run on travis ci for every commit and results are pushed to codecov.io

burn exit can be abused by byzatine validator. replace with this:

https://ethresear.ch/t/simple-fast-withdrawals/2128/6

npm test doesn't work

deposits create an event in the bridge contract. what if the operator does not include the transaction in the block or withholds the block?

Scope

• define a depositInclusionTime — reasonable number of periods to wait for deposit tx to be included. It should be changeable via governance.
• create startDepositExit(depositId) method for exiting inflight deposits (deposit without tx included in the period). It should create an exit with depositId instead of utxo part of priority.
• create challengeDepositExit to challenge invalid deposits. Challenger should present a proof of deposit tx inclusion. Provided deposit tx should not be younger than exit + depositInclusionTime
• make sure leap-node is working correctly with the change, picking up deposits as it should be

Deliverables

• updated root chain contracts with the feature
• (probably) new leap-node release with necessary changes
• (probably) new leap-core release with necessary changes

Gain for the project

• increased security for users — they will be able to exit their deposits even if the block with deposit tx was withheld (requires #85 for MoreVP exits)

Roles:

bounty gardener: @troggy / 5%
bounty worker: @johannbarbie / 85%
bounty reviewer: @eezcjkr / 10%

Bounty 8 : MoreVP

Implement MoreVP for better UX.

Scope

• implement an ExitHandler contract the conforms to MoreVP on refactoring branch
• unit tests

Deliverables

Branch is pushed to GitHub that solves the above.

Gain for the project

It's good design.

https://github.com/omisego/research/blob/master/plasma/plasma-mvp/delegated-exits.md

chose a variant that will work for transactions to smart contracts as well

Bounty

Delivery

• deploy LEAP token contract on Rinkeby. Make sure it has a good name (no MOCK please 💩). Mint some coins
• change migrations to optionally use predefined token instead of deploying new token. This way it is easier to redeploy contracts (when testing manually). Keep the old functionality (new token per run) for integration tests
• decide on proposal time for governance contract and get peeps opinion on Slack/Tactical.
• deploy new Minimal Viable Governance contract on Rinkeby
• deploy plasma contracts on Rinkeby
• register LEAP token with the bridge
• transfer ownership of plasma contract to governance
• do basic smoke testing
• coordinate with Testnet commander to ensure the contracts are running fine with node software and bridge UI. Fix things if needed. Bounty is concluded once the contracts are in use in the network

Bounty setup

Size: M (8)

gardener: @troggy / 10% of worker share
worker: @troggy / Size M — 550 DAI
reviewer: @eezcjkr / 10% of worker share

I've removed the reward payment from bridge. hence we should have another contract where rewards can be claimed based on the data in the bridge.

• The contract should have minting rights, verify proofs and remembers claimHeight per validator slot.
• Have a governance parameter rewardTax that determines how much of the claimed reward goes to multi-sig.
• implement RISS model
• implement inflation cap as described in token model (first x years: 50%, after that: 10%)

Keep later integration with #101 in mind, so that reward payments are possible as in Bouquet Chain design.

gardener: @johannbarbie 10%
worker: @johannbarbie 70%
reviewer: ??? 20%

a validator can include any imaginary outpoint, because we use transaction hashes to identify them.

options:

• interactive proof for non-existing outpoint
• go back to block-id + position to identify outpoints.

cancel loop after x itterations