PGov - Delegate Proposal
- PGovOP 4
PGov - Delegate Proposal
A. Delegation Address: pgov.near
B. Forum Username: PGov
C. Twitter Username: PGovTeam
E. Target Voting Participation: 100%
F. History of Interactions with NEAR Protocol:- Team members work for Near Foundation and Proximity Labs for 2 years.
- $Near and $Aurora holders since 2022.
G. History of Governance Participation:
- Delegate for Uniswap, Compound, Optimism, Arbitrum, etc.
- Grants Council positions across various Defi protocols
- Governance Stewards for various DAOs
H. Top 3 Priorities:
- Growth: Our decisions are primarily focused on the growth of the protocol. This often results in how to spend money efficiently, but even more importantly and objecting for unreasonable spends and knowing when to vote no.
- Transparency: Clear communication with votes and explanations of reasoning, and an equivalent demand for proposals to do the same. Too often we see thousands, if not millions, being rolled up together and glossed over during proposals.
- Accountability: Too often once a decision is done, having proper accountability becomes an afterthought. Whether it’s a DAO promise or a grant or a new program, once a DAO votes something in, we forget about it. Our goal with PGov is to both continue to check in on these decisions as well as ensure that there are proper channels set up to ensure accountability.
I. Reasoning for past votes: N/A
J. Conflicts of Interest: We are delegates and involved in other DAOs in defi. If COI situations arise, we will abstain from a vote, and clearly state the conflict on the forums.K. Our Rationale for Hypothetical Delegate Scenario
- Additional Info: Parties proposing, size of allocation, duration of allocation, team’s past history and involvement, personal opinion on team and quality of output, legal ramifications, token value/accrual if applicable, etc.
- Key Metrics: Total request, ROI on invested tokens, costs per working group member, etc.
- Ultimately support: In favor if the cost justify the expected output, and if the team is strong. Not support if the team is weak or not trusted, and if the cost is ridiculously high.
L. What is your motivation for becoming a NEAR delegate?: Our team has been a Near holder for over three years now and members have worked directly for the Near Foundation and Proximity Labs.
M. Anticipated delegation support (if applicable): N/ASelf Assessment:
Summary
- Experience (2/2): DAO Governance for 4 years, Grants program across half a dozen ecosystems, Governance stewards for multiple DAOs
- Diversity of Perspective (1-2/2): Team has worked directly with Near foundation in the past.
- Alignment with NEAR Ecosystem (1-2/2): Team has been a Near Investor since 2021. Participated in Near hackathons and Nearcon since Lisbon 2022. Has been involved with Near Education through UPenn.
- Governance Engagement (2/2): Strong governance footprint across over a dozen DAOs in the Defi space.
- Conflicts of Interest (2/2): No direct conflicts of interest. Aligned in the overall propensity of Near given significant investments in $Near we well.
Code of Conduct: We have read and agree to the outlined code of conduct.
- satojandro 4
Thanks for your nomination.
Couple of questions;
- Is Pgov being nominated as an Institutional Delegate?
- Are there any links or resources where I can learn more about Pgov?
- Who are the humans behind Pgov (NF/Proximity?) that will be involved in the day to day decision making?
Thanks,
AVB
- PGov 2
Hello! Thanks for the questions,
- Not sure what you mean by an institutional delegate but as far as we know, no.
- pgovteam on twitter (can’t post links), happy to hop on a call if you DM as well!
- We have yet to decide full who will focus on this delegation for us, but we are independent from the NF/Proximity. Team members in the past have worked for and with these entities, but we are fully independent.
- DDeAlmeida 2
As i understand, you are a “Company” and not individual.
How many employee have you ?
How can you be involved in so many Governances, and still make relevant decision for the Near ecosystem ? - PGov 4
Yes, we are a small team of 5, focused part to full time on governance with extensive experience in the space.
- PGov
Establish House of Stake Operational Budget for July 2026 – June 2027
We voted For: The 196,000 USD and 60,000 NEAR operating budget is a reasonable ask for House of Stake to function as an independent governance institution covering governance operations, legal compliance, treasury management, and execution capabilities. We appreciate that this is a deliberately lean model that leans on existing NEAR Foundation infrastructure where appropriate and excludes personnel and product development costs, which keeps the tokenholder-authorized spend scoped to the core mandate rather than the full operating cost. Leaving any unused funds in the House of Stake treasury is the right default, and we are comfortable giving the Head of Governance and the House of Stake Foundation the operational capacity to execute over the next year.
- PGov 1
Establish House of Stake as Registrar for the NEAR Top-Level Account Namespace
We voted For: This places governance of NEAR’s top-level account namespace root under House of Stake on behalf of NEAR tokenholders and appoints the Security Council as Registrar, keeping the exceptional authority to create Top-Level Accounts separate from the commercial platform that operates on top of the namespace. As TLAs open up through nearaccounts.com and new namespace economies form beneath them, a durable and credibly neutral steward for the root is the right foundation, and locating that authority in tokenholder governance rather than a single operator is the more legitimate default. Users keep full control of the accounts they lease and the on-chain authorization of any created account stays outside the Registrar’s remit, so the scope of the authority being granted is appropriately bounded and we are comfortable supporting it.