Cryptosi
Active Pivian
Code:
Title: PIVX Alliances
Name: pivx-alliances
Term: 1 Cycle (single installment - support commitment runs 12 months)
Cycle Amnt: 10000
Total Amnt: 10000
Author: cryptosi
Receiver: cryptosi
Address: D9sth7Bhe3QAuUq36T9VfonaKcoc2nrktX
Created: 2026-11-15
Status: Live
Vote Hash: a159a70b6b7f123bbdc1c4169ef26c10e3df8e56154deddf17e97ad65e9676f6ABSTRACT
This Proposal outlines the funding and responsibilities for myself (cryptosi) as the operator of PIVX Alliances V2.0: the revived PIVX Alliance Protocol - a public registry of decentralised, uncensored, ratified alliances, a hardened vetting framework, and 12 months of alliance intake and stewardship. In January 2018, a fake "official partnership" announcement went viral; the partner's founder went to federal prison; the Alliance Protocol was drafted ten days later so it could never happen again - then over time it became unmaintained. The registry is built and live today. The protocol documents are published. The intake path is open. This proposal funds twelve months of operation with a single installment. One protocol, one registry, one vote - and PIVX is open for business.
RESPONSIBILITIES
As the operator of PIVX Alliances, my responsibilities under this proposal include the following:
- Maintain the Alliance Registry (https://pivx-alliance-registry.vercel.app) proper domain to follow -- as the single public source of truth for the full 12 months: every ratified alliance with scope, envoys, start date, expiry, and status - plus full history, so nothing quietly disappears
- Operate alliance intake under Protocol v2: every application acknowledged within 7 days, vetting sheet reviewed, envoy coordinated, each alliance's forum thread stewarded. Community members will be encouraged to put forward their own alliance proposals also.
- Maintain the Alliance Protocol v2 document and the downloadable alliance proposal template (the 2018 Allnodes vetting template, revived)
- Operate the review/disavowal banner path: any registry record can flip to "under review" or "disavowed" within 48 hours of a steward decision - no governance-cycle wait
- Publish 4 quarterly public reports: registry status, alliances processed, incidents, disavowals
- Deliver the month-12 handover: full JSON data dump, MIT-licensed repo, and a renewal-or-wind-down proposal - the community's choice
Additionally, work already undertaken under this initiative - before asking for a single PIV - includes the following:
- The Alliance Registry, built and live at https://pivx-alliance-registry.vercel.app: the register, the protocol page, the submission path, and a working disavowal-mechanism demo --
- The founding artifacts recovered and filed: the Alliance Protocol draft (5 February 2018, ten days after the AriseBank ICO halt), the Alliances LitePaper (immutable copy), and the 2018 Allnodes vetting template - the protocol's first filled example
- The pre-proposal thread, live and taking community input: PIVX is OPEN for Business - PIVX Alliances V2.0 - four governance questions posed and still open
DELIVERABLES
Every deliverable below is a public artifact - something a voter can click or check. Counts cover the 12-month term funded by this single installment.
1. Alliance Registry website - live now, (Domain pending) maintained for 12 months
The public register of PIVX alliances: visible, dated, revocable. A record per ratified alliance, full history of expiries and renewals, and a disavowal banner that can go up in hours - the exact machinery January 2018 lacked.
Verify: https://pivx-alliance-registry.vercel.app
2. Alliance Protocol v2 + downloadable vetting template - published, maintained
The 2018 protocol, hardened by eight years of hindsight: mandatory vetting sheet (legal name, jurisdiction, entity registration, litigation history), 12-month hard expiry, renewal only by fresh vote, an alliance is a cooperation instrument, never an endorsement, investment, custody arrangement, or promise of returns.
Verify: the protocol page on the registry.
3. Alliance intake and support - continuous, 12 months
Processing of incoming alliance applications under Protocol v2: acknowledgment within 7 days, vetting review, envoy coordination, and forum stewardship of every alliance thread.
Verify: reply timestamps in the alliance threads on this forum.
4. Review / disavowal banners - standing mechanism
Any registry record can carry an "under review" or "disavowed" banner within 48 hours of a steward decision, with date, rationale, and evidence link. No waiting on a governance cycle.
Verify: the demo record on the registry shows the mechanism working today.
5. Quarterly reports - 4 (months 3, 6, 9, 12)
Public posts on this forum: registry status, alliances processed, incidents, disavowals.
Verify: this forum, quarterly.
6. Open-source and handover - month 12
The registry repo is MIT-licensed and registry data exports as JSON. At month 12: full data dump published, repo handed over, and a renewal proposal or wind-down filed - decided by the community, not by me.
Verify: the repo + the pinned month-12 data dump.
That is one public institution - registry, protocol, intake, disavowal path, four reports, twelve months of stewardship - for a single 10,000 PIV installment. Partners receive no treasury funds, ever: every alliance files its own proposal and takes its own vote, so the per-alliance cost of this framework is zero.
Success criteria - checkable at month 12:
- Registry live for the full term and cited in every alliance thread
- 3+ alliances processed through Protocol v2
- Zero unregistered entities publicly claiming PIVX partnership without a thread pointing the other way
Why These are important
- In January 2018 a scam announced an "official partnership" with PIVX and it went viral; its founder went to federal prison; PIVX had no way to say "official" or "never was" - the Alliance Protocol was drafted ten days later to make sure it could never happen again
- The disavowal banner gives PIVX a 48-hour response path to fake-partnership claims, instead of a governance-cycle wait
- Nobody else is doing it: no core workstream or lab team covers partnership verification and alliance record-keeping
- Clonable by design: the LitePaper's original vision was an industry standard other DAOs could adopt - MIT license and JSON export make that a forkable protocol.
Funding
The funding I am asking for to cover the duties and responsibilities listed above is 10,000 PIV, paid as a single installment. The above lists are extensive in nature, but not exhaustive, and minor or nuanced tasks may not be listed. Stewardship covers a rather broad range of tasks that, if done well, should really not be noticeable from an outside perspective. In practical terms the installment covers: domain and hosting for 12 months; the registry build (already shipped); Protocol v2 documentation and the downloadable template; 12 months of intake, vetting reviews, forum stewardship, and quarterly reporting; and the month-12 handover. The 50 PIV on-chain submission collateral is self-funded by the author and explicitly not claimed back. Partners receive no treasury funds from this proposal; any partner seeking funding files its own separate proposal.
Roadmap
In the future I want to complete the following - each scoped, costed, and voted separately, never silently absorbed:
- Process the founding-cohort candidates through Protocol v2 - each files its own alliance proposal and stands for its own vote
- On-chain anchoring of registry records: a hash per ratified alliance committed to the chain itself - scoped, costed, and voted separately
- A registry API so wallets and explorers can badge official alliances automatically
- Multilingual alliance intake - the 2018 rule kept: an English translation must exist at the time of voting
- A non-mandatory state-of-the-alliances address at the monthly governance call
- Independent steward audits of disavowal decisions with reports.
- The PACK concept from the original 2018 protocol draft (partnership kits) - only if the community wants it
- Template localization so other DAOs can clone the framework whole
Impact on existing proposals
Financially none: a single 10,000 PIV installment - roughly 2.3% of one monthly budget cycle, once - touching no funded proposal's budget or scope. This proposal compliments BizDev, allowing us to enter into officially recognised alliances with established legal entities or other decentralised entities. It also complements PIVX-DAOWatch (governance media) with alliance record-keeping: different mandate, zero deliverable overlap. If the community later prefers a different steward or maintenance model, the month-12 handover makes that transition a signature, not a rebuild.
Voting
Qt GUI wallet users can use the built in DAO page to cast their votes. For console users, use one of the below commands.
To vote yes:
mnbudgetvote a159a70b6b7f123bbdc1c4169ef26c10e3df8e56154deddf17e97ad65e9676f6 many yes
To vote no:
mnbudgetvote a159a70b6b7f123bbdc1c4169ef26c10e3df8e56154deddf17e97ad65e9676f6 many no
Last edited: