|
1 | | -# Eligibility criteria |
2 | | - |
3 | | -**To respond to an open tender, please ensure the following:** |
4 | | - |
5 | | -* Applicants must meet all of the requirements stated within the proposal. |
6 | | -* The proposed work cannot also be funded by another source, for example through Catalyst. |
7 | | -* Only one entry per member is allowed in each category. |
8 | | -* The proposal must be submitted before the due date and time, with all of the required information provided. Unfortunately, late submissions cannot be accepted. |
9 | | -* Winners must provide the information requested for, and pass Intersect’s due diligence process to receive funding. |
10 | | -* Winners must be a member of Intersect to be awarded the tender and receive payment through Intersect as the administrator. |
11 | | -* Winners must be able to accept deliverable-based payment terms. |
12 | | -* Winners must consent to their project information and outputs being published on Intersect channels such as intersectmbo.org, Discord, Twitter and LinkedIn. |
| 1 | +# Minimum Administration Requirements |
| 2 | + |
| 3 | +Intersect continues to act as an administrator, overseeing the delivery of projects which have successfully received treasury funding via community-ratified on-chain governance actions. |
| 4 | + |
| 5 | +This page clarifies what information is required for Intersect to be able to act as your Administrator, why this information is important, and Intersect’s position should it not be provided.  |
| 6 | + |
| 7 | +#### Proposal Submission Route |
| 8 | + |
| 9 | +While the annual Budget Cycle represents a key pathway through which proposals are typically submitted for treasury consideration, proposals may be presented and approved through governance processes at any time. Regardless of when a proposal is submitted or approved, the same administrative requirements apply for Intersect to act as Administrator. |
| 10 | + |
| 11 | +During the governance voting process, DReps ultimately approve proposals as they are presented on-chain. This approval represents support for the idea, intent, and expected outcomes of the proposal, based on the information available at the time of voting. |
| 12 | + |
| 13 | +However, the information included in an on-chain proposal may not always contain all of the details required to establish a formal legal contract between Intersect and the vendor responsible for delivering the work. In such cases, additional information will be requested by Intersect following approval to enable proper contracting and project administration. |
| 14 | + |
| 15 | +This supplementary information is intended to clarify implementation and delivery details and is not expected to change the approved scope or outcomes of the proposal. |
| 16 | + |
| 17 | +Where the required administrative or contracting information is not provided, Intersect may be unable to execute a legal agreement or administer the project, and therefore treasury funds cannot be released until these requirements are satisfied. |
| 18 | + |
| 19 | +#### Administration Minimum Requirements |
| 20 | + |
| 21 | +As an administrator we have a minimum set of information required to oversee the delivery of a proposal and to sign written legal contracts which contain the needed constitutional dispute resolution clauses and other safeguards. |
| 22 | + |
| 23 | +The following information will be requested and collected as a minimum. |
| 24 | + |
| 25 | +**Legal Entity and Contracting Details** |
| 26 | + |
| 27 | +* Contracting Party Details |
| 28 | +* Legal Entity Name (Company / Individual details if sole trader) |
| 29 | +* Registration Number (Company) |
| 30 | +* Country of Incorporation (Company) |
| 31 | +* Registered Address (Company) |
| 32 | +* Country of Residence (Individual) |
| 33 | +* Government Issued ID Number (Individual) |
| 34 | +* Full Residential Address (Individual) |
| 35 | +* Primary Contact Full Name |
| 36 | +* Primary Contact Email |
| 37 | +* Signatory Name |
| 38 | +* Signatory Title |
| 39 | +* Signatory Email |
| 40 | +* Signatory Authorization |
| 41 | +* KYC/KYB Submitted |
| 42 | +* KYC Contact Email (if required) |
| 43 | + |
| 44 | +**Proposal and Project Information** |
| 45 | + |
| 46 | +* Proposal Title / Project Name |
| 47 | +* Executive Summary / Project Description |
| 48 | +* Timeline (Project Start & End Date) |
| 49 | +* Scope of Work |
| 50 | +* Estimated Effort / Duration |
| 51 | +* Intersect Administrator |
| 52 | +* Other Administrators |
| 53 | +* Third Party Assurers |
| 54 | + |
| 55 | +**Milestones and Delivery Information** |
| 56 | + |
| 57 | +Milestones should include: |
| 58 | + |
| 59 | +* Number |
| 60 | +* Name |
| 61 | +* Description |
| 62 | +* Acceptance Criteria / Definition of Done |
| 63 | +* Date / Duration |
| 64 | +* Value (proportion of the total proposal) |
| 65 | +* Deliverables |
| 66 | + |
| 67 | +Milestones are important so that treasury funds can be protected and released only when tangible progress has been achieved. Without milestones, an administrator's only option would be to release all funds at the beginning or the end of a project, which lacks transparency to the community on the progress of the project. Acceptance Criteria or Definition of Done is key, as this manages both the vendor’s and the ecosystem’s expectation of what they will receive for the value attributed to the milestone. |
| 68 | + |
| 69 | +#### Why This Information Is Important |
| 70 | + |
| 71 | +To sign legal contracts with vendors, Intersect must obtain information on who the legal entity is that will receive treasury funds. Without knowing this information up front, DReps may not ultimately know who the beneficiary of treasury funds is until after the fact. |
| 72 | + |
| 73 | +Vendors should provide easily identifiable project names so that they can be easily followed and identified by the community. Simple descriptions (written in English) should also be provided so DReps understand what the project intends to do. Projects should provide an overarching tangible, where practical and possible, deterministic outcome so that DReps understand what will be provided upon completion of the project. |
| 74 | + |
| 75 | +It is the Vendor’s responsibility to provide information on their contracts clearly, so that the community is able to understand what the Vendor is planning to deliver and can verify this. This is also required for Intersect to draft a high-quality legal contract. |
| 76 | + |
| 77 | +#### What Happens if Information Is Not Provided |
| 78 | + |
| 79 | +Should any of the information above not be provided during on-chain governance, Intersect will take this as a signal from DReps that the proposal has been approved, even if the information is omitted. |
| 80 | + |
| 81 | +Intersect will request missing information during contract creation after on-chain governance actions have taken place. However, without the required minimum information, Intersect may not be able to draft or administer the contract. Should Intersect determine that it cannot administer a proposal due to insufficient information, this position will be made clear prior to final on-chain voting. |
| 82 | + |
| 83 | +#### Intersect’s Rights as an Administrator  |
| 84 | + |
| 85 | +Intersect’s role as an administrator includes overseeing delivery and ensuring treasury-funded projects are executed in line with agreed contractual obligations. If you are planning to submit a proposal, please be aware that Intersect reserves the right to decline acting as the administrator for any new proposal submitted. |
| 86 | + |
| 87 | +For example, where there is a demonstrable history of non-delivery or contractual non-performance, Intersect may determine, at its reasonable discretion, that it is unable to provide administration services for subsequent proposals. |
| 88 | + |
| 89 | +Where such conditions exist, Intersect may, in its reasonable discretion, determine that it cannot responsibly administer future proposals submitted by the same vendor. This position is intended to ensure responsible stewardship of treasury funds and maintain delivery confidence across the ecosystem. |
0 commit comments