*https://github.com/snowblossomcoin/snowblossom/compare/75dbf36a5389...b50c4f336c78* https://github.com/snowblossomcoin/snowblossom/commit/b50c4f336c78adafac89d5c4f3e224e443e22445 - Update notes

*https://github.com/snowblossomcoin/snowblossom/compare/b50c4f336c78...ce7da0b37a2a* https://github.com/snowblossomcoin/snowblossom/commit/17347f7f9e7149c9ef32f692ce5c765bda49078c - Version 1.5.0 https://github.com/snowblossomcoin/snowblossom/commit/ce7da0b37a2a41600cf0a99ede9891c3661a2230 - Update notes

*1.5.0 - Purring Chains* • Adding benchmarking features to Arktika • Improve error logging in Arktika • Add terrible vanity address generator • Add terrible hole generator that is of no use • Added exceptions for invalid characters in address, previously would have probably been a checksum failure • Updated 'monitor' command to only print a new line when something is different • Added ability to send 'all' to empty a wallet • Update proto rules to new system, requires newer bazel • Add BIP44 based seed wallets • Switch default wallet type to BIP44 • Added 'import_seed' and 'show_seed' commands • Added dynamic fee estimation based on mempool • Notes for wallet type migration: https://wiki.snowblossom.org/index.php/Migrate:_Standard_Keys_to_Seed_Keys

the link on http://snowblossom.org for v1.5.0 points to 1.4.2.

yeah, fixed

top!

[2019-01-11 22:38:34] SEVERE io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference cleanQueue *~*~*~ Channel ManagedChannelImpl{logId=6, target=snowblossom.hamster.science:2338} was not shutdown properly!!! ~*~*~*

is this bad? getting this with client monitor.

that bullshit

you can ignore it

ok. i am ignoring it.

I'm not sure how it is happening, but I can't imagine it being a problem

i’ll still stick to 1.4.0

i know no fear. pool and node on 1.5.0 now.

as long as pools are running 1.4.0+ we are fine

if someone uses the tx out requirement feature a pre 1.4 miner could make an invalid block

errors seem to be gone after client and node are on the same version.

weird

there have been more errors but lazy me didn't bother to write them down.

I am not happy with the logging setup

it never seems to do what I want

I don't want people to be bothered by errors that mean nothing and are not a problem

of course. if there are SEVERE errors people tend to think something is not working as indented. :wink:

which is understandable

SEVERE to the developers of gRPC maybe

might even be SEVERE if you really needed the rpcs to work right every time

but this is p2p networking, so we don't require that at all

if it mostly works most of the time, that is great