renBTC Delisting Communications: Team Roles and Handoffs
If your DeFi product team is planning to delist renBTC, assign data to identify affected holders, product and engineering to preserve exits, and communications to set the timeline and script that support will use. This is a user communication plan: the goal is to give every holder the same clear route to withdraw.
How should the team identify and reach renBTC holders?
The data team should produce a current list of addresses holding renBTC positions and explain how it was assembled. Include the relevant chains and the time the snapshot was taken, so communications can describe who may be affected and support can interpret a holder’s case. For an app that handled assets moved through RenBridge, this list concerns the app’s users and positions; it is not a list of everyone who ever used the bridge.
Direct wallet balances may not capture every affected user. For example, a holder may have deposited renBTC into a liquidity pool and now hold an LP token, which represents a pool position rather than the underlying renBTC in their wallet. Ask data to identify known renBTC pool positions where the app’s records allow it, and separate those users from direct holders so the notice can explain whether they need an additional step.
Who keeps the withdrawal route clear, and who explains it?
Engineering should stop new deposits while preserving withdrawals, and the frontend should keep balances and the withdrawal path visible in read-only mode. Those responsibilities need to line up: a disabled deposit control should not hide the balance or make an available exit look unavailable.
- Contracts: Disable new renBTC deposits; do not add a restriction that blocks withdrawals.
- Frontend: Show existing balances as read-only and keep the withdrawal route visible, with plain instructions on any remaining user action.
- Communications: Set the timeline, explain who is affected, and state the withdrawal route and any relevant deadline.
- Support: Use the identical approved wording in replies and help content; escalate cases the script does not cover rather than inventing a different exit instruction.
This handoff matters because renBTC was minted and burned through RenVM, while a product delisting is a separate app-level change. RenBridge’s historical role in moving Bitcoin into renBTC does not tell a holder what their current app balance can do; the app’s withdrawal route and the approved user instructions do.
With these owners and handoffs in place, the team can distinguish stopping new exposure from preserving an exit, and give holders consistent guidance at every touchpoint.
What should the team decide about related user needs?
Should we keep a renBTC price feed running after delisting?
Keep the feed available for as long as balances, withdrawal screens, or support tools rely on it to show a value. Retire it only after those views no longer depend on that price, and label any remaining quote clearly if it is stale or informational.
Do users holding LP tokens with renBTC need separate notices?
Yes, when the LP position requires a different action from withdrawing a direct renBTC balance. Explain how to exit or unwind the pool position, and send the notice based on identified positions rather than assuming every renBTC holder has the same route.
How long should a withdrawal-only interface remain online?
Keep it available for the period users need to complete withdrawals and for support to resolve outstanding cases. Set the end date from the app’s actual withdrawal and support plan, then communicate it in advance; the right duration depends on those operational commitments.
Comments
Post a Comment