Onion Service PoW stabilization
This issue exists to collect notes about what is needed to stabalize Proof-of-Work for onion services. The TODO
for PoW is TODO POW:
. Current TODO
s are:
-
Implement disable_pow_compilation
setting -
Figure out what to do with pow_queue_rate
setting (do we need that setting? should it relate torate_limit_at_intro
?) -
Check that enable_pow
setting works assimply_update
(introduced in !2609 (merged)) -
Error if enable_pow
is set in config but feature flag is disabled (introduced in !2609 (merged))
Related issues:
-
#1676 (Limit number of tasks spawned for PoW solves)
Misc things to be fixed:
-
Merge all the hs-pow-*
/pow-*
features into a singlehs-pow-full
feature.
In addition to fixing the TODO
s, we will also need to do some testing:
- Ensure interop between Arti and C Tor works as expected
- Let people use it in practice and see if there are any reports
#1680 exists for writing shadow tests.
We may want to separate out client-side and host-side PoW and stabilize them at different times.
Edited by wesleyac