Question about RPC and wallet parameters.

[tumblingman]

Hi guys!

I'm writing a Go RPC client for your wallet and manager to control CoinJoin rounds. In brief, here's the case: there's a hot wallet receiving payments to various addresses. Automatic CoinJoin is disabled on this wallet. In situations where network fees are below a set threshold and a specific amount accumulates on the wallet, a CoinJoin to a cold wallet should be executed in a single round.

While writing code and testing I had a number of questions:

1. After executing the startcoinjoinsweep method, when all coins have moved from the hot wallet to the cold one, and CoinJoin has been completed, will it continue to run when new coins arrive on the hot wallet, or do I need to start it again?

2. During tests, with auto-CoinJoin enabled on the hot wallet (though not meeting the amount criteria), after executing startcoinjoinsweep, the round was successful, all coins moved to the cold wallet, but getwalletinfo on the hot wallet started returning "coinjoinStatus":"In schedule" - what does this mean?

3. What should the listpaymentsincoinjoin method return? Could you provide a JSON example? Looking at the code, it seems I should see transactions with the status Finished, but with completed CoinJoin rounds, both hot and cold wallets respond with an empty array for this method...

4. During the CoinJoin process, will I see coinjoinStatus in both wallets or only in the hot one?

5. If I interrupt CoinJoin in the In progress status, can the coordinator block me? Or am I causing harm to other participants only if I interrupt in the In critical phase status?

6. When executing getfeerates, I get a map where the key is the target number of blocks, and the value is the cost in satoshis/byte, right? If yes, how does this correlate with the parameter in my hot wallet "FeeRateMedianTimeFrameHours": 24? How does this FeeRateMedianTimeFrameHours parameter work?

7. What is the parameter in the wallet "CoinjoinSkipFactors": "0.7_0.8_0.9"?

8. How is my share of the transaction weight calculated precisely? Can I at least estimate it? All my source addresses are segwit, and the target is 50%/50% segwit/taproot. This is important considering fee level fluctuations so that I can temporarily stop CoinJoin.

9. When (theoretically) could the setwalletinfo method be introduced? It is crucial to have the ability to modify the values of the following parameters through RPC: MinGapLimit, AutoCoinJoin, AnonScoreTarget, FeeRateMedianTimeFrameHours.

Thank you in advance for your help!

[MaxHillebrand]

I'm glad you're playing around with the RPC, thanks for the feedback!

---

3. listpaymentsincoinjoin only lists the "currently not yet paid" attempts.

4. The cold wallet does not know about the coinjoin process, so coinjoinstatus is only in the hot wallet.

5. I believe the big trouble is only in critical phase.

6. Fee rate median time frame is about what is the median fee rate of the last X hours, and if the current cj fee rate is higher than that, the client does not coinjoin. This is a "relative fee rate sanity check".

7. The coinjoin skip factor randomly skips registering to a round with X propability, so if it's set to 0.01, there is only a very small chance to register the next round.

8. The fee rate depends on exactly how many inputs and outputs, and if they are segwit v0 or v1. All of these are random choices, so it's not possible to predict your exact fee rate usage until after output registration.

9. That sounds like a good feature request, I've opened an issue here, stay tuned. [RPC] setwalletinfo command #12238

---

I don't know more details, so pinging @lontivero for the other open questions.

[tumblingman]

Thank you very much!

If it's not too much trouble, can I ask for clarification?

Regarding the sixth question - if I call the getfeerates method and it returns {"2": 30}, what does that mean? Am I correct in understanding that 2 is the estimated number of blocks, and 30 is the fee in satoshis per byte?

[MarnixCroes]

correct

[tumblingman]

Thanks!

[MarnixCroes]

FYI, I wrote some docs about these.
They are still a PR and not on docs website, as it is not yet in a release
You can find some here https://github.com/zkSNACKs/WasabiDoc/pulls

[tumblingman]

Oh, this is what I need! Thank you so much!