Author: gulan
Date: (2022-11-18)

Synopsis#

State what the proposal does in one sentence. CogniDAO was setup to handle recurring infrastructure payments for Juicebox’s contributors.

Motivation#

What problem does this solve? Why now?

Contributors pay for services out of pocket and get reimbursed by Juicebox. Sometimes this can be a difficult thing with many different persons paying for many different things. Using CogniDAO, Juicebox contributors are able to pay for all of their needed services and have that information transparently recorded and displayed automatically.

Specification#

How exactly will this be executed? Be specific and leave no ambiguity.

Provide 1 month’s worth of liquidity to pay for services: $1500. The funds will be used to pay for recurring subscriptions for juicebox.

Every cycle the bookkeeper will provide a report of all of the incurred costs and will reimburse CogniDAO via the CogniDAO Juicebox v2 Project.

Gulan may in the future inform the DAO and switch the destination to a CogniDAO v3 Treasury.

The funds will sit in public view via the banking api in the bookkeeping app or other public source, e.g. juicytool.

If the dao wish's to stop working with CogniDAO, the remaining funds in the account will be returned to the active Treasury

Rationale#

Why is this specification appropriate?

Juicebox does not have any alternative means to pay for things. This gives a payment rail to execute reccuring payments in a fully transparent way.

Risks#

What might go wrong?

CogniDAO is a legal entity that is setup specifically to pay for things on chain. This can have inherent risks but the primary goal is to reduce this risk to zero and provide this service for as long as juicebox needs it.

Timeline#

When exactly should this proposal take effect? When exactly should this proposal end?

FC#36