Great work!
This is just what I was looking for.
Any reason not to run a Hive-Engine witness on the same machine as a Hive witness?
You are viewing a single comment's thread from:
Great work!
This is just what I was looking for.
Any reason not to run a Hive-Engine witness on the same machine as a Hive witness?
IP gets revealed. Would not recommend. I'm going to add that to my post. Thanks for reminding.
Thanks. So you need to run it on an IP that is OK to be public.
So it could be on the same machine as a Hive full API node.
Can you hide it behind a reverse proxy like you can use jussi to hide an API node's actual IP behind?
When you broadcast to enable, it publishes the ip and ports that are open(see ex: https://hiveblocks.com/tx/14e6c348ced9d4211ce8392bf413ba290c754bb2). I guess if you manually broadcast the enable trx(I was told you could do it at https://tribaldex.com/witnesses) and you have a setup that forwards the requests to the proper ports on your engine witness I guess it could work. I'm not really too good with networking stuff though so maybe try it out on an ip you don't care about. I can give it a try this weekend to see how it goes.