Proposal for Resolution of Technical Debt
Redemption of Legacy wZNN (5,000 ZNN Batch)
Bridges burn, but the community never ceases.
Note: The term “BSC” is used throughout this proposal to differentiate the deprecated contract from the most current contract on BNB.
**TL;DR**
- Burn 5,000 “BSC” wZNN on BNB chain and send 100 QSR to AZ (verifiable proof).
- AZ releases exactly 5,000 native ZNN.
The ZNN in AZ are **the original BSC token counterparts** transferred to AZ custody upon deprecation – not ecosystem grant funds.
This proposal resolves supply redundancy/overcount via verifiable proof-of-burn.
**Background – The “BSC” Bridge & Exact Custody Transfer**
The old BSC bridge (contract: [0x84b174628911896a3b87fa6980d05dbc2ee74836]( Zenon Network: wZNN Token | Address: 0x84b17462...c2ee74836 | BscScan )) was custodial and deprecated in 2023.
When community members asked about remaining wZNN, Mr. Kaine confirmed (July 11, 2023):
> “Everything should be OK now. All remaining funds were sent to AZ. The community has full control over the funds.”
The transfer from the bridge custodian to the AZ address was executed on-chain: 97,444.67469346 ZNN transferred directly from bridge liquidity (z1qqs774auqksj94mtnes4qwvvzc8x8955en039j) to the Accelerator-Z contract (z1qxemdeddedxaccelerat0rxxxxxxxxxxp4tk22).
- TX: [Zenon Hub]( Transaction Details: Hash 9e8f5e58...6b1ab9d9 | Zenon Hub )
**Crucial Point**: The ZNN requested for release are **literally those original bridge counterparts** – the exact 1:1 match to outstanding “BSC” wZNN. They were never “AZ program funds” or general treasury.
The current state creates supply confusion and redundancy: outstanding “BSC” wZNN tokens exist on BNB chain, with their native ZNN counterparts now held in AZ custody. Since the native ZNN are no longer under bridge control (transferred to AZ), this results in an effective overcount of 97,444.67469346 ZNN in broader supply metrics. This proposal enables verifiable, decentralized release of the counterparts via proof-of-burn, eliminating this legacy redundancy.
Why Not Snapshot?
Snapshots would require arbitrary decisions and intervention. Moreover, a snapshot would not solve the supply redundancy – lingering “BSC” wZNN on the BNB chain would persist as unresolved debt/overcount. It exacerbates the problem due to post-snapshot trading: sellers who exchanged “BSC” wZNN for BNB and reinvested elsewhere could claim unintended benefits, while buyers of “BSC” wZNN post-snapshot would be denied resolution. A snapshot approach would attempt to rewind time, creating dilemmas antithetical to blockchain’s premise of immutable, forward-moving on-chain logic.
Solution: proof of burn verifies the claim. Timeless, future-proof, and fully on-chain.
Proposed Process
- Recommended AZ Template
-
After AZ Proposal approval in s y r i u s (prior to payout):
-
User will burn 5,000 “BSC” wZNN to the BNB blackhole address (0x000000000000000000000000000000000000dEaD) – fully verifiable on BSCScan.
-
Simultaneously, send 100 QSR to the Accelerator-Z contract (This is a pre-emptive payback to AZ due to AZ’s minimum 100 QSR payout requirement. (The effective sum total is 0 QSR).
-
-
Submit proof BNB chain burn TX + NoM QSR deposit here on the forum.
-
AZ releases 5,000 native ZNN (and 100 QSR payback) to the specified NoM address.
Future-Proof Design
Process in batches of 5,000 ZNN each (the maximum per AZ proposal). This is the initial batch – once established, additional batches can follow as needed. As long as the BNB chain exists, the mechanism remains available. No deadlines – pure opt-in, verifiable cleanup. Looking far into the future, if Zenon succeeds and ZNN reaches high value, holders of “BSC” wZNN will inevitably return demanding resolution (e.g., “I’m missing $500,000 – you stole it by absorbing into treasury or snapshotting to others”). This solution eliminates these problems by enabling direct, on-chain redemption, standing up to the highest external scrutiny through cold, verifiable logic rather than arbitrary interventions.
Benefits
- Releases precise counterpart ZNN upon verifiable destruction of “BSC” wZNN.
- Eliminates supply redundancy and overcount from legacy overlap.
- Clarifies accurate circulating supply metrics.
- Demonstrates AZ handling legacy resolution in a trust-minimized, on-chain verifiable manner.
- Sets repeatable precedent without arbitrary intervention.
- Supply-clarifying and fully verifiable.
- Prevents future disputes in a high-value Zenon era by honoring on-chain claims directly, avoiding accusations of misappropriation.
Risks & Safeguards
-
Low: Burn and QSR submission occur first; release only after on-chain proof. No new contracts, no new attack surface, no impact on remaining wZNN.
-
Low: There is the possibility that a bad actor could preemptively spam AZ and claim that every “BSC” wZNN holder address on BNB belongs to them. In order to prevent this, it will be prudent to create a new BNB address for a Burnback Relay proposal and keep that address empty and private until after submitting your proposal. (Don’t forget to later transfer your wZNN to that address before burning it.)
-
As per usual, the main risks are user errors. Users who feel uncomfortable with the process should not attempt a Burnback Relay. The option to sell into the wZNN/BNB liquidity pool exists, albeit with very thin liquidity which also requires great caution in order to avoid unexpected slippage.
Request
- 5,000 ZNN (exact bridge counterparts)
- 100 QSR (protocol minimum, will be deposited by proposer pre-payout)
This is straightforward logic – please vote in s y r i u s to approve the resolution.
Bridges burn, but the community never ceases.
