The issue of address binding was discussed in the first AMA, and I’d like to clarify it again here.
First, the term “address binding” doesn’t accurately reflect its actual purpose; a more precise name would be “vote delegate”.
We still use “address binding”, however, because this technology applies not only to DAO voting scenarios but also to others—it’s a more technical, neutral term.
DAO voting is a serious process, much like the US presidential election: voting is a fundamental right of every citizen.
Under normal circumstances, everyone should cast their vote in person, and only those unable to do so due to physical or other reasons would entrust someone else to vote on their behalf.
Delegate is not a standard procedure, but an emergency process designed for extreme cases.
Bringing this back to DAO voting: currently, all wallets and locks supported by CCC can participate in voting directly.
The only users who face difficulties voting directly are early adopters who used Neuron for Nervos DAO operations.
For this reason, address binding now only supports Neuron (secp256k1) as the from side, while the other end of the binding—the to side—can be any wallet or lock supported by CCC.
By the way, this is also aligned with DAO 1.0.
for your questions:
- Neuron (secp256k1) as the from side, the to side can be any wallet or lock supported by CCC.
- Aligned with DAO 1.0.
- fix extreme cases.
- For new kind of locks, maybe a PR to CCC is better. Address binding aimed to fix extreme/historical cases not new features.