[DIS] iCKB & dCKB Rescuer Funding Proposal (Non-Coding Expenses)

Hello, any dCKB rescuer update, please?

Good morning @matt.eth, thank you for the question!! :grin:

Let’s make this an informal update: currently I’m collaborating to extend some aspects of CCC, in particular related to UDT. In short, I’m bringing in my experience of working with iCKB and allowing all Community to benefit from it, thanks to CCC and @Hanssen hard work!

Once that is stabilized and CCC-based iCKB libraries well-tested, I can launch the new CCC based interface and bot. Once that is done, I’ll move to dCKB Rescuer!

In the meantime, I was also asked to review the Quantum Resistant Lock, which I plan on doing this week.

Circling back to dCKB Rescuer, I’d like to provide here some additional context that I already provided in Nervos Nation:

What is dCKB?

For all newcomers: dCKB is an old protocol wrapping NervosDAO deposits. In theory dCKB and iCKB are similar, but dCKB had a naive design that lead to its downfall. Once the creators realized their error, they try to release a v2, shortly before closing down everything, locking up user funds in the process and ghosting the community in the end.

iCKB is different in creators, design and open source-ness.

Any hope of exchanging the DCKB purchased from the secondary market?

Short answer: Nope, only those who created the original dCKB deposits can withdraw them using the dCKB tokens. Nothing I can do about that.

Long answer: Yes IF someone buys those dCKB off from your hands and that’s the whole point about the upcoming dCKB Rescuer refresh, so provide a place where:

  • Secondary holders can sell back the dCKB tokens
  • Original depositors can buy back the dCKB tokens

For any more doubts or questions, I’m here :hugs:

Phroi %26

2 Likes

Hello @phroi , thank you for your ongoing work. I’d like to follow up on the progress of this project. Or more specifically—I want to know if the dckb I hold still holds value :sweat_smile: (ckb1qzl58smqy32hnrq6vxjedcxe2fugvnz497h7yvwqvwel40uh4rltcqd4hfdg7w6rs4mujq688qy8jm45rsvzrecrehagr, I had to move my dckb here due to godwoken’s termination, but I find I can’t even transfer it anymore). In any case, thank you again for your ongoing work.

2 Likes

Hey @matt.eth, thank you for the question! :hugs:

TLDR: No, likely

Longer Version:

  • For those dCKB tokens to have any value we need to find the Original Depositors of dCKB, willing to buy them back and use them to unlock their dCKB Deposits.
  • These Original Depositors seems to be gone: in all this time I heard of exactly one user who needed a bit of dCKB to unlock a deposit (more than one year ago). Since then I didn’t heard from him anymore. (Likely he got already those dCKB from the secondary market.)

That said, I would be happy to be wrong, so I shoot a message to anybody who ever told me about dCKB and from there we can see if any Original Depositors emerge.

My reach in the Chinese community is very limited, I would be grateful if you could spread the question @matt.eth: Does anyone have dCKB-deposits that need some dCKB to unlock?

Anybody who needs help with dCKB please comment here, specifying if you have any dCKB deposits.

Phroi

Thank you for your reply. I have two questions I’d like your assistance with:

1. Will there be any further developments for the ā€œdCKB Rescuerā€ project? You previously mentioned an ā€œoverhaul of the dCKB Rescuer DAppā€;

2. How can I transfer dckb? I’ve noticed that while I can view my dckb balance on the explorer and in Mobit, I’m unable to perform any transfers.

Thank you!

1 Like

If we can find even a single dCKB Original Depositor who needs dCKB, yes, by all means!!

Without OD, dCKB tokens are worthless and it doesn’t make sense to spend time on it.

My biggest issue is that the next hypothetical dCKB Rescuer iteration would be a pain to develop and test due to this bugfix: https://blog.cryptape.com/ckb-vm-changes-under-the-meepo-hardfork#heading-fix-nervos-dao-occupied-capacity-vulnerability

With that bugfix you can’t deposit & withdraw new dCKB deposits with the original v1 nor v2 dCKB protocol (cause deposit lock size != withdrawal request lock size), so how can I even test if my tool works or not?

I’m still wrapping my head how I would need to hypothetically work around it.

Also all the tech involved in the previous iteration is now legacy, for example PW_Lock, Lumos… So you can understand why I’m not really keen on this undertaking.

I would try ckbccc.com: it is more of a demo for devs (so not intended to meet all user needs), but it may support sUDT + PW_Lock.

Merry Christmas and thank you for the questions,
Phroi

Alright, I understand. Merry Christmas! Thank you again for your contributions to the community.

1 Like