PIRs are mainly focus on integrations and would regroup several topics
such as :
Partnerships (initially included in PGP)
Front end hosting/Integration request (initially included in PPP)
Whitelist of DAO/Contracts to lock hPAL (New)
Support of a new asset on Paladin Lending (New)
Support of a new veToken on Warden (New)
Whitelist a new token as reward on Quest (New)
Additional informations required for a PIR:
Project Presentation: (After summary)
Protocol name, app link and TVL
Asset TVL (If new asset on Paladin or Warden)
Docs & audit(s) links
Twitter/Discord/Telegram/Lens links and community sizes
Considering that integrations proposals could happen a lot in the future, and that the risk for the protocol is lower than other proposal types, we could consider the following parameters:
Reminder of the required information for any proposal type
Governance forum post: Each proposal should be posted on the forum for at least 48h which allows the community to give feedback, propose changes, and vote on a sentiment poll. Forum topics also need to reach some consensus before posting on snapshot.
Proposal type, number and name: Each proposal must be easily identifiable and classified :
Type: This will be detailed in the second part of the proposal
Name: The name must be the same on the forum post and snapshot (Max 10 words)
Number: Each topic needs a n° to identify the post order on the forum & on snapshot
Summary: Short description of the proposal (1-2 sentences max) Rationale: Detailed explanation of the proposal Means: Resources needed for this proposal (if any)
Human resources: Special skills required (Dev or others)
Treasury resources: Proposal cost, % of the treasury required
Voting options: List the options available on the snapshot vote, including an “Abstain” one.