i've written a shim that sits between cryptonite and the stratum, that reads the result of 'getblocktemplate' and rebuilds it to suit stratum-mining.
the issue then seems to be the transport layer, which is what i'm working on right now.
https://www.youtube.com/watch?v=IV3jTOsPdX8
i've got an alternative approach written in case this fails; where it actually decodes/interprets coinbasetx to suit.
what makes it difficult, is only having an amd gpu..
the standard xcn cpuminer only requests 'getwork' regardless of what you tell it to use (ie --no-getwork).
james
Topic: [ANN][XCN] Cryptonite - NEW Thread | 1st mini-blockchain coin | Bounties! - page 149. (Read 215807 times)
July 08, 2017, 02:45:00 AM
July 08, 2017, 02:31:43 AM
does anyone build pool use nomp and mpos successfully?
Yes, but only with Litecoin.Still figuring out how to add in a new algorithm (a new coin to an existing supported algorithm, is easy enough).
With an added difficulty of communicating with the XCN Wallet... I think I got the idea of what is needed to be modified. The hardest part for me is the algorithm at this stage.
i'd actually created a m7 stratum module for nomp a little while back,
it was the getblocktemplate giving me issues.
however i've just got that part sorted and doing some testing now.
EDIT: depending on how you handle the getblocktemplate, you will run into a specific issue using nomp.. (just a hint)
For the getblocktemplate seems to just need to re-arrange the values from the wallet to the server standards.
Code:
Standard Wallets
00 - "capabilities"
01 - "version"
02 - "rules"
03 - "vbavailable"
04 - "vbrequired"
05 - "previousblockhash"
06 - "transactions" {data, txid, hash, depends {fee, sigops, weight}}
07 - "coinbaseaux" {flags}
08 - "coinbasevalue"
09 - "longpollid"
10 - "target"
11 - "mintime"
12 - "mutable" {time, transactions, prevblock}
13 - "noncerange"
14 - "sigolimit"
15 - "sizelimit"
16 - "curtime"
17 - "bits"
18 - "height"
XCN Wallet
00 - "version"
01 - "previousblockhash"
02 - "accountroothash"
03 - "transactions" {data, fee, sigops}
04 - "coinbasevalue"
05 - "coinbasetx"
06 - "longpollid"
07 - "target"
08 - "mintime"
09 - "mutable" {time, transactions, prevblock}
10 - "noncerange"
11 - "sigolimit"
12 - "sizelimit"
13 - "curtime"
14 - "bits"
15 - "height"
Thus remap/rearrange things.00 - "capabilities"
01 - "version"
02 - "rules"
03 - "vbavailable"
04 - "vbrequired"
05 - "previousblockhash"
06 - "transactions" {data, txid, hash, depends {fee, sigops, weight}}
07 - "coinbaseaux" {flags}
08 - "coinbasevalue"
09 - "longpollid"
10 - "target"
11 - "mintime"
12 - "mutable" {time, transactions, prevblock}
13 - "noncerange"
14 - "sigolimit"
15 - "sizelimit"
16 - "curtime"
17 - "bits"
18 - "height"
XCN Wallet
00 - "version"
01 - "previousblockhash"
02 - "accountroothash"
03 - "transactions" {data, fee, sigops}
04 - "coinbasevalue"
05 - "coinbasetx"
06 - "longpollid"
07 - "target"
08 - "mintime"
09 - "mutable" {time, transactions, prevblock}
10 - "noncerange"
11 - "sigolimit"
12 - "sizelimit"
13 - "curtime"
14 - "bits"
15 - "height"
In Pseudo Code:
GetBlockXCN[0..15] = [XCN Wallet's GetBlockTemplate];
GetBlockTemp[0..18] = GetBlockXCN['proposal', 00, 'csv', '', '0', 01, 03, '', 04, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15]
GetBlockTemplate[0..18] = GetBlockTemp[0..18]
Other than for verifying the correct hard values (ie: proposal and csv), I think that is all there is to it.
Ref:
https://en.bitcoin.it/wiki/Getblocktemplate
https://chainquery.com/bitcoin-api/getblocktemplate
July 07, 2017, 10:56:05 PM
does anyone build pool use nomp and mpos successfully?
Yes, but only with Litecoin.Still figuring out how to add in a new algorithm (a new coin to an existing supported algorithm, is easy enough).
With an added difficulty of communicating with the XCN Wallet... I think I got the idea of what is needed to be modified. The hardest part for me is the algorithm at this stage.
i'd actually created a m7 stratum module for nomp a little while back,
it was the getblocktemplate giving me issues.
however i've just got that part sorted and doing some testing now.
EDIT: depending on how you handle the getblocktemplate, you will run into a specific issue using nomp.. (just a hint)
July 07, 2017, 09:35:21 PM
If anyone wants to be involved in building a Pool for XCN, these are two systems I am working with. The link are to the file repositories.
MPOS - https://github.com/MPOS/php-mpos
NOMP - https://github.com/zone117x/node-open-mining-portal
MPOS - is the front end, the web graphical interface, which I believe I have it figured out. MPOS also has a Stratum for python, but I am giving NOMP, the NodeJS a try.
NOMP - is the mining backend and I expect to be a pain to integrate.
MPOS
For MPOS, the following modifications were needed:
- In the \include\lib\ folder, the file global.inc.php (the original is global.inc.dist.php, but gets copies and renamed to global.inc.php during the install process);
--- Line 38 for the algorithm is changed from "scrypt" to "m7".
--- Lines 93 to 96 are changed to reflect the coin name, url's and ports used.
--- Line 142 to change to XCN
- Create a file in the \include\classes\coins folder, named as coin_n7.class.php
--- The file I have it coded as:
- May need to modify line 82 in include\autoloader.inc.php, from scrypt to m7:
- Need to create a file in the includes\lib\ folder named, m7.php.
This file appears to have the algorithm process.
NOMP
The following files look like they need modifications or needed:
- Create a coin file in \coins folder, named as cryptonite.json
--- Need to figure out the values in that file
- Modify the file, package.json located in the root of nomp, to add in "m7" in the keywords section (starting at line 5).
I'm sure there are more that is needed, but that is the start I have so far.
MPOS - https://github.com/MPOS/php-mpos
NOMP - https://github.com/zone117x/node-open-mining-portal
MPOS - is the front end, the web graphical interface, which I believe I have it figured out. MPOS also has a Stratum for python, but I am giving NOMP, the NodeJS a try.
NOMP - is the mining backend and I expect to be a pain to integrate.
MPOS
For MPOS, the following modifications were needed:
- In the \include\lib\ folder, the file global.inc.php (the original is global.inc.dist.php, but gets copies and renamed to global.inc.php during the install process);
--- Line 38 for the algorithm is changed from "scrypt" to "m7".
Code:
$config['algorithm'] = 'm7';
--- Lines 69 to 71 are changed to reflect the port and rpcuser and rpcpassword used in the wallet's cryptonite.conf file.--- Lines 93 to 96 are changed to reflect the coin name, url's and ports used.
Code:
$config['gettingstarted']['coinname'] = 'Cryptonite';
$config['gettingstarted']['coinurl'] = 'http://cryptonite.info';
$config['gettingstarted']['stratumurl'] = 'ServerIPAddressHere';
$config['gettingstarted']['stratumport'] = '8008';
--- Lines 103 to 106 if to add in the values from an Exchange$config['gettingstarted']['coinurl'] = 'http://cryptonite.info';
$config['gettingstarted']['stratumurl'] = 'ServerIPAddressHere';
$config['gettingstarted']['stratumport'] = '8008';
--- Line 142 to change to XCN
Code:
$config['currency'] = 'XCN';
- Create a file in the \include\classes\coins folder, named as coin_n7.class.php
--- The file I have it coded as:
Code:
$defflip = (!cfip()) ? exit(header('HTTP/1.1 401 Unauthorized')) : 1;
/**
* We extend our CoinBase class
* No need to change anything, base class supports
* M7
**/
class Coin extends CoinBase {
protected $target_bits = 64;
}
/**
* We extend our CoinBase class
* No need to change anything, base class supports
* M7
**/
class Coin extends CoinBase {
protected $target_bits = 64;
}
- May need to modify line 82 in include\autoloader.inc.php, from scrypt to m7:
Code:
require_once(INCLUDE_DIR . '/lib/m7.php');
- Need to create a file in the includes\lib\ folder named, m7.php.
This file appears to have the algorithm process.
NOMP
The following files look like they need modifications or needed:
- Create a coin file in \coins folder, named as cryptonite.json
--- Need to figure out the values in that file
- Modify the file, package.json located in the root of nomp, to add in "m7" in the keywords section (starting at line 5).
I'm sure there are more that is needed, but that is the start I have so far.
1GH ran a pool, I mined on it for months solid, possibly years! no issues.
July 07, 2017, 07:17:52 PM
The hardest part for me is the algorithm at this stage.
I know this is replying to my own post, providing this as an update.But Eureka!
Found the algo script (I knew I saw it before somewhere...)
Ok, beginning the integration with the algorithm.
Ref Link:
https://github.com/pallas1/Cryptonite/blob/master/src/hashblock.h
Nice! Keep up the good work.
One of you bag holders in here needs to tip this dude.
July 07, 2017, 07:00:35 PM
The hardest part for me is the algorithm at this stage.
I know this is replying to my own post, providing this as an update.But Eureka!
Found the algo script (I knew I saw it before somewhere...)
Ok, beginning the integration with the algorithm.
Ref Link:
https://github.com/pallas1/Cryptonite/blob/master/src/hashblock.h
July 07, 2017, 06:56:02 PM
pallas if you can fix this
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
I don't have that any longer, and it was slower than djm34 current binary anyways.
oh ok, what about this version, seems to be open public https://bitcointalk.org/index.php?topic=1801595.1460, i posted in the other thread
24 Mh/s for two cards isn't very fast ;-)
With two 1070's, Windows 10 (I tried with Linux, but I keep getting compile errors with CUDA 8.0 for the ccminer... so its on the backburner) and no overclocking, I am averaging 27-28 MH/s.
Ideally, the top speed I have seen is 30MH/s, when the pool is functioning nicely and during off peak neighborhood bandwidth usage.
July 07, 2017, 05:39:18 PM
does anyone build pool use nomp and mpos successfully?
Yes, but only with Litecoin.Still figuring out how to add in a new algorithm (a new coin to an existing supported algorithm, is easy enough).
With an added difficulty of communicating with the XCN Wallet... I think I got the idea of what is needed to be modified. The hardest part for me is the algorithm at this stage.
July 07, 2017, 02:54:26 PM
any suggestion on how to get my 540,000 xcn off of Polo?
look like polo didn't want to slove this issue ,i open 3 tickets ,but no response
Polo has huge ticket delays because it says it's dealing with a giant backlog of tickets. There are people waiting months to get their accounts verified. You 'll probably have to wait a long time for a reply.
July 07, 2017, 12:05:41 PM
pallas if you can fix this
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
I don't have that any longer, and it was slower than djm34 current binary anyways.
oh ok, what about this version, seems to be open public https://bitcointalk.org/index.php?topic=1801595.1460, i posted in the other thread
24 Mh/s for two cards isn't very fast ;-)
yeah missed that, talking about something else, what about a better exchange like cryptopia?
July 07, 2017, 11:03:53 AM
Same thing with 3 tickets over the last 2 months
July 07, 2017, 10:58:09 AM
any suggestion on how to get my 540,000 xcn off of Polo?
look like polo didn't want to slove this issue ,i open 3 tickets ,but no response
July 07, 2017, 10:56:07 AM
any suggestion on how to get my 540,000 xcn off of Polo?
July 07, 2017, 09:52:54 AM
pallas if you can fix this
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
I don't have that any longer, and it was slower than djm34 current binary anyways.
oh ok, what about this version, seems to be open public https://bitcointalk.org/index.php?topic=1801595.1460, i posted in the other thread
24 Mh/s for two cards isn't very fast ;-)
July 07, 2017, 09:42:31 AM
pallas if you can fix this
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
I don't have that any longer, and it was slower than djm34 current binary anyways.
oh ok, what about this version, seems to be open public https://bitcointalk.org/index.php?topic=1801595.1460, i posted in the other thread
July 07, 2017, 09:40:55 AM
pallas if you can fix this
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
I don't have that any longer, and it was slower than djm34 current binary anyways.
July 07, 2017, 09:30:28 AM
pallas if you can fix this
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
Check here for pre-compiled cuda miner binaries for Win64:
dropbox.com/sh/56lnq52g4gny0m0/AADMJa2QTMSSc4g9gx1BfWIla
not working, it's missed
July 07, 2017, 09:29:36 AM
July 07, 2017, 06:51:29 AM
does anyone build pool use nomp and mpos successfully?
July 07, 2017, 06:27:49 AM
What are the solo mining conf settings? I can't seem to get it to work, and I cant find the info in the thread
Something like this, cryptonite.conf @ %AppDatA%addnode=5.157.115.132 [change these to fresh working ones from http://xcn-explorer.selektion21.de/?page=peers]
addnode=96.244.98.123
addnode=194.88.107.212
addnode=158.69.27.82
addnode=46.105.118.15
listen=1
rpcport=8252
daemon=1
server=1
rpcallowip=192.168.0.*, [change this to match your local ip/ network, 127.0.01 if mining with wallet computer, "*" as a wildcard]
rpcuser=[write something here and use it in your miner.bat]
rpcpassword=[write something here and use it in your miner.bat]
To run your miner:
ccminer -a m7 -s 1 -o http://[local ip of your wallet computer:8252] -u something you wrote to .conf -p something you wrote to .conf
Jump to: