Login with Hive Keychain
Enter your Hive username to sign in securely.
Welcome to HiveComb
HiveComb runs on Hive — an open, decentralized blockchain where your posts, votes, and communities belong to you, not a company. To get started, follow these steps:
Create a Hive account
Set up your free account — it only takes a minute.
Install Hive Keychain
A browser extension that securely signs your transactions — your keys never leave your device.
Refresh & log in
Once Keychain is installed, refresh this page and click Login again.
Need help? Join our Discord and we'll help you get set up.
No account? Create one
Having trouble creating your account? Come to our Discord and we'll get you set up.
No posts found
Try adjusting your filters or wait for the worker to classify more posts.
No posts found
Try adjusting your filters or wait for the worker to classify more posts.
No posts found
Try adjusting your filters or wait for the worker to classify more posts.
Welcome to HiveComb!
Choose your default filters to see the content you care about most.
Languages
Categories
Sentiment
RE: HIVE developmet with limited computing resources: Tips needed.
Take a look at wax and workerbee, as those fancy tools already can do what you are aiming for :-)
Comments
1 commentWax looks very interesting and promising. Though I'm hesitant how I could fit it in without abandoning what felt like a clean design setup where I keep the HIVE specific code (including dual-signing pigybaging) inside aiohivebot and the blockchain agnostic code (mostly cryptographic primitives inclusing hash based signatures and least authority subkey management) in the coinzdense libs.
I'm definetely going to be looking into the project, and consider if there are posibilities for me to prevent code duplication without abandoning the curently envisioned split.
Report Misclassification
Why is this post incorrectly classified?