Invite and Funding Campaigns

[n13]

There will be two Campaign proposals sub types: Invite campaign and funding campaign

Both are voted on from the campaign votes, so no changes there, it's not really a new voting type.

Funding campaign - no different from existing campaign type

Invite campaign -

• Takes additional parameter max amount for invite. Default 1000 Seeds.
• When funded, creates an entry in the campaign table in onboarding contract #236
• Funds still come from funds.seeds but they go to onboarding, along with the table entry
• When voted down while still running, this type of campaign returns the funds from the onboarding contract to funds.seeds
• When the owner (campaign winner) decides to cancel the campaign, the funds go back to funds.seeds (the origin) as well
• eval period is set to 6 cycles by default so people have time to vote down if needed. Even though all the funds are paid out immediately to oboarding.

[IanMendozaJaimes]

Hello, I have a question:

• The only additional parameter it should take is the max invite amount, right? But what would happen with the parameters described in #236: planted, reward owner and reward, should they be settings?

[n13]

Hello, I have a question:

• The only additional parameter it should take is the max invite amount, right? But what would happen with the parameters described in #236: planted, reward owner and reward, should they be settings?

Yeah I think they need to be parameters also

[julioholon]

The bank for invite proposals, should be the Campaigns bank. Only campaign proposals have sub types (it has subtypes, because the voting tokens should be the same)

What if instead of subtypes, we have a "voting pool id" for each Type, so we can have two different Types that uses the same voting pool.

Ex: Campaign Type: Alliances Voting Pool ID: Alliances Funding bank: Alliances

Campaign Type: Funding Campaigns Voting Pool ID: Campaigns Funding bank: Campaigns

Campaign Type: Invite Campaigns Voting Pool ID: Campaigns Funding bank: Campaigns

Campaign Type: Referendums Voting Pool ID: Referendums Funding bank: Referendums

Campaign Type: Milestones Voting Pool ID: Campaigns Funding bank: Milestones

[julioholon]

Maybe add an index to walk accross only on eval proposal, with their own cpu time, so we can schedule processing each type on a different time.