Quote from: sunk818 on December 31, 2019, 06:28:21 PM

Quote from: bible_pay on December 31, 2019, 05:45:34 PM

Quote from: capulo on December 30, 2019, 10:27:18 PM

have some questions:
auto sendgscc is sent only at this height? "next_podc_gsc_transmission": 166767
so if i have wallet off and stat it later, it is not send?
it looks like this

second: i did some manual sents because of previous
tx id cfb2e2bf3ba18efbb07e9a1bb9e7c1549519b479e12bd445a3bd6f727df03146
but then i leave wallet online and autosenddid c8cf23f5e888ebe9628768fef5130ff51ee525422ff0f561099a793d5dccb175
it sent almost nothing, so when previous tx expired i disappeared from leaderboard
is this ok?

third:
can i set somehow that sendgscc will be send more times per day or send with specific amount at autosend height?

1) If you start the wallet after the exec rac sendgscc height, it will not auto send one.
2) We always calculate your coin-age-requirement based off of 'exec rac', so we will always calculate it correctly, so it should not send a .10 tx for wcg if you need a big reqt. That I believe is a bug that is being fixed this week (thats the same as the unlink bug). So, I believe you can scratch this one off when that liesure is released.
3) We have a key called 'dailygscfrequency'. This is set by default at 205. If you decrease it to 100 for example, you would send one out every 100 blocks. That might be what you need and will also handle most late starts.

If set dailygscfrequency=100 , does this have any negative impact on wcg points on the leaderboard at ll? I thought there was some warning about sending wcg too often?

Also, what happens to cameroon-one and kairos with this setting?

Since we add coin-age once per day, sending two per day is not a problem. I'm not aware of a warning, except for total network inefficiency.

With Cameroon-one nothing important happens, biblepay gets two records in per day, but we pay only once - off of the sum of the record.