@Defaultplayer13@salvium_io From what I’ve observed, the underlying technology isn’t very mature and hard forks happen quite often.
Its core narrative is inspired by Monero, but it sacrifices some privacy so exchanges and regulators can identify coin ownership.
The narrative is stronger than the technology.
@PQabelian Otherwise, does that imply that participation requires the project’s permission? This seems to be a gray area that has never been clearly addressed.
@PQabelian As for companies producing imitation mining hardware, I think this falls within the scope of normal market competition. Hako Metal should respond by innovating and iterating more quickly, rather than relying on an official statement from Abel.
@PQabelian 3. From Abel’s perspective, should the project issue an official statement? This brings us back to the point I raised earlier: the rules should allow mining hardware manufacturers to participate without requiring permission.
@PQabelian I noticed the article mentioned that some manufacturers are selling imitation mining machines.
1. They could simply be scam websites.
2. They could be copying Hako Metal. In this case, they may have real mining hardware, but they don’t have their own brand.
@PQabelian 2. Can mining hardware manufacturers enter the ecosystem on equal terms? This is a key indicator of permissionless participation.
3. Governance transparency and premine transparency are also critical. These issues may be causing community members to leave quickly before a strong
@PQabelian I believe credible neutrality is one of Abel’s biggest challenges at the current stage.
1. Is the mining algorithm finalized and effectively locked? Will there be no further algorithm changes or additions in the future?
2. Can mining hardware manufacturers
Official Binary Release: v1.1.3b
We understand that some community members downloaded the v1.1.3a binaries directly from GitHub before the official release announcement. Due to an issue during the GitHub release process, an incorrect hard fork height was unintentionally included in the v1.1.3a binaries.
To correct this, we have released v1.1.3b, which restores the correct hard fork height and ensures stable network synchronization.
New release: https://t.co/mNJhFpK03A
If you are currently running v1.1.3a, please upgrade to the v1.1.3b binaries immediately. This update is required to ensure proper network synchronization and full compatibility with tomorrow's hard fork.
We apologize for any confusion or inconvenience this may have caused and appreciate your patience and continued support.
The Salvium Team