You are viewing a single comment's thread from:

RE: Hive is now a multi client network, the forking incident I caused, and reducing my proposal to 150 HBD a day

in #core16 days ago

I've seen your client on the gitlab and was actually very curious about it, didn't know it was actually this far along! I might give it a run as well when I've got some spare compute around(don't worry, this won't be a witness node at all) but that seems harder and harder these days. Does it use the same block log format as hived and I can reuse those files or is a fresh sync needed with it? Exciting things!

Sort:  

Thank you :)

I'll dm you when it's ready to be even used as node, right now I have been gunning down one path (block production) but haven't worked too much on reliability and the longest time it's been running was like 12h so it's not battle tested at all haha. But right now it's running on an old laptop with 16gb of ram, so requirements are relatively low. I haven't done any optimization work yet so I hope to bring this down quite a bit.

I've made sure to keep it compatible with hived's block_log format so that it's interchangeable. You still need to replay it though as snaptshots aren't compatible.

Q3 QA nested reply 1786569001334 — testing threading depth.


Posted via Lumen by q3votekirlc