Witness Update
As many of you know I'm the lead developer for HoneyComb, which is a Hive Layer 2 solution for smart contracts. This is currently powering Decentralized Limitless User eXperiences, dlux.io, the Speak Network Claim Chain and Ragnarok backend DUAT. Our Layer 2 currently has over 100 registered nodes and this is only likely to grow. To help alleviate some of the demand on the current public nodes I've set up a Hive Witness with Account History and Transaction Status. This is no small piece of hardware:
Dedicated Server with
- 8-core AMD Ryzen 7 3700X
- 64G DDR4 RAM
- 4x 1TB SSDs each on their own NVMe
- 1gbps network
This has been purring along nicely for about a week, but my current node was still experiencing some issues of it's own. I'll be bringing up a backup Hive node to sign blocks and when that's stable I'll release the API details of this dedicated server.
I've also heard some rumors that the setup of this API will be changing with some new software on team @blocktrades ... Implementation of this may also impact the release of the API details... hopefully for the better.
As always I thank you for your consideration for your witness vote.
SPK Update
I've been working on building out the multi-token ecosystem and the Proof-of-Access reward system for the decentralized IPFS storage protocol. The communities vision is becoming reality every day. I'll be back on Cryptomaniacs podcast on the 28th to talk more about our progress; and I expect to release some more technical details here shortly.
These are not bad specs! But is 64 GB RAM enough for a node? I have the impression to remember vaguely that in the past with Steemit more like 128 GB were needed for a Witness node =)
There has been some work done on the base code to help push data to the hard disks. Check out the current usage.
# free total used free shared buff/cache available Mem: 65761476 4690116 427336 22666552 60644024 37679884 Swap: 33520636 1252096 32268540
# df -h Filesystem Size Used Avail Use% Mounted on udev 32G 0 32G 0% /dev tmpfs 6.3G 1.1M 6.3G 1% /run /dev/md2 1.8T 1.3T 393G 78% / tmpfs 64G 22G 43G 34% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 32G 0 32G 0% /sys/fs/cgroup /dev/md1 989M 174M 764M 19% /boot overlay 1.8T 1.3T 393G 78% /var/lib/docker/overlay2/id/merged tmpfs 6.3G 0 6.3G 0% /run/user/0
Interesting, thank you for the detailed answer! I just voted for you as a witness =)
Thank you for your witness vote!
Have a !BEER on me!
To Opt-Out of my witness beer program just comment !STOP below
Thank you! =)
View or trade
BEER
.Hey @grider123, here is a little bit of
BEER
from @isnochys for you. Enjoy it!Do you want to win SOME BEER together with your friends and draw the
BEERKING
.We don't require anything like the memory that Steem nodes need nowadays.
Thank you for your reply. That is great to hear!
keep it up steve!
p.s. Ive forgotten how to get to the larynx claim page. Can you put a link on the dlux homepage or is that not appropriate?
it's currently at vue.dlux.io/dex and you select the larynx token... It'll be on the live site shortly... @markegiles has been busy :)
@disregardfiat i open a 1000 hive order to buy spk. But in order book only HIVE: 269.99 show up.
Is something goes wrong?
Sent to spk-cc-1,000.491 HIVE
4 minutes ago
{"rate":0.00357,"hours":720}
It looks like everything is fine. The multi-sig wallet takes about 10 minutes to clear, and there were some collateral limits.
collateral limits were the problem :D All fine, thanks for the fast reply :P