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 PIVXie Wallet

Alexxiy

New Pivian
Warning! Re-read the post, it's only about one cycle, not as in the submitted proposal! That was my mistake, thanks for understanding!

Code:
Title:        PIVXie - Multi-Platform PIVX Wallet: Infrastructure & Development
Name:         pivxie-wallet
Term:         1 cycle (5 next cycles should be ignored, my mistake)
Cycle Amount: 30,000 PIVX
Total Amount: 30,000 PIVX
Author:       Alexxiy
Receiver:     Alexxiy
Address:      DDN2g5w75yb88Ujdu54mmpeQnbgGeg5Sec
Created:      2026-11-15
Status:       Active
Vote hash:    99e021afdf61bbaa2338e32a96b8f431bfa035db909c18435bb8cd4d71037520

PIVXie - Your PIVX. Your Keys. Total Control.​

https://pivxie.me

Overview​

PIVXie is a free, open-source (GPLv3), self-custodial PIVX wallet for Android, Windows, macOS and Linux, and it's coming soon to iOS. My goal was one wallet, on every platform, that supports everything the PIVX blockchain can do, from SHIELD privacy and Cold Staking to masternodes, DAO voting, PIVX Names and DeFi. It should be easy enough for a newcomer and complete enough for a masternode owner.

PIVXie is already live and can be downloaded from Google Play, GitHub Releases (APK, AppImage, Flatpak, Windows, macOS) and pivxie.me. The source code is public at github.com/alexxiy/PIVXie.

This proposal pays for the server infrastructure behind the wallet and for continued development and maintenance.

Features​


🏷️ PIVX Names​

No more copying and double-checking 78-character addresses. PIVX Names connects simple, readable names like alice.pivx to private SHIELD addresses. The service is fully decentralized, self-custodial and protected by zero-knowledge proofs.
  • Send PIV to any registered name directly from the send screen
  • Register your own name and manage it inside the app
  • Payments to a name go to a SHIELD address, so they're private by default
  • Trustless resolution: name registrations are batched into zero-knowledge proofs (Succinct SP1 zkVM), and the proven state is anchored in a public verifier contract on BNB Smart Chain. You don't need to trust a server to know a name is correct
  • The resolved address is shown before you confirm, so you always know where your coins go
Website: https://pivx.name
GitHub: github.com/PIVX-Name: registrar frontend, indexer, ZK prover, Merkle tree storage proxy and EVM anchor contract

🌉 DeFi Bridge​

The DeFi Bridge connects PIVX to BNB Smart Chain and opens the door to the wider DeFi world for PIV holders.
  • Move PIV from the PIVX blockchain to BNB Smart Chain and back
  • Use your PIV in the BNB Smart Chain DeFi ecosystem
  • Going fully open-source: the smart contract with all its governance documentation, plus the bridge frontend, will be released on GitHub soon
Website: https://defi-bridge.pivxie.me
Smart contract (BSC): 0x804850D326471123b0736e5818e91b87D49A877C
GitHub: smart contract, governance docs and frontend coming soon

🛡️ SHIELD Privacy​

Full support for PIVX SHIELD, which is built on zk-SNARK (Sapling) zero-knowledge cryptography.
  • Shield, unshield and send PIV privately
  • One-tap "Shield All" moves your whole transparent balance into SHIELD
  • Optional encrypted memos that only the recipient can read
  • Optional built-in Tor routing for network-level privacy

❄️ Cold Staking​

Earn staking rewards without keeping your wallet online 24/7.
  • Delegate your PIV to a trusted staker listed on masternode.space, or to your own node
  • The coins never leave your wallet. The staker can only stake them and can't spend them
  • Undelegate at any time with one tap

🖥️ Masternodes​

A complete masternode manager in your pocket.
  • Create new masternodes or import existing ones
  • Start masternodes remotely
  • Inspect collateral UTXOs
  • Monitor status and reward payouts

🗳️ DAO Governance​

Take part in PIVX governance from any device.
  • Browse past, current and upcoming budget proposals and superblock allocations
  • Submit your own proposals
  • Vote YES or NO with all your masternodes at once. Votes are signed locally on your device

🔑 Backup & Recovery​

  • 12- or 24-word BIP39 recovery phrase with an optional passphrase
  • Fully compatible with MyPIVXWallet phrases
  • Encrypted, automatic local backups

🔒 Security​

  • PIN or biometric lock
  • Duress PIN: a second PIN that opens only chosen decoy wallets, which protects you if someone forces you to unlock the app

⚙️ Everyday Use​

  • Send and receive with QR codes and pivx: links
  • Coin Control for advanced users
  • Labeled and filterable transaction history
  • View-only wallets
  • Message signing and verification
  • Easy Crypto mode shows fiat estimates and the 24h price change. Incognito mode makes no third-party lookups at all

🌐 Self-Hosting​

PIVXie connects to the default PIVXie bridge servers, or you can run your own pivx-bridge (open-source) and point the wallet to it in Settings.

Work Done for PIVX​

Besides PIVXie, I contribute directly to other PIVX projects:

🏷️ PIVX Names integration in MyPIVXWallet
PIVX-Labs/MyPIVXWallet#630
  • Lets MyPIVXWallet users send PIV to names ending in .pivx, .private, .secure and .safe
  • Cryptographically verified resolution: the Merkle proof is checked locally in the wallet and matched against the anchor contract on BNB Smart Chain before a send is offered
  • Existing send behavior is unchanged for regular addresses
  • Covered by unit tests, and I'm addressing the code-review feedback

🛠️ PIVX Core wallet fixes
PIVX-Project/PIVX#2988
  • Imported Sapling viewing keys are now saved to the wallet. Before, they were kept only in memory and lost after a restart, which could crash the wallet on startup
  • Startup no longer crashes on notes whose viewing key is missing
  • The witness cache size is now saved together with the notes, which fixes a startup assertion failure
  • Includes new functional tests

What the Funding Is For​


1. Distributed infrastructure: 12,000 PIVX (12 months)
Three good VPS servers, each running a PIVX full node + pivx-bridge, placed for the best connectivity worldwide:
  • 🇪🇺 Europe
  • 🇺🇸 United States
  • 🇸🇬 Singapore
These servers handle wallet sync, broadcasting, SHIELD data and governance data for every PIVXie user. Spreading them across regions means fast response times everywhere and no single point of failure.

2. Publishing & legal costs: 10,800 PIVX
  • Apple Developer Program membership (1 year): $100 ≈ 4,000 PIVX. Required to publish PIVXie on iOS and the App Store
  • Company registration: £127.58 (~$170) ≈ 6,800 PIVX. App stores require a registered organization to publish crypto-related apps

3. Development & maintenance: 7,200 PIVX
  • Bug fixes, stability improvements and keeping up with new PIVX Core releases and network upgrades
  • Server security and updates: patching the OS and all server software (PIVX node, pivx-bridge, system packages) as soon as vulnerabilities are disclosed. AI tools now find and publish new vulnerabilities much faster than before, so I keep the infrastructure patched continuously instead of on a fixed schedule. That keeps user connections and the network safe.
  • Further development of PIVX Names and the DeFi Bridge, including publishing the bridge smart contract, governance docs and frontend on GitHub
  • Continued contributions to MyPIVXWallet and PIVX Core
  • Publishing on iOS and the App Store, and maintaining releases for every platform
  • New features and UX improvements based on community feedback
  • User support

Total (1 cycle)
Infrastructure (3 nodes + bridges)12,000 PIVX
Publishing & legal (Apple Developer, company registration)10,800 PIVX
Development & maintenance7,200 PIVX
Total30,000 PIVX


Transparency & Reporting​

The servers for the PIVX nodes and bridges are already paid for a full year. I will publish reports in this thread with the payment details for that hosting, so everyone can see exactly where the infrastructure part of the funding goes. I will also post regular progress updates on development and maintenance.

Thank You​

I want to sincerely thank everyone who tried PIVXie, reported bugs, left reviews and shared kind words about my work. I've received a lot of positive feedback from community members, and it means a great deal to me. It's what keeps me going.

My focus is expanding PIVX infrastructure. A wallet that is easy to use and available to everyone, on any device, lowers the entry barrier for new users dramatically. Every feature of the PIVX blockchain should be one tap away, not hidden behind a command line.

Why Vote YES​

  • It's already built and working. You're funding a live product, not a promise.
  • It covers every platform and every PIVX feature: SHIELD, Cold Staking, masternodes, governance, PIVX Names and the DeFi Bridge.
  • I contribute beyond my own app, to MyPIVXWallet and PIVX Core.
  • It's open source and self-custodial. Users always keep their keys, anyone can run their own bridge, and the DeFi Bridge contract and frontend are being open-sourced too.
  • The funding is transparent: the servers are already paid, reports will be published, and the budget is spread over 6 small cycles.

I hope you'll support me through these 6 cycles. In return, I'll do my best to make PIVXie rock-solid, and I'll keep building more infrastructure projects for PIVX.

Questions, suggestions and feedback are very welcome in this thread. 🙏
 
Last edited:
6 cycles is a long time. Price will fluctuate between that alot. What $ figure are you wanting back for your investment should be taken into account.
 
Thanks for raising it, it's a fair point to check. So let's look at the real numbers.

At the current price, 180,000 PIVX is about $450–460 in total.

  • ~$300 of that I've already spent on the servers (PIVX nodes + pivx-bridge in Europe, US and Singapore) for a full year. I'd just like that covered, and I'll post the payment reports here as promised.
  • That leaves ~$150–160 for development and maintenance: around 3–4 months of a developer's work done on PIVXie and all of its features, also participating in MyPIVXWallet and PIVX Core.

Now the "price fluctuation" scenario. Even if PIVX does a x10 during these 6 cycles, the development part becomes ~$1,500–1,600. For several months of full-time development across multiple PIVX projects. I honestly don't think that's a figure the DAO needs to lose sleep over 🙂

And funnily enough, nobody ever worries the other way: "you've asked for too little, in 6 months it could be worth even less." 😄 (but I really believe in PIVX, it's just hypothetically)

That's exactly why I split it into 6 small cycles instead of one big request. The load on the budget stays small, and the community can see progress every month and stop voting YES any time it isn't happy with the work.
 
Yes there is always chance for a drop but what figure over the 6 months are you looking for? So if this gets funded with the current plan in 3 months the rest can be downvoted?
 

TrekPay

Those are some impressive amounts you're asking for to duplicate an application that you also have available on Google Play.
Overall, the proposal is ambitious, but it looks more like an attempt to get money out of the community.
Just look at the 96,000 PIV you're requesting for 12 months of server hosting, when it's unclear how those servers even operate.
It's not my business, but you're asking for amounts that are even higher than what PIVX Core developers request.
And the most interesting part is that the domain is only one month old.
How much time have you actually spent developing your solution?
You also mentioned a token and a bridge. I doubt this will be of much interest to the altcoin community. PIVX has been around for years, and these things have never been implemented.
 

TrekPay

Those are some impressive amounts you're asking for to duplicate an application that you also have available on Google Play.
Overall, the proposal is ambitious, but it looks more like an attempt to get money out of the community.
Just look at the 96,000 PIV you're requesting for 12 months of server hosting, when it's unclear how those servers even operate.
It's not my business, but you're asking for amounts that are even higher than what PIVX Core developers request.
And the most interesting part is that the domain is only one month old.
How much time have you actually spent developing your solution?
You also mentioned a token and a bridge. I doubt this will be of much interest to the altcoin community. PIVX has been around for years, and these things have never been implemented.
Good research! Just seems like a clone based on pivx with an ai overhaul
 
In any case, the community will be voting on this.
Right now, it would be much more useful to allocate 30–180k towards the testnet for version 6 rather than duplicating the application I mentioned above.
The forum proposal is certainly very professionally presented, though.
 
Gerrald said:
...what total figure over six months, and could the remaining cycles be downvoted if the first one is funded?
The total is exactly what's in the proposal: 180,000 PIVX, which is about $450–460 at today's price. And yes, absolutely. Every cycle is paid only if the proposal still has enough YES votes at that superblock. Masternode owners can switch to NO at any moment, and the remaining payments simply stop. That's the whole point of splitting it into small cycles.

a44319826 said:
Those are some impressive amounts you're asking for to duplicate an application that you also have available on Google Play.
I'm not asking for money to duplicate anything. The app is already built. The funding is for the infrastructure behind it and its further development, as described in the proposal. I'm not sure how another app of mine is related to this discussion. Which apps I build is my own decision.

a44319826 said:
...when it's unclear how those servers even operate.
Happy to explain, in case it really is unclear: there's Linux on them, with a PIVX Core node and pivx-bridge running on top, which is open-source on my GitHub. Sarcasm intended, of course 🙂

a44319826 said:
...you're asking for amounts that are even higher than what PIVX Core developers request.
The Core developers have been receiving funding for years. This is my first proposal. I'd suggest comparing the totals. Nothing against the Core team at all, just a gentle reminder about the math.

a44319826 said:
And the most interesting part is that the domain is only one month old.
Should I have registered it back in 1990, when I was going to school? A domain gets registered when the project needs one.

a44319826 said:
I doubt this will be of much interest to the altcoin community.
Thank you, your opinion is very important to me. Although it seems the bot didn't even bother to replace "altcoin" with the actual name of the coin 🤣 Luckily, deciding whether it's of interest is exactly what the vote is for.

Gerrald said:
Good research! Just seems like a clone based on pivx with an ai overhaul
Truly impressive research. It took one whole click on the developer name on Google Play.

a44319826 said:
Right now, it would be much more useful to allocate 30–180k towards the testnet for version 6
Haha! Had you been registered on the forum about a week ago, on Thursday at 6:36 PM (your account is about as new as the pivxie.me domain you mentioned), you could have voted for exactly that: PIVX.Ninja - PIVX Testnet Maintenance & Development.
I built a fully working testnet for the current 5.6.1 version, so any developer who wanted to start building on PIVX could do it right away. Moving it to v6 would have taken me about one extra day.
But instead of being supported, that proposal almost immediately got a comment that put the community off it, and it was voted down.
It's disappointing when a small group holding a large number of masternodes supports only the proposals that benefit them. The wider community barely has a voice, and that slowly makes PIVX more centralized. Apparently even a testnet has to be "official".


To sum up: it's hard not to notice two accounts working quite hard to convince the community to vote NO, without engaging with what the proposal actually delivers.

A light wallet is essential for any ecosystem. Wallets like this are easy to install, and they let non-technical users join in minutes. Or should every new user set up a Core node and read hundreds of pages of documentation first? A rhetorical question, of course.

Everything is open-source and already working. The community can try it and decide for itself.
 
Last edited:
I've read the entire proposal, along with the messages and your point of view. However, I wish people had been a little kinder in their responses. I apologize on their behalf. I know how discouraging it can be when you put in the effort and then get treated this way.

From what I understand, you made a mistake in your calculations and only intended to cover the server costs. However, the proposal has already been submitted, and there is no way to amend it.

We have two options:

  1. Submit a new proposal with the correct figures.
  2. Vote YES on your current proposal for one cycle. You would use 30,000 PIVX (30,000 × $0.025) to cover your server costs, and the remaining amount would go towards developer costs.
I'd also like to make one thing clear for masternode owners so everyone knows exactly how to vote. Please choose the option you believe is fairest and vote accordingly. If you support the current proposal for one cycle, vote YES. If you prefer a new proposal with corrected figures, vote NO on the current proposal.
 
I've read the entire proposal, along with the messages and your point of view. However, I wish people had been a little kinder in their responses. I apologize on their behalf. I know how discouraging it can be when you put in the effort and then get treated this way.

From what I understand, you made a mistake in your calculations and only intended to cover the server costs. However, the proposal has already been submitted, and there is no way to amend it.

We have two options:

  1. Submit a new proposal with the correct figures.
  2. Vote YES on your current proposal for one cycle. You would use 30,000 PIVX (30,000 × $0.025) to cover your server costs, and the remaining amount would go towards developer costs.
I'd also like to make one thing clear for masternode owners so everyone knows exactly how to vote. Please choose the option you believe is fairest and vote accordingly. If you support the current proposal for one cycle, vote YES. If you prefer a new proposal with corrected figures, vote NO on the current proposal.
Thank you! Yep, it was late evening and once an extra 0 came after the comma and I remember that amount so next calculations was according it without a re-check. Sorry for that and thanks for flagging it! I admit, this is my mistake.
I'll fix the head post right now and fix all the number there.
I can re-submit the proposal, but I think your second option looks better so we don't have multiple proposals which can be confusing.
I also add some expenses which I forgot to mention, so we can cover 30k and then other cycles should be downvoted.

Thank you, Mr. Ali. Yet you are the most constructive here, without attacks.
 
Top