Aaron Li
Aaron Li
I triggered recovery at `0x523f15fb6f2a1fbe256ff7e601d0d6b7b04655ab`, which sent all funds to `0x5Ca3220D2C54Eb5582B5fe9c0143A5492D500112`. To recover the funds in there, we need to use 1wallet multisig to trigger the next recovery function. I...
click confirm? we can recover some time next month. But there is only 100 ONE there
Can you post all your addresses? Recovery through "1wallet DAO" is a public process and requires multiple signatories to approve. It will also give others some time to challenge this...
This will be addressed in a few weeks
1. No. After expiry the smart contract no longer has the ability to check the code 2. Yes, ideally it is an address that originally sent funds to the (expired)...
Yes, there is a way to use your recovery wallet to control the expired wallet to do anything, though this feature is never exposed at the UI. I can implement...
I reviewed all these addresses. Technically, we can recover the funds, though it seems to be a lot of work to just recover less than $50. Can you provide some...
Since there are so many, and the amount is small, I would rather do this after another feature is implemented, which allows read-only access to any wallet in the UI....
Yes, even some periodical auto-discovery functionality would help a lot.
I have to switch back to Java client (lettuce) because of this. My project requires robust, dynamic cluster support. Perhaps we can implement something like what they do here https://github.com/lettuce-io/lettuce-core/wiki/Redis-Cluster