Following up on the progress on the roadmap as we passed 2/3 of the Q1 and we might have some updates
- Basic flows Maximum of 1 user bug per month
We seem to have reached a plateau where no issues have been reported in this area. This is a positive sign, especially considering that we also shipped the interface for borrowing from strategies and the frontend proposals matching engine—both of which directly relate to this flow.
- Advanced features / flows (max 1 user bug per week):
The current average number of reported bugs per week is 5, with some related to recently released features.
While the overall number of reported bugs has decreased, we still have room for improvement in transparency. Introducing a #bugs-and-feedback channel in Discord could provide better visibility into the current state and serve as an open communication channel for users.
Establish a robust user testing routine (reward testers with reputation points).
Addressing this point required change in the process in favor of using Notion as the only source of through instead of Slack to coordinate work.
However, on the community side, we are falling behind significantly. To address this, I will start a forum discussion to organize a bi-weekly or weekly open call where users can share their experiences with PWN.
This initiative should help establish a dedicated communication channel for future rewards.
Additionally, to fairly distribute rewards for bug reports and feedback, we need an open and transparent database of contributors.
- Target: Conduct 10 full user interviews per month (2–3 per week).
I’m aware of at least one interview that took place during this period, but as this is not my direct responsibility, I don’t have complete data on the total number.
- Target: Organize 7 external testing sessions.
With four weeks left in the quarter, we could push this to 5/7 by scheduling open calls. While this isn’t ideal, we need to take action immediately.
Open Lending Strategies Editor to all users.
We have version that is really close to release and probably would be subject of some next external testing call
Release PWN on UniChain & Ink (potentially Starknet mainnet).
Progress: 1/3 completed
UniChain – Deployed
Ink – No blockers; ready to go once we decide to move forward.
Starknet – Only 1/2 audits completed. We could proceed with deployment while clearly stating in the UI that this version of the protocol has only undergone a single audit.
Good news:
Q2
Implement a Referral & Future fee-share system.
We are actively working on this and should have updates soon.
- Release PWN SDK for integration into wallet interfaces and DeFi yield aggregators.
Development on pwn-sdk-v1 has started. To efficiently handle external API requests, we should set up a dedicated communication channel (Telegram/Discord).
The SDK will include Vue and React libraries to facilitate access to core protocol functions, including:
- Posting proposals to the API
- Accepting proposals (borrow/lend)
- Encoding proposals based on terms (collateral, credit, APR, LTV, etc.)
- Repaying loans
- And more
- Perpetually available liquidity through dynamic commitments or commitment pools.
The Ethereum SDK will support this proposal type by default, so the next step is integrating it on the platform side.