selsta
selsta
@tobtoht you worked a lot with wallet2_api, what is your opinion here?
Developing a new wallet implementation sounds like significantly more work than the API itself, why do all this work but then inheret an unmaintained and buggy API? It seems like...
I can open a PR to bring the checkpoints up to date, and in the future always open 2 PRs to update checkpoints (one for master, one for release).
Increasing the number of out peers has an impact on privacy and network topology. We won't do any changes to it without corresponding research. The bandwidth limits could be increased...
Can you add more information to what you are asking/suggesting?
Did you rescan your wallet? Is this a multisig wallet?
Does the receipient show up when you submit a transaction and not rescan the wallet?
Closing due to lack of reply.
What is the benefit of using SAM over our current I2P implementation?
Can you explain how the current implementation is "built for" i2p-zero or link to i2p-zero specific code?