-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redeem 1EXoDus marker outputs #314
Comments
Unrelated to redeeming the dust, I'd also like to know how is in charge of 1EXoDus, because at this point it's not yet clear, whether this address may be whitelisted for alerts or feature activations. |
I am against using the Exodus address for feature activations at this stage - it's a single key and thus could be authorized by a single individual. I advocate for a P2SH address from the foundation which requires multiple board members as signatories. @CraigSellars has agreed to arrange this, I'm not sure where the progress is (I was going to raise it at the last meeting but unfortunately Craig wasn't available). |
I understood that to be part of the 'social contract' for the project (ie that Exodus UTXOs would be consolidated) & 200% agree it's time we started asking a bit 'louder' for that component to be honoured :) |
Right now there are 28181 unspent dust~ish outputs with a value beween 0.00000546 and 0.00018 BTC, with a total value of 1.0736786 BTC.
A transaction spending all outputs would have a size of more than 5 MB (unless I screwed up the estimation), and if not for the sake of retrieving that BTC, then they should be sweeped for the sake of cleaning the UTXO.
I would like to know who currently has control over 1EXoDus, and whether that person may be willing to clean up. I can prepare smaller chucks, which just need to be signed.
The text was updated successfully, but these errors were encountered: