I found on wikipedia a better explanation of number 42, I guess we should stick with this: 42 (forty-two) is the natural number immediately following 41 and directly preceding 43.
I just did the math 1,000,000 blocks current block is: 347,058 2,064 blocks per day : 753,350 block per year. therefore my man - this coin will be mined out in less than 1 year  |
|
|
|
No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..
no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best. i just did that.. nothing special mate. also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention. I suspect your server, your connectivity or your pool wallet has a problem, not the network. look here: https://qtl.suprnova.cc/index.php?page=dashboardand refresh every 2-3 mins.. you'll see the blocks come in as usual and expected actually - I have been comparing dashboards and I am right - often it does not refresh every two to three minutes - sometime it can be 10 to 15 minutes or longer because a new block is released into the block chain. http://qtl.lifeforce.info/index.php?page=dashboardsame mpos software - same block chain - the block chain freezes from time to time....and then all of a sudden a bunch of blocks are released. 46501, 502, 503, 504 and 505 were all released into the chain within 1 minute of each other. these two blocks were 9 seconds apart 2014-09-11 22:04:14 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-09-11 22:04:20 received block b9c88b91d00f478a38d35ffe53268b20f72b143a56a197403f85aacad8d86d88
2014-09-11 22:04:20 Committing 1 changed transactions to coin database...
2014-09-11 22:04:20 SetBestChain: new best=b9c88b91d00f478a38d35ffe53268b20f72b143a56a197403f85aacad8d86d88 height=46503 log2_work=53.199544 tx=59785 date=2014-09-11 22:03:38 progress=0.999992
2014-09-11 22:04:20 ProcessBlock: ACCEPTED
2014-09-11 22:04:20 CreateNewBlock(): total size 1000
2014-09-11 22:04:38 ThreadRPCServer method=getblockhash
2014-09-11 22:04:42 AcceptToMemoryPool: 192.99.167.159:17012 /Satoshi:0.1.1.2/ : accepted e01ab890d9e636efded7d3ff0c7fb21b3b045d5e3ce2939093207fcc8466cb3d (poolsz 1)
2014-09-11 22:04:42 CreateNewBlock(): total size 1193
2014-09-11 22:04:42 received getdata for: tx e01ab890d9e636efded7d3ff0c7fb21b3b045d5e3ce2939093207fcc8466cb3d
2014-09-11 22:04:55 AcceptToMemoryPool: 72.78.100.12:17012 /Satoshi:0.1.1.2/ : accepted 2a84cb58b45ca9cda1d0b839791d9284af90518992980f72aea715fbbdd08343 (poolsz 2)
2014-09-11 22:04:55 CreateNewBlock(): total size 1385
2014-09-11 22:05:01 ThreadRPCServer method=getinfo
2014-09-11 22:05:01 keypool reserve 2
2014-09-11 22:05:01 keypool return 2
2014-09-11 22:05:01 ThreadRPCServer method=listsinceblock
2014-09-11 22:05:02 ThreadRPCServer method=help
2014-09-11 22:05:02 ThreadRPCServer method=listaccounts
2014-09-11 22:05:02 ThreadRPCServer method=getbalance
2014-09-11 22:05:02 ThreadRPCServer method=listaccounts
2014-09-11 22:05:02 ThreadRPCServer method=getbalance
2014-09-11 22:05:10 received block c4ecde1f809648d5cb1402f6380b492da613dcc85bc59aa2cfe7fcaa4a76bcbd
2014-09-11 22:05:10 Committing 3 changed transactions to coin database...
2014-09-11 22:05:10 SetBestChain: new best=c4ecde1f809648d5cb1402f6380b492da613dcc85bc59aa2cfe7fcaa4a76bcbd height=46504 log2_work=53.199598 tx=59786 date=2014-09-11 22:03:47 progress=0.999984
2014-09-11 22:05:10 ProcessBlock: ACCEPTED
2014-09-11 22:05:10 CreateNewBlock(): total size 1385
2014-09-11 22:05:10 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-09-11 22:05:17 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-09-11 22:05:32 received block 018f32f6ab2aad1ab432eab4615b5005439c562da7da3ac46414fd9e8eac3ec6
|
|
|
|
|
sam - how long before they're all minted? have you done the math?
you never know what kind of life a coin will have after they're all minted - some coins live long and prosper and some just fade way - I think it depends on the dev and if the dev tries to breath new life into the coin with some marketing.
|
|
|
|
Mr_MarKus,
Can you guys update the list of pools?
Some of those pools don't seem to live anymore.
Also, what pools are other people using?
i'm mining on suprnova - as usual - and mostly alone - all coins for me ^^:) I'll be throwing 275MH at the coin tomorrow on qtl.lifeforce.info if you want to find more blocks and join me. |
|
|
|
There is good node support No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..
no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best. i just did that.. nothing special mate. also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention. I suspect your server, your connectivity or your pool wallet has a problem, not the network. look here: https://qtl.suprnova.cc/index.php?page=dashboardand refresh every 2-3 mins.. you'll see the blocks come in as usual and expected I have refreshed and I see what it's not doing. please post your nodes. lots of nodes, currently 42 connections: http://pastebin.com/EHVkU5WFI will try your node list thanks ps: does this coin need "txMessages": true in the stratum - some coins do - like syscoin... and thanks your posted nodes are much better - this is the only wallet that has been giving me problems. but it's humming along fine now |
|
|
|
No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..
no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best. i just did that.. nothing special mate. also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention. I suspect your server, your connectivity or your pool wallet has a problem, not the network. look here: https://qtl.suprnova.cc/index.php?page=dashboardand refresh every 2-3 mins.. you'll see the blocks come in as usual and expected I have refreshed and I see what it's not doing. please post your nodes. lots of nodes, currently 42 connections: http://pastebin.com/EHVkU5WFVersion Protocol Version Wallet Version Connections Errors 10102 70002 10000 8 OK I compiled the wallet from the source posted in the OP - is there newer source? |
|
|
|
No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..
no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best. i just did that.. nothing special mate. also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention. I suspect your server, your connectivity or your pool wallet has a problem, not the network. look here: https://qtl.suprnova.cc/index.php?page=dashboardand refresh every 2-3 mins.. you'll see the blocks come in as usual and expected I have refreshed and I see what it's not doing. please post your nodes. root@ns500637:/home/wallets/.quatloo# quatlood getpeerinfo
[
{
"addr" : "72.78.100.5:17012",
"services" : "00000003",
"lastsend" : 1410470532,
"lastrecv" : 1410470536,
"bytessent" : 1777589,
"bytesrecv" : 21659468,
"blocksrequested" : 0,
"conntime" : 1410463419,
"version" : 70002,
"subver" : "/Satoshi:0.1.1.2/",
"inbound" : false,
"startingheight" : 46405,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "72.78.100.7:17012",
"services" : "00000003",
"lastsend" : 1410470536,
"lastrecv" : 1410470536,
"bytessent" : 155967,
"bytesrecv" : 1908224,
"blocksrequested" : 0,
"conntime" : 1410463419,
"version" : 70002,
"subver" : "/Satoshi:0.1.1.2/",
"inbound" : false,
"startingheight" : 46405,
"banscore" : 0
},
{
"addr" : "72.78.100.13:17012",
"services" : "00000003",
"lastsend" : 1410470536,
"lastrecv" : 1410470536,
"bytessent" : 159551,
"bytesrecv" : 1893337,
"blocksrequested" : 0,
"conntime" : 1410463421,
"version" : 70002,
"subver" : "/Satoshi:0.1.1.2/",
"inbound" : false,
"startingheight" : 46405,
"banscore" : 0
},
{
"addr" : "46.105.118.15:17012",
"services" : "00000003",
"lastsend" : 1410470532,
"lastrecv" : 1410470536,
"bytessent" : 234921,
"bytesrecv" : 1939933,
"blocksrequested" : 0,
"conntime" : 1410463427,
"version" : 70002,
"subver" : "/Satoshi:0.1.1.2/",
"inbound" : false,
"startingheight" : 46405,
"banscore" : 0
},
{
"addr" : "82.226.151.241:17012",
"services" : "00000003",
"lastsend" : 1410470671,
"lastrecv" : 1410470672,
"bytessent" : 2138686,
"bytesrecv" : 5060105,
"blocksrequested" : 0,
"conntime" : 1410463432,
"version" : 70002,
"subver" : "/Satoshi:0.1.1.2/",
"inbound" : false,
"startingheight" : 46405,
"banscore" : 0
},
{
"addr" : "192.99.167.159:17012",
"services" : "00000003",
"lastsend" : 1410470532,
"lastrecv" : 1410470536,
"bytessent" : 150263,
"bytesrecv" : 1883949,
"blocksrequested" : 0,
"conntime" : 1410463514,
"version" : 70002,
"subver" : "/Satoshi:0.1.1.2/",
"inbound" : false,
"startingheight" : 46405,
"banscore" : 0
},
{
"addr" : "162.243.118.225:17012",
"services" : "00000003",
"lastsend" : 1410470536,
"lastrecv" : 1410470536,
"bytessent" : 156816,
"bytesrecv" : 1900687,
"blocksrequested" : 0,
"conntime" : 1410463533,
"version" : 70002,
"subver" : "/Satoshi:0.1.1.2/",
"inbound" : false,
"startingheight" : 46405,
"banscore" : 0
},
{
"addr" : "54.244.118.104:17012",
"services" : "00000003",
"lastsend" : 1410470536,
"lastrecv" : 1410470531,
"bytessent" : 19943,
"bytesrecv" : 21870,
"blocksrequested" : 0,
"conntime" : 1410469120,
"version" : 70002,
"subver" : "/Satoshi:0.1.1.2/",
"inbound" : false,
"startingheight" : 46455,
"banscore" : 0
}
]
root@ns500637:/home/wallets/.quatloo#
|
|
|
|
No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..
no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best. and it's been 500 blocks since that pool has even found a block so how would you know? |
|
|
|
block chain has been stuck at 46,405 for the last few hours
you guys need some reliable nodes - block chain get stuck and then pops lose... I had added this coin to my pools - but because of the block chain problems - I'm removing it -nothing but complaints from miners....lots of wasted hash |
|
|
|
|
block chain has been stuck at 46,405 for the last few hours
|
|
|
|
that's the problem with the block chain on this coin? are the nodes simply turned on and off every 30 minutes? if you take a look and the chain you'll see that no blocks were generated for nearly an hour as of the time this snapshop was taken. 2014-09-11 18:48:59 SetBestChain: new best=13551833ab336f55daebfcfaabf925b74c16a338b70fd724cb8176f33b0f032f height=46387 log2_work=53.196148 tx=59649 date=2014-09-11 17:49:19 progress=0.999306
2014-09-11 18:48:59 SetBestChain: new best=30ec8d19336d6aed70f5f56ab305d1a719b6afcc060c00644129a4dcffbd9d24 height=46388 log2_work=53.19618 tx=59651 date=2014-09-11 17:49:28 progress=0.999308
2014-09-11 18:48:59 SetBestChain: new best=24da23581a560de5470eb72a151859d8765294ad9cdd1d133a9fc69c56cfcce3 height=46389 log2_work=53.196211 tx=59652 date=2014-09-11 17:49:31 progress=0.999308
2014-09-11 18:48:59 SetBestChain: new best=5f434a4234017c9e84bd6b477938fd5a51d3f48ac6cf4a754982a30efe9df917 height=46390 log2_work=53.196243 tx=59653 date=2014-09-11 17:49:40 progress=0.999310
2014-09-11 18:48:59 SetBestChain: new best=25c83c751bfb85c2cb0625b6a7f1b447e439fde615b8f121bf2ff89e3f07cc71 height=46391 log2_work=53.196273 tx=59654 date=2014-09-11 17:49:43 progress=0.999311
2014-09-11 18:48:59 SetBestChain: new best=c1b8e5ff9d13fbe5e407d92fe70ff34faf2fd2688ca059e5dfeb0ea3ad5416af height=46392 log2_work=53.196304 tx=59655 date=2014-09-11 17:49:44 progress=0.999311
2014-09-11 18:48:59 SetBestChain: new best=2a8ee177eba20ea9807a0e06532b33691bcdf70037a938364484c16f83e8e14f height=46393 log2_work=53.196334 tx=59656 date=2014-09-11 17:49:46 progress=0.999311
2014-09-11 18:48:59 SetBestChain: new best=536553e3150c9fdf84e71463665636a24da0cd3c3bdc2b4dee811fb49fa88d9c height=46394 log2_work=53.196365 tx=59657 date=2014-09-11 17:49:47 progress=0.999311
2014-09-11 18:48:59 SetBestChain: new best=9639230461e38f37ea52c3e399d0be8f1c6d60beb6d05d86dc1ec41f9427a4d2 height=46395 log2_work=53.196395 tx=59658 date=2014-09-11 17:49:49 progress=0.999312
2014-09-11 18:48:59 SetBestChain: new best=fd7b45065dd931d6a36c0b9fc722a9db982ebf892876332832bdfca1a58551dc height=46396 log2_work=53.196425 tx=59659 date=2014-09-11 17:49:56 progress=0.999313
2014-09-11 18:48:59 SetBestChain: new best=8c80ae9dd84e86ae1dc135e22c21a0ea0f8de3e3f5f83818cdc85f3973fd68e3 height=46397 log2_work=53.196454 tx=59660 date=2014-09-11 17:50:05 progress=0.999315
2014-09-11 18:48:59 SetBestChain: new best=8ad5dad3e2b7f3362657a75934dd45c3ce0d2a71bd6b1a1f0aa5223e61860a5e height=46398 log2_work=53.196483 tx=59662 date=2014-09-11 17:50:12 progress=0.999316
2014-09-11 18:48:59 SetBestChain: new best=1b10665e4cb9699f9f0bdaed10b9727990727eb27b600b9afb28c531603ffe6a height=46399 log2_work=53.196512 tx=59663 date=2014-09-11 17:50:14 progress=0.999317
2014-09-11 18:48:59 SetBestChain: new best=61f136f188424d26dc971454417a8e1fbe101b001efde7e831784ca1bc0c2b94 height=46400 log2_work=53.196541 tx=59664 date=2014-09-11 17:50:19 progress=0.999318
2014-09-11 18:48:59 SetBestChain: new best=ab83329da63ed383728fe3048e9a1d1308cd939b537612bc6e95e5eb18a05092 height=46401 log2_work=53.19657 tx=59666 date=2014-09-11 17:50:23 progress=0.999318
2014-09-11 18:48:59 SetBestChain: new best=cf8861fd18bc8d51ee457ea088794208a2d063de5ccf0af2ea383a6022833bfb height=46402 log2_work=53.196598 tx=59667 date=2014-09-11 17:50:33 progress=0.999320
2014-09-11 18:48:59 SetBestChain: new best=e4d1f7015f48f4ef1d5e5f9f7a18f7215ec2393089c1aba2bf89b3e607099309 height=46403 log2_work=53.196626 tx=59668 date=2014-09-11 17:50:38 progress=0.999321
2014-09-11 18:48:59 SetBestChain: new best=37416facd21df54d818b7da8b5de486412a0d8fbf55dd8a6341494bc17bb6f59 height=46404 log2_work=53.196656 tx=59669 date=2014-09-11 17:50:44 progress=0.999323
2014-09-11 18:48:59 SetBestChain: new best=b200f0eb0e34677a34b66c5eafd1b9402062c1bc6f401f8ef542f20b7f93aa84 height=46405 log2_work=53.196751 tx=59670 date=2014-09-11 17:50:47 progress=0.999323
|
|
|
|
|
wallet/stratum question:
do txtx messages needs to be set to true for this wallet?
"algorithm": "scrypt",
"txMessages": true
??
|
|
|
|
YOUR BLOCKCHAIN IS STUCK. you isseud your last block over 2 hours ago. Lifeforce Pools is shutting down the stratum port for TopCoin until the devs get the problem fixed. connection timeout
trying connection 54.244.114.212:20821 lastseen=2.1hrs
connection timeout
trying connection 71.218.197.198:20821 lastseen=2.6hrs
connection timeout
root@ns500637:~/.42# tail -f /root/.TopCoin2/debug.log
trying connection 54.244.114.212:20821 lastseen=2.3hrs
Flushed 122 addresses to peers.dat 2ms
connection timeout
trying connection 64.208.157.250:20821 lastseen=3.5hrs
connect() failed after select(): Connection refused
trying connection 201.127.125.204:20821 lastseen=26.6hrs
ThreadRPCServer method=submitblock
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
connection timeout
trying connection 194.151.121.212:20821 lastseen=4.4hrs
|
|
|
|
Getting reports of missing deposits from user
Txids not found in wallet
Block hashes non existant in blockchain
I have suspended 42 deposits and withdrawals until we can get a consensus on the situation
good idea. Only just got round to investigating this. TXID e9ada5d200bd1c4e294bf95a08fd465baa83b6e8323acac14b1f6ac8bac03b53 gone astray ! Im using v0.7.0.0-gbff08fa-beta, noticed transferring between wallets or cryptsy TX disappears. Tried New Wallet: http://www.mediafire.com/download/7m652pme8x9pdxo/42-Win-QT_7.00.zipNew .Conf File: http://www.mediafire.com/download/hnahh4e86zdue1u/42.confStill no joy. Just installed windows wallet: https://www.mediafire.com/?26oz9d29fh9zpzj If it actually sent on the official 42 blockchain then Bigvern at Cryptsy should not have a problem helping you. If it sent on the old chain then you will have to get the newest client and rescan to recover the coins.` Ah, hold on while 9months of blockchain download ...... So how do you know what chain U R on ? you're on the old block chain for sure you can check here: http://42.altcoinexplorer.cf/here's a recent deposit of mine on the new block chain: 52f50ed48661bec9182be2c710a7cc73eca46d1107a549bcdd1d6899251d41e0 |
|
|
|
Getting reports of missing deposits from user
Txids not found in wallet
Block hashes non existant in blockchain
I have suspended 42 deposits and withdrawals until we can get a consensus on the situation
good idea. Only just got round to investigating this. TXID e9ada5d200bd1c4e294bf95a08fd465baa83b6e8323acac14b1f6ac8bac03b53 gone astray ! Im using v0.7.0.0-gbff08fa-beta, noticed transferring between wallets or cryptsy TX disappears. Tried New Wallet: http://www.mediafire.com/download/7m652pme8x9pdxo/42-Win-QT_7.00.zipNew .Conf File: http://www.mediafire.com/download/hnahh4e86zdue1u/42.confStill no joy. Just installed windows wallet: https://www.mediafire.com/?26oz9d29fh9zpzj If it actually sent on the official 42 blockchain then Bigvern at Cryptsy should not have a problem helping you. If it sent on the old chain then you will have to get the newest client and rescan to recover the coins.` Ah, hold on while 9months of blockchain download ...... So how do you know what chain U R on ? my 42 coins have been making it just fine to cryptsy for about 6 weeks now. |
|
|
|
Jeremy this looks good. have you compiled this yourself ? Why did you decide to compile the wallet and help out? I see the mining is still up and down. I've been watching CoinWarz.com for the past 3 months since I enjoy mining for the most profitable. 42 has been the most profitable in the top 10 for a long time now. http://www.coinwarz.com/cryptocurrencyhttp://www.coinwarz.com/cryptocurrency/coins/42Seems like coinwarz had it listed as the #1 most profitable coin since this morning. It's been very stable in the top 1-5 positions for a while expect no one talks about it here. The answer to your question is very simple and I'm a little surprised you're even asking - here's the way it works. There are only N number of 42coins minted per day for mining. 'N' number - and the more people you have competing for those 'N' number of coins the less each individual makes with his or her given Hash. so raising awareness accomplishes one thing: less profit for each of the individuals smart enough to determine the coin was a good bet on their own. I've been mining this coin like crazy for months since it fell to 2.5 BTC because I knew it was a good investment. Coinwarz and Whatmine serve one purpose and that's to point lazy miners in the right direction, however those site also ruins it for the people who do their own research and bring a good thing to an end. Now that 42's Network hash is over 2 GH/s it's time me to move on to another coin since 'the word is out' and profitability is going down faster than a sinking ship. My mining philosophy is in direct contradiction to the multi pools and sites like Coinwarz. They only look at instant profitability and the problem is (or good thing for me) is that many people follow their top list list like lemmings and run from coin to coin only to discover that once they arrive, that network hash and difficulty have skyrocketed and then they sit and wonder why that haven't made what Coinwarz said they would make - well DUH!!! I work the opposite way - I ONLY mine coins with low network hash that have low difficulties and are in troughs value wise and thank you very much - it works great for me. 42 has been like that for the past 3 months. YEEHAW! - Sold at 14 yesterday and mined at 2.5 when Network Hash was down around 400MH. do yourself a favor when you visit those sites - start looking at the bottom of their lists - not the top - you'll be much better off long term and never late to the show. LOL |
|
|
|
Yes, I am still holding. After dumping, rise again. I'm throwing 275 MH of my own at it right now - could use a little help |
|
|
|
Because I like the coin - it has tremendous upside potential and I think with the right marketing it could do well.
this coin was selling for 23 BTC a few months ago!
Sounds like you need more than just a one time update, someone has to support the coin and it's more than a full time job. You should do a take over and organize a team to stand behind the coin. well - it you take a look at that 42 thread you'll see that's exactly what I'm trying to do... |
|
|
|
|
My only caution to everyone about his coin is that it has a very limited mining value per day.
.000042 is the block reward and blocks are created every 42 seconds.
at it's current value; the total per day is : .000042 * 85 (blocks per hour) * 24 hours = .08568 42/day which equals about $212 / day in mineable coins.
compare this is a coin like QTL that has a block value of over $1 and the totals there are about $640 / day in mineable coins
just an fyi....
|
|
|
|
|
Show Posts
