Wrapmeister Wrap Side Outage

Hello,

just to inform the community what is up with wrapmeister. The PPC ↔ wPPC bridge.

As you may know, I designed wrapmeister protocol as there was a strong push in the community to have a wrapped coin liquidity on EVM chains.

Here we are about 3 years later. The person who started the project and led it until launch has left the community about a year ago. The person who implemented the coordinator software left like a month after the project was launched, never to return. Who is left is me, running the coordinator node on my server, and this coordinator node is falling apart. And I did not even agree to this, I just said it was fine for me to donate a VPS server.

Software decays.
Especially modern software, it needs updates and patches and versions of everything keep changing. It needs maintenance. I can’t do but basic maintenance on a codebase I am not familiar with. The codebase is written in typescript, on node.js, and I am just not into that.

I asked the witnesses if it is ok to put the pause on wraps until software can be re-implemented in something more manageable. They agreed.

Unwraps will continue working, I rewrote that part in python sometime last year, and it now runs independent of the coordinator as standalone software. It is based on this code:

The agreement is to put the pause on wraps until replacement software is made, by either me or someone else. The new software should also revolve around ROAST this time, which just got launched.

3 Likes

If you find the bridge service useful and want wrapping to continue, then be sure to ask in this thread what we need from the community in order to recode the coordinator node. Silence will be taken as the community not being interested. I personally don’t think we should get too comfortable with our current set of centralized exchanges and believe wPPC is still needed.

If you had a bad experience or delays with the current bridge software, just note what Peerchemist said above about a rebuild utilizing the new ROAST technology. It should be much quicker with less delays, and a better user experience overall. I think decreasing the wait time for bridging will lead the community to use wPPC more than it is currently being used.

Also, currently there are two different contracts, one for Ethereum and another for Polygon. To make things simpler and avoid confusion, we would want to build in such a way that there is only a single contract/token that can work on multiple EVM blockchains. There are ways to do this now.

1 Like