the stratum-mining with tx message support dev here.
TX Message support refers to coins with a specific message field as part of each transaction. While its possible to store a small message with bitcoin transactions, it isnt the same thing
Ahmed
Topic: bitcoin pool software setup curiosity, my pool, python stratum or node.js pool. (Read 844 times)
November 18, 2016, 05:34:58 PM
November 16, 2016, 06:59:05 AM
First, this is about Bitcoin and Bitcoin only.
Running 0.13.0.
The question/curiosity:
I found a seriously not/ill-documented option in the txMessages support (for proper block serialization)
In both python-stratum-mining and node-open-mining-portal, for Bitcoin expressly, tx_messages are disabled by default.
Bitcoin supports tx_messages. tx_messages sould be integrated into the mined block if exist and many TXs contain tx_messages, right?
So, My conclusion is that, for the pool software chain to validate a mined block, tx_messages sould be on.
So, for Bitcoin/nomp, par example, why is the txMessages support set to false? It is set true for other sha256 coins, false for others, not set at all and defaulted to false in the code.
I have this question opened on the gits too but I fear I won't be getting any attention, not to mention any answers or ideas...
Cheers folks.
And, if wondering, I'm running (testing for now) a private pool, very small, where I'll be solo with about 600Th now and about 1Ph by the next year.
Nothing fancy but the only mainnet successful tests I made (mining, solving and correct payout) was with ppc, not btc. Which is sha256 too but not the exact same thing.
I know, I should had made a test on testnet but I already stet it up on mainnet...
(edited few typos)
Running 0.13.0.
The question/curiosity:
I found a seriously not/ill-documented option in the txMessages support (for proper block serialization)
In both python-stratum-mining and node-open-mining-portal, for Bitcoin expressly, tx_messages are disabled by default.
Bitcoin supports tx_messages. tx_messages sould be integrated into the mined block if exist and many TXs contain tx_messages, right?
So, My conclusion is that, for the pool software chain to validate a mined block, tx_messages sould be on.
So, for Bitcoin/nomp, par example, why is the txMessages support set to false? It is set true for other sha256 coins, false for others, not set at all and defaulted to false in the code.
I have this question opened on the gits too but I fear I won't be getting any attention, not to mention any answers or ideas...
Cheers folks.
And, if wondering, I'm running (testing for now) a private pool, very small, where I'll be solo with about 600Th now and about 1Ph by the next year.
Nothing fancy but the only mainnet successful tests I made (mining, solving and correct payout) was with ppc, not btc. Which is sha256 too but not the exact same thing.
I know, I should had made a test on testnet but I already stet it up on mainnet...
(edited few typos)
Jump to: