leapdao/meta

Everything meta and not-fitting to other repos

meta's Issues

Perfomance tests

Bounty :

We need to develop a performance test suit to simulate real Leap network with many users and transactions and see how Leap node works under load

Flaws:

• Deposit
• Transfer
• Exit - no need as Exits are done through mainnet

Deliverables

• Performance test suit that:
  • Allows to test flows with any number of users and duration
  • Generates results with metrics (transactions per second, throughput etc.) and statistics or the run

Gain for the project

• Being able to estimate the actual speed and load limits of the network under load
  gardener: @eshavkun | 10%
  worker: @eshavkun | 80%
  reviewer: | 10%

create script to claim period rewards

inputs: swapAddr, validatorPriv

outputs: batched transactions to claim period rewards

Alignment with Purpose:

• kickstart chain economy

Bounty:

gardener: @johannbarbie | 10%
worker: @johannbarbie | 70%
reviewer: @sunify | 20%

how-to video tutorial for spending conditions

Scope

• write spending conditions
• deploy spending condition
  • get tokens from faucet
  • hash code of spending condition
  • send funds received from faucet to hash
• spend spending conditions
  • create a transaction
  • publish transaction through rpc
• verify that transaction has been executed
• repeat with invalid transactions, verify that failed

Deliverables

• screen recording

Gain for the project

• educate the team how to write spending conditions
• interest others to write spending conditions

Roles:

bounty gardener: @johannbarbie / 10%
bounty worker: @pinkiebell @eshavkun / 80%
bounty reviewer: @johannbarbie / 10%

Bouquet chain design description (non technical)

For bizdev

Tendermint migration: set up new network (deploying contracts, starting services)

Size L
As part of migration to latest Tendermint version new mainnet will be built. This bounty is about setup of the actual new network once other related bounties are completed:
leapdao/bridge-ui#194
https://github.com/leapdao/meta/issues/81
leapdao/leap-contracts#163
leapdao/leap-contracts#164
#82

Deliveries

• Following contracts are deployed for the new mainnet:
  • Bridge
  • Exit Handler
  • Operator
  • SwapRegistry
• New plasma mainnet is setup:
  • at least one sentinel + AWS loadbalancer
  • validator node
  • call PoaOperator.setValidator for the validator node and send some ETH to validator address
  • set up a sniper rifle: deposit 1 LEAP cent to a sniper address, set up a new CloudWatch cron, set up a new domain in SimpleDb
  • set up tx-store
  • set up token faucet (if there was one)
• Current token is registered on a new Bridge
• Register other tokens from the existing mainnet
• Deposits and exits are freezed on the current mainnet
• Minting rights are transfered to a new Swap Registry
• "Dispenser" address is fund on the new network
• UTXOs migration script is run and UTXO set on the new mainnet is equal to the one on current
• Bridge UI is switched to a new network

Purpose Alignment

• To finish migration to latest Tendermint version

Bounty

gardener: | 15%
worker: @troggy | 75%
reviewer: | 10%

Create a Plasma dApp

Prize Title
LeapDAO Plasma dApp Award

Challenge Description

Create a functional dApp that demonstrates the advantages of Plasma using the documentation and resources we provide.

Submission Requirements
the following points should be fulfilled:

• a web interface for users.
• use of at least one spending condition (smart contract running on Plasma).
• ability for users and judges to use the dApp on the Leap testnet.
• sketch a produce how the dApp + users can exit to the root chain if the Plasma chain becomes corrupted.

Submission Deadline
30. April 2019

Judging Criteria
We award two top submission with the 1st and 2nd prize.

Judging Date
30. April 2019

Bounty
First place --> 1300 DAI + 1300 LEAP
Second place --> 1000 DAI + 1000 LEAP

Create Sales Deck for Prospects

A deck that condenses #50 into a 30 min presentation to a non-technical audience.

---

gardener: | 10%
worker: | 70%
reviewer: | 20%

Create Plasma Fast Exit Market Maker

Prize Title
LeapDAO Fast Exit Market Maker Award

Challenge Description
Plasma enables fast, cheap and secure transactions for users, but it binds capital through its long exit duration. When a user registers a UTXO for an exit, a 3.5 to 7 day challenge period starts. Only after the the challenge period expires the user can withdraw his funds on the Ethereum mainnet. A fast exit market maker is a service that purchases exits from users. In exchange for a small fee the market maker pays the tokens to the user while receiving and waiting for the exit to complete.

You can find out more about the exit market makers here. This blog post also touches upon the concept of exit market makers.

You need to implement the front end from this smart contract.

Submission Requirements
the following points should be full-filled:

• An API that users can submit offers to to sell their Plasma exit.
• At least one mainnet token registered with the Leap Network Bridge.
• Ideally an integration to http://mainnet.leapdao.org.

Submission Deadline
30. April 2019

Judging Criteria
Best Submission

Judging Date
30. April 2019

Bounty
1000 DAI + 1000 LEAP

Apply for gitcoin grants

Scott from gitcoin blocked by that to co-fund more of our bounties

set up an operational bank account

Scope

• set up and verify Holvi account

Deliverables

• KYC/AML verification
• pay in founding capital

Gain for the project

• banking

Roles:

bounty worker: @johannbarbie / 100%

Create a Plasma wallet // Ethereal Virtual Hackathon

Prize Title
LeapDAO Plasma Wallet Award

Challenge Description
Build a Plasma wallet using the documentation we provide. It should show the mainnet value of the token. The user should be able to deposit and exit tokens.

Submission Requirements

Submission Deadline
30. April 2019

Judging Criteria
Best submission receives the prize.

Judging Date
30. April 2019

Bounty
800 DAI + 800 Leap

Setup leapchain monorepo

Scope:

• include repos:
  • leap-node
  • integration-tests
  • leap-contracts
• consider using some monorepo manager, like lerna (if needed)
• monorepo should have README explaining how to work with the repo
• add deprecation note to old repos linking to the monorepo. Temporary keep old repos
• preserve commit history of the migrated repos
• look through README for all the repos and docs.leapdao.org and use new repo urls instead of the old urls
• proper versioning of the monorepo
• everything which depended on the previous repos should be changed to work with monorepo
• nothing should be broken with this change

Deliverables

• new github repo with multiple packages and instructions how to work with it

Publicly visible delivery

• add "Development setup" page to docs.leapdao.org with explainer (similar to README).

Gain for the project

⚠️no direct impact on the roadmap, so second priority
However:

• it should become easier for ecosystem developers to set up local environment
• easier for developers to make cross-repo changes

Write Proposal for Partner Dapps

A document that can be shared with prospects to convert them into partners.

Content Outline

Why Plasma?

• Security of PoW
• throughput of BFT
• Which usecases?
  • Exchanges
  • high volume transactions

Why Spending Conditions

• non-custodial chain
• exit to main-net possible
  => contracts need to be migrateable

How Spending Conditions?

• contracts nat not have state
  => state-minimized storage tokens
• contract have to be exitable
  => exit function
• contract spends have to be authenticated
  => spend function

Getting Started

• docs
• repo
• testnet

Benefits

• cost comparison with main-net
• cost comparison with PoA

Milestones

• driftwood
• the raft
• ...

Proposal

• main-net launch partner
• staking/gas token

Gain for the project

• partners
• finally delivering value

---

gardener: | 10%
worker: | 70%
reviewer: | 20%

Turn off spending conditions support on mainnet

There is a config option for that which can be applied with 0-downtime restarts, however dangerous (see leapdao/leap-node#188 (comment)).

Migrate from waffle.io

Waffle is closing soon, let's stop using it.

We gonna miss:

• issue sizing options
• burndown graphs

Let's find alternative

create policy for mainnet Token Faucet

We need rules for LEAP token allocation for the faucet:

• how much to allocate
• is the allocation regular (e.g. per month) or done once
• who is accountable to maintain the balance
• ...

create a crypto-economic scavenger hunt for devs

Scope

• split the group in merchants and scavengers
• set up each sides with burner wallets
• give scavengers some initial funds on the wallet
• prepare a set of riddles and have the merchants sell them to scavengers
• have the scavengers solve the riddles and earn money
• keep a score board of the addresses with highest balance
• select winner and give them a crypto kitty

Deliverables

• set up burner.leapdao.org with a working wallet
• set up challenge.leapdao.org with instructions, lib & web3 provider
• create a hackmd for each riddle and fund it on-chain

Gain for the project

• have fun with devs
• test transfers and spending conditions with increasing amount of participants

Roles:

bounty gardener: name / share
bounty worker: name / share
bounty reviewer: name / share

monthly active UTXOs - metric

Scope

1. find a way to measure how many UTXOs have been created/spent during the last month.
2. propose metric and get feedback on slack.
3. implement micro-service (ideally without active infrastructure, we like AWS lambda) to collect and expose metric.

Deliverables

• hosted microservice for testnet
• hosted microservice for mainnet

Gain for the project

• ability to measure utilization of chain.
• ability to conclude how much transactions we have taken off the mainnet.

Roles:

bounty gardener: @johannbarbie / 10%
bounty worker: name / share
bounty reviewer: name / share

set up a testnet on https://goerli.net/

write Token faucet terms

approve with legal:

Sonja from status expects a description of the faucet to be able to draft terms of service for us

Apply as team to ETH-Denver to do a live airdrop

short announcement about DAI registered

Scope

• note that governance proposal to register dai finalizes
• talk about xDai vs pDai (plasma DAI)
• list opportunities for wallet providers (fast exit market maker)
• objective: get people to build stuff with it

Deliverables

• blog post
• twitter post

Gain for the project

• transaction volume

Roles:

bounty gardener: @johannbarbie / 10%
bounty worker: @kohola71 / 60%
bounty reviewer: @sunify / 30%

pimp goerli testnet to replace testnet Zeta

have a "proper" deployment of a testnet, including things like web sockets, ssl, code verification, exit market maker, tx store, using our existing infrastructure (aws ssl + load balancers + alarms)

write an announcement about it.

write a thought-leadership piece about plasma

Scope

• write something good

Gain for the project

• show people where the journey goes

Roles:

bounty gardener: @johannbarbie / 15%
bounty worker: @johannbarbie / 65%
bounty reviewer: name / 20%

LeapDAO Playbook

for outsiders it might be hard to understand how we work. write a summary of most important workflows for new-comers.

• How we manage bounties. Describe roles:
  • gardener accountabilities:
    • Sizing of bounties from XS to XL, planning poker, estimated time only one component of size.
    • bounty board
    • gitcoin
    • waffle
  • worker accountabilities: code-style, stay in scope, ask for help
    • Submit PR when 50% of estimate spent.
    • Ask for help (pair programming) when 75% of estimate spent.
    • Start reducing scope when 100% of estimate spent.
    • find a reviewer
  • reviewer: how to do a good code review? 🤷‍♂️
• Other ways of contributions
  • billable
  • salaried roles
• How we run sprints
  • 1.5x reputation reward.
  • reducing scope instead of moving deadline

inspiration: https://sophilabs.co/playbook/

Deliveries

• short and precise markdown file included in this repo.
• link from all contribution guidelines in other repos.
• link from community page.

Purpose Alignment

• make new contributions easier.
• be more aligned on process and hopefully deliver future sprints on time.

Bounty

gardener: @johannbarbie | 15%
worker: ?? | 60%
reviewer: ?? | 25%

🖥🗼Plasma Watchtower

Prize Title
🖥🗼 Plasma Watchtower Prize

Challenge Description
The Leap Network implements the More Viable Plasma design with a single operator. If the operator turn malicious and starts submitting invalid or dark blocks, then the users of the Plasma chain have 7 days to exit their funds back to the main net. Create a monitoring solution with a synced node that follows and validates the Plasma chain and notifies registered users of malicious activity occurring on the chain in real time.

Submission Requirements
the following points should be full-filled:

• running Leap node is fully synced with mainnet.
• Scripts to check the validity of the chain (size of UTXO sets compared with balance of contract).
• a webform for users to sign up, as in this example.

Submission Deadline
30. April 2019

Judging Criteria
Best Submission

Judging Date
30. April 2019

Bounty
1200 DAI + 1200 LEAP

create script to call challengeExit

intputs: exitTxHash, spendTxHash, nodeUrl, providerUrl, privKey

output: transaction sent to the exitHandler

Purpose:

• ability to firefight invalid exits

bounty:

gardener: @johannbarbie | 10%
worker: | @eezcjkr 65%
challenger: @pinkiebell | 25%

Requiem of zeta

• Write a burial post for testnet zeta

• Use references from fightclub

create policy for mainnet Fast Exit Market Maker

We need rules for LEAP token and ETH allocation for the FEMM:

• how much to allocate
• who is accountable to maintain the balance
• ...

add rootNetworkId to mainnet config for all the nodes

same as #90 but for mainnet

add bounties on gitcoin (how meta is that!) 🤓

Scope

• Review bounties on LeapDAO Github and pick the self-contained bounties from the current or next sprint. Add them on Gitcoin.

Deliverables

• curate 5 issues & size them
• get feedback form the team
• put them on Gitcoin
• fund them

Gain for the project:

• brings more contributors to the project

Roles:
bounty gardener: @kohola71 / 15%
bounty worker: @johannbarbie / 60%
bounty reviewer: @kohola71 / 25%

Additional TX helpers

• Prepare exit: collecting all unspent for address and combine it to one (transfer tx with many inputs and one output)
• Exit

Write a script to read unspents on current network and dispense on new network

Size S
As part of migration to latest Tendermint version new mainnet will be built. This will includes migration of UTXOs from current plasma mainnet to a new one. To do this we need to have as script that will:

1. Read all current UTXOs and save them (make a snapshot)
2. On the new network: use specially funded address to distribute LEAP tokens according to snapshot

Deliveries

• Runnable script

Purpose Alignment

• To make sure users users will get their funds on the new network after migration

Bounty

gardener: @eshavkun | 15%
worker: @eshavkun | 70%
reviewer: | 15%

announce Ethereal sponsorship and bounties

Bounty

Scope

• describe virtual hackathon
• describe bounties
• give some ideas

Deliverables

• post copy

Gain for the project

• good utilization of sponsorship
• have teams build on the chain

Roles

bounty gardener: @johannbarbie / 15%
bounty worker: @kohola71 / 70%
bounty reviewer: @johannbarbie / 15%

setup a staging environment for mainnet

Rationale:
On DAOcon, burner wallet will be running on the mainnet. While we preparing the software for DAOcon, we want to test it against the similar network.

Requirements:

• should have exactly the same infrastructure as a mainnet:
  • load balancer for sentinels
  • same number of nodes with the same security group configuration
  • same leap-node version
  • sniper rifle
  • (optional) token faucet
• additional infstructure:
  • fast exit market maker
• should be using testnet as a root network (rinkeby/goerli)

add rootNetworkId to testnet config for all the nodes

To address this issue: https://leapdao.slack.com/archives/CFKUNHHC7/p1554402530000900

Otherwise, the latest leap-node is not working with remote config for testnet

start failover nodes for Testnet Eta

Current network setup:

• 1 sentinel (sen1.testnet.leapdao.org)
• 1 validator (val1.testnet.leapdao.org)

For 0downtime updates at least two sentinels and two validators needed.
We already have:

• sen2.testnet.leapdao.org — has dead zeta testnet setup, stopped now
• val2.testnet.leapdao.org — has dead zeta testnet setup, stopped now

Scope

• setup val2 and sen2 to run compatible leap-node version
• add sen2 to sentinel-ws load balancer
• val2 should be started as readonly
• preserve node_key and validator keys, so we don't need to change peers in leap-testnet.json for Testnet Eta
• (optionally) switch over to val2 and sen2, so that sen1 and val1 can be upgraded as well

Solve subset sum/knapsack problem for optimal outputs usage in makeTransfer helper

get agreement with Status executed

Scope

• set up company
• finish agreement
• execute agreement
• receive second half of incubation tranche

Deliverables

• company registration
• executed SAFTE

Gain for the project

• continue incubation / get help on market strategy

Roles:

reviewer: @eezcjkr / 30%
worker: @johannbarbie / 70%

Integration Testing Utility

Bounty 42:

Requirements

check https://hackmd.io/s/r100DohCQ#TODO

Deliverables

• a repo that holds scripts to launch a local testnet
• example tests that can be run against the testnet

Gain for the project

• Ability to do integration tests.
• automation of manual testing.

---

gardener: @eezcjkr | 10%
worker: @eezcjkr | 80%
reviewer: @troggy | 10%

Plasma Leap Development Milestones

Request:

We need to define milestones and deliverables a little more clearly. Ideally milestones should correspond to public deliverables which we and the community can see and check for example publishing code and description of Computation Verification Game so that others can audit and check it might be an appropriate intermediate milestone. So please have a think about what appropriate timeline/milestones& deliverables might look like. 

Scope:

• rework funding request according to message above.
• work started by pinkiebell

Purpose Alignment:

• better definition of goals and roadmap
• transparency of delivery
• funding

Bounty:

gardener: @johannbarbie | 10%
workers: @pinkiebell @johannbarbie | 90%
reviewer: reality

run Ethereum nodes with failover

Scope

• set up at least 2 instances (docker with geth/parity)
• put them behind loadbalancer
• create an alarm for unhealthy instances
• post alarms to slack
• run healthcheck that compares block height of our node to etherscan.

Deliverables

• endpoint for goerli
• endpoint for rinkeby
• endpoint mainnet
• alarms posted into slack #testnet and #mainnet
• instructions how to add new instance to target gorup

Gain for the project

• have reliable high performing root chain endpoints

Roles:

bounty gardener: @johannbarbie / 10%
bounty worker: @pinkiebell @johannbarbie / 70%
bounty reviewer: name / 20%

Present LeapDAO at ethCC

Scope

• present LeapDAO at ethCC

Deliverables

• get a ticket (~200 EU)
• travel (~300 EU)
• prepare presentation
• present

Gain for the project

• spread the message
• educate on building plApps

Roles:

bounty worker: @johannbarbie / 100%

Draft: Leap Testnet launch

• setup network nodes (> 2 nodes)
• setup contracts
  • deploy properly named token on Rinkeby
  • deploy plasma contracts (using the proper token, not MOCK)
  • deploy governance contract and make it own plasma contracts
• setup bridge UI
• set up LEAP token faucet
• define an executable set of integration tests
• set up monitoring
• execute smoke tests
• create blog post

invent a secure way to do child-chain breeding

Bounty

design explainer

Scope

• a way to breed off-chain

Deliverables

• ethResearch article

Gain for the project

• make Plasma more attractive for NFTs

Roles

bounty gardener: @johannbarbie / 10%
bounty worker: @johannbarbie / 60%
bounty reviewer: name / 30%

create a proof-data provider for sparse-merkle-trees

Scope

• create a lambda function + simpleDb backend to store proof-data for sparse-merkle-trees
• use sparse merkle tree with any key length and values of 32 bytes
• provide an endpoint to store proofs for key-value pairs
• provide an endpoint to generate proofs for each key/value pair
• research integration into web3 plugins

Deliverables

• code
• deployed service
• specification of contract interface that consumes proofs
• estimate of effort to implement web3 plugin

Gain for the project

• simplify development of apps with client-side storage management.

Roles:

bounty gardener: @johannbarbie / 15%
bounty worker: name / share
bounty reviewer: name / share

PIP-006: No motivation for mentee

In the first 4 weeks the Mentee can claim half basic income without tacos.

It means mentee has low/no motivation to progress. Also "hit&run" possible

Prepare Governance proposal for Dev Curator role

The role is a substitute for Dev Circle Lead Link.

❓TODO: What would be a better name for the role? Dev Lead is not accurate. Repo Maintainer is something more appropriate, but doesn't jive with invoice policy

Suggestions:

• Dev Curator

Draft

Domains:

• Development Invoice Budget

Accountabilities:

• curate leap-node, leap-core, leap-contracts and bridge-ui repos:
  • ensure issues list is up to date
  • ensure README is up to date, delegate to Docs Maintainer if needed
  • ensure PRs don't become stale, push gardeners to take care of their issues
  • ensure the code matches project style guides. ❓TODO: do we have it defined? Link to
• review and payout invoices for the relevant work done on the curated repos (on the discretion of Dev Lead) ❓TODO: Link to budget policy? TODO: how can we make more transparent for what the budget can be used for?

Write an April Fools' Announcement

Bounty

Create an announcement that sounds almost real.

Scope

• write an announcement
• have media-rich presentation like google nose

Deliverables

• video
• announcement text

Gain for the project

• create awareness for Plasma
• claim a memetic leadership in the blockchain space

Roles

Priests/Journey Operators: @johannbarbie @pinkiebell

Find memory leak that halts validator

1. wait until a validator crashes
2. analyze memory heap and try to identify issue.

related: leapdao/leap-node#175

Purpose

• stable operations

Bounty

gardener:
worker:
reviewer: