iCKB & dCKB Rescuer Funding Proposal (Non-Coding Expenses)
The vote for this proposal can be found here.
Summary
Activities funded:
- Funding of user/dev support and generally non-coding expenses, if any, for iCKB & dCKB Rescuer.
- Refund of iCKB L1 Scripts deployment & audit costs.
Grant amount: 673,400 CKB (roughly 10,000 USD at the current 0.01485 CKB/USD exchange rate)
CKB Address: ckb1qzda0cr08m85hc8jlnfp3zer7xulejywt49kt2rr0vthywaa50xwsqfey5wjqn7f059napy0nl9llw4ss50mmsgfrjtqs
Introduction
Hello Nervos Community DAO folks, Phroi here
Let me reintroduce myself once again: I’m a developer and I like to spend my time working on projects that give meaning to my life and improve the life of users. Win-win situations.
For example, in the past I created dCKB Rescuer as an alternative front-end for dCKB withdrawals, after the original NexisDAO front-end abrupt shutdown. More recently I’m launching iCKB, a protocol that aims to solve the illiquidity problem of NervosDAO by tokenizing NervosDAO deposits into a liquid iCKB token.
More generally, I’m active in the CKB Ecosystem as contributor, reviewer and vulnerability & bug hunter.
In these years the Foundation supported my coding work and I have an agreement where I can ask for grants to cover hours spent on developing specific projects, like iCKB & dCKB Rescuer.
That said, there are a lot more expenses when running a project, costs in time and resources that I’m not able to afford without economical support.
iCKB
iCKB is a project in the launching phase that will benefit the CKB ecosystem as a whole, available on testnet and mainnet.
In this past month I sustained the following expenses:
- 117437.00119141 CKB for the deployment on mainnet, creation of Dependency Group and creation of on-chain metadata needed by the explorer (all these cells are locked with a zero lock).
- 4,000 USD for the External Audit of iCKB
Also non-coding time expenses are piling up as more and more persons interact with the project both as users and developers. Feel free to check 1, 2 and 3.
dCKB Rescuer
While dCKB Rescuer has feature parity with the NexisDAO, there are two issues:
- There still are users unable to withdraw due to the mismatch between their dCKB Assets and dCKB deposit.
- dCKB Rescuer could break with the upcoming Fleek update.
To address both these issues I need to overhaul of dCKB Rescuer DApp. Shortly my targets are:
- Adding Limit Orders to dCKB Rescuer (users can exchange between dCKB and CKB at a reasonable ratio)
- Adding support for Omnilock with Metamask (that said dCKB V2 users still need to withdraw with a PWLock by contract, nothing I can do about that, later on converted to Omnilock by the DApp)
While the development hours are covered by the agreement with the Foundation, user support is not. Also I’ll have to make sure all dCKB holders are aware of these new features, so they can convert the dCKB back to CKB.
Requested Funding
I’d kindly ask to be funded 673,400 CKB, roughly 10,000 USD at the current 0.01485 CKB/USD exchange rate.
Once funded, I’ll set apart right away:
- The equivalent of 4,000 USD spent for the iCKB audit.
- 117437.00119141 CKB spent for deploying the iCKB contracts.
Whatever remains, roughly half, I’ll gradually convert to iCKB and I’ll use as credits for user/dev support and generally non-coding expenses, if any, for iCKB & dCKB Rescuer.
Given my rate of 50 USD / hour, I’ll convert iCKB to USD, little by little, only at actual work being done. The hours I’ll be able to provide will vary depending on the iCKB price at the moment of conversions.
I’ll publicly document the work done, hours spent and iCKB amounts used. This way the community can judge the goodness of their investment in my work and possibly fund future proposals in this direction.
Love & Peace, Phroi