Topic: [ANN] Tianhe 天河 [TIA] POW ONLY | LYRA2REv2 | No ICO/Premine | Ninja Launched - page 6. (Read 14256 times)
September 14, 2015, 10:40:49 AM
not working on 32bit windows ?
September 14, 2015, 10:35:55 AM
That is for TestNet as you can see and its not important, simply forgot to change the L letter and its no big issue, yes a clone from Lyrabar but the hash files changed to V2 as of vertcoin.
Lyrabar: https://github.com/Lyrabar/Lyrabar/blob/master/src/Lyra2RE/Lyra2.c and https://github.com/Lyrabar/Lyrabar/blob/master/src/Lyra2RE/Lyra2RE.c
tianhe : https://github.com/tianhecoin/tianhe/blob/master/src/Lyra2RE/Lyra2.c and https://github.com/tianhecoin/tianhe/blob/master/src/Lyra2RE/Lyra2RE.c
vertcoin : https://github.com/vertcoin/vertcoin/blob/master/src/Lyra2RE/Lyra2.c and https://github.com/vertcoin/vertcoin/blob/master/src/Lyra2RE/Lyra2RE.c
Lyrabar: https://github.com/Lyrabar/Lyrabar/blob/master/src/Lyra2RE/Lyra2.c and https://github.com/Lyrabar/Lyrabar/blob/master/src/Lyra2RE/Lyra2RE.c
tianhe : https://github.com/tianhecoin/tianhe/blob/master/src/Lyra2RE/Lyra2.c and https://github.com/tianhecoin/tianhe/blob/master/src/Lyra2RE/Lyra2RE.c
vertcoin : https://github.com/vertcoin/vertcoin/blob/master/src/Lyra2RE/Lyra2.c and https://github.com/vertcoin/vertcoin/blob/master/src/Lyra2RE/Lyra2RE.c
The Github page seems to be still private, so had to check bitbucket.
True, the algo is changed to Lyra2REv2, you're right. Still, a concensus should be achieved that two coins can't have same Protocol version in the wallet, Base58 addressing and same pchMessages.
Can't have two wallets that can see each other.
If the developer is not changing at least two of those, pchmessage magics and the addressing, hope at least Lyrabar developer makes the old protocol version incompatible in their updates with the version Tianhe have.
I can't host you a pool if those are not met, the stratum will not work because I'm already running a LYB Pool on the poolserver.
At this start point of your chain, modifications that only supports your coin are very recommended. Not a big deal to start from beginning.
September 14, 2015, 10:19:56 AM
NOT FUDding, but really:
At least change main values from Lyrabar, pchMessageStart hex's and too many values are identical with Lyrabar.
main.cpp:
if (fTestNet)
{
pchMessageStart[0] = 0x4d;
pchMessageStart[1] = 0x4c;
pchMessageStart[2] = 0x4d;
pchMessageStart[3] = 0x4c;
hashGenesisBlock = uint256("0xaee7d4e5636f6899faa729aa26e543f0d06d3ee9ccdc56b385c4a668410cfcc9"); // Testnet genesis block hash
}
...
unsigned char pchMessageStart[4] = { 0x4d, 0x4d, 0x4d, 0x4d };
...
base58.h
{
PUBKEY_ADDRESS = 48, // Tianhe addresses start with L
SCRIPT_ADDRESS = 5,
PUBKEY_ADDRESS_TEST = 111, // Tianhe testnet addresses start with l
SCRIPT_ADDRESS_TEST = 196,
};
Exactly same as Lyrabar's
...
Lyra2.c, Lyra2.h, Lyra2RE.c, Lyra2RE.h:
Not updated to v2, this is Lyra2RE version 1 coin, not version 2, so this is not with a Lyra2REv2 algo.
...and other parameters that may cause a fork with Lyrabar.
I Would put a pool, but this is a straight Lyrabar fork without changes with main parameters, what I recommend the the developer is that they should change at least those parameters and the walletversion value and start a new chain. The danger of the source available is it forks with Lyrabar.
At least change main values from Lyrabar, pchMessageStart hex's and too many values are identical with Lyrabar.
main.cpp:
if (fTestNet)
{
pchMessageStart[0] = 0x4d;
pchMessageStart[1] = 0x4c;
pchMessageStart[2] = 0x4d;
pchMessageStart[3] = 0x4c;
hashGenesisBlock = uint256("0xaee7d4e5636f6899faa729aa26e543f0d06d3ee9ccdc56b385c4a668410cfcc9"); // Testnet genesis block hash
}
...
unsigned char pchMessageStart[4] = { 0x4d, 0x4d, 0x4d, 0x4d };
...
base58.h
{
PUBKEY_ADDRESS = 48, // Tianhe addresses start with L
SCRIPT_ADDRESS = 5,
PUBKEY_ADDRESS_TEST = 111, // Tianhe testnet addresses start with l
SCRIPT_ADDRESS_TEST = 196,
};
Exactly same as Lyrabar's
...
Lyra2.c, Lyra2.h, Lyra2RE.c, Lyra2RE.h:
Not updated to v2, this is Lyra2RE version 1 coin, not version 2, so this is not with a Lyra2REv2 algo.
...and other parameters that may cause a fork with Lyrabar.
I Would put a pool, but this is a straight Lyrabar fork without changes with main parameters, what I recommend the the developer is that they should change at least those parameters and the walletversion value and start a new chain. The danger of the source available is it forks with Lyrabar.
That is for TestNet as you can see and its not important, simply forgot to change the L letter and its no big issue, yes a clone from Lyrabar but the hash files changed to V2 as of vertcoin.
Lyrabar: https://github.com/Lyrabar/Lyrabar/blob/master/src/Lyra2RE/Lyra2.c and https://github.com/Lyrabar/Lyrabar/blob/master/src/Lyra2RE/Lyra2RE.c
tianhe : https://github.com/tianhecoin/tianhe/blob/master/src/Lyra2RE/Lyra2.c and https://github.com/tianhecoin/tianhe/blob/master/src/Lyra2RE/Lyra2RE.c
vertcoin : https://github.com/vertcoin/vertcoin/blob/master/src/Lyra2RE/Lyra2.c and https://github.com/vertcoin/vertcoin/blob/master/src/Lyra2RE/Lyra2RE.c
September 14, 2015, 10:12:08 AM
NOT FUDding, but really:
At least change main values from Lyrabar, pchMessageStart hex's and too many values are identical with Lyrabar.
Developer has generated a new genesis block, but all the rest:
main.cpp:
if (fTestNet)
{
pchMessageStart[0] = 0x4d;
pchMessageStart[1] = 0x4c;
pchMessageStart[2] = 0x4d;
pchMessageStart[3] = 0x4c;
hashGenesisBlock = uint256("0xaee7d4e5636f6899faa729aa26e543f0d06d3ee9ccdc56b385c4a668410cfcc9"); // Testnet genesis block hash
}
...
unsigned char pchMessageStart[4] = { 0x4d, 0x4d, 0x4d, 0x4d };
...
base58.h
{
PUBKEY_ADDRESS = 48, // Tianhe addresses start with L
SCRIPT_ADDRESS = 5,
PUBKEY_ADDRESS_TEST = 111, // Tianhe testnet addresses start with l
SCRIPT_ADDRESS_TEST = 196,
};
Exactly same as Lyrabar's
...
Lyra2.c, Lyra2.h, Lyra2RE.c, Lyra2RE.h:
Not updated to v2, this is Lyra2RE version 1 coin, not version 2, so this is not with a Lyra2REv2 algo.
...and other parameters that may cause a fork with Lyrabar.
I Would put a pool, but this is a straight Lyrabar fork without changes with main parameters, what I recommend the the developer is that they should change at least those parameters and the walletversion value and start a new chain. The danger of the source available is it forks with Lyrabar.
I'll host a pool if all those be changed, can't run two coins on a stratum poolserver with same magic values. (I run a Lyrabar and Vertcoin pool myself)
At least change main values from Lyrabar, pchMessageStart hex's and too many values are identical with Lyrabar.
Developer has generated a new genesis block, but all the rest:
main.cpp:
if (fTestNet)
{
pchMessageStart[0] = 0x4d;
pchMessageStart[1] = 0x4c;
pchMessageStart[2] = 0x4d;
pchMessageStart[3] = 0x4c;
hashGenesisBlock = uint256("0xaee7d4e5636f6899faa729aa26e543f0d06d3ee9ccdc56b385c4a668410cfcc9"); // Testnet genesis block hash
}
...
unsigned char pchMessageStart[4] = { 0x4d, 0x4d, 0x4d, 0x4d };
...
base58.h
{
PUBKEY_ADDRESS = 48, // Tianhe addresses start with L
SCRIPT_ADDRESS = 5,
PUBKEY_ADDRESS_TEST = 111, // Tianhe testnet addresses start with l
SCRIPT_ADDRESS_TEST = 196,
};
Exactly same as Lyrabar's
...
Lyra2.c, Lyra2.h, Lyra2RE.c, Lyra2RE.h:
Not updated to v2, this is Lyra2RE version 1 coin, not version 2, so this is not with a Lyra2REv2 algo.
...and other parameters that may cause a fork with Lyrabar.
I Would put a pool, but this is a straight Lyrabar fork without changes with main parameters, what I recommend the the developer is that they should change at least those parameters and the walletversion value and start a new chain. The danger of the source available is it forks with Lyrabar.
I'll host a pool if all those be changed, can't run two coins on a stratum poolserver with same magic values. (I run a Lyrabar and Vertcoin pool myself)
September 14, 2015, 10:09:08 AM
Tianhe QQ Group 439671974
Tianhe QQ Group 439671974
Very nice , thanks
September 14, 2015, 09:36:57 AM
hmm lyra2rev2 
ill mine some
ill mine some 
September 14, 2015, 09:21:01 AM
Tianhe QQ Group 439671974
Tianhe QQ Group 439671974
September 14, 2015, 09:05:09 AM
September 14, 2015, 08:59:40 AM
addnode=45.32.233.53:7030
or
addnode=45.32.233.53
is the explorer node
or
addnode=45.32.233.53
is the explorer node
oh we got explorer already.. good!
September 14, 2015, 08:58:46 AM
addnode=45.32.233.53
is the explorer node
is the explorer node
September 14, 2015, 08:54:33 AM
addnode=45.32.232.190 , no sync
Code:
[
{
"addr" : "45.32.232.190:7031",
"services" : "00000003",
"lastsend" : 1442235061,
"lastrecv" : 1442235061,
"bytessent" : 1556,
"bytesrecv" : 4343,
"blocksrequested" : 0,
"conntime" : 1442235018,
"version" : 70002,
"subver" : "/Satoshi:0.9.0.1/",
"inbound" : false,
"startingheight" : 455,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "210.195.205.178:7031",
"services" : "00000003",
"lastsend" : 1442235061,
"lastrecv" : 1442235062,
"bytessent" : 290,
"bytesrecv" : 996,
"blocksrequested" : 0,
"conntime" : 1442235032,
"version" : 70002,
"subver" : "/Satoshi:0.9.0.1/",
"inbound" : false,
"startingheight" : 455,
"banscore" : 0
},
{
"addr" : "24.89.45.196:7031",
"services" : "00000003",
"lastsend" : 1442235039,
"lastrecv" : 1442235061,
"bytessent" : 229,
"bytesrecv" : 386,
"blocksrequested" : 0,
"conntime" : 1442235039,
"version" : 70002,
"subver" : "/Satoshi:0.9.0.1/",
"inbound" : false,
"startingheight" : 455,
"banscore" : 0
},
{
"addr" : "212.17.40.234:7031",
"services" : "00000003",
"lastsend" : 1442235039,
"lastrecv" : 1442235061,
"bytessent" : 229,
"bytesrecv" : 356,
"blocksrequested" : 0,
"conntime" : 1442235039,
"version" : 70002,
"subver" : "/Satoshi:0.9.0.1/",
"inbound" : false,
"startingheight" : 455,
"banscore" : 0
},
{
"addr" : "119.52.65.39:7031",
"services" : "00000003",
"lastsend" : 1442235061,
"lastrecv" : 1442235062,
"bytessent" : 991,
"bytesrecv" : 1057,
"blocksrequested" : 0,
"conntime" : 1442235046,
"version" : 70002,
"subver" : "/Satoshi:0.9.0.1/",
"inbound" : false,
"startingheight" : 455,
"banscore" : 0
},
{
"addr" : "93.157.25.130:7031",
"services" : "00000003",
"lastsend" : 1442235061,
"lastrecv" : 1442235061,
"bytessent" : 930,
"bytesrecv" : 356,
"blocksrequested" : 0,
"conntime" : 1442235046,
"version" : 70002,
"subver" : "/Satoshi:0.9.0.1/",
"inbound" : false,
"startingheight" : 455,
"banscore" : 0
},
{
"addr" : "31.215.224.56:7031",
"services" : "00000003",
"lastsend" : 1442235071,
"lastrecv" : 1442235072,
"bytessent" : 229,
"bytesrecv" : 295,
"blocksrequested" : 0,
"conntime" : 1442235070,
"version" : 70002,
"subver" : "/Satoshi:0.9.0.1/",
"inbound" : false,
"startingheight" : 456,
"banscore" : 0
}
]
September 14, 2015, 08:51:22 AM
addnode=45.32.232.190 , no sync
September 14, 2015, 08:32:54 AM
no HW, but only rejects with GPU solo-mining. 
yes gpu is not working for solo cpu only
need a pool
September 14, 2015, 08:32:28 AM
Hi dev, i can't download windows-qt wallet from mega,bitbucket.org, please replace to another filehosting
I'm not dev but here is another link
http://s000.tinyupload.com/index.php?file_id=46946927749217995432
https://www.virustotal.com/en/file/42137e9a6ed7a8b30a2ab88653e5d85a82fb1d8c1704b59e3768b3ed0d8da4dc/analysis/
thanks
September 14, 2015, 08:32:07 AM
no HW, but only rejects with GPU solo-mining.
September 14, 2015, 08:30:04 AM
Hi dev, i can't download windows-qt wallet from mega,bitbucket.org, please replace to another filehosting
I'm not dev but here is another link
http://s000.tinyupload.com/index.php?file_id=46946927749217995432
https://www.virustotal.com/en/file/42137e9a6ed7a8b30a2ab88653e5d85a82fb1d8c1704b59e3768b3ed0d8da4dc/analysis/
September 14, 2015, 08:29:15 AM
Tianhe QQ Group 439671974
September 14, 2015, 08:22:36 AM
Hi dev, i can't download windows-qt wallet from mega,bitbucket.org, please replace to another filehosting
September 14, 2015, 08:15:56 AM
{
"blocks" : 430,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.06994884,
"errors" : "",
"generate" : true,
"genproclimit" : 8,
"hashespersec" : 413528,
"networkhashps" : 1599648,
"pooledtx" : 0,
"testnet" : false
}
I would just ignore that guy.. He obviously purchased that Hero account..
September 14, 2015, 08:14:20 AM
diff is good for pool and gpu now
no way to late difficulty up 10,000%
"difficulty" : 0.06910183,
I still finding blocks with CPU! Found last 5 minutes ago...
Jump to: