Peercoin is a hybrid coin, retaining mining with SHA256d in addition to Proof-of-Stake. Will Patchchoin also be a hybrid PoW / PoS coin or only a PoS coin ?  If a hybrid, will there me only a single PoW algo, or multiple PoW algos ?

---

---

---

---

---

---

---

---

Is there a technical paper with details on Peercoin minting ?

Argentum is trading on https://FreiExchange.com

Yes, most of the chatter regarding development is on Telegram

Great to have you back akrmn2021 !

example:

addnode=217.254.41.220
addnode=178.255.21.168
addnode=185.162.251.41
addnode=162.212.157.38
addnode=195.201.24.50
addnode=23.94.44.103
addnode=85.214.70.216

Try adding these nodes via your helix.conf file:

addnode=162.212.156.200
addnode=139.162.122.138
addnode=175.255.212.141
addnode=107.152.46.198
addnode=5.78.68.170

Thanks for your reply. It's a Yiimp pool that I'm setting up to mine eMark and merge-mine Bitmark simultaneously.   I understand that Yiimp does not support asicboost, so my problem is actually how to turn asicboost off on the Avalon 1047.

If I can't turn off asicboost, then I have to modify Yiimp or go to a different pool software like miningcore, but miningcore does not support merge-mining.

Hi All,

Trying to mine Deutsche eMark, a SHA256 coin, with an Avalon miner 1047, but the pool is rejecting the hashrate with the message "unknown message mining.configure <ip-number>", apparently indicating the miner is using 'asicboost'.

But I have looked at the canaan.io website and cannot find any reference to 'asicboost'. There is a "Work Mode" choice on the miner's interface, "Normal Mode" or "High Performance", but neither choice appears to make any difference.

Any help or clues appreciated ....

Won't compile on Ubuntu 22 nor 20 (SSL Bignum issues) and, won't even compile one Ubuntu 16 ...

AI assisted clues, if anyone want to fix:

Summary of the issues and possible solution paths for the developer to explore:

rpcrawtransaction.cpp: This file contains the code where the ExtractDestinations function is called, and the handling of the extracted information is performed.

script.h and script.cpp: These files contain the implementation of the ExtractDestination and ExtractDestinations functions.

Compilation Error: The error message indicates an issue with the Boost variant library and the usage of boost::get and boost::strict_get functions.

Possible Solution:

Verify that the Boost library is installed correctly and accessible by the compiler.
Include the necessary Boost headers, specifically the Boost variant-related headers such as boost/variant.hpp.
Double-check the compatibility of the Boost library version with your code.
Ensure that the Boost variant types and related functions are used correctly and that the necessary types are defined and included.
Incomplete Type Error: The error message mentions an invalid application of sizeof to an incomplete type.

Possible Solution:

Review the Boost variant-related code and ensure that all necessary types and definitions are correctly included and accessible.
Check for any missing or incorrect type definitions related to Boost variant usage.
Verify that the Boost headers are included in the correct order before the relevant code snippets.
Extraction and Handling of Destinations: The code snippets involve the extraction and handling of destination addresses from scriptPubKeys.

Possible Solution:

Review the implementation of the ExtractDestinations function and ensure it correctly extracts the necessary information.
Verify that the ExtractDestinations function returns the expected values for type, addresses, and nRequired.
Check the implementation of the GetTxnOutputType function to ensure it returns the proper output type based on the input txnouttype.
Ensure that the objects (out, addresses, etc.) used to store the extracted information are properly defined and capable of storing the required key-value pairs.
By exploring these solution paths, reviewing the code implementations, and addressing any identified issues, the developer should be able to resolve the compilation error and ensure correct handling of destination addresses in the code.

Yes the PoW algo for eMark has been SHA256
It also has staking