{"method":"mining.notify","params":["6","11747279a8107a59599d3b20f6af6d75d8796369635eaffd057c0c3200000000","01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff260366eb14062f503253482f03f3b91608","0d2f436f696e69756d536572762f0000000002f20140bad30100001976a914a04c734d1754c9adf ad0a77aeef784bffc38147f88ac902e7ab9040000001976a914f880e402b50b12d4c127c36173b7 e3744337b4a288ac00000000",["b1725a98bcc5632df80798990f6e0f9e14cf0f53773f0d2a78ea1a9a73a9762a"],"00000001","31714.294077","58c65e27",true],"id":null}
It looks like there is some parameter the miner doesn't like. I see bigger field sizes than suprnova's.
If you PM me your email, we will talk on slack.
Topic: [ANN][XCN] Cryptonite - NEW Thread | 1st mini-blockchain coin | Bounties! - page 218. (Read 215807 times)
March 13, 2017, 03:56:08 AM
March 13, 2017, 03:43:14 AM
this is my hash function looks.
using HashLib;
using System.Collections.Generic;
using System.Security.Cryptography;
using Mpir.NET;
using System.Numerics;
using System;
public sealed class M7:IHashAlgorithm
{
public uint Multiplier { get; private set; }
private readonly List _hashers;
BigInteger[] hash=new BigInteger[7];
public M7()
{
_hashers = new List
{
HashFactory.Crypto.CreateSHA256(),
HashFactory.Crypto.CreateSHA512(),
HashFactory.Crypto.SHA3.CreateKeccak512(),
HashFactory.Crypto.CreateWhirlpool(),
HashFactory.Crypto.CreateHaval_5_256(),
HashFactory.Crypto.CreateTiger2(),
HashFactory.Crypto.CreateRIPEMD160()
};
Multiplier = (UInt32)Math.Pow(2,
;
}
public byte[] Hash(byte[] input)
{
var buffer = input;
mpz_t product=new mpz_t();
mpir.mpz_set_ui(product, 1);
foreach (var hasher in _hashers)
{
var hashbytes = hasher.ComputeBytes(buffer).GetBytes();
mpir.mpz_mul(product, product, new mpz_t(hashbytes, -1));
}
uint bytes = mpir.mpz_sizeinbase(product, 256);
byte[] data= mpir.Mpir_mpz_export(-1,bytes,0,0,product);
buffer = HashFactory.Crypto.CreateSHA256().ComputeBytes(data).GetBytes();
return buffer;
}
}
using HashLib;
using System.Collections.Generic;
using System.Security.Cryptography;
using Mpir.NET;
using System.Numerics;
using System;
public sealed class M7:IHashAlgorithm
{
public uint Multiplier { get; private set; }
private readonly List
BigInteger[] hash=new BigInteger[7];
public M7()
{
_hashers = new List
{
HashFactory.Crypto.CreateSHA256(),
HashFactory.Crypto.CreateSHA512(),
HashFactory.Crypto.SHA3.CreateKeccak512(),
HashFactory.Crypto.CreateWhirlpool(),
HashFactory.Crypto.CreateHaval_5_256(),
HashFactory.Crypto.CreateTiger2(),
HashFactory.Crypto.CreateRIPEMD160()
};
Multiplier = (UInt32)Math.Pow(2,
; }
public byte[] Hash(byte[] input)
{
var buffer = input;
mpz_t product=new mpz_t();
mpir.mpz_set_ui(product, 1);
foreach (var hasher in _hashers)
{
var hashbytes = hasher.ComputeBytes(buffer).GetBytes();
mpir.mpz_mul(product, product, new mpz_t(hashbytes, -1));
}
uint bytes = mpir.mpz_sizeinbase(product, 256);
byte[] data= mpir.Mpir_mpz_export(-1,bytes,0,0,product);
buffer = HashFactory.Crypto.CreateSHA256().ComputeBytes(data).GetBytes();
return buffer;
}
}
March 13, 2017, 03:33:34 AM
now:
{"method":"mining.notify","params":["19","c072775672a78ad846ecfb37049810e0ac4f455b13eed297161c397000000000","01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff26033ceb14062f503253482f03f1b91608","0d2f436f696e69756d536572762f0000000002f4a7e9bad30100001976a914a04c734d1754c9adf ad0a77aeef784bffc38147f88ac40e57bb9040000001976a914f880e402b50b12d4c127c36173b7 e3744337b4a288ac00000000",[],"00000001","31748.075332","58c65669",true],"id":null}
09:21:21 - Stratum notify: invalid parameters
{"method":"mining.notify","params":["19","c072775672a78ad846ecfb37049810e0ac4f455b13eed297161c397000000000","01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff26033ceb14062f503253482f03f1b91608","0d2f436f696e69756d536572762f0000000002f4a7e9bad30100001976a914a04c734d1754c9adf ad0a77aeef784bffc38147f88ac40e57bb9040000001976a914f880e402b50b12d4c127c36173b7 e3744337b4a288ac00000000",[],"00000001","31748.075332","58c65669",true],"id":null}
09:21:21 - Stratum notify: invalid parameters
need to check it with miner , ok let me try to compile miner.
March 13, 2017, 03:22:09 AM
now:
{"method":"mining.notify","params":["19","c072775672a78ad846ecfb37049810e0ac4f455b13eed297161c397000000000","01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff26033ceb14062f503253482f03f1b91608","0d2f436f696e69756d536572762f0000000002f4a7e9bad30100001976a914a04c734d1754c9adf ad0a77aeef784bffc38147f88ac40e57bb9040000001976a914f880e402b50b12d4c127c36173b7 e3744337b4a288ac00000000",[],"00000001","31748.075332","58c65669",true],"id":null}
09:21:21 - Stratum notify: invalid parameters
{"method":"mining.notify","params":["19","c072775672a78ad846ecfb37049810e0ac4f455b13eed297161c397000000000","01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff26033ceb14062f503253482f03f1b91608","0d2f436f696e69756d536572762f0000000002f4a7e9bad30100001976a914a04c734d1754c9adf ad0a77aeef784bffc38147f88ac40e57bb9040000001976a914f880e402b50b12d4c127c36173b7 e3744337b4a288ac00000000",[],"00000001","31748.075332","58c65669",true],"id":null}
09:21:21 - Stratum notify: invalid parameters
March 13, 2017, 03:05:41 AM
please give me windows compile minerd if you have one .
sorry can't find one.
March 13, 2017, 03:02:07 AM
please give me windows compile minerd if you have one .
March 13, 2017, 02:58:45 AM
ahh , i guess its an issue with algorithm multiplier setting for ex: sha256 multiplier is 1 ,keccak multiplier is Math.Pow(2, 8 ).
March 13, 2017, 02:54:25 AM
here my test pool . can anyone test it for me, please...
stratum+tcp://213.125.232.37:3334
-u=address -p x
i am having all 480x AMD gpus, but problem is claymore not support latest gpus.
and i not have any nvidia gpus.
stratum+tcp://213.125.232.37:3334
-u=address -p x
i am having all 480x AMD gpus, but problem is claymore not support latest gpus.
and i not have any nvidia gpus.
Stratum authentication failed
your address start with = , sorry typo mistake
it should be -u address -p x
thanks.
now:
08:49:07 - Stratum difficulty set to 512
08:49:07 - Stratum notify: invalid parameters
{"method":"mining.notify","params":["4","e5450e9d4cbde69d3fbce5207ffab1155764ddb5f03f721e0604c02100000000","01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff25030eeb142f503253482f03efb91608","0d2f436f696e69756d536572762f0000000002897ea3bbd30100001976a914a04c734d1754c9adf ad0a77aeef784bffc38147f88accdc57db9040000001976a914f880e402b50b12d4c127c36173b7 e3744337b4a288ac00000000",["669934a4e20b868a1f64062c760d32924c5e488c61d149fe8eb173d34d3c9f6c"],"00000001","31812.966828","58c64f21",true],"id":null}
here is what suprnova returns instead:
{"params": ["4596", "12bc06197cecc8c0dd243600764eedc1dbb6495058ff6a73941dfd1f00000000", "1b9eae83f89a83a2cc547cddff96ce4054943728f71bc2b9ef622134b3d9c23f", "215ac6c55a77a7c9fb72bb6f6a6d1f74b3dc7463fe7ab2cc046d1b1b2a1d737a", 1370898, "0001", "0000000058c64fcf", false], "id": null, "method": "mining.notify"}
March 13, 2017, 02:53:58 AM
pallas , do you have windows compiled minerd? , it will be helpful for me to try few tests myself.
i see you miner keep disconnecting somehow...
i see you miner keep disconnecting somehow...
March 13, 2017, 02:46:09 AM
here my test pool . can anyone test it for me, please...
stratum+tcp://213.125.232.37:3334
-u=address -p x
i am having all 480x AMD gpus, but problem is claymore not support latest gpus.
and i not have any nvidia gpus.
stratum+tcp://213.125.232.37:3334
-u=address -p x
i am having all 480x AMD gpus, but problem is claymore not support latest gpus.
and i not have any nvidia gpus.
Stratum authentication failed
your address start with = , sorry typo mistake
it should be -u address -p x
March 13, 2017, 02:44:53 AM
ahh, one more thing need to setup, what can be possible vardiff range for M7?
I suggest 512 - 65536
March 13, 2017, 02:43:31 AM
here my test pool . can anyone test it for me, please...
stratum+tcp://213.125.232.37:3334
-u=address -p x
i am having all 480x AMD gpus, but problem is claymore not support latest gpus.
and i not have any nvidia gpus.
stratum+tcp://213.125.232.37:3334
-u=address -p x
i am having all 480x AMD gpus, but problem is claymore not support latest gpus.
and i not have any nvidia gpus.
Stratum authentication failed
March 13, 2017, 02:43:10 AM
ahh, one more thing need to setup, what can be possible vardiff range for M7?
March 13, 2017, 02:40:35 AM
Here it is, new blockchain snapshot:
https://mega.nz/#!JBpXhZLA!CSAKL2oa-EFoQnaAsxIhVdo-ur9Dby4bb3gmYykJlq0
https://mega.nz/#!JBpXhZLA!CSAKL2oa-EFoQnaAsxIhVdo-ur9Dby4bb3gmYykJlq0
WARNING: AFTER CLEAN ALL DATA FILES (EXCEPT WALLET.DAT) AND USE BLOCKCHAIN SNAPSHOT ABOVE, MY WALLET HAS BROKEN
Tried to use -salvagewallet or even -upgradewallet not no luck.
I copied old wallet.dat to new data folder, and open the QT again, not loading normally but end up with empty wallet, no transactions, no receiving address. It create wallet.xxxxx.bak in the data folder.
Did you use the same wallet binary now and before? Did you try a wallet backup?
March 13, 2017, 02:29:01 AM
here my test pool . can anyone test it for me, please...
stratum+tcp://213.125.232.37:3334
-u address -p x
i am having all 480x AMD gpus, but problem is claymore not support latest gpus.
and i not have any nvidia gpus.
stratum+tcp://213.125.232.37:3334
-u address -p x
i am having all 480x AMD gpus, but problem is claymore not support latest gpus.
and i not have any nvidia gpus.
March 13, 2017, 02:07:56 AM
can anyone provide me link for compiled minerd for windows?
March 13, 2017, 01:59:01 AM
pool require this
"coinbaseaux" : {
"flags" : "062f503253482f"
}
but it doesn't exist in getblocktemplate?
"coinbaseaux" : {
"flags" : "062f503253482f"
}
but it doesn't exist in getblocktemplate?
March 12, 2017, 11:15:53 PM
I just downloaded that blockchain, allowed it to sync and made som test transactions to BTER. Everything worked smooth, so probably something just went wrong on your particular wallet.
I just work properly with old wallet QT... dont know what happen... felling worried about my coins in wallet
March 12, 2017, 11:13:22 PM
Here it is, new blockchain snapshot:
https://mega.nz/#!JBpXhZLA!CSAKL2oa-EFoQnaAsxIhVdo-ur9Dby4bb3gmYykJlq0
https://mega.nz/#!JBpXhZLA!CSAKL2oa-EFoQnaAsxIhVdo-ur9Dby4bb3gmYykJlq0
WARNING: AFTER CLEAN ALL DATA FILES (EXCEPT WALLET.DAT) AND USE BLOCKCHAIN SNAPSHOT ABOVE, MY WALLET HAS BROKEN
Tried to use -salvagewallet or even -upgradewallet not no luck.
I copied old wallet.dat to new data folder, and open the QT again, not loading normally but end up with empty wallet, no transactions, no receiving address. It create wallet.xxxxx.bak in the data folder.
What happenning with my wallet, my coin>?
[/quote]
I just downloaded that blockchain, allowed it to sync and made som test transactions to BTER. Everything worked smooth, so probably something just went wrong on your particular wallet.
March 12, 2017, 09:02:53 PM
Here it is, new blockchain snapshot:
https://mega.nz/#!JBpXhZLA!CSAKL2oa-EFoQnaAsxIhVdo-ur9Dby4bb3gmYykJlq0
https://mega.nz/#!JBpXhZLA!CSAKL2oa-EFoQnaAsxIhVdo-ur9Dby4bb3gmYykJlq0
WARNING: AFTER CLEAN ALL DATA FILES (EXCEPT WALLET.DAT) AND USE BLOCKCHAIN SNAPSHOT ABOVE, MY WALLET HAS BROKEN
Tried to use -salvagewallet or even -upgradewallet not no luck.
I copied old wallet.dat to new data folder, and open the QT again, not loading normally but end up with empty wallet, no transactions, no receiving address. It create wallet.xxxxx.bak in the data folder.
What happenning with my wallet, my coin>?
debug.log
Quote
2017-03-13 03:48:02 Cryptonite version v0.1.1.0-g3fb0591-beta (Sun, 26 Oct 2014 23:10:32 +1100)
2017-03-13 03:48:02 Using OpenSSL version OpenSSL 1.0.1l 15 Jan 2015
2017-03-13 03:48:02 Default data directory C:\Users\XXX\AppData\Roaming\Cryptonite
2017-03-13 03:48:02 Using data directory F:\XXX\XCN\data
2017-03-13 03:48:02 Using at most 125 connections (2048 file descriptors available)
2017-03-13 03:48:02 Using 8 threads for script verification
2017-03-13 03:48:02 Using wallet wallet-original.dat
2017-03-13 03:48:02 init message: Verifying wallet...
2017-03-13 03:48:02 CDBEnv::Open : LogDir=F:\XXX\XCN\data\database ErrorFile=F:\PTS-RDP\XCN\data\db.log
2017-03-13 03:48:02 Renamed wallet-original.dat to wallet.1489376882.bak
2017-03-13 03:48:02 CDBEnv::Salvage : Database salvage found errors, all data may not be recoverable.
2017-03-13 03:48:02 Salvage(aggressive) found no records in wallet.1489376882.bak.
2017-03-13 03:48:02 Initialization result: 0
2017-03-13 03:48:02 Requesting shutdown
2017-03-13 03:48:02 Running Shutdown in thread
2017-03-13 03:48:02 Shutdown : In progress...
2017-03-13 03:48:02 StopNode()
2017-03-13 03:48:02 Shutdown : done
2017-03-13 03:48:02 Shutdown finished
2017-03-13 03:48:02 Shutdown result: 1
2017-03-13 03:48:02 Stopping thread
2017-03-13 03:48:02 Stopped thread
2017-03-13 03:48:02 Using OpenSSL version OpenSSL 1.0.1l 15 Jan 2015
2017-03-13 03:48:02 Default data directory C:\Users\XXX\AppData\Roaming\Cryptonite
2017-03-13 03:48:02 Using data directory F:\XXX\XCN\data
2017-03-13 03:48:02 Using at most 125 connections (2048 file descriptors available)
2017-03-13 03:48:02 Using 8 threads for script verification
2017-03-13 03:48:02 Using wallet wallet-original.dat
2017-03-13 03:48:02 init message: Verifying wallet...
2017-03-13 03:48:02 CDBEnv::Open : LogDir=F:\XXX\XCN\data\database ErrorFile=F:\PTS-RDP\XCN\data\db.log
2017-03-13 03:48:02 Renamed wallet-original.dat to wallet.1489376882.bak
2017-03-13 03:48:02 CDBEnv::Salvage : Database salvage found errors, all data may not be recoverable.
2017-03-13 03:48:02 Salvage(aggressive) found no records in wallet.1489376882.bak.
2017-03-13 03:48:02 Initialization result: 0
2017-03-13 03:48:02 Requesting shutdown
2017-03-13 03:48:02 Running Shutdown in thread
2017-03-13 03:48:02 Shutdown : In progress...
2017-03-13 03:48:02 StopNode()
2017-03-13 03:48:02 Shutdown : done
2017-03-13 03:48:02 Shutdown finished
2017-03-13 03:48:02 Shutdown result: 1
2017-03-13 03:48:02 Stopping thread
2017-03-13 03:48:02 Stopped thread
db.log
Quote
file wallet.dat has LSN 1/2295, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/2295, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/2295, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/2295 past current end-of-log of 1/476
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 10
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
file unknown has LSN 1/15617, past end of log at 1/28
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
Page 0: metadata page corrupted
Page 0: could not check metadata page
wallet.dat: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 1/15617, past end of log at 1/1073
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
wallet.1489369816.bak: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 1/15617, past end of log at 1/1257
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
__db_meta_setup: F:\PTS-RDP\XCN\data\wallet.dat: unexpected file type or format
file unknown has LSN 1/15617, past end of log at 1/2397
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
wallet.1489370397.bak: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 1/15617, past end of log at 1/1103
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
wallet.1489376882.bak: DB_VERIFY_BAD: Database verification failed
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/2295, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
file wallet.dat has LSN 1/2295, past end of log at 1/476
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
DB_ENV->log_flush: LSN of 1/2295 past current end-of-log of 1/476
Database environment corrupt; the wrong log files may have been removed or incompatible database files imported from another environment
PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
wallet.dat: unable to flush page: 10
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
PANIC: fatal region error detected; run recovery
file unknown has LSN 1/15617, past end of log at 1/28
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
Page 0: metadata page corrupted
Page 0: could not check metadata page
wallet.dat: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 1/15617, past end of log at 1/1073
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
wallet.1489369816.bak: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 1/15617, past end of log at 1/1257
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
__db_meta_setup: F:\PTS-RDP\XCN\data\wallet.dat: unexpected file type or format
file unknown has LSN 1/15617, past end of log at 1/2397
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
wallet.1489370397.bak: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 1/15617, past end of log at 1/1103
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
wallet.1489376882.bak: DB_VERIFY_BAD: Database verification failed
Jump to: