Menu
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.

Roadmaps, Core Updates, and Building Market Momentum

MrAli

MrAli

Pivian
Hello PIVX Community, Developers, and Masternode Operators,

Based on our modest experience in trading and market observation, a significant portion of crypto traders, retail investors, and outside capital make positioning and investment decisions based on visible milestones, active catalysts, and transparent roadmaps.

The Current Visibility Gap
Right now, there is an apparent communication gap between behind-the-scenes developer activity and what the broader market perceives:
  • Active Code vs. Market Perception: Pull requests are actively being reviewed and merged on GitHub, which clearly shows ongoing development. However, the average trader or investor does not read code diffs or commit logs.
  • The Roadmap Page: Our official roadmap (https://pivx.org/roadmap) currently displays generic stages (Planning, Development, Testing, Completed) without estimated target windows (ETAs) or quarters.
  • Core Release Perception: Because the Core hasn’t had a major release since 2024, outside observers can easily misinterpret this as development being stalled or dormant.


Understanding the Developer Reality
In a recent discussion in Discord, some very fair and realistic points were raised:
  1. Pioneering Technology: PIVX is building cutting-edge privacy and Proof-of-Stake tech. Technical unknowns and unexpected hurdles are inevitable, making rigid, day-to-day hard deadlines unrealistic.
  2. Developer Sustainability ("People need to eat"): Given current market conditions, developers naturally face livelihood constraints and may need to balance their time with external commitments.

The Win-Win Cycle
This is precisely why closing this visibility gap benefits everyone—especially the developers:
  • When the market has clear milestones to rally around, volume, market interest, and liquidity follow.
  • A stronger market directly bolsters our DAO treasury and proposal values, enabling sustainable, proper funding for developers to build full-time with peace of mind.


Practical & Realistic Steps Forward
We are not asking for inflexible, day-to-day promises. Instead, we propose:
  1. Target Windows / Quarters: Introducing realistic milestone targets (e.g., Q3, Q4) or a simple board showing “What’s next in the pipeline.”
  2. Prioritizing Near-Term Releases: Identifying which PRs and features are closest to completion and can be packaged into an upcoming release.
  3. Periodic Dev Digests: Brief, plain-English monthly or bi-weekly summaries translating recent technical progress into user/investor benefits.

We warmly invite our core developers, masternode operators, and all community members to share their perspectives:
  • What are the current technical priorities?
  • Which milestones are closest to the finish line?
  • How can the community and masternodes best support the developers in moving these forward?

Looking forward to hearing everyone’s thoughts and working together to build positive momentum for PIVX!
 
I'm happy to do a bi-weekly or monthly video or audio podcast with the devs, we could/should rotate the devs that have to endure chatting with me.

I've got a decent if a little outdated understanding of the codebase and a good understanding of the industry in general and privacy tech in particular. I think 30 minutes is plenty for bi-weekly, if it's monthly (which i think is a bit wide) then it should be an hour.

I dont like this line --
Prioritizing Near-Term Releases: Identifying which PRs and features are closest to completion and can be packaged into an upcoming release.
We should not alter dev process for 'number go up' purposes, otherwise the immediate next logic would be 'remove privacy and get back on exchanges'. Technical debt is a real problem and the order in which things are integrated and completed absolutely does matter.

As I understood it, the problem with our community trying to help the devs is that reviewing code takes longer than writing code, so in the past when I was hunting for MORE devs, thinking that more devs = more code, I ran head-on into that barrier. That's why I'm keen to start a 'fork federation' where we can help PIVX forks grow, these forks may implement new features, expose us to new devs and act like how formula 1 acts for the car industry. AI coding is also soo going to become a factor here, regardless of what the devs say, so community could start to consider how/where we can integrate it into the fringes of development. Testing new governance models would be a decent place to start.

Community can also help by testing new releases thoroughly, and this role should not be understated. Developers cannot test their own software, because they are too smart. They will not be able to produce the edge cases that us mortals can produce consistently. Everyone who asks for when the next release is scheduled to arrive should be pushed to an organised testing group, they will then get a an incredibly accurate idea of how far we are from completion and they will see the setbacks happen in real time.

Is there a community member willing to run such a testing group? I'm assuming one already exists, but I don't see regular requests for participation, this is somewhere community can lighten the devs load.
 
@Cryptosi
Totally agree with the overall vision, and I want to clarify why that line about prioritizing near-term releases was brought up in the first place:

Whenever this came up in Discord, the common explanation was that because of the current price, the developers aren't earning enough to cover their living expenses and are forced to juggle multiple side jobs. The only reason we pushed for packaging ready PRs was to help the token gain healthy momentum so the treasury can actually pay the devs properly, allowing them to focus 100% on PIVX instead of side hustles. It was never about cutting corners or sacrificing privacy for quick hype.

That said, your point on technical debt is completely valid.

As for your ideas:

  1. The bi-weekly podcast with rotating devs is fantastic for regular updates and transparency.
  2. On the testing side—we're actually already testing different PRs and builds right now to help move things along. I'd love to help organize this into a proper community testing group so more people can get involved.
Let's definitely coordinate and make this happen.
 
You must log in or register to reply here.
Top