Hive API Node for under $750 - Hive can scale at very low cost.
Recently @blocktrades revealed the specifications of a computer capable of running an Hive API node which can handle ALL of Hive's current transactions.
This is the result of dramatic improvements in the efficiency of the core blockchain code (hived & hivemind).
I was astounded at how moderate the requirements were:
- CPU 4/8 cores/threads 4.0Ghz
- 64 Gb RAM
- 2 x 2 TB NVME SSD
I confirmed with him that similarly specced PCs such as my current witness node could also run ALL of Hive's current traffic.
I've been saying in various comments that one can purchase a PC meeting or exceeding those specs for around $1000 and thought I should actually price things out.
It turns out that the basic components for a Hive API node cost less than $750!
You'll need to add a power supply and case (around $50) if you don't have them already from an older PC.
You can run the Hive API node headless and SSH in from another machine or use another machine's monitor and keyboard / mouse to get things running.
So for as little as $750 outlay anyone with a bit of technical experience can run a Hive API node.
This surely makes Hive by far the lowest-cost content-storing blockchain to run.
This means Hive can offer the lowest cost transactions to DApp developers sick of Ethereum's crazy gas fees.
It means Hive can scale and become much more decentralised, at very little cost.
I call on all witnesses who have decent internet connections to consider running an API node.
- The more API nodes we have, the more resilient we are to attacks by enemies of free speech.
- The more API nodes we have the more refugees from The Purge we can onboard.
I also call on the amazing developers of Hive who have improved efficiency by orders of magnitude to properly and simply document the process of setting up an API node so that it is easy for people with average technical skills to do.
Hive is the Bitcoin of content, social media and DApps.
It can be as resiliant and decentralised as Bitcoin too.
Please vote for my Hive witness. (KeyChain or HiveSigner)
Very interesting. What kind of traffic does the box see on a daily basis? I have been kicking around the idea of setting up a node, but I am not sure I would be able to handle the traffic. I think my connection is more than adequate, but I have a feeling my ISP might take offense to it.
Posted Using LeoFinance Beta
I don't have figures on how much internet traffic an API node takes as it depends on how popular it is, but I know that @techcoderx is running one on a fairly basic internet connection.
I wouldn't think it would use that much bandwidth at all because it is all text.
Images are handled by separate image servers and video is completely separate.
API calls are very small and the returned data is generally pretty small too (except for full account history). Even then it is just text.
A witness node is around 250GB-300GB/month, an API node much more (can be in TB if it is popular). Many home Internet connections have data caps and companies like Comcast are enforcing them pretty hard.
Posted Using LeoFinance Beta
Thanks for that useful data.
I had struggled to find it.
There is no capping on my fibre internet service and even monthly caps on 4G/5G mobile plans here are in the 250-500 GB range.
I'm a bit surprised how high you say the witness monthly bandwidth usage is.
I just checked both of my witnesses and one is averaging around 10% of "1 Mbps" (Windows) while the other is averaging around 40 "KiB/s" (Ubuntu).
Thus the Windows Witness is reporting 0.0125 Megabytes per second and the Ubuntu Witness is reporting 0.041 Megabytes per second.
Multiplying by 60 x 60 x 24 x 30 = 2,592,000 to get month usage this is 32,400 Megabytes per month for one and 106,272 Megabytes per month for the other.
I'm not sure why there is such a discrepancy but both measures are well below the 250Gb to 300Gb per month estimate you gave.
This is obviously excluding re-downloading the whole block_log which you should only have to do once.
already voted you as a witness, and not planning on removing any time soon.
Thanks.
That does sound VERY reasonable, but it also makes me wish we could spread out witness rewards a bit more widely to say 21-50, maybe even beyond - once you get passed 20 you hardly earn anything as I understand it!
Posted Using LeoFinance Beta
I agree. I think there should be a 22nd backup witness position that only backup witnesses that run API nodes are eligible for.
I don't know much about nodes/ API nodes or the difference but assuming it's a lot more expensive to run an API one, I think some kind of encouragement for witnesses lower down the order would certainly be good.
Posted Using LeoFinance Beta
!BEER
Just for the fun of it
I plan to see the possibility
to run a node one day.
Not too bad it show how decentralized
the system will be.
Posted Using LeoFinance Beta
Sorry, out of BEER, please retry later...
Hardware isn’t as much of a concern as Internet reliability is far more important. Home Internet is not adequate to provide a reliable witness or full node.
I totally disagree, unless you are referring to a "standard" home setup.
You can run what you want out of your home. What do you f@cking want from home? What do you want, a T1? lol
I know you get what I mean. You want a fixed IP, you contract it, you know what I mean? You can contract the bandwidth and redundancy you like, as long as you don't live in the middle of nowhere.
Or was that what you were referring to?
A T1 is slow and super expensive compared to standard home Internet. More importantly though is home Internet is not very reliable and any hiccup will cause a node to have to replay for a few days.
I cannot believe you're spouting this crap. Do you even know what a T1 is? Don't you get a joke? And then you come back and treat that like it's something serious to be debated! Obfuscation? Sorry that my joke lent itself to that - I should have known better. (But you could even get the job done with a T1, as long as your not living at the last mile, anyway, but let's forget about satire and try not to get distracted on the irrelevant and impertinent).
So anyhow, how about fibre optics? Have you heard of that where you live? What kind of "hiccups" are you referring to? The town where I come from gives me the same reliability that any data center could have, or are you saying that second line redundancy is actually necessary? Seriously? (My redundancy statement above was also a joke on that level.)
The idea is that you can do what you damned well please from home, all you have to do is contract it. Again, unless you live in the middle of nowhere . . .
My God, I'm appalled at your remarks, your negativism, and total lack of cooperative attitude. Simply stunned! Instead of snide, discouraging remarks, how about something constructive, like, for example, some specific specifications you might recommend? How about sharing the info on what you have? Or are you on a rented, centralized, out-of-your-control shared data server?
A T1 is 1.5Mbps, slow compared to what is available for home use for a fraction of the cost.
I thought you were serious.
Yes, I used to have Fiber, I have 1Gbit now, nearly the best you can get for a home and I wouldn't host a witness or full node on it due to reliability.
What reliability issues? Power outage is the most common, bad weather and we lose power. This typically happens 2-6 times every winter.
ISP issues, this usually happens once and a while, not too often but sometimes. Again, any problem and the node requires 3-4 days to replay and will be down for this entire time.
Seriously?
You got all that from me making a very factual and accurate observation.
I did, not home service. It's pretty simple and easy to understand and well known in the witness community. Home Internet is unreliable Home providers are low priority for carriers and most homes don't have reliable power and back up power. Add in the fact home workstations are not as reliable as server class hardware.
You seem to be really bothered about all this.
Please stop with your distractions - I don't know why you continue to "educate" us about an obsolete T1 after finding out it was a joke, or continue talking about vague ISP "issues" that you don't specify, or power outages! Power outages? Is that the best you can come up with? Can you say UPS? Hellooo? Give me a break! And then a 1Gbit symmetrical connection wouldn't be enough for you!?!?
Let me help you focus. The only thing you talk about are vague, boggeyman negatives. (Are you catching the drift on why your remarks bother me? And what bothers me even more is that you were happy to leave your first comment at that!) So, let's really try to focus:
And so what?
What does it matter to you?
Based on all your hypothetical threats which you make no effort to describe and less effort to recommend prevention methods, the node would have to do a 3-4 day reply (which, BTW, to my understanding, is being drastically reduced as we speak . . .).
And so what?
What's it going to do? Bring the network down? 🤣
UPS don't outlive power outages caused by snow or any weather related outage. UPS will give you 2-5 minutes on a powerful system, maybe 15-20 minutes with no monitor attached and a huge battery.
Actually they are very real realities.
Again, you fail to actually understand. Witnesses are here to protect the blockchain, sure you can use a snapshot in get back up and running in an hour or two, but during a hard fork and an emergency you won't have snapshots and will need to do a full replay and it is critical that core witnesses are back online as fast as possible.
Posted Using LeoFinance Beta
And so what?
Let's see if I can help. So what if one node goes down for 72 hours?
An API Node? Not a huge problem, although it could be critical to some apps that don't handle the failure well.
A witness node? That will destabilize the Hive network. A top 100 witness is not that big of a deal as they are only producing blocks every hour or so but we barely have 50 reliable witnesses if that. As you go up the ranks, you are depended on to produce blocks more frequently.
Posted Using LeoFinance Beta
Ah, finally, we get to something specific. Why was it so difficult to reach this point?
And there are solutions for all this too, but since that would mean a couple of trips around the sun, I'll pass.
And, with you just having insulted me in your comment before this one, I've signed off with you anyway.
Best regards,
oh yeah, you were a pleasure to talk to right from the start...
Go buy a mirror.
You fail to address the issue. You continue to obfuscate. Everyone knows what the specs are on a UPS. And no-one would put up a server where you have anything other than 2-5 sec. occasional (like once or twice a year) outages, but you make it sound like it is common place for the vast majority. What's your motivation for doing that? I can only say to obfuscate, to beat around the bush, to avoid addressing the main issue, which, in this case would be justifying your boogeyman issues for not putting up a home based node.
Your example of the completely unrelated hard fork "emergency" is more of the same. What next shall we talk about that has nothing to do with your original, oh so empowering claim?
You would know best mate, I'll leave it to you.
On a secondary note - so as to not confuse ourselves any more than necessary.
Anyone who considers the three words "not home service" to be a constructive example giving specific specifications for recommended minimum connection requirements really needs to have their head checked. Sorry about being so blunt, but it's the truth. At minimum you'd need to ask yourself the hard and fast question of "what are you really doing here?" with that kind of input. What's your intention with that kind of demagogic negativity? And it's not once, but TWICE that you've put forth the same thing with what seems to be a clear intent of trying to "just leave it at that".
Constructive cooperation helps people move forward. All your comments on this thread serve to hold people back.
Most people that have any clue about technology under stands what home service means when referring to Internet connectivity.
Blunt? you kind of had a temper tantrum.
Let me guess, you are the poster child for Constructive cooperation?
Posted Using LeoFinance Beta
As if I didn't.
As if that was what this conversation is all about (I simply stated a general truth).
Ask yourself how you're doing on constructive cooperation in this thread instead of making a insidious personal attack on me. What do you think? I guess that when you have no rational argument with which to back up outlandish claims, you don't have any other option but to get personal.
Sorry, but I won't go down to that level. I'll stay with the issue and continue to press for answers based on logical reasoning complete with specific recommended specifications - a "no you can't because I said so" doesn't cut it, in my opinion.
You can poke fun at me in an attempt to undermine my arguments, but, be sure, to the wise and understanding, i.e. the vast majority, they see that exactly for what it is.
Good day to you, and I'll be looking forward to talking to you again, another time, in another thread . . . maybe . . . since it's impossible to get useful answers and productive engagement from you, perhaps not. In any event, rest assured, it's nothing personal. Cheers
Marky smart smart smart smart smart.
Rent a server is cheaper anyway. Energy, computer power + connection are cheaper than ever :)
Posted Using LeoFinance Beta
Also much more centralized and haven't we learned what happens when you host on CENTRALIZED servers!?! Nothing good..
Nodes are generally not run on VPS units but dedicated servers, so they can't be centralized. Data centers can be though.
makes no sense. Sorry.
This is a gross generalisation and based on my experience is simply not true.
I have had absolutely no internet problems with my witness and plenty of other people are running reliable witnesses on home internet, even on 4G mobile.
Of course there are HUGE differences in quality of home internet and some home internet may be too unreliable.
Reading your comments below the main issue you seem to have is power outages (2-6 times every winter). That is terrible power reliability and is not typical.
External power outages where I live are so rare I'd say once in 3 years is typical.
My new backup witness will be a laptop with the ability to change internet connection to 4G, neighbour wifi or even city wifi in the event of a power outage.
Secondly, the new snapshot facility means you do not need to replay a node for every outage. I can generally have my witness up and running within 20 minutes of the machine going down (and I have auto-switching to a backup).
Thirdly, the whole point about decentralisation is that having lots of people run nodes means that individual nodes DO NOT NEED the ultra high uptime that data centers provide. If one API node is down front ends auto switch to others.
For an API node, I agree, for a witness node I disagree. Every time a witness misses a block, it has to be passed on to the next witness and puts the chain at risk.
Glad you agree on API nodes because that is actually what my post was about. :-)
Hive has enough witnesses (although more is always better) but does not have enough API nodes because people think they are very expensive to run.
The specs required to run a witness node are so low these days that you can run a backup witness on a 9 year old laptop (admittedly with 8Gb RAM and 500Gb NVME SSD and i7 4 core - my old Macbook Pro was a beast in its day).
A laptop is the poor man's uninteruptible power supply and 4/5G or alternate wifi (neighbours) can provide internet redundancy.
That's my bad, I know you run your witness on a workstation and assumed it was the same thing.
I disagree, we have far fewer witnesses than we did on Steem and very few who really know anything more than getting the witness up and running, which is just following some instructions and typing in a few commands.
Sure if you don't mind missing blocks, oh and I know the answer is going to be "But I haven't", performance of a top 100 witness is vastly difference than the requirements of a top 20, the higher you get the more demanding it is.
I agree that the level of knowledge about witnessing and running nodes needs to improve and broaden.
This is precisely why I am both calling for far better documentation by Hive devs and encouraging people to run nodes on owned equipment, physically located with them.
If you have a witness running beside you at your desk and you can see the logs running all the time (and immediately when they go down) you are much more connected to being a witness than having it run on some "cloud" server somewhere.
You are more likely to learn how it works. That is certainly what I am trying to do.
According to @someguy123 you can even run a witness on a 4Gb RAM machine.
8Gb RAM with a 4/8 core CPU should be plenty sufficient for a backup witness.
My main witness will have 24Gb & 6 core CPU and my API node 128Gb and 6/12 core CPU & 2x1Tb RAID0 NVME.
Why do you suggest that I would be missing blocks with this setup if I made it to a top20 witness slot? I can always add a second backup witness node to provide further redundancy if necessary. I've got heaps of PC parts lying around. :-)
I disagree, I can see logs from anywhere in the world at similar efficiency. While I am not against having your own equipment what so ever, I do have concerns running critical servers on a home network. Granted not everyone has to deal with snow I won't run even simple services like Poshbot on my home network as I don't trust a home connection being available. This is just my own opinion.
I see no problem with that hardware, but you did mention a 9 year old laptop. The thing is, running a witness is a lot different than replaying one. While we do have the ability to do snapshots now, it can still take hours to transfer block logs and snapshots even with 1 Gbit Internet connection. The real problem comes during hard forks and emergency patches, you won't have a snapshot to rely on, and will need to do a full sync, witness nodes and API nodes.
Most witnesses are no where to be seen when critical shit happens, the witnesses that are and have the hardware, Internet, and knowledge to support agile recovery are who I want protecting the Hive blockchain. Unfortunately, this list is rather tiny and doesn't reflect in the witness rankings.
Posted Using LeoFinance Beta
Of course you can see logs from anywhere in the world, just as you can do Zoom calls with anyone in the world but my point was not about efficiency.
My point was about physicality, commitment, and the "in-your-face" rather than "out of sight and out of mind" aspect.
You are right that a lot of witnesses just set and forget and some don't even notice they are missing blocks for days or weeks.
It is precisely because they are using far away rented servers that they have less commitment and interest in learning witness skills than if the witness node was living with them.
I keep my own backups of block_log and do my own snapshots which I can transfer to whichever Hive node needs them over my Gigabit Ethernet LAN. Even the 330Gb block_log only takes less than one hour to transfer.
While I agree that the ability to replay is also important for hard-forks and emergency patches, replay speed is NOT about internet connection or where a node is located.
Its about single core CPU performance, RAM and I/O speed.
The fact is that the machine I specced above will beat 90% of servers in those factors.
In particular, server CPUs generally have a large number of cores but relatively poor single thread performance. High end desktop and gaming PCs by contrast generally have fewer cores but much better single thread CPU performance.
Regarding knowledge: if you want more people to have it then more effort needs to be made to spread it.
While I have got great assistance from people like @someguy123, @deathwing and @rishi556 the availability and accessibility of documentation on running Hive nodes is quite poor and out of date.
This is something that really needs to be remedied. There needs to be an Idiots Guide accessible on all major front-ends and hive.io.
I disagree, I don't think that has anything to do with it. Granted if someone buys hardware they likely care more about Hive than renting, but correlation is not causation.
I will agree this is far easier on your own LAN.
Yes, but that wasn't my point. My point is you cannot rely on snapshots, especially when a witness is needed most (during hard forks and chain down events).
Regardless, I have no problems with running an API node on a home network if you have the resources to do it, a witness node I am not so agreeable about. I merely was saying the Internet is more of the critical factor especially as the chain gets larger and providers make their data caps smaller.
Wow, I'm not going to take the time to count them, but what would you say, 20 comments or so to get to this point?
I'm so impressed that I'll ask you for the same information once again: can you share what you think those necessary resources are?
Edit: please forgive me if you've already laid them out - I got tired of getting lost in your maze and stopped reading but did want to see how you ended things. Even if you have, maybe you might consolidate your thoughts and dedicate a of post of your own on the subject? Remember, focused, with a title something like: Running an API Node from Home. ;-)
Good job on all this, but I think it's very clear that there is heavy resistance to the idea (you can bet that more than one have been following this thread closely, and they've probably got Discord burning hot!), and that this is going to be a long haul marathon. To be honest, I wouldn't be surprised if you, and a few others too, might just end up being who does the documentation. Lots of work, but it'll be worth the effort. Count on me to help in any way that you think may be useful and possible. Maybe you might want to start a "Documentation Community". It's an idea that came up the other day on one of @taskmaster4450's threads. It might seem a bit like overkill, but it's really the only way to have admin control to be able to manage, update, and, ultimately control the content, and it seems to me that with the importance documentation carries with it, administrative control is absolutely necessary. Food for thought, and thanks for taking the lead. This is really good stuff. I, for one (and I'm also absolutely sure - on this one too - that I'm not alone on this), am lapping up every bit of your contributions on the subject! 😋
I admire your persistence and patience (I can't even bear to continue reading more of that "wet blanket power" - don't have the patience or the time). You're definitely doing the right thing and thank you so much for your efforts. My "reality check" response fell on deaf ears, but was nonetheless very revealing and worth taking note of. In my opinion, what you are proposing is a key step forward that we must take, it's in our own best interests, and we must press forward in spite of whatever resistance that may arise, no matter how great (or small) it may be. A big thumb's up!
I don't think he means to be a wet blanket, he just comes from the perspective of a professional IT guy.
As a profession they have become far too used to using "cloud" services.
Its easier, more comfortable, easier to scale (for centralised solutions) and no one got fired for using AWS or other "cloud" based solutions.
But what is sacrificed is control, independence and higher costs than buying and running you own equipment.
There are also substantial dis-economies of scale with massive data farms - George Gilder has written about this in "Life After Google".
Also there is a loss of hardware technical skills, although @themarkymark is impressive this regard.
Now the chickens are coming home to roost for those that want independence and free speech.
It isn't about cloud as much as Home data center vs real data center reliability.
And there you go again. It has nothing to do with "reliability". If anything clear has come out of this "conversation", it's precisely that. Or haven't your realized that you agreed that for an API Node . . .
How tiring . . .
It has everything to do with the IT professional in charge (and, of course, and this is without question, that means, by definition, having PHYSICAL ACCESS), and his or her systems and connectivity solutions contracted and implemented.
But nooooooooooooooooooo.
I've never been so infuriated!
Next you'll be telling us that Bitcoin wallets are better stored on data center shared servers (head's up: that's a joke that's meant to be an exaggerated extreme to try to make evident the obvious in a funny way, which means that a pedantic response on that is not necessary - save your breath).
You sound like you have lots of friends.
And that's all you have to say.
Says a lot, don't you think?
(And I mean that seriously: all your arguments summed up in one nice little phrase. Or do you think serious issues are for brown-nosing only? Are you serious? This is about making friends?)
Nah just got tired of your dribble.
Hahaha. You don't even get it.
Anybody and everybody can clearly see that your previous comment was nothing more than yet another personal attack.
In spite of all your efforts to the contrary, you've actually done a wonderful job expressing yourself with absolute clarity.
I've said all the "dribble" I have to say on the subject, and it's here to stay, for all to see, forever, on this immutable blockchain, and, given such, 'I rest my case'.
I used to work in IT, and I would say that anyone relying on cloud services for sensitive data is not a professional (even though all the "kids" do it - hey, we live in a world where a 100k hack is solved by "printing" more tokens - not serious at all). This is my opinion, no doubt about it, but with the cybersecurity issues we ALL know about, I never ever had a client's sensitive data in the "cloud". NEVER! Not even backups. That's all done ON SITE, and multiple locations if the data is extremely sensitive.
To be honest, everything I've heard here on his part sounds extremely "amateur". Sorry, but that's my take on what I've seen him say (and how he's said it, etc., etc.).
Troll Alert: Warning, the following is strictly trolling now:
No! Your bad was your totally flippant and outright dismissing of the entire post!
Remember?
And then you continue by ending your comment with yet more negativity totally absent of possible solutions . . .
How apropos!
/end trolling
You are not even a good troll at that.
Thank you for the compliment . . . even though I'm sure that wasn't your intention. 🤣
And that's what I think is THE point this person wants to avoid, or doesn't realize exists, and I'm not sure which is worse (even though lower he does talk about it with you).
Look at what it took me just to get him to talk about the number of witnesses! Amazing! I'm flabbergasted. And he is a top 3 witness.
(Well, maybe all that is not so surprising . . . depending on how suspecting of a mind one may have.)
Glad to see you got him focused. He finished with my by insulting me.
I second that!
(Instead of happy-go-lucky, piss-on-your-parade comments.)
They don't program anymore on Hive.
There are more blockchain and app devs on Hive than Steem and Blurt combined.
Posted Using LeoFinance Beta
Congratulations @apshamilton! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s) :
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPoh, ok, go on then -...I'll vote for your witness thingy! lol
Thanks.
I think all under 200$ a month for rent + host is super cheap API Node.
Longterm I think hive doesn't need to become cheaper, it needs more onchain applications. Like Smts and smart contracts. And if things slowly become more expensive, there becomes a need to get cheaper again. With the Top 20 Witness setup, we don't need a Home computer set up to Host Hive. That's why they earn something from inflation.
Compare to the price from one Asic for POW, hive is super cheap to run.
Posted Using LeoFinance Beta
BLURT can run on much a less, in fact a Raspberry PI! A lot cheaper, and a lot smaller footprint!
With thousands of Raspberry Pi node users around the world, that would be a better idea for a more decentralized social platform. Can Hive upgrade to do this too I wonder?
Raspberry Pi's IO poor, especially to SD card.
Did Blurt ditch the Steem blockchain history?
The Hive blockchain is 330Gb - not something that a rPI can handle.
If Blurt is successful it will end up with a very large chain too.
What code changes did Blurt make to be able to run a node on an rPI?
Raspberry Pi's are atrocious at SD IO, the Pi 4 made a big improvement, but it is still bad, especially if you don't use a Samsung EVO+ (the best performing SD card by a long shot on a Raspberry Pi).
But anything serious I'd highly recommend just using an SSD drive, you can get one for about $30 and be 100x faster.
Some tests I did. Using something other than a Samsung EVO+ would have been much worse.
Maximum performance out of the Raspberry Pi 4 with an SSD drive
I'm planning to run the jussi for my API node on a Raspberry Pi 4 with 4Gb RAM and SD card.
Is this sufficient in your view or should I add a SSD on USB?
I have both the cable and SSD drive but understood jussi just used RAM for cache and didn't really do IO.
It will mostly be cpu/ram so I don't see a huge difference /w SD vs SSD outside of management time (and reliability on power outages as SD corrupt easier).
You can get a 250G SSD and cable for around $40.
No it can't. Not since it was spammed and is now over that threshold.
(There is a post about this by the Blurt dev, they are building a new chain now)
They also started the chain from scratch, if Hive didn't bring over state, it would be able to as well.
Posted Using LeoFinance Beta
https://twitter.com/Bhattg18/status/1351382900072017922
Are you running yours from home?
I was semi-contemplating running a node on my tiny little desktop "server" (it's actually a NUC) with more than enough specs to run my low traffic webservers and possibly the Minecraft server if I could be bothered moving that but looks like it's nowhere near enough to manage a node.
I am running two Hive witness nodes which is soon to become an API node and two Hive witness nodes. All from home.
For the API node I'll run jussi (reverse proxy server) on a Raspberry Pi 4 running on a different internet connection.
If your NUC has at least 8Gb RAM and at least 500 GB SSD and a 2/4 core fairly recent CPU you can manage a witness node though 24+Gb RAM and a better CPU with decent single core performance are recommended if you want to be able to replay.
I am still thinking about running my own API node. This post may have encouraged me to actually do it after all :D The current constraint for me right now is still time. Once I find enough of that I will definitely do it.
Anyways, great to see that running an API node has such low requirements. I am looking forward to seeing a post about the actual performance of the node.
!gif hive
Via Tenor
How am I supposed to convince my gf I need a Threadripper now... lol
By telling her you can make money as a witness and buy her nice things with it. :-)
Good info but what incentive is there to run an API node - will I be rewarded with Hive?
Not directly but you are more likely to get votes for your witness if you do.
More witness votes gets you more Hive Power as Producer Rewards.
Also, if you run a DApp you are guaranteed better performance if you run your own API node.
https://twitter.com/alientoblog/status/1352412953455124480