POTLOCK
WebsiteGithub
  • ๐Ÿ‘‹Welcome to POTLOCK
    • ๐Ÿ”“POTLOCK Protocol
    • ๐Ÿš€Value Proposition
    • ๐Ÿ’ธRevenue Model
      • ๐Ÿ’ตCurrent Fees
    • ๐Ÿ”ฎRoadmap
    • โ™จ๏ธUnderstanding Pots (Funding Rounds)
    • ๐Ÿš€End Game
  • โ“FAQ
    • ๐ŸšงPot Not Deployed
  • User Guides
    • โž•๐Ÿ’ผProjects
      • ๐Ÿ“‹ Create Project
      • ๐Ÿ—ƒ๏ธCreate Project As DAO
      • ๐Ÿ“–Project Guidelines
      • ๐Ÿ™Donate to A Project
      • ๐Ÿ’ธCreate Project Referral Link
    • ๐Ÿš€Project Tips for Success
    • ๐Ÿ‘จโ€๐ŸณPot Owners & Chef Training (Pot)
      • ๐ŸŒŸ Key Roles in a Pot
        • ๐Ÿ‘จโ€๐ŸณChef
      • ๐Ÿ‘จโ€๐Ÿ’ปDeploy Pot
    • ๐Ÿง Planning A Pot
      • ๐Ÿ”ŽChoosing a Chef
      • ๐Ÿ˜ฉ Biggest Challenges of A Round
    • ๐Ÿ“ฌApply to A Pot
      • ๐Ÿ›๏ธApply to Pot as a DAO
        • ๐ŸŒฑCreate A DAO
    • ๐Ÿ’—Matched Donations | Donate Through A Pot
    • ๐Ÿ’ฐSponsors | Funding A Matching Round
    • ๐Ÿ“ฃFor Approved Projects in Pot
    • ๐ŸฅŠChallenging Pot Results
      • ๐Ÿ“How to Create A Challenge
      • โœ…Resolve A Challenge
    • ๐Ÿ˜‡Donors
      • ๐Ÿค–Verify As Human
    • ๐Ÿ‘€Soon / Personas
      • ๐Ÿ›๏ธPotluck Foundation DAO
      • ๐Ÿ˜’Observor
      • ๐Ÿ“Projects
    • ๐Ÿ“คCampaigns
      • ๐Ÿ”ŽExplore Campaigns
      • ๐Ÿ“ฌCreate Campaigns
      • ๐Ÿ—ž๏ธCampaign Page
    • ๐Ÿ“‹ Lists
      • Create List
      • Edit List
      • Apply to List
      • Donate to List
    • mpDAO RPGF
      • Apply to mpDAO Pot
      • Voting Mechanism
      • How to Vote
  • Contracts
    • ๐Ÿ“ƒContracts Overview
    • ๐ŸญPotFactory [live]
    • ๐ŸฒPot [live]
    • ๐Ÿ™Donation [live]
    • ๐Ÿ“œLists [live]
    • ๐Ÿ—บ๏ธRegistry [deprecated]
    • ๐Ÿ’ฒCampaigns [live]
    • ๐Ÿค–Sybil Contract - NADABOT
    • ๐Ÿ—ƒ๏ธAttestations [WIP]
      • ๐Ÿ’ฌOther Attestation Services (Research)
    • ๐Ÿ“‡Staging and Test Environments
  • ๐Ÿ“šTerms
    • โฃ๏ธQuadratic Funding
  • Front-End
    • React (NextJS)
    • ๐Ÿ‘ทโ€โ™‚๏ธBOS Gateway + Workspace
      • ๐ŸŽBrand Kit (WIP)
  • Get Involved
    • ๐Ÿ‘ฉโ€๐Ÿ’ปFor Devs
      • Using NEAR API JS
    • โœ๏ธCreate Guides
    • ๐Ÿ’‘Volunteer
    • ๐Ÿ‘€Watch Us Cook
  • General Information
    • ๐Ÿ“šCode of Conduct
      • ๐Ÿ“QF Rules
    • ๐Ÿ›Beta Phase
    • ๐Ÿ“ŠData
  • Products
    • nada.bot
    • Potlock App
    • GrantPicks
    • AI-PGF
    • Agentoor
Powered by GitBook
On this page
  • Access the Pot Factory:
  • Understand What a Pot Is:
  • Initiate Deployment
  • Roles in Deployment
  • Set Parameters
  • Human Verification:
  • Funding Process:
  • Payouts
  • Final Steps:
  • Ongoing Management

Was this helpful?

Edit on GitHub
  1. User Guides
  2. Pot Owners & Chef Training (Pot)

Deploy Pot

Deploying a pot involves several steps within the POTLOCK ecosystem, which facilitates quadratic funding rounds.

Previous๐Ÿ‘จโ€๐ŸณChefNextPlanning A Pot

Last updated 4 months ago

Was this helpful?

Access the Pot Factory:

Navigate to the POTLOCK decentralized front end at and find the "Pots" tab. This is where you can deploy a pot.

Understand What a Pot Is:

A pot is essentially a quadratic funding contract that allows for funding rounds to be deployed from the factory contract. It enables permissionless deployment of other contracts.

Initiate Deployment

Click on "Deploy Pot." The owner (the person logged in) pays 4.4 NEAR to create an independent pot contract. Itโ€™s advisable for the owner to negotiate with sponsors beforehand to secure funding commitments.

Roles in Deployment

The owner appoints a chef, who is the subject matter expert responsible for reviewing applications and initiating payouts. An admin can perform all functions of an owner except adding or removing other admins.

Set Parameters

During deployment, the owner can set various parameters, including:

  • Application start and end dates

  • Matching round start and end dates

  • Minimum and maximum donation amounts

  • Fees associated with donations and sponsorships

  • Note that certain parameters, like the pot's name and description, cannot be changed after deployment.

Human Verification:

To prevent Sybil attacks (where individuals create multiple accounts to manipulate funding), human verification is required through nada.bot. This ensures that only verified individuals can donate.

Funding Process:

Donations made during the matching round are logged in the pot contract but are passed directly to approved projects. The actual money in the pot is used for payouts at the end of the matching round.

Payouts

After the matching round concludes, there is a cooldown period during which calculations for payouts are made off-chain to ensure accuracy. Stakeholders can challenge any discrepancies during this time.

Final Steps:

Once all challenges are resolved, payouts can be initiated, distributing funds to eligible projects based on their matched donations.

Ongoing Management

After deployment, itโ€™s crucial for the chef to manage marketing efforts and ensure timely onboarding of projects and donors.

๐Ÿ‘จโ€๐Ÿณ
๐Ÿ‘จโ€๐Ÿ’ป
nada.bot
https://alpha.potlock.org
Deploy Pot