---
# System prepended metadata

title: Fundraising sync (10/16/2019)

---

# Fundraising sync (10/16/2019)

## Action items

- Tooltips everywhere
- Form error handling system in onboarding
- More default parameters
- Split presale configuration from campaign configuration
- Reorganizing onboarding screens to be function-specific vs. app-specific?
- Changing multisig-token configuration to include voting settings (e.g. 2 of 3 need to agree)
- Agent/Pool: show balances, since no Finance app is attached
- Finance: detect if Tap is installed, watch for its Withdraw events to show Fundraising transactions

## Topics Discussed

- Why is there a Finance app included in the Fundraising template?
    - Flow of money is unclear at the moment:
        - Agent is the "pool", but it does not show the pool balance
        - Tap takes funds from the Agent and passes it to the Vault, but the Vault is not shown in the UI
        - Finance app does not show vanilla ETH and token transfers
- Does it make sense to keep the Board and Beneficiary inside the same org?
    - Could choose arbitrary address for both
        - Board would have to be either a Voting app or an Agent app
    - Onboarding could ask users if they already have an org set up and fetch its addresses automatically
- Could we decouple the Presale and Campaign phases?
    - Lots of people are confused about:
        - Share token vs board token
        - Presale vs. campaign, and campaign configuration options
- Fundraising architecture
    - Architecture right now is based on being "feature adds" for an organization, so it's coupled inside an organization
    - Does it make sense to take Fundraising out to be a "service", outside of an organization, so we can decouple these from being bundled as part of organizations?
    - There are a lot of technical problems with only using the Presale part at the start (e.g. installing rest of the apps later, etc.)
- How do we wind down an organization or give back all the money?
    - As the invested funds stabilize, the batch period could be adjusted to be longer (to stabilize the token price)
    - Difficult to do wind down correctly, since as soon as you open a vote to decide to close the organization, there will be a race to divest out of the org
    - Continuous organization **should not** be used for finite period contracts; it's meant for *long* periods of times