Topic: [ANN] Mincoin Cryptocurrency Project, World's Fastest Rare Altcoin [ANN] - page 22. (Read 114841 times)
June 09, 2013, 02:56:55 AM
I would strongly advise against using any client that was not put out by the official MNC devs.
June 09, 2013, 01:19:56 AM
Total fail now... links all point to crap that doesn't work. Seems they only have it working for themselves, mining all the coins... again... All ten linux users.
Another-one bites the dust... dust-coin or bust.
0.6.3 beta = fail, will not even connect
0.6.4 beta = fail, will connect but 100% reject rate
The "links" point to 0.6.3, the ones that actually point to anything that runs. (Links to incomplete projects, links to failed GUI's links to failed binaries.)
dead = dead
Another-one bites the dust... dust-coin or bust.
0.6.3 beta = fail, will not even connect
0.6.4 beta = fail, will connect but 100% reject rate
The "links" point to 0.6.3, the ones that actually point to anything that runs. (Links to incomplete projects, links to failed GUI's links to failed binaries.)
dead = dead
Not sure what it is your doing wrong, but I am using the Windows GUI QT Client v0.6.4.0- beta and it is working PERFECTLY. In fact I just recently received an
auto-payout via vircurpool from the last time I had a miner running there. Also, I currently have 5 connections to the network and that fluctuates anywhere from 3-8.
As for mining, looks like there are currently 42 "workers" mining just on VirCurPool alone, and current network hashrate is about 33MH/s, down from around 52MH/s 40mins ago.
June 08, 2013, 11:23:07 PM
Total fail now... links all point to crap that doesn't work. Seems they only have it working for themselves, mining all the coins... again... All ten linux users.
Another-one bites the dust... dust-coin or bust.
0.6.3 beta = fail, will not even connect
0.6.4 beta = fail, will connect but 100% reject rate
The "links" point to 0.6.3, the ones that actually point to anything that runs. (Links to incomplete projects, links to failed GUI's links to failed binaries.)
dead = dead
Another-one bites the dust... dust-coin or bust.
0.6.3 beta = fail, will not even connect
0.6.4 beta = fail, will connect but 100% reject rate
The "links" point to 0.6.3, the ones that actually point to anything that runs. (Links to incomplete projects, links to failed GUI's links to failed binaries.)
dead = dead
June 08, 2013, 12:23:45 AM
Updated client reported those results...
Had to delete everything except my wallet, and let it rebuild from scratch... Seems the "code" is bugged, trying to handle forks. Might want to add an option to "Repair Block-chain", which simply rebuilds the chain from the latest valid blocks-up. Thus, also rebuilding the user DB also.
Ok, got it to work, mined for hours, got rejected for every valid block attempted to submit... then today... nothing... no connection to the network.
You need more than one node to keep this thing alive.
So what is the marketing strategy for this coin? Who is the target audience?
I would think this would be great for adding to a forum's "Reputation" payment integration. (Lots of these forums have ghetto coin-rewards or forum-currency.) That would help get a constant "Flow" of coins in circulation.
M.I.N. Coin.
Most Intelligent/Interesting Notice/Note (Rewarding smart posts)
More Insight Now
My Itty Nickle (Encourage MNC 0.05 transactions)
My Inter-Net Coin
Being just a shadow of a soon to be shadow-coin (BitCoin), is not enough to "be". Bitcoins were intended to be a mini-coin. They screwed that up, when they all got greedy, and let pool operators dictate things like minimum transactions, and fees, which were NOT intended to be "enforced".
Hope it connects soon... I got a few people to add to mining. You also need to add some pool-contacts and encourage more people to use the other forum. That other forum makes the coin look dead... "MincoinTalk"...
Had to delete everything except my wallet, and let it rebuild from scratch... Seems the "code" is bugged, trying to handle forks. Might want to add an option to "Repair Block-chain", which simply rebuilds the chain from the latest valid blocks-up. Thus, also rebuilding the user DB also.
Ok, got it to work, mined for hours, got rejected for every valid block attempted to submit... then today... nothing... no connection to the network.
You need more than one node to keep this thing alive.
So what is the marketing strategy for this coin? Who is the target audience?
I would think this would be great for adding to a forum's "Reputation" payment integration. (Lots of these forums have ghetto coin-rewards or forum-currency.) That would help get a constant "Flow" of coins in circulation.
M.I.N. Coin.
Most Intelligent/Interesting Notice/Note (Rewarding smart posts)
More Insight Now
My Itty Nickle (Encourage MNC 0.05 transactions)
My Inter-Net Coin
Being just a shadow of a soon to be shadow-coin (BitCoin), is not enough to "be". Bitcoins were intended to be a mini-coin. They screwed that up, when they all got greedy, and let pool operators dictate things like minimum transactions, and fees, which were NOT intended to be "enforced".
Hope it connects soon... I got a few people to add to mining. You also need to add some pool-contacts and encourage more people to use the other forum. That other forum makes the coin look dead... "MincoinTalk"...
June 07, 2013, 06:50:13 AM
I have 6.3.0 and it is stuck at block 75051 and will not update to block 80508...
What is going on?
It starts-off saying "up to date" at that block... then after a minute, it is suddenly "out of date" and just does nothing... shows that 2755 blocks are needed to download, but nothing ever comes. Only getting three connections, apparently dead connections not sharing anything?
Amazingly, it still allows me to mine... Am I mining under block 80508, from 75051? That could make it real difficult to ever "fix" any forks, if it allows people to mine from pre-forked blocks that are not at the ends??? Or is this what a fork looks like... only block 75051 is the "real block", and 80508 is the one you are trying to kill?
What is going on?
It starts-off saying "up to date" at that block... then after a minute, it is suddenly "out of date" and just does nothing... shows that 2755 blocks are needed to download, but nothing ever comes. Only getting three connections, apparently dead connections not sharing anything?
Amazingly, it still allows me to mine... Am I mining under block 80508, from 75051? That could make it real difficult to ever "fix" any forks, if it allows people to mine from pre-forked blocks that are not at the ends??? Or is this what a fork looks like... only block 75051 is the "real block", and 80508 is the one you are trying to kill?
There was a hard fork at block 75000 and you're on the wrong side of it. You need to update your client
June 07, 2013, 06:36:13 AM
So many new currencies!
Good luck.
Good luck.
Its raining coins!!!
June 07, 2013, 06:21:40 AM
I have 6.3.0 and it is stuck at block 75051 and will not update to block 80508...
What is going on?
It starts-off saying "up to date" at that block... then after a minute, it is suddenly "out of date" and just does nothing... shows that 2755 blocks are needed to download, but nothing ever comes. Only getting three connections, apparently dead connections not sharing anything?
Amazingly, it still allows me to mine... Am I mining under block 80508, from 75051? That could make it real difficult to ever "fix" any forks, if it allows people to mine from pre-forked blocks that are not at the ends??? Or is this what a fork looks like... only block 75051 is the "real block", and 80508 is the one you are trying to kill?
What is going on?
It starts-off saying "up to date" at that block... then after a minute, it is suddenly "out of date" and just does nothing... shows that 2755 blocks are needed to download, but nothing ever comes. Only getting three connections, apparently dead connections not sharing anything?
Amazingly, it still allows me to mine... Am I mining under block 80508, from 75051? That could make it real difficult to ever "fix" any forks, if it allows people to mine from pre-forked blocks that are not at the ends??? Or is this what a fork looks like... only block 75051 is the "real block", and 80508 is the one you are trying to kill?
June 03, 2013, 02:46:19 AM
public service bump.
And another bump for block 75,061
June 02, 2013, 11:34:25 PM
public service bump.
May 31, 2013, 10:28:45 PM
can any dev comment on this? It's preventing me from doing some needed code updates on my pool.
Hey, devs, I'm having a problem on my pool with mincoin.. The block hash in the shares table isn't matching up with the hash on the block itself..
e.g.:
stratum.log says:
2013-05-16 05:16:43,426 CRITICAL interfaces interfaces.on_submit_block # Block 0000000049efc1e88c1975998ad92165f8041d9725d6a77f7fec5f463034fed1 ACCEPTED
shares table has:
mysql> select solution from shares where upstream_result =1 order by id desc limit 1;
But when I try to get the transaction, I get:
If I do listtransactions, the tx shows a completely different blockhash:
This is unique to mincoin, all of the other coins on my pool the hash matches up between the shares table and the daemon.
So what's going on?
e.g.:
stratum.log says:
2013-05-16 05:16:43,426 CRITICAL interfaces interfaces.on_submit_block # Block 0000000049efc1e88c1975998ad92165f8041d9725d6a77f7fec5f463034fed1 ACCEPTED
shares table has:
mysql> select solution from shares where upstream_result =1 order by id desc limit 1;
Code:
+------------------------------------------------------------------+
| solution |
+------------------------------------------------------------------+
| 0000000049efc1e88c1975998ad92165f8041d9725d6a77f7fec5f463034fed1 |
But when I try to get the transaction, I get:
Code:
$ mincoind getrawtransaction 0000000049efc1e88c1975998ad92165f8041d9725d6a77f7fec5f463034fed1 1
error: {"code":-5,"message":"No information available about transaction"}
If I do listtransactions, the tx shows a completely different blockhash:
Code:
{
"account" : "",
"category" : "generate",
"amount" : 2.00000000,
"confirmations" : 31,
"blockhash" : "737be8276389a097e120d5689f9bae5e19a5ca939fb8660451398a4e47db1ee9",
"blockindex" : 0,
"txid" : "7b912bbac1ce92d69138e9db8a8c916c105529f39b3836fe454ea82148b772c2",
"time" : 1368681397
},This is unique to mincoin, all of the other coins on my pool the hash matches up between the shares table and the daemon.
So what's going on?
Did you ever get this sorted out?
May 31, 2013, 10:16:22 PM
Thank you for the continued Developer support.
May 27, 2013, 11:30:39 PM
Updated the OP with the following:
I'm sure many of you have noticed that MinCoin has been having some issues with our Difficulty re-target causing a lot of
instability in MNC network hashrate Transaction Confirmation times and overall mining profitability compared to other coins.
Today we have made a change to that Difficulty re-target in an effort to help create a more stable network hashrate
and to also help stabilize the 1min block/confirm target. This should also help with mincoin mining profitability from
a stability standpoint.
However, this does require a mandatory update to the mincoin qt client and daemon for all miners and pool operators.
We have made a thread to this effect here: http://mincointalk.com/index.php/topic,87.msg560.html#new
We request that everyone upgrade prior to block 75000 as that is the target block for the new Difficulty re-target of 60blocks
to take effect.
You can download here:
Source: https://github.com/SandyCohen/mincoin
MinCoin GUI client & MinCoin Headless: http://www.vircurpool.com/gettingstarted
Dropbox for daemon here: https://dl.dropboxusercontent.com/u/38674765/mincoin604.zip
Thanks again for your continued support. I think this change will help benefit everyone involved with this project.
I'm sure many of you have noticed that MinCoin has been having some issues with our Difficulty re-target causing a lot of
instability in MNC network hashrate Transaction Confirmation times and overall mining profitability compared to other coins.
Today we have made a change to that Difficulty re-target in an effort to help create a more stable network hashrate
and to also help stabilize the 1min block/confirm target. This should also help with mincoin mining profitability from
a stability standpoint.
However, this does require a mandatory update to the mincoin qt client and daemon for all miners and pool operators.
We have made a thread to this effect here: http://mincointalk.com/index.php/topic,87.msg560.html#new
We request that everyone upgrade prior to block 75000 as that is the target block for the new Difficulty re-target of 60blocks
to take effect.
You can download here:
Source: https://github.com/SandyCohen/mincoin
MinCoin GUI client & MinCoin Headless: http://www.vircurpool.com/gettingstarted
Dropbox for daemon here: https://dl.dropboxusercontent.com/u/38674765/mincoin604.zip
Thanks again for your continued support. I think this change will help benefit everyone involved with this project.
May 21, 2013, 05:56:55 AM
Hi,
As previously discussed my pool http://mnc.coinmine.pl is stable now so can i claim last bounty slot? My address: MVLSskBPgLBkje7iduNtCboUAgwSNfZF6G
BTW - great profitability now for MNC - please join our pool!
feeleep
As previously discussed my pool http://mnc.coinmine.pl is stable now so can i claim last bounty slot? My address: MVLSskBPgLBkje7iduNtCboUAgwSNfZF6G
BTW - great profitability now for MNC - please join our pool!
feeleep
Wow - I already received bounty! Thanks!
feeleep
May 21, 2013, 05:56:11 AM
Hi,
As previously discussed my pool http://mnc.coinmine.pl is stable now so can i claim last bounty slot? My address: MVLSskBPgLBkje7iduNtCboUAgwSNfZF6G
BTW - great profitability now for MNC - please join our pool!
feeleep
As previously discussed my pool http://mnc.coinmine.pl is stable now so can i claim last bounty slot? My address: MVLSskBPgLBkje7iduNtCboUAgwSNfZF6G
BTW - great profitability now for MNC - please join our pool!
feeleep
Thank you for supporting the MinCoin community and I wish you continued success with you MinCoin mining pool !!!
Bounty Sent !!!
http://blockexplorer.vircurpool.com/tx/09f8d1ff2e44df8bfe2630b27c42ea4c4d4b7229623967784acd3a80f5181df6#o1
May 21, 2013, 05:46:40 AM
Hi,
As previously discussed my pool http://mnc.coinmine.pl is stable now so can i claim last bounty slot? My address: MVLSskBPgLBkje7iduNtCboUAgwSNfZF6G
BTW - great profitability now for MNC - please join our pool!
feeleep
As previously discussed my pool http://mnc.coinmine.pl is stable now so can i claim last bounty slot? My address: MVLSskBPgLBkje7iduNtCboUAgwSNfZF6G
BTW - great profitability now for MNC - please join our pool!
feeleep
May 18, 2013, 12:53:57 AM
flound: What type of server are you hosting on? I've heard of wierd hash issues with certain types of architecture. I'm not of much help in this regard, but if your hashes are off, it could be a CPU/OS problem.
Linux 64/Intel
May 17, 2013, 03:44:21 PM
flound: What type of server are you hosting on? I've heard of wierd hash issues with certain types of architecture. I'm not of much help in this regard, but if your hashes are off, it could be a CPU/OS problem.
May 17, 2013, 10:55:20 AM
can any dev comment on this? It's preventing me from doing some needed code updates on my pool.
Hey, devs, I'm having a problem on my pool with mincoin.. The block hash in the shares table isn't matching up with the hash on the block itself..
e.g.:
stratum.log says:
2013-05-16 05:16:43,426 CRITICAL interfaces interfaces.on_submit_block # Block 0000000049efc1e88c1975998ad92165f8041d9725d6a77f7fec5f463034fed1 ACCEPTED
shares table has:
mysql> select solution from shares where upstream_result =1 order by id desc limit 1;
But when I try to get the transaction, I get:
If I do listtransactions, the tx shows a completely different blockhash:
This is unique to mincoin, all of the other coins on my pool the hash matches up between the shares table and the daemon.
So what's going on?
e.g.:
stratum.log says:
2013-05-16 05:16:43,426 CRITICAL interfaces interfaces.on_submit_block # Block 0000000049efc1e88c1975998ad92165f8041d9725d6a77f7fec5f463034fed1 ACCEPTED
shares table has:
mysql> select solution from shares where upstream_result =1 order by id desc limit 1;
Code:
+------------------------------------------------------------------+
| solution |
+------------------------------------------------------------------+
| 0000000049efc1e88c1975998ad92165f8041d9725d6a77f7fec5f463034fed1 |
But when I try to get the transaction, I get:
Code:
$ mincoind getrawtransaction 0000000049efc1e88c1975998ad92165f8041d9725d6a77f7fec5f463034fed1 1
error: {"code":-5,"message":"No information available about transaction"}
If I do listtransactions, the tx shows a completely different blockhash:
Code:
{
"account" : "",
"category" : "generate",
"amount" : 2.00000000,
"confirmations" : 31,
"blockhash" : "737be8276389a097e120d5689f9bae5e19a5ca939fb8660451398a4e47db1ee9",
"blockindex" : 0,
"txid" : "7b912bbac1ce92d69138e9db8a8c916c105529f39b3836fe454ea82148b772c2",
"time" : 1368681397
},This is unique to mincoin, all of the other coins on my pool the hash matches up between the shares table and the daemon.
So what's going on?
May 16, 2013, 09:01:20 AM
http://min.cryptcoins.net/ we're up and running and hitting blocks.
May 16, 2013, 08:45:48 AM
Because of MinCin being the most profitabel Coin at the moment, i set up a MNC-P2Pool
Just point you cgminer to : crypto-coins.de:8903
Use your MNC-Wallet Adress as Username and a random Passwort.
For Example:
Code:
cgminer.exe --scrypt -u -p -o crypto-coins.de:8903
Fee is set to 2%
You can see the stats at www.crypto-coins.de:8903
Just point you cgminer to : crypto-coins.de:8903
Use your MNC-Wallet Adress as Username and a random Passwort.
For Example:
Code:
cgminer.exe --scrypt -u
Fee is set to 2%
You can see the stats at www.crypto-coins.de:8903
Jump to: