*https://github.com/snowblossomcoin/snowblossom/compare/73d721de683c...a6459188cbf0* https://github.com/snowblossomcoin/snowblossom/commit/a6459188cbf046f6fb042340af67d3e823296970 - adding title to windows *.bat files

Hot

[snowblossomcoin/snowblossom] Issue closed by tster123

[snowblossomcoin/snowblossom] Issue opened by tster123

Oh snap

@Clueless so I screwed up, on a mining pool where it adjusts the target to get about 1 share per minute, 1 minute metrics don't have much meaning

I think I'm going to make it 5-min, 10-min, hour

*https://github.com/snowblossomcoin/snowblossom/compare/a6459188cbf0...e09426630f57* https://github.com/snowblossomcoin/snowblossom/commit/e09426630f5788883a532bc37edb6d5344c3cd0a - Longer time period reports

*https://github.com/snowblossomcoin/snowblossom/compare/e09426630f57...bbfeb111ad24* https://github.com/snowblossomcoin/snowblossom/commit/bbfeb111ad24c4a22823bb4fcab38cc8cdf42cb7 - Report hash rates from miner

[snowblossomcoin/snowblossom] Issue closed by fireduck64

*https://github.com/snowblossomcoin/snowblossom/compare/bbfeb111ad24...a8193ddc826a* https://github.com/snowblossomcoin/snowblossom/commit/a8193ddc826af9691047b93f9e9e820abb64eb7d - Tracker votes with explorer

[snowblossomcoin/snowblossom] Issue closed by fireduck64

@Fireduck how about pool version and uptime too? and 15min, 1h, 24h averages instead?

1m, 5m, 1h

honestly, we can tear at random minutia a ton, we should probably have a meeting on what we feel is important for the framework next

1m means essentially nothing if that’s also the share difficulty target

it means something in the context

Yeah, the 1 minute was silly. Changed in code last night.

oh ignore me, I was on something else

i suppose the share difficulty retargeting could gravitate towards being an actual PID with minimal memory impacts, we already have the proportional and the integral there for ’free’

hmm, that’d also work for miner tunables like threads

What is PID in this context?

process id doesnt seem to make sense

Once this vote passes, I want to make release 1.1 with sip1 included

and that will be what everyone has to upgrade to for block 50000 or whatever it is

*https://github.com/snowblossomcoin/snowblossom/compare/a8193ddc826a...aaee6bf5512b* https://github.com/snowblossomcoin/snowblossom/commit/aaee6bf5512b1313062e55dba698a20ed9af4756 - fix test maybe idk

*https://github.com/snowblossomcoin/snowblossom/compare/aaee6bf5512b...a6b31fd2f7d5* https://github.com/snowblossomcoin/snowblossom/commit/a6b31fd2f7d57bd8938747ef7845b26157608813 - 1.0.7 release

[snowblossomcoin/snowblossom] Release -

*https://github.com/snowblossomcoin/snowblossom/compare/a6b31fd2f7d5...c16b76b7c365* https://github.com/snowblossomcoin/snowblossom/commit/c16b76b7c3654df4f52135b5dedabf5efa85926c - dev

@Fireduck If there's no objection, I have a deployment thing I'm working on. Basically it treats the jar files as more the "goto" deployment, and uses the exact same configurations. Not a big change, but should make it easier to support people, and installs more uniform.

I've already noticed a certain measure of users confused by documentation, varying install, varying config files, etc.

of course

don't confuse the shit out of the windows users

why did you remove the link to the windows release page?

me?

@Tyler Boone If you're asking me, it's because I consolidated things to here: https://github.com/snowblossomcoin/snowblossom/wiki/6.-Quickstart

which needs to be renamed to Quickstart, but I don't want to break fireduck's website link

I guess that means I need to upload the release zip to github

Ah, I see, that's right you did initially have the releases on your website. >.>;

if by initially, you mean always and still, yes

sorry, that's my oversight

if we didn't make it a little hard, no one would value it

for the moment, I'll fix the wiki to point to fireduck's website as well (first)

in the future, we'd automate it. I'm probably jumping the gun

@Fireduck https://en.wikipedia.org/wiki/PID_controller A proportional–integral–derivative controller (PID controller or three term controller) is a control loop feedback mechanism widely used in industrial control systems and a variety of other applications requiring continuously modulated control. A PID controller continuously calculates an error value e ( t ) {\displaystyle e(t)} as the difference between a desired setpoint (SP) and a measured process variable (PV) and applies a correction based on proportional, integral, and derivative terms (denoted P, I, and D respectively) which give the controller its name. In practical terms it automatically applies accurate and responsive correction to a control function. An everyday example is the cruise control on a road vehicle; where external influences such as gradients would cause speed changes, and the driver has the ability to alter the desired set speed. The PID algorithm restores the actual speed to the desired speed in the optimum way, without delay or overshoot, by controlling the power output of the vehicle's engine. The first theoretical analysis and practical application was in the field of automatic steering systems for ships, developed from the early 1920s onwards. It was then used for automatic process control in manufacturing industry, where it was widely implemented in pneumatic, and then electronic, controllers. Today there is universal use of the PID concept in applications requiring accurate and optimised automatic control.

the problem that solves is about the same as result sizing or mining throughput tweaking

@Fireduck Is the plowdb key "special/pplns_state"?

Hmm, that looks correct.

special/pplns_state : 2 -snow:

*https://github.com/snowblossomcoin/snowblossom/compare/c16b76b7c365...c741afe37051* https://github.com/snowblossomcoin/snowblossom/commit/c741afe37051b2f41494d6435ca83b7767ac1474 - redo peer info checking, change to 4 year block reward halving (SIP1)