Active Luke (Q3 2026)

[Luke]

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

 

[MrAli]

Luke, since this proposal covers 3 cycles, could you give us an update on how much progress you’ve made on the Q3 deliverables so far?

Also, since you mentioned that your hours and scope are unchanged, could you give us an approximate number of hours per day or per week that you’re dedicating to this work?

It would be helpful for the community to understand the progress and the amount of time being spent on the proposal.

 

[LeacyMcK]

Luke, since this proposal covers 3 cycles, could you give us an update on how much progress you’ve made on the Q3 deliverables so far?

Also, since you mentioned that your hours and scope are unchanged, could you give us an approximate number of hours per day or per week that you’re dedicating to this work?

It would be helpful for the community to understand the progress and the amount of time being spent on the proposal.

Please stop using the word community in your asks as we all know and have seen Luke's work. We see him working daily. These questions are from you only and quite frankly they are written at the worst possible time when they could have been asked months ago. Choosing to ask these questions during a time when PIVX is getting v.6.0 ready for testnet, when the price is the worst and PIVX devs are being paid pennies but are still here fighting, is a red flag to me. If you're here to support the team, let them continue to work.

 

[Luke]

Luke, since this proposal covers 3 cycles, could you give us an update on how much progress you’ve made on the Q3 deliverables so far?

Also, since you mentioned that your hours and scope are unchanged, could you give us an approximate number of hours per day or per week that you’re dedicating to this work?

It would be helpful for the community to understand the progress and the amount of time being spent on the proposal.

Good morning/afternoon/night,

So far as it goes for the deliverables, I have worked with Liquid and the other developers to get the testnet v6 running. The faucet and testing tooling has not been needed yet so that hasn't been released. You can see my reviews and commits when it comes to pushing v6 forward, a lot of it has been behind the scenes discussions with Liquid and working reviewing. MPW, and labs services have not been tested as we aren't at that stage yet.

There has also been a lot of work that I have done on projects not currently listed on this proposal to push PIVX forward quicker such as all the upgrades to the wallet tool kit and creating the multi-wallet tool kit version that you can also find on my and pivx labs GitHub. These were pushed out due to needs from the community for marketing and upcoming projects.

I have been maintaining and handling tickets when they occur for services like PIVCards, as well as maintaining and updating the servers that these services are on. Both of these are ongoing deliverable and not really sure how you would like me to display this, but the community has seen my name and talked to me any time there are issues. Most times these are private tickets in the PIVX labs discord server that we clear out, so no personal information can be leaked/available after the ticket is closed. Sometimes however when a user doesn't care you can see it in the Pivcards channel in the PIVX labs discord server.

As far as hours and scope go, when I say that I don't mean that I sit at my computer for x hours per day. What I mean and have done for all previous PIVX contracts/DAO payments is make sure that the deliverables that are stated in my proposals are done by the end of the proposed time, and generally extra work always occurs as well. I also mean that I have set times of day that I am contactable and able to service emergency issues, such as a down server, misconfiguration, change to a provider api, etc. A lot of the loose wording is because a lot changes weeks by week and sometimes priorities need to get moved around, or something that was thought to be needed isn't needed. For instance sometimes we are trying to push out something for marketing really quickly due to a recent news event, this means that what I had planned for that period of time might get moved or discontinued in favor of the other work. All of this is generally discussed in public channels (discord, telegram) when it happens, and it's fairly clear that the community supports it. It is far easier to do that then rewrite proposals, then get the necessary vote count, wait for the payout then complete something when it is time-sensitive. Generally I am fairly flexible and haven't had any complaints from the community about this in the past.

I'd also like to make it clear that if we want to start talking about hours worked/per amount of funds, I am by far under charging for my time. At my current rate with most clients and the current payout of the DAO I wouldn't be working more than 5-6 hours per month. The PIVX community has been good to me for a long time and I appreciate everyone here so I have kept working and pushing things forward even with the significant drop in payment. If you are just curious about the number of hours I generally work on PIVX and associated systems (labs) specifically we are looking at probably 40-160 hours per month depending on work load, product release times, service and server issues/maintenance, etc., which at current rates would put me somewhere between 16 and 4 dollars an hour. I don't think I have to explain to you how silly this is pay wise for an experienced developer. This amount at the most (16/hour) is currently below the minimum wage of the area I reside in, meaning I could get any job off the street and get paid more than that. I'd also like to include most if not all days I am on call for emergencies, which isn't something you get from a normal developer without an on call rate. I am happy to be able to help PIVX and the community here, my goal has always been to push everything forward and to make sure everyone is as happy as they can be. I do however want to spell it out and make it clear that I am not some huge siphon that is draining PIVX DAO dry. In the past I have purposely kneecapped my proposals to make sure that other people could get in so that we can have as much going on as possible and push PIVX forward. I'm hoping you didn't mean to imply that I am not worth the tiny amount of PIVX I am charging the DAO. Sometimes It's difficult to read text, and the implications can be wildly misconstrued, so I'm going to simply assume you are just new and curious.

I hope this answers your questions, if you have more feel free to reach out to me on discord, or respond here if you like, just know I check discord/telegram far more frequently then here.

Have a great rest of your day!

 

[MrAli]

Hello my friend,

You are one of the long-time members of PIVX, and asking questions to someone with your experience helps a newcomer like me learn more. I’m trying to increase my knowledge because I would like to join the development team and contribute in these areas.

The reason I asked my questions was that I wanted to join the development team and understand how the process works. I also wanted to know roughly how many hours of work would be expected for someone working under a proposal.

However, so far, I’ve noticed that whenever I’ve asked someone a question, I’ve received a rather harsh or defensive response, as if there was something wrong with asking. I believe everyone should be able to ask questions, and honestly, questions should be answered in a friendly and constructive way rather than with hostility.

So I have one question for you: Do you think new people are encouraged to join the PIVX team when they receive this kind of response?

In any case, I understand your point now and I’ve received the information I was looking for.

Thank you for taking the time to answer me.

 

[SiggeB]

Do you think new people are encouraged to join the PIVX team when they receive this kind of response?

Trying my best to help both sides understand each other:

The whole PIVX community is in a tense state. People try to make ends meet, pay their rent and groceries. Some of the team are way past being able to make even a part a living from what PIVX can give them. Most of us, if not all, are putting in a LOT more hours than what they're paid for.

Another point is that most of those who are still here have been members of the community for many years. They have a reputation, a standing, and other community members knows what they stand for and how to handle them.

It doesn't need mentioning that the PIVX community needs more help, more engagement, more development manpower. But...

We always say that the PIVX community is a meritocracy. It's not a business. At all. And should never be seen that way. Newcomers are welcome, but need to gain trust, first. I'm sure you have good intentions, but somehow the wording didn't convey that. I'm not blaming the sender nor the recipient of the message here. I'm just stating a fact that there seems to be a discrepancy between wanting to understand how PIVX works and questioning what people are actually doing. And again, there are a lot of sore toes here after the price drop and infighting, and it's not too hard to accidentally step on one of those.

Then there's also the on-chain facts of voting down certain proposals, creating competing proposals, that raise eyebrows.

I want to close by inviting everyone reading this: We are only responsible for our own actions, not other people's. Each one of us needs to remind themselves about what is really important here, what's at stake. This shouldn't be about anyone's ego. Egoism has brought too many problems and bad reputation to the PIVX community. Whatever action we take forward, we need to make sure that it's for the bet of PIVX, not for the best of our ego. We should have a common goal, and that is to bring PIVX forward.

Let's take a step or two back, see the big picture and ask ourselves mor often: What can I, right now at this moment, do that helps improve PIVX?

(No AI has been used to write this post.)