Minimum Contract Requirements
Version: 1.0
Updated On: 27/02/2026
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.
This blog 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.
Proposal Submission Route
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.
During the voting process, the DReps will ultimately sign off the proposals as they are presented on-chain. This may not include all the pertinent information required to form a legal contract, but the DReps are providing their approval on the proposal as an idea or project. In some instances, specific details may not be required to obtain sufficient approval from DReps, but will be required to form part of the legal contract. This supplementary information will not change the outcome or output of the proposal but will clarify in greater detail how the proposal will be delivered and when.
Administration Minimum Requirements
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.
The following information will be requested and collected as a minimum.
Legal Entity and Contracting Details
Contracting Party Details
Legal Entity Name (Company / Individual details if sole trader)
Registration Number (Company)
Country of Incorporation (Company)
Registered Address (Company)
Country of Residence (Individual)
Government Issued ID Number (Individual)
Full Residential Address (Individual)
Primary Contact Full Name
Primary Contact Email
Signatory Name
Signatory Title
Signatory Email
Signatory Authorization
KYC/KYB Submitted
KYC Contact Email (if required)
Proposal and Project Information
Proposal Title / Project Name
Executive Summary / Project Description
Timeline (Project Start & End Date)
Scope of Work
Estimated Effort / Duration
Intersect Administrator
Other Administrators
Third Party Assurers
Milestones and Delivery Information
Milestones should include:
Number
Name
Description
Acceptance Criteria / Definition of Done
Date / Duration
Value (proportion of the total proposal)
Deliverables
Milestones are important so that treasury funds can be protected and released only when tangible progress has been achieved. Without milestones, as an administrator, the 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.
Why This Information Is Important
In order 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.
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.
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.
What Happens if Information Is Not Provided
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.
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.
Intersect’s Rights as an Administrator
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.
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.
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.
More About Intersect Administrative Services
Last updated