# Contracts Overview ## All Contracts To ensure that all projects are coming from the official POTLOCK team they are deployed as [**subaccounts**](https://docs.near.org/tutorials/crosswords/basics/add-functions-call#create-a-subaccount) under the POTLOCK.near namespace. Testnet and Mainnet follow the same naming conventions to avoid any confusion. There are 7 main contracts, (technically [Pot](https://docs.potlock.io/contracts/pot-live) has many contracts as many Pots are deployed under the PotFactory) ## Contract Addresses ### [Donate](https://docs.potlock.io/contracts/donation-live) (for a direct donation to any account with referrer fees, optional donations and fungible token support) Source Code: Mainnet: [donate.potlock.near](https://nearblocks.io/address/donate.potlock.near) Testnet: [donate.potlock.testnet](https://testnet.nearblocks.io/address/donate.potlock.testnet) ### **Lists** Contract Source code: Mainnet: [lists.potlock.near](https://nearblocks.io/address/lists.potlock.near) Staging: [lists.staging.potlock.near](https://nearblocks.io/address/lists.staging.potlock.near) Testnet: [lists.potlock.testnet](https://testnet.nearblocks.io/address/lists.potlock.testnet) ### [**Registry**](https://docs.potlock.io/contracts/registry-deprecated) **\[depricated]\(for accounts to add themselves and for owner + admins controlled by the owner to change the status of projects on the registry. Used to display projects and also enforced on Pots for application requirements)** Source code: Mainnet: [registry.potlock.near](https://nearblocks.io/address/registry.potlock.near) Testnet: [registry.potlock.testnet](https://testnet.nearblocks.io/address/registry.potlock.testnet) ### [**Sybil**](https://docs.potlock.io/contracts/sybil-contract-nadabot) **aka nadabot (for people to submit sybil verification stamps from different contracts, users to verify stamps to increase the score to meet the human threshold, and owner + owner controlled admins, to approve & flag stamps, set weights, and set human thresholds, used as a sybil contract aggregator and managed contract enforced human checker)** Source Code Mainnet: [v1.nadabot.near](https://nearblocks.io/address/v1.nadabot.near) Staging: [v1.staging.nadabot.near](https://nearblocks.io/address/v1.staging.nadabot.near) Testnet: [v1.nadabot.testnet](https://testnet.nearblocks.io/address/v1.nadabot.testnet) ### [**Pot Factory**](https://docs.potlock.io/contracts/potfactory-live) **(deploys quadratic funding rounds (pots), and sets fees)** Source code: Staging: Testnet: [potfactory.potlock.testnet](https://testnet.nearblocks.io/address/potfactory.potlock.testnet) ### [**Pot**](https://docs.potlock.io/contracts/pot-live) **(quadratic funding round deployed by factory contract as a subaccount by anyone that specifies application dates, matching requirements, fees, a chef that can be changed by the owner, where QF payouts are calculated off-chain, initiated on the chain with a cooldown veto period, application & donation requirement according to registry and Sybil contract interfaces and allows anyone to sponsor for matching rounds, and donations to be passed through for optional fees and to keep track of matching payouts)** Source Code [**https://github.com/PotLock/core/tree/main/contracts/pot**](https://github.com/PotLock/core/tree/main/contracts/pot) Mainnet (whatever you deploy form pot contracts above) ### **Campaigns** Source Code: Testnet: [campaignstest2.potlock.testnet](https://testnet.nearblocks.io/address/campaignstest2.potlock.testnet) Testnet: [v1.campaigns.potlock.testnet](https://testnet.nearblocks.io/address/v1.campaigns.potlock.testnet) Mainnet: [v1.campaigns.potlock.near](https://nearblocks.io/address/v1.campaigns.potlock.near) Staging: [v1.campaigns.staging.potlock.near](https://nearblocks.io/address/v1.campaigns.staging.potlock.near) ### Voting Source Code: Testnet: Mainnet: [mpdao.vote.potlock.near](https://nearblocks.io/address/mpdao.vote.potlock.near) Staging: [mpdao.vote.staging.potlock.near](https://nearblocks.io/address/mpdao.vote.staging.potlock.near) ### **Grantpicks** Source Code: Testnet: [v2.grantpicks.potlock.near](https://nearblocks.io/address/v2.grantpicks.potlock.near) {% content-ref url="potfactory-live" %} [potfactory-live](https://docs.potlock.io/contracts/potfactory-live) {% endcontent-ref %} {% content-ref url="pot-live" %} [pot-live](https://docs.potlock.io/contracts/pot-live) {% endcontent-ref %} {% content-ref url="donation-live" %} [donation-live](https://docs.potlock.io/contracts/donation-live) {% endcontent-ref %} {% content-ref url="attestations-wip" %} [attestations-wip](https://docs.potlock.io/contracts/attestations-wip) {% endcontent-ref %} {% content-ref url="sybil-contract-nadabot" %} [sybil-contract-nadabot](https://docs.potlock.io/contracts/sybil-contract-nadabot) {% endcontent-ref %} {% content-ref url="lists-live" %} [lists-live](https://docs.potlock.io/contracts/lists-live) {% endcontent-ref %} {% content-ref url="registry-deprecated" %} [registry-deprecated](https://docs.potlock.io/contracts/registry-deprecated) {% endcontent-ref %} {% hint style="info" %} Do you have any suggestions for our contracts? Make an[ issue request](https://github.com/PotLock/core/issues/new) on Github today {% endhint %} ### Mainnet ([potlock.near](https://nearblocks.io/address/potlock.near)) ### Testnet ([potlock.testnet](https://testnet.nearblocks.io/address/potlock.testnet)) ### Campaigns Mainnet Staging [v1.campaigns.staging.potlock.near](https://nearblocks.io/address/v1.campaigns.staging.potlock.near) 🔗 Campaigns Contract 💻 --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.potlock.io/contracts/contracts-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.