Hoosat Vote: A Fresh, Purely On-Chain Contender in Decentralized Governance for 2025

https://medium.com/@toni.lukkaroinen/hoosat-vote-a-fresh-purely-on-chain-contender-in-decentralized-governance-for-2025-cfaa6d32272a

🦉Possibly HF level voting platform issue in node. 🦉

@everyone I have realized there is issue in the voting platform. If you try to use longer than 64 character inputs. The node uses Shannon entropy of the inputs to check that the data is not binary or encoded data like base64 or hashed. But I've used way too low Shannon entropy as the maximum. As typical human text is around 4 - 4.5 bits and I've put a limit of 2.5 bits.

So for now. In the voting platform please try to use repetitive words or shorter than 64 character texts to avoid hitting the Shannon entropy checks.

I'm not sure at the moment if this maximum Shannon entropy bits change would be soft or hard fork level update, but if we increase the limit the nodes can be updated in any possible manner, it's just that those who don't update will not accept the voting platform transactions.

I will think about this more after Christmas and we can have slow ~30 day update time to allow more data in the voting platform polls.

[HTN] Should Tonto stop addressing FUD?

@everyone should we just tell those who spread FUD about HTN that they can come to the voting platform, create polls and see what the community thinks.

https://vote.hoosat.net/polls/99ffc6c1c4931f19d00884a84ae8dad83674eb49e7f8c29f64829c8a19f9527c

Start Date 19.12.2025 klo 16.25
End Date 28.2.2026 klo 16.25

[Voting Platform] Increase price to create poll?

@everyone should we increase HTN Voting platform poll creation price?

https://vote.hoosat.net/polls/88aa4899627a4975bc2e067ad3d33c6b8ec65252b8d2f162009e03db3284d856

Start Date 19.12.2025 klo 16.09
End Date 28.2.2026 klo 16.09

🦉HTND 1.6.3 released 🦉

This release brings small hard fork at DaaScore 123_956_218 to increase 0x03 subnetworks data Shannon entropy check max value from 2 to 4.5 to allow natural language in the data. Additional update is lowering the LRU cache sizes and Pebble cache default size to 1GB from 8GB to decrease RAM usage.

The DAAScore is 30 days from today in around 21th of January. I'll update the explorer to show the HF time after Christmas.

https://github.com/Hoosat-Oy/HTND/releases/tag/v1.6.3

🎄 Merry Christmas and Happy Holidays! 🎄

As we gather with loved ones during this joyful season, let's celebrate the incredible journey we've shared in 2025. From groundbreaking innovations in GhostDAG and Hoohash to strengthening our decentralized, CPU & GPU-friendly network, you've made Hoosat Network a true people's blockchain, accessible, secure, and built for the future.

Thank you to every miner, developer, holder, and supporter who's contributed to our growth. Your passion and dedication light up our community like the brightest holiday stars. 🦉💫

May this Christmas bring you peace, happiness, and prosperity. Here's to an even brighter 2026 filled with fast transactions, exciting developments, and continued success together!

Warmest wishes,
Hoosat Network team

🦉 Initial Steps Toward DAGKnight in Hoosat Network! 🦉

Hey @everyone in the community, here is a little tech teaser for you: I've kicked off some exploratory work on possibly integrating DAGKnight, the advanced parameterless consensus protocol in to Hoosat Network.

I've created a dedicated DAGKnight branch in the HTND repository to lay the groundwork for potential future implementation. The core DAGknight dynamic K calculation logic is now in place, though this is still very early-stage, experimental, and thoroughly untested and I want to see community support for this direction of development.

Check out the initial commit here:
https://github.com/Hoosat-Oy/HTND/commit/0bc9424a262865c2e04e325cc4fd64be22b036ad
This could open doors to enhanced security, responsiveness, and adaptability in our network down the line. Feedback, ideas, or contributions are welcome as we research further!

Will the owl meet the knight?

Stay tuned 🦉

🦉DAGKnight continued. 🦉

I may have The DAGKnight protocol paper faithful implementation done in Github for Hoosat Network. So I think sometime in January we can start testnet testing it to see if it can handle 5 BPS or whatever crazy numbers we want to test. Hard Fork activation code is not yet done and switching from GhostDAG to DAGKnight is untested. I have also not yet really started to implement any kind of optimizations and I've noticed at least one thing that the DAGKnight rank calculation can be sped up considerably on larger K values.

🦉Q1 of 2026 roadmap. 🦉

Here is Q1 2025 roadmap of Hoosat Network:
https://wiki.hoosat.fi/roadmap/2026Q1

It may get some changes depending on the mood of the developers and how votes go in the voting platform.

🦉Social Media Management and Marketing. 🦉

HE23 has offered to lead and handle the social media presence of Hoosat Network, in the coming days I'll give him access to Hoosat Network X account and everything required so that he can communicate with the community. He will receive 50% of the developer fee for airdrops and marketing and for whatever he needs while he does the job for the community.

This will leave me more room to focus on R&D and hopefully less drama as I don't need to go to the social media platforms and check every notification.

Hopefully HE23 does the job well!

🦉 HTND 1.6.4 released 🦉

This release includes fixed test data and few small bugs in data stores and one serious bug, when blue block could be disqualified because it's merge set has red block that has acceptance data missing for whatever reason. Now such red block is skipped and the blue block will not be disqualified. Now you can run go test . ./... and all the test passes!

https://github.com/Hoosat-Oy/HTND/releases/tag/v1.6.4

🦉 HTND 1.6.5 released 🦉

This release fixes default pebble cache size in HTND 1.6.4 from 1MiB back to 1GiB and optimizes header and block cache sizes to use less RAM.

https://github.com/Hoosat-Oy/HTND/releases/tag/V1.6.5

🦉 New website is up. 🦉

I have now setup the new website to https://network.hoosat.fi/.

🦉 Hoosat Oy will shut down.🦉

Hoosat Community, after careful consideration, the shareholders of Hoosat Oy have made the decision to wind down the company's operations and dissolve Hoosat Oy as a legal entity. This means there will no longer be a single centralized company controlling or directing the Hoosat Network project.

Going forward:

- The Hoosat Network (HTN) will operate fully under decentralized community consensus.
- Development, decisions, and direction will be driven collectively by project contributors, miners, users, and community members.
- Code remains open-source, and the network continues to run independently as a permissionless, decentralized blockchain.

This transition aligns with the core ethos of decentralization that has always been at the heart of Hoosat Network. We believe this step will enable broader participation, innovation from anywhere in the world, and long-term resilience without reliance on any single entity.

We encourage everyone to stay involved:

- Join discussions on community channels (Discord, Telegram, etc)
- Contribute to the codebase or propose improvements.
- Continue mining, holding, and using HTN as the network evolves through consensus.

Thank you to everyone who has supported Hoosat Oy and the project so far, your contributions have brought us to this point. The future of Hoosat is now truly in the hands of the community.

Hoosat Oy closed source code will be released as open source in https://github.com/tmkcodes/

Hoosat Oy github organization changed to Hoosat Network
https://github.com/HoosatNetwork

Hoosat Oy website changed to Hoosat Network website
https://hoosat.fi

We appreciate your understanding during this transition.
Best regards, The former Hoosat Oy.

🦉 HTND 1.6.6 released 🦉

This release mainly decreases RAM usage of the node, with some more stability changes. I hope we can have few mining nodes below 8GB ram, though running high traffic nodes will require more RAM, like the explorer will hit over 12GB.

Reset db might be required because of the PebbleDB setting changes.

https://github.com/HoosatNetwork/HTND/releases/tag/v1.6.6

🦉 DAGKnight testnet starting🦉

@everyone since I have now tested IBD and it worked on my local testnet of DAGKnight. I have now one node mining from scratch from genesis. So sometime tomorrow or tuesday you will be able start participation in the testnet by syncing from mainnet-node-1.hoosat.fi. I'll drop more information when that is possible.

- So I'm going to give you here simple guide how to participate in the DAGKnight testnet and you will have few days to learn the ropes and make sure you can compile the node.
- I won't be doing Github release, so testnet participation will require compiling from Github, as there might be changes that I want testnet participants to update fast, so the compiling from Github is kind of the simplest and easiest way.

I expect that you have Golang setup and in path.

To install

git clone https://github.com/HoosatNetwork/HTND.git
cd HTND
git checkout dagknight
go install -tags "deadlock pebblegozstd" . ./cmd/...

To update

cd HTND
git pull
go install -tags "deadlock pebblegozstd" . ./cmd/...

To run

HTND --utxoindex --testnet -a mainnet-node-1.hoosat.fi 

Generate testnet address with genkeypair or use htnwallet with --testnet flags

genkeypair --testnet

Then you can mine with htnminer or setup your stratum bridge pointing to 42422 and mine with hoominer or hoo_xpu. Remember to use --testnet flag when necessary.

Drop a message in #🪐-node if you are going to participating in the testnet. I'll be informing more and listening for issues there.

Thank you, lets make DAGKnight happen!

🦉 HTN Wallets and Explorer down since yesterday. 🦉

We've today with Foztor hunted down an issue in my current modifications in master branch, which stopped the balances from being updated. I'm currently syncing the public Wallet/Explorer node to working version. If you have done transactions out of the web wallet or mobile wallet. Try reimporting your wallet once I have the explorer up and running, then your missing HTN should be back and if not they are where you sent them.

Work towards finding the issue with slow IBD is ongoing.

🦉Wohoo hoo hoo!! HTND 1.6.7 release! 🦉

This is non-breaking update to HTND 1.6, fixing many things.

Release Highlights:
- Fix slow IBD caused by block window cache broken.
- Upgraded Go version to 1.26.0
- Major cache and memory optimizations.
- PebbleDB option changes.
- Reduced GC (Garbage Collection) churn and improved memory usage.
- Added per-script UTXO cache with thread-safe LRU caches.
- Improved error handling and fixed several nil pointer and memory leak issues.
- Enhanced logging, metrics, and RPC request reporting if using "HTND_PROFILER=1" environment variable.
- Added a vote command to htnwallet, but it does not work yet because need to send notify to vote.hoosat.fi api and need API access from Namp88.
- General performance improvements and bug fixes.
- Respect GOMEMLIMIT and GOGC environment variables. Default 14 GB GOMEMLIMIT and GOGC 200%

https://github.com/HoosatNetwork/HTND/releases/tag/v1.6.7

🦉 HTND 1.6.8 🦉

This is a release few issues that came out with 1.6.7.

- Remove code that partially disabled RPC connections from outside network.
- Reduce GC Churn of UTXOs even more to stabilize windows usage.
- Fix two places where node could send blocks without PoW hash to alleviate nodes banning each other for sending blocks without PoW hashes.

https://github.com/HoosatNetwork/HTND/releases/tag/v1.6.8

🦉HTND 1.6.9 released🦉

@everyone this release is optimizing even more the GC churn.

Switched to vtprotobuf (github.com/planetscale/vtprotobuf).
Htnwallet send and balance fetch utxo on demand.
Htnwallet decreases address seeking from every 1s to 10s.
Disable relay while node is in IBD, even if nearly synced.
Optimize out ton of allocations to alleviate GC churn
Build with experimental SIMD and JSONv2 to add some speedup.

Default values:
GOMEMLIMIT 8GB
GOGC 100
PebbleDB Memory Tables up to 4GB
PebbledB cache 2GB

Explorer at the moment running with 8.8GB SSR and 30-300% CPU usage 80 cores. Compounding dev fee and explorer and wallet functionality.

This is about how far I can optimize HTND gc churn, before moving out of the Golang and starting to rewrite the node with C for self managed memory usage. So the CPU usage and RAM usage are what they are and you can play with the environment values if you need less CPU usage over more RAM being used. For example export GOMEMLIMIT=20GB and export GOGC=200 will allow the RAM to raise and the node CPU usage will be smaller and in part you could do export GOMEMLIMIT=6GB and export GOGC=25 and the RAM will be cleaned up as fast as possible, but CPU will be utilized.

https://github.com/HoosatNetwork/HTND/releases/tag/v1.6.9

🦉HTN Stratum Bridge 1.6.9 released🦉

Upgrades to HTND 1.6.9 and adds get block template cache to alleviate hitting the node so much when mining.

https://github.com/HoosatNetwork/htn-stratum-bridge/releases/tag/v1.6.9