There was an update on sentinel on block 124630 ~ 124650.
checking for boostlib >= 1.20.0... yes checking whether the Boost::System library is available... yes checking for exit in -lboost_system... yes checking whether the Boost::Filesystem library is available... yes checking for exit in -lboost_filesystem... yes checking whether the Boost::Program_Options library is available... no checking whether the Boost::Thread library is available... no checking whether the Boost::Chrono library is available... no checking whether the Boost::Unit_Test_Framework library is available... no checking for dynamic linked boost test... no configure: error: No working boost sleep implementation found.
I don't understand how qwizzie mixed that much, yet my liquidity provider apparently only managed to help with a single transaction (running with -liquidityprovider=1). All my test nodes appear to be staying synced properly, but maybe some tMNs aren't?
Hmm... Why would you expect ALL inputs to reach 8 rounds? Both wallets have 11 inputs 100 DASH each at 8 rounds, which is exactly 1100 DASH you see in private balance, so I'm not sure what's the problem exactly...Beside the amount to mix problem there is also a problem with the rounds, when i put the wallet to 8 rounds of mixing and it reaches 100%
not all input amounts have actually reached 8 rounds.
Hmm... Why would you expect ALL inputs to reach 8 rounds? Both wallets have 11 inputs 100 DASH each at 8 rounds, which is exactly 1100 DASH you see in private balance, so I'm not sure what's the problem exactly...
It's the other way around - it fills from the smallest to the largest. But the way it selects inputs later isn't linked to the way funds was split, it just tries to select _some_ denomination (that's why your smaller inputs also have non-zero rounds). Not sure why it overshoots, but this shouldn't hurtYou are right, i should not exspect all inputs to reach 8 rounds, only those input amounts that together would form the anonymized 1000 amount.
This means the wallet should mix a max of 10x 100 Dash, not 11x 100 Dash or 12x 100 Dash.
If i remember correctly from the past mixing, this actually means a breakdown towards 9x 100 Dash and the rest filled up by smaller amounts
like 10's and 1's .. which will then all end up getting mixed till they reach round 8.
Unless something changed in the mixing process and what is happening now is actually a desired outcome or feature?
Testing ... build 755, git commit eddfa5a
I have 890 tDash mixed.
Tried to send 705 tDash. Both PrivateSend and InstantSend.
I get this message: "Unable to locate enough PrivateSend denominated funds for this transaction. PrivateSend uses exact denominated amounts to send funds, you might simply need to anonymize some more coins. InstantSend requires inputs with at least 6 confirmations, you might need to wait a few minutes and try again."
Please translate that error message for a mere human. By the way, 700 tDash will go through just fine. As will 710.
I would assume that my bucket of PrivateSend included stuff denominated 10 tDash and greater and no .1's or 1's and hence the error. But that message doesn't tell me that. In fact, I am not really sure what it is trying to say. Heh.
I came across that as well a couple of builds back : https://www.dash.org/forum/threads/12-1-testnet-testing-phase-two-ignition.10818/page-6#post-106812
It is a bit of a bummer that certain amounts that are well within the boundries of my Privatesend Balance can not be used for Privatesend because the input amounts limits that somehow.