Can developers of other pools trust to your code? Is the code universal?
Anything new about this pool and Moneta Verde? 
Topic: [ANN] Xmining Pool [BCN/XMR/FCN/QCN/XDN/BBR/DSH/AEON] CryptoNote Merge Mining - page 4. (Read 12487 times)
July 06, 2014, 03:59:03 AM
July 05, 2014, 04:08:52 PM
Can developers of other pools trust to your code? Is the code universal?
July 05, 2014, 04:02:12 PM
It is great! This is the first pool for Fantomcoin on open source which I was waiting for a long time.
July 04, 2014, 12:08:16 PM
I'm working to implement Moneta Verde at the moment.
Great! Good luck mate! Im waiting for updates!
July 04, 2014, 09:47:34 AM
Payout is the same as for all open source pools.
I'm working to implement Moneta Verde at the moment.
I'm working to implement Moneta Verde at the moment.
July 04, 2014, 05:11:42 AM
Good job guys!
Haven't tried it yet but the description looks promising. I also don't get why did you skip Moneta verde.
Haven't tried it yet but the description looks promising. I also don't get why did you skip Moneta verde.
Same question. But in general you guys did a great job.
July 03, 2014, 03:11:25 PM
Fantomcoin opensource mining pool thats what ive been waiting for!
Massive thanks to those who finally put it together.
Massive thanks to those who finally put it together.
July 03, 2014, 02:38:51 PM
I'm curious what payment system is in this pool and what about payouts?
July 03, 2014, 02:13:59 PM
Good job guys!
Haven't tried it yet but the description looks promising. I also don't get why did you skip Moneta verde.
Haven't tried it yet but the description looks promising. I also don't get why did you skip Moneta verde.
July 03, 2014, 11:21:08 AM
Good luck. And what about Moneta Verde? Will you add it to your pool?
Yeah, that will be nice. Que viva the merged mining! =D July 03, 2014, 11:01:15 AM
Code:
+ b.nonce = nonce;
+ if (b.major_version == BLOCK_MAJOR_VERSION_2) {
+ block parent_block;
+ b.parent_block.nonce = nonce;
+ if (!construct_parent_block(b, parent_block))
+ return except("Failed to construct parent block");
+
+ if (!mergeBlocks(parent_block, b, std::vector()))
+ return except("Failed to postprocess mining block");
+ }
+ if (b.major_version == BLOCK_MAJOR_VERSION_2) {
+ block parent_block;
+ b.parent_block.nonce = nonce;
+ if (!construct_parent_block(b, parent_block))
+ return except("Failed to construct parent block");
+
+ if (!mergeBlocks(parent_block, b, std::vector
+ return except("Failed to postprocess mining block");
+ }
you make merge block in solo mining
I do not understand why you do
There are block of two types: one is traditional blocks (Monero, Bytecoin, QuazarCoin, etc.), while the other one is for Fantomcoin only. This second block type allows merge mining of the first ones and is the only block type accepted by FCN (and MCN). FCN mining requires doing work with the block template of the second type (native to FCN). These blocks also allow merge mining with the first type blocks, but I started with fixing pool's block template to single mine FCN.
As for high orphan rates, I've found two problems. The first one was related to the network parameters, which turned out to be misconfigured. The second one was that the block hash was taken invalidly from the block explorer, which marked valid blocks as orphaned. The fix will be released soon.
July 03, 2014, 10:31:48 AM
Good luck. And what about Moneta Verde? Will you add it to your pool?
July 03, 2014, 08:28:24 AM
Code:
+ b.nonce = nonce;
+ if (b.major_version == BLOCK_MAJOR_VERSION_2) {
+ block parent_block;
+ b.parent_block.nonce = nonce;
+ if (!construct_parent_block(b, parent_block))
+ return except("Failed to construct parent block");
+
+ if (!mergeBlocks(parent_block, b, std::vector()))
+ return except("Failed to postprocess mining block");
+ }
+ if (b.major_version == BLOCK_MAJOR_VERSION_2) {
+ block parent_block;
+ b.parent_block.nonce = nonce;
+ if (!construct_parent_block(b, parent_block))
+ return except("Failed to construct parent block");
+
+ if (!mergeBlocks(parent_block, b, std::vector
+ return except("Failed to postprocess mining block");
+ }
you make merge block in solo mining
I do not understand why you do
July 03, 2014, 08:25:00 AM
up to now in your pool
only blocks orphans left
it is not because you are using the function
merge
also to mine only fcn?
miner.cpp from the file miner.cpp
I do not see the use of the merge works
I know that you should not use it
also you do not need to do
the nonce on parentblock
just have to modify the file so pool.js
in this way
only blocks orphans left
it is not because you are using the function
merge
also to mine only fcn?
miner.cpp from the file miner.cpp
I do not see the use of the merge works
I know that you should not use it
also you do not need to do
the nonce on parentblock
just have to modify the file so pool.js
in this way
Code:
var shareBuffer = new Buffer(blockTemplate.buffer.length);
blockTemplate.buffer.copy(shareBuffer);
shareBuffer.writeUInt32BE(job.extraNonce, blockTemplate.reserveOffset);
new Buffer(nonce, 'hex').copy(shareBuffer, 73);
no 39 but 73
and in the function convert_blob
you have to use
get_bytecoin_block_hashing_blob
blockTemplate.buffer.copy(shareBuffer);
shareBuffer.writeUInt32BE(job.extraNonce, blockTemplate.reserveOffset);
new Buffer(nonce, 'hex').copy(shareBuffer, 73);
no 39 but 73
and in the function convert_blob
you have to use
get_bytecoin_block_hashing_blob
There is no merge mining implemented at the moment. I'm working on the solution but it is way more complicated than just Fantomcoin's blocks support. I hope to release it next week. At the moment Xminingpool implements single mining for FCN.
As for orphaned blocks, it's just the FCN daemon's configuration. I'm tuning it to fix the issue at the moment.
July 03, 2014, 07:46:32 AM
up to now in your pool
only blocks orphans left
it is not because you are using the function
merge
also to mine only fcn?
miner.cpp from the file miner.cpp
I do not see the use of the merge works
I know that you should not use it
also you do not need to do
the nonce on parentblock
just have to modify the file so pool.js
in this way
only blocks orphans left
it is not because you are using the function
merge
also to mine only fcn?
miner.cpp from the file miner.cpp
I do not see the use of the merge works
I know that you should not use it
also you do not need to do
the nonce on parentblock
just have to modify the file so pool.js
in this way
Code:
var shareBuffer = new Buffer(blockTemplate.buffer.length);
blockTemplate.buffer.copy(shareBuffer);
shareBuffer.writeUInt32BE(job.extraNonce, blockTemplate.reserveOffset);
new Buffer(nonce, 'hex').copy(shareBuffer, 73);
no 39 but 73
and in the function convert_blob
you have to use
get_bytecoin_block_hashing_blob
blockTemplate.buffer.copy(shareBuffer);
shareBuffer.writeUInt32BE(job.extraNonce, blockTemplate.reserveOffset);
new Buffer(nonce, 'hex').copy(shareBuffer, 73);
no 39 but 73
and in the function convert_blob
you have to use
get_bytecoin_block_hashing_blob
July 03, 2014, 07:23:47 AM
this is my function
for merge mining
for merge mining
You should take a look at my pull requests to see my solution. It doesn't have the problem that you've mentioned.
July 03, 2014, 07:08:18 AM
this is my function
for merge mining
in main.cc from node cryptonote util
for merge mining
in main.cc from node cryptonote util
Code:
Handle merging_block(const Arguments& args) {
HandleScope scope;
if (args.Length() < 1)
return except("You must provide one argument.");
Local
HandleScope scope;
if (args.Length() < 1)
return except("You must provide one argument.");
Local
July 03, 2014, 06:41:56 AM
i have made this thing two week ago
but i have this error
"Aux block hash wasn't found in merkle tree"
but i have this error
"Aux block hash wasn't found in merkle tree"
July 03, 2014, 06:36:20 AM
I've made several commits to the open source code. The changes need to be taken by both zone117x and LucasJones
1) Major update with FCN Fantomcoin support (should be compatible with MCN Moneta Verde and any other upcoming merge mining coin)
https://github.com/LucasJones/node-cryptonote-util/pull/2
https://github.com/zone117x/node-cryptonote-pool/pull/47
2) Proper address validation for all CryptoNote coins.
https://github.com/LucasJones/node-cryptonote-util/pull/3
https://github.com/zone117x/node-cryptonote-pool/pull/48
Previously node-cryptonote-pool didn't provide proper address validation. Here are some addresses that are accepted by the pool but rejected by the wallet:
2Aui6ejTFsd11111111111111111111111111111111111111111111111111111111111111111111 11111111114W5UeV - BCN invalid but accepted address
4BKnGLZNZ5q11111111111111111111111111111111111111111111111111111111111111111111 11111111113S9JYY - XMR invalid but accepted address
Pool is checking whether the coin's address starts with a proper character, but this is an invalid rule of thumb unfortunately. The address is being created based on the currency's prefix (6 for Bytecoin, 18 for Monero), which shouldn't be confused with the address's first number. It is possible to create an address for Bytecoin with prefix 7 (and for Monero with prefix 19), which would look exactly like the two addresses above. The outcome is a potential attack on the open source pools which would freeze all payouts once the invalid address is processed by the wallet.
I've also fixed the duckNote's address validation.
1) Major update with FCN Fantomcoin support (should be compatible with MCN Moneta Verde and any other upcoming merge mining coin)
https://github.com/LucasJones/node-cryptonote-util/pull/2
https://github.com/zone117x/node-cryptonote-pool/pull/47
2) Proper address validation for all CryptoNote coins.
https://github.com/LucasJones/node-cryptonote-util/pull/3
https://github.com/zone117x/node-cryptonote-pool/pull/48
Previously node-cryptonote-pool didn't provide proper address validation. Here are some addresses that are accepted by the pool but rejected by the wallet:
2Aui6ejTFsd11111111111111111111111111111111111111111111111111111111111111111111 11111111114W5UeV - BCN invalid but accepted address
4BKnGLZNZ5q11111111111111111111111111111111111111111111111111111111111111111111 11111111113S9JYY - XMR invalid but accepted address
Pool is checking whether the coin's address starts with a proper character, but this is an invalid rule of thumb unfortunately. The address is being created based on the currency's prefix (6 for Bytecoin, 18 for Monero), which shouldn't be confused with the address's first number. It is possible to create an address for Bytecoin with prefix 7 (and for Monero with prefix 19), which would look exactly like the two addresses above. The outcome is a potential attack on the open source pools which would freeze all payouts once the invalid address is processed by the wallet.
I've also fixed the duckNote's address validation.
July 03, 2014, 05:30:44 AM
We've tuned our balancing software. Xmining should be working even faster now.
Give it a try; we are waiting for your feedback!
Give it a try; we are waiting for your feedback!
Jump to: