Luke
New Pivian
Proposal Details:
- Name: Luke (Q3 2026)
- Term: 3 Cycles
- Cycle Amount: 45,000 PIV
- Total Amount: 135,000 PIV
- Author: Luke
- Receiver: Luke
- Address: DRCftD2Xqmoud7x5EdhnBnMjof5qfE4rEn
- Created: 7-23-2026
- Status: Active
- Vote Hash: 02a1b2151e5205f63158a72cfb99975cdbe1a1fc765cc4c4e0ff05251221ea46
---
Role and Introduction
I'm Luke, a backend developer working across the PIVX ecosystem. For the past several quarters my time has gone primarily into Labs platforms: PIVCards, PIVX Labs, node maintenance, and the supporting infrastructure, alongside code review and general ecosystem work.
This quarter I'm shifting the majority of my time to PIVX Core. The Labs platforms are in a stable, maintained state, and the highest-value place for my hours right now is helping get v6 across the line.
---
Q2 2026 Accomplishments:
- Continued maintenance and uptime of PIVCards, Labs Oracle, and node systems
- Supported early v6 release preparation and testnet groundwork
- Investigated the Coinbase x402 protocol as a payment path for PIVX and built a live solution for it
- Started work on the Edge wallet integration and published a testing beta for that integration
---
Q3 2026 Focus: Back to Core
1. Get a v6 testnet running
The official testnet for v6, and the most important deliverable this quarter:
- Verify chain startup, sync, and consensus behavior end to end on testnet
- Work with Liquid on testing edge cases and network problems
- Publish clear instructions, so anyone can join the testnet with minimal friction
- Provide a faucet and any supporting tooling testers need
- Keep the testnet alive and reset or redeployed as v6 changes land
2. Push v6 development forward
Testnet exists to surface problems. The follow-through is fixing them and closing out the remaining work:
- Work through the open v6 issue and PR backlog
- Triage, reproduce, and fix bugs found during testnet operation
- Review and help land v6 contributions from other developers
3. Wallet and ecosystem compatibility
- Validate MyPIVXWallet and Labs services against v6 testnet
- Fix compatibility issues in wallets and tooling as they're found
- Coordinate with integrators so they can test ahead of mainnet
4. Continued maintenance
Labs platforms stay online. PIVCards, Labs Oracle, and node systems continue to be maintained and supported. This is reduced but not dropped, and I'll respond to anything urgent.
---
Why this matters
PIVX has spent a long stretch with development effort spread across peripheral platforms. Those platforms matter, but a coin's value ultimately rests on its protocol. Getting v6 tested on a real testnet and shipped is what moves PIVX forward, and that's where I want my hours going this quarter. I'd ask for the community's support in doing it.
---
Budget
45,000 PIV per cycle for 3 cycles, 135,000 PIV total.
This is an increase from the 30,000 PIV per cycle I've requested in previous quarters. It isn't a raise. It's due to the major drop in market price, and even with this increase I will still make less than I did in any previous quarter. My hours and scope are unchanged.
If you have questions or comments let me know
Thank you
- Name: Luke (Q3 2026)
- Term: 3 Cycles
- Cycle Amount: 45,000 PIV
- Total Amount: 135,000 PIV
- Author: Luke
- Receiver: Luke
- Address: DRCftD2Xqmoud7x5EdhnBnMjof5qfE4rEn
- Created: 7-23-2026
- Status: Active
- Vote Hash: 02a1b2151e5205f63158a72cfb99975cdbe1a1fc765cc4c4e0ff05251221ea46
---
Role and Introduction
I'm Luke, a backend developer working across the PIVX ecosystem. For the past several quarters my time has gone primarily into Labs platforms: PIVCards, PIVX Labs, node maintenance, and the supporting infrastructure, alongside code review and general ecosystem work.
This quarter I'm shifting the majority of my time to PIVX Core. The Labs platforms are in a stable, maintained state, and the highest-value place for my hours right now is helping get v6 across the line.
---
Q2 2026 Accomplishments:
- Continued maintenance and uptime of PIVCards, Labs Oracle, and node systems
- Supported early v6 release preparation and testnet groundwork
- Investigated the Coinbase x402 protocol as a payment path for PIVX and built a live solution for it
- Started work on the Edge wallet integration and published a testing beta for that integration
---
Q3 2026 Focus: Back to Core
1. Get a v6 testnet running
The official testnet for v6, and the most important deliverable this quarter:
- Verify chain startup, sync, and consensus behavior end to end on testnet
- Work with Liquid on testing edge cases and network problems
- Publish clear instructions, so anyone can join the testnet with minimal friction
- Provide a faucet and any supporting tooling testers need
- Keep the testnet alive and reset or redeployed as v6 changes land
2. Push v6 development forward
Testnet exists to surface problems. The follow-through is fixing them and closing out the remaining work:
- Work through the open v6 issue and PR backlog
- Triage, reproduce, and fix bugs found during testnet operation
- Review and help land v6 contributions from other developers
3. Wallet and ecosystem compatibility
- Validate MyPIVXWallet and Labs services against v6 testnet
- Fix compatibility issues in wallets and tooling as they're found
- Coordinate with integrators so they can test ahead of mainnet
4. Continued maintenance
Labs platforms stay online. PIVCards, Labs Oracle, and node systems continue to be maintained and supported. This is reduced but not dropped, and I'll respond to anything urgent.
---
Why this matters
PIVX has spent a long stretch with development effort spread across peripheral platforms. Those platforms matter, but a coin's value ultimately rests on its protocol. Getting v6 tested on a real testnet and shipped is what moves PIVX forward, and that's where I want my hours going this quarter. I'd ask for the community's support in doing it.
---
Budget
45,000 PIV per cycle for 3 cycles, 135,000 PIV total.
This is an increase from the 30,000 PIV per cycle I've requested in previous quarters. It isn't a raise. It's due to the major drop in market price, and even with this increase I will still make less than I did in any previous quarter. My hours and scope are unchanged.
If you have questions or comments let me know
Thank you