What's new
  • Due to abuse, self-registration is disabled.

    Registration is only required for posting topics or replies. To register, make a request on any of the PIVX social media or chat channels.

    NOTE: To enhance forum security, new accounts that have no posts within a 30-day period are subject to being deleted.

Active PIVX-DAOWATCH - GOVERNANCE INTELLIGENCE & FULL MEDIA STACK

Cryptosi

Active Pivian
Code:
Title: PIVX-DAOWatch - Governance Intelligence & Full Media Stack
Name: pivx-daowatch
Term: 3 Cycles (renewal only by fresh community vote, never automatic)
Cycle Amnt: 20000
Total Amnt: 60000
Author: cryptosi
Receiver: cryptosi
Address: D9sth7Bhe3QAuUq36T9VfonaKcoc2nrktX
Created: 2026-10-22
Status: Live
Vote Hash: 139ed6d3077704b7c80e420d417d38f2398deca780722862ea650cfcaa64cfb8

ABSTRACT

This document outlines the funding and responsibilities for myself (cryptosi) as the operator of PIVX-DAOWatch: a live governance
intelligence dashboard and a full media stack covering PIVX governance - the weekly PIVX Weekly show, written governance recaps
on this forum, specials, tutorials, a monthly governance call, and the PIVX Fork Federation initiative. The operation has been running
for weeks without asking the DAO for anything; this proposal funds its continuation and expansion. One operator, one full governance
media stack, one vote.


RESPONSIBILITIES
As the operator of PIVX-DAOWatch, my responsibilities under this proposal include the following:
- Monitor all five PIVX governance feeds daily and maintain the live dashboard (https://pivx.daowatch.org), with honest status labels when anything is down
- Produce and publish PIVX Weekly - 4 episodes per cycle, new episode every Friday (https://pivx.daowatch.org/videos)
- Write and post a weekly written governance recap on this forum
- Book, produce, and publish at least 1 special with guests per cycle, pushing for 2.
- Host 1 governance call per cycle and publish the minutes
- Produce 1 superblock recap video and 1 end-of-round voting graphic per cycle
- Produce 1 tutorial video per cycle
- Run the monthly 'Mooty' Awards ceremony
- Deliver the PIVX Fork Federation (definition below)
- Publish a public monthly transparency report: uptime, items published, videos shipped, progress towards longer term goals (fork federation)

Additionally, work already undertaken under this initiative - before asking for a single PIV - includes the following:

- Live governance dashboard tracking all 5 governance feeds, refreshed daily (https://pivx.daowatch.org)
- PIVX Weekly Ep 1 - From $0.02 to $10: the PIVX story
- PIVX Weekly Ep 2 - Price dropping, MN manager, governance next steps
- PIVX Weekly Ep 3 - Community Development and More


DELIVERABLES

Every deliverable below is a public artifact - something a voter can click, watch, or read. Counts are per cycle. At the end of each cycle,
the monthly transparency report lists every deliverable with a direct link, so checking this list takes one click.

1. PIVX Weekly episodes - 4 per cycle
One full episode every Wednesday: governance recap, ecosystem news, the honest segment. Published to the PIVX Weekly YouTube
channel and linked at pivx.daowatch.org/videos.

Verify: the videos page (new episode within each 7 days).

2. Specials with guests - 1 or 2 per cycle
Interview or discussion episodes featuring community members, devs, or proposal authors. Guests are human-verified humans.
Verify: the videos page, labeled "Special".

3. Governance call - 1 per cycle
A public voice call on the PIVX Discord, open to all, with the written minutes published on this forum within 48 hours.

Verify: minutes thread + call announcement.

4. Superblock recap video - 1 per cycle
What passed, what failed, who got funded, and what it means - published within 7 days of each superblock.

Verify: the videos page, labeled "Superblock Recap".

5. Tutorial video - 1 per cycle
From the tutorial roadmap below. First in series: how to vote on a proposal (debug console / mnbudgetvote).

Verify: the videos page, labeled "Tutorial".

6. Dashboard + Mooty Awards - continuous
Dashboard refreshed daily for the entire cycle, with honest status labels if anything breaks; monthly Mooty Awards ceremony

Verify: pivx.daowatch.org uptime + ceremony thread.

7. PIVX Fork Federation - to completion (definition below)
The finish line is four checkable artifacts: (a) federation charter published, (b) fork-project registry live on the
dashboard, (c) at least 3 founding fork communities signed on, (d) joint announcement. -- https://forum.pivx.org/threads/pivx-fork-federation-creating-the-pivx-codeisphere.3039/

Verify: each artifact is public and linked when shipped.

That is a minimum of 9 published media items per cycle, plus the transparency report - for 20,000 PIV.

Why These are important
- Voter apathy is quite high, we need to increase engagement and get more people and masternode owners voting
- Barrier to creating a proposal is high, we need to increase awareness and familiarity with our system in hopes of attracting new proposals and the progress that comes with new people working for PIVX
- Accountability keeps funded teams honest, when proposal owners know that there will be a recap and follow up on their proposals in a public forum they are more likely to be honest.
- Nobody else is doing this, PIVX labs are building tools, Core is building V6.0.0, Jeffrey is doing biz dev, nobody is focused on governance and codeisphere development
- A fork federation will allow us to monitor devs work on PIVX codebase or very similar forks and promote them to our CORE team in time, currently many of our core devs were fork devs previously
- A fork federation will champion the thesis that app chains should be fully sovereign, private and proof of stake, PIVX provides all 3 features and more forks means a bigger ecosystem for us to grow into
- A fork federation will allow us to negotiate better with exchanges for listings as we will be bringing more than one project, community and set of users each time they build to integrate PIVX and her forks

Funding


The funding I am asking for to cover the continued duties and responsibilities listed above is 20,000 PIV per cycle. The above lists are extensive in nature, but not exhaustive, and minor or nuanced tasks may not be listed. DevOps covers a rather broad range of tasks that, if done well, should really not be noticeable from an outside perspective.

Roadmap
In the future I want to complete the following:
- Move PIVX weekly and the specials to a professional studio, with professional lighting, sound and editing
- Build out the daocouncil application as a further way to gather engagement and help educate on current proposals https://github.com/Crypto-SI/daocouncil
- Multi language editions , French, spanish, swahili, mandarin, yoruba, and other languages
- Audio podcast versions, posted directly to spotify and other audio venues
- proposal owner spotlight, interviews with serial proposal owners
- Proposal clinic, 1/2 hours per week for people with pre-proposal to join me and help flesh out their idea and produce awesome proposals


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 139ed6d3077704b7c80e420d417d38f2398deca780722862ea650cfcaa64cfb8 many yes

To vote no:
mnbudgetvote 139ed6d3077704b7c80e420d417d38f2398deca780722862ea650cfcaa64cfb8 many no
 
Last edited:
I have decided to vote NO for the proposals listed below. They are valuable proposals, but we decided as a Community to focus only on what helps get v6.0 released. Anything else in my mind, should be spent on Market Making Proposals, because we are at risk of being delisted on MEXC if we don't. All other proposals should be 'paused' IMHO.

PIVX is 'infected' with 'Suicidal Empathy' from the woke culture. Everyone cuts back their proposal funds request, trying to leave room for everyone else. All that does is cause everyone - and by extension PIVX - to die slowly.

In a healthy Governance system, there are many competing proposals and even good ones fail to get funded - because there are better and/or more important ones that need priority. In other words, mediocre ones should fail to get funded. Only necessary/exceptional ones should be funded.

Not everyone is going to agree with me, and frankly, unless multiple other MNOs agree with me and change their votes, mine will have no effect.

Hopefully the MNOs will do their due diligence, speak with Jeffrey, review the related issues with CoinPayments, CardsRelay, and NOWPayments in Telegram, and come to the same conclusion I did. If the other MNOs stay silent, everyone will think it was all me - and everyone gets upset with me. But, I would rather that then have PIVX get delisted by MEXC.

Hang in there everyone - it's going to be a bumpy ride.

PIVXAmbOct26
PIVXSpaOct26
PIVXAfricaOct26
PIVX-DAOWatch
BusinessDev15
MrAliMMFund01
 
As it stands now, there is 151,000 Unclaimed PIV in the governance pool. So we are not nearly close to having to cut proposals to make way for other proposals, and to say that ONLY market making is going to be funded is a view that I respect but of course will disagree with.

I'm assuming also you are cutting WAMS too? or is there a reason why this one is being counted as DEV or Market making? when it certainly is neither?
Trying to appease a single 2nd tier exchange surely should not come at the cost of EVERYTHING else, if indeed it does then perhaps we should spend the time finding another 2nd tier exchange, or being creative with our solutions?

But I'm defintely NOT going to be drawn into a 'THIS VS THAT' debate on ANY of the proposals, If I want something to win, I will vote based on the merit of that particular proposal, IF the pool becomes fully saturated, ONLY then will I change votes within winning proposals and my own criteria is as follows in order of importance :
1 - Dev
2 - Community onboarding (including Devs)
3 - Biz dev (including exchange integrations)
4 - 3rd party development
5 - marketing (social media and content)
6 - Customer support
7 - Alliances, Fork foundation and any other documentation based onboarded plans
8 - Anything that fool CryptoSI is involved with.
9 - Market making ;)

PS - In seriousness, I'd put market making around 5th, but perhaps after more discussions with our emporer Jeffrey perhaps our understandings can be improved, both in favour or against prioritising MM over everything but dev.
 
Ya. In my mind, it should be this order:

1. Core Development
2. Business Development
3. Marketing
4. Market Making Fund.
5. Everything else if there is room.

But, 1 thru 3 should be fair for their effort, and 4 should max out until we hit a safe target. THEN we can consider other proposals.

Instead, everyone has been allowed to be a higher priority than Market Making, and here we are. MASSIVE liquidity problems.

My position is 'short term pain for long term gain'.

It is my understanding that Mr. Ali let it be known that he would vote down a Market Maker proposal from Jeffrey. So, someone else is going to submit it. Better be soon!

I would like to see the Market Maker proposal at 151,000 PIV (Currently available) + 60,000 (3 Ambassador proposals & DAO Watch)

To be clear - I think the Ambassador and DAO Watch proposals are solid proposals from really good people - but I feel we are at a critical point, and ANYTHING that can be paused, should be. Every remaining PIV should go to Market Maker liquidity. We all know what effect the Binance de-listing had. What is the plan when we get de-listed from other exchanges, and the price drops to $0.01? We won't even be able to fund Development then. It will be a ghost town here.

As a team, we've always allowed Market Making to get the 'table scraps'. THAT is the WRONG approach. It is 'Self-Destructive Empathy'. (Hope that doesn't trigger anyone - but 'A rose by any other name would smell as sweet' - so good luck with that.)

No. I did not vote Wams down. He does incredible work, and has built an extremely efficient AI work flow he is ready to unleash. Looks like he will never get to use it for PIVX. Hope I am wrong about that. I did vote Jeffrey down - because he offered to 'take one for the team' and increase the amount that could go to Market Making. Otherwise, I would have voted YES for him. The Developers, Jeffrey and Wams are the most valuable members of the team. Their skill sets, loyalty, sacrifice, passion, dedication and trust, are extreme in my experience. But, a whale who can't read a UTXO block chain is refusing to admit mistakes, and is protecting his ego (at the expense of his reputation) instead of being focused on what is right for PIVX.

It is what it is .... the truth will come out. But, I'm guessing we need to take a bunch of steps backwards first.
 
To me this reads like, please lets appease the overlords at the exchanges, lets call it 'self destructive cowardice'. The reason why PIVX even exists is because Baby Giraffe of Dash convinced the dashkuza that appeasing the overlords in trad-fi was the correct route, they then had a ten year development desert, which they have only really recovered from in the past 12 or so months. Eric I really think you need to find the manifesto! NOWHERE in there does it say anything about prioritising liquidity, or exchanges at the cost of community, frontier economies, future development, or anything else, infact, liquidity, exchanges and the likes were not in there, because we CANNOT jump through their hoops, They will ALWAYS attack our project because the privacy and it's delivery are best in class.

Remember Almost ALL the devs have come through our forks, yet we have no active or deliberate interaction with our current forks, IF we had not built these bridges to them in the past we would have 0 devs now (excluding fuzz - who is from another world entirely,absilute LEGEND)
Voting For DAO watch is not EMPATHY, that does not trigger me because I live here in Africa now and dog whistle words like 'woke' are a distant memory of consistent micro aggressions that only exist in the same western world that you are fleeing from, interestingly you are fleeing here, but whatever.

Please remember that the mission we are on will never get the blessing of exchanges, and even if it does, they will have to leave us when they want to collect their 'institutional paycheck', otherwise the next thing you will be asking us to drop will be privacy, but by that time you will be talking solely to yourself.

Our volume on Bittrex was higher than Polo for MONTHS and they never even considered listing us! Yet you want exchanges to come and save our clearly unkillable project.

READ THE MANIFESTO THAT YOU HELPED TO RATIFY.

READ IT DAILY

PIVX IS the truth, bending over for exchanges is the compromise.

PIVX cannot compromise, if you came here to see your dollar value grow, please remember dollar growth has ONLY ever been a BI-product of a strong, committed and unwavering project.

I am not turkish, I am not crazy, I am not woke, I am not triggered, I have been here just as long as you, I have seen first hand the tricks that the industry has pulled to keep this project down, I STILL do not feel that surrender is the correct option.

please be brave! bring back the old stubborn, focused eric. This new snowflake bending over to the whims of tier 2 exchanges is not fit to lace 2017 Eric's boots.

Thank you for your attention on this matter

(MPGA)
 
Top