 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
a little help for that ones who run nodes on linux ubuntu
following script stop node and fix blockchain automatic including downloading the proper chain files
THANK YOU!!!! MC |
|
|
|
Hi,
i had to restart my windows machine this morning and after coming back the wallet won't start staking any more.
I restarted the wallet a few times and blocked and un-blocked it another bunch of times but it always says "Staking is not active"
Is there something going on the network? Is there a way to force it to start stacking?
Is there a command for doing so in the debug window?
Cheers
MC
you can try putting 'staking=1' in the config, along with 'stakesplitthreshold=500' (assuming you have more than that. set this to at least 200 I noticed worked better for me) stakesplittreshhold is 200 at default no need set that value beside u did changed upfront to something else 200 means coinpiles will be in area 200-400 if below 200 it merge if above 400 it split when its involved in blockfindig It didn't work, I have my wallet encrypted, could be a factor? I type "setgenerate true 200" in the debug window and doesn't give me any error, but if I type "getinfo" it always says "staking status" : "Staking Not Active", I took an old copy of the "blocks" directory (that I know is fine, I stacked more than one months after the last time I had to do it) but not joy either |
|
|
|
|
Hi,
i had to restart my windows machine this morning and after coming back the wallet won't start staking any more.
I restarted the wallet a few times and blocked and un-blocked it another bunch of times but it always says "Staking is not active"
Is there something going on the network? Is there a way to force it to start stacking?
Is there a command for doing so in the debug window?
Cheers
MC
|
|
|
|
Blocks corruption is only possible if the computer suddenly shuts down and synchronization is not yet complete. If the wallet sync has reached 100% then the sudden power off does not harm the blockchain. In other cases, any other causes of corruption are related to the automatic updates feature, which roughly terminates many system processes. The easiest way to protect against this is to use a properly configured computer with UPS and disabled automatic updates. For safety net, you can always create your archive with the folders blocks and chainstate and in case of damage to the blockchain, just to replace the data. Delete old folders and unpack new ones to their place. Then the re-sync process will only take a few minutes. Sorry but not... In my case, EVERY TIME I do a proper windows 10 shutdown, if I forgot to shutdown the wallet first, I get a wallet corruption error and it has to "re-verify" the whole 50 weeks. That is after been stacking for days (meaning, the wallet is fully synchronised) I have 3 other stacking wallets running on that computer and this is the only one affected... There is clearly something going on... Doesn't have windows something similar to the Unix signals that you can subscribe to and close all the files as soon you you get the "shooting down signal"? Actually thing jut got worst, since it last happened, every time I try to run it now, it aborts with the typical "Windows had encountered an error in this application..." Any one knows a way to fix that? Cheers MC
2018-09-19 00:53:38 DMD version v3.0.1.2-gcbcb549 (Tue, 9 Feb 2016 16:54:57 -0500)
2018-09-19 00:53:38 Using OpenSSL version OpenSSL 1.0.1l 15 Jan 2015
2018-09-19 00:53:38 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2018-09-19 00:53:38 Default data directory C:\Users\user\AppData\Roaming\DMDV3
2018-09-19 00:53:38 Using data directory C:\Users\user\AppData\Roaming\DMDV3
2018-09-19 00:53:38 Using config file C:\Users\user\AppData\Roaming\DMDV3\diamond.conf
2018-09-19 00:53:38 Using at most 125 connections (2048 file descriptors available)
2018-09-19 00:53:38 Using 0 threads for script verification
2018-09-19 00:53:38 Old backup deleted: "C:\Users\user\AppData\Roaming\DMDV3\backups\wallet.dat.2018-08-27-15-33"
2018-09-19 00:53:38 Using wallet wallet.dat
2018-09-19 00:53:38 init message: Verificando monedero...
2018-09-19 00:53:38 CDBEnv::Open: LogDir=C:\Users\user\AppData\Roaming\DMDV3\database ErrorFile=C:\Users\user\AppData\Roaming\DMDV3\db.log
2018-09-19 00:53:38 Bound to [::]:17771
2018-09-19 00:53:38 Bound to 0.0.0.0:17771
2018-09-19 00:53:38 init message: Cargando el Ãndice de bloques...
2018-09-19 00:53:38 Opening LevelDB in C:\Users\user\AppData\Roaming\DMDV3\blocks\index
2018-09-19 00:53:38 Opened LevelDB successfully
2018-09-19 00:53:38 Opening LevelDB in C:\Users\user\AppData\Roaming\DMDV3\chainstate
2018-09-19 00:53:38 Opened LevelDB successfully
2018-09-19 00:53:38 LoadBlockIndexDB: last block file = 0
2018-09-19 00:53:38 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2018-09-19 00:53:38 Checking all blk files are present...
2018-09-19 00:53:38 LoadBlockIndexDB: Last shutdown was prepared: false
2018-09-19 00:53:38 LoadBlockIndexDB(): transaction index enabled
2018-09-19 00:53:38 Initializing databases...
2018-09-19 00:53:38 init message: Verificando bloques...
2018-09-19 00:53:38 block index 37ms
2018-09-19 00:53:38 Read 100 fee samples and 100 priority samples
2018-09-19 00:53:38 Read 47 fee samples and 32 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 init message: Cargando monedero...
2018-09-19 00:53:38 nFileVersion = 3000102
2018-09-19 00:53:38 Keys: 0 plaintext, 3073 encrypted, 3073 w/ metadata, 3073 total
2018-09-19 00:53:38 wallet 158ms
2018-09-19 00:53:38 Waiting for genesis block to be imported...
2018-09-19 00:53:38 Reindexing block file blk00000.dat...
2018-09-19 00:53:38 CheckBlock: block=0000029b550c0095513d9bb9dd14f88442573baca94d70e49018a510979c0f9b is proof of stake=0if you constantly have these problems, perhaps something with your system settings. Try using a different location for the DMDv3 folder. For example, another disk or removable device. 23. Q: Alternative way https://diamond-info.github.io/#q23-altwayIt could be that my particular configuration is more prone than others... BUT that doesn't take away the fact that there is a Fault in the wallet's programming. I know that this kind of things happen, specially if you are writing something to the disk and the system freezes or the power is cut, but it shouldn't happen if you close the system the right way. It shouldn't happen because the OS notifies all the programs that it is going to shutdown and they should trap this notification for do their "clean up". I think there is one of two options; or the wallet is not trapping this signal for "committing" the pending work and close the open files. Or this "cleanup" is taking too long.. Both are a programming issue. As I said, I stake more coins on the same system and Diamond is the only that gets corrupted when I shutdown the system properly MC For what it is worth - I also run Windows 10 64 bit and never have a problem with the wallet corrupting. Whenever I get the update notice, I shut down all of my wallets, then I restart the computer in update mode. When I come back, I restart all my wallets with no issues whatsoever. Try that technique first before just choosing shutdown from the start button. Also, do you store your wallet.dat and other files on the C: drive or another location? Mine are saved to the default directory on the C: drive. Yep, but that shouldn't be needed. I use that machine for more things and it needs to restart from time to time. If you follow the proper OS shutdown procedure you shouldn't break anything. Even Word asks you if you want to save stuff, if you have an unsaved document. Yes, my walled is in the default folder as well. Cheers MC |
|
|
|
Blocks corruption is only possible if the computer suddenly shuts down and synchronization is not yet complete. If the wallet sync has reached 100% then the sudden power off does not harm the blockchain. In other cases, any other causes of corruption are related to the automatic updates feature, which roughly terminates many system processes. The easiest way to protect against this is to use a properly configured computer with UPS and disabled automatic updates. For safety net, you can always create your archive with the folders blocks and chainstate and in case of damage to the blockchain, just to replace the data. Delete old folders and unpack new ones to their place. Then the re-sync process will only take a few minutes. Sorry but not... In my case, EVERY TIME I do a proper windows 10 shutdown, if I forgot to shutdown the wallet first, I get a wallet corruption error and it has to "re-verify" the whole 50 weeks. That is after been stacking for days (meaning, the wallet is fully synchronised) I have 3 other stacking wallets running on that computer and this is the only one affected... There is clearly something going on... Doesn't have windows something similar to the Unix signals that you can subscribe to and close all the files as soon you you get the "shooting down signal"? Actually thing jut got worst, since it last happened, every time I try to run it now, it aborts with the typical "Windows had encountered an error in this application..." Any one knows a way to fix that? Cheers MC
2018-09-19 00:53:38 DMD version v3.0.1.2-gcbcb549 (Tue, 9 Feb 2016 16:54:57 -0500)
2018-09-19 00:53:38 Using OpenSSL version OpenSSL 1.0.1l 15 Jan 2015
2018-09-19 00:53:38 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2018-09-19 00:53:38 Default data directory C:\Users\user\AppData\Roaming\DMDV3
2018-09-19 00:53:38 Using data directory C:\Users\user\AppData\Roaming\DMDV3
2018-09-19 00:53:38 Using config file C:\Users\user\AppData\Roaming\DMDV3\diamond.conf
2018-09-19 00:53:38 Using at most 125 connections (2048 file descriptors available)
2018-09-19 00:53:38 Using 0 threads for script verification
2018-09-19 00:53:38 Old backup deleted: "C:\Users\user\AppData\Roaming\DMDV3\backups\wallet.dat.2018-08-27-15-33"
2018-09-19 00:53:38 Using wallet wallet.dat
2018-09-19 00:53:38 init message: Verificando monedero...
2018-09-19 00:53:38 CDBEnv::Open: LogDir=C:\Users\user\AppData\Roaming\DMDV3\database ErrorFile=C:\Users\user\AppData\Roaming\DMDV3\db.log
2018-09-19 00:53:38 Bound to [::]:17771
2018-09-19 00:53:38 Bound to 0.0.0.0:17771
2018-09-19 00:53:38 init message: Cargando el Ãndice de bloques...
2018-09-19 00:53:38 Opening LevelDB in C:\Users\user\AppData\Roaming\DMDV3\blocks\index
2018-09-19 00:53:38 Opened LevelDB successfully
2018-09-19 00:53:38 Opening LevelDB in C:\Users\user\AppData\Roaming\DMDV3\chainstate
2018-09-19 00:53:38 Opened LevelDB successfully
2018-09-19 00:53:38 LoadBlockIndexDB: last block file = 0
2018-09-19 00:53:38 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2018-09-19 00:53:38 Checking all blk files are present...
2018-09-19 00:53:38 LoadBlockIndexDB: Last shutdown was prepared: false
2018-09-19 00:53:38 LoadBlockIndexDB(): transaction index enabled
2018-09-19 00:53:38 Initializing databases...
2018-09-19 00:53:38 init message: Verificando bloques...
2018-09-19 00:53:38 block index 37ms
2018-09-19 00:53:38 Read 100 fee samples and 100 priority samples
2018-09-19 00:53:38 Read 47 fee samples and 32 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 init message: Cargando monedero...
2018-09-19 00:53:38 nFileVersion = 3000102
2018-09-19 00:53:38 Keys: 0 plaintext, 3073 encrypted, 3073 w/ metadata, 3073 total
2018-09-19 00:53:38 wallet 158ms
2018-09-19 00:53:38 Waiting for genesis block to be imported...
2018-09-19 00:53:38 Reindexing block file blk00000.dat...
2018-09-19 00:53:38 CheckBlock: block=0000029b550c0095513d9bb9dd14f88442573baca94d70e49018a510979c0f9b is proof of stake=0if you constantly have these problems, perhaps something with your system settings. Try using a different location for the DMDv3 folder. For example, another disk or removable device. 23. Q: Alternative way https://diamond-info.github.io/#q23-altwayIt could be that my particular configuration is more prone than others... BUT that doesn't take away the fact that there is a Fault in the wallet's programming. I know that this kind of things happen, specially if you are writing something to the disk and the system freezes or the power is cut, but it shouldn't happen if you close the system the right way. It shouldn't happen because the OS notifies all the programs that it is going to shutdown and they should trap this notification for do their "clean up". I think there is one of two options; or the wallet is not trapping this signal for "committing" the pending work and close the open files. Or this "cleanup" is taking too long.. Both are a programming issue. As I said, I stake more coins on the same system and Diamond is the only that gets corrupted when I shutdown the system properly MC |
|
|
|
Blocks corruption is only possible if the computer suddenly shuts down and synchronization is not yet complete. If the wallet sync has reached 100% then the sudden power off does not harm the blockchain. In other cases, any other causes of corruption are related to the automatic updates feature, which roughly terminates many system processes. The easiest way to protect against this is to use a properly configured computer with UPS and disabled automatic updates. For safety net, you can always create your archive with the folders blocks and chainstate and in case of damage to the blockchain, just to replace the data. Delete old folders and unpack new ones to their place. Then the re-sync process will only take a few minutes. Sorry but not... In my case, EVERY TIME I do a proper windows 10 shutdown, if I forgot to shutdown the wallet first, I get a wallet corruption error and it has to "re-verify" the whole 50 weeks. That is after been stacking for days (meaning, the wallet is fully synchronised) I have 3 other stacking wallets running on that computer and this is the only one affected... There is clearly something going on... Doesn't have windows something similar to the Unix signals that you can subscribe to and close all the files as soon you you get the "shooting down signal"? Actually thing jut got worst, since it last happened, every time I try to run it now, it aborts with the typical "Windows had encountered an error in this application..." Any one knows a way to fix that? Cheers MC
2018-09-19 00:53:38 DMD version v3.0.1.2-gcbcb549 (Tue, 9 Feb 2016 16:54:57 -0500)
2018-09-19 00:53:38 Using OpenSSL version OpenSSL 1.0.1l 15 Jan 2015
2018-09-19 00:53:38 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2018-09-19 00:53:38 Default data directory C:\Users\user\AppData\Roaming\DMDV3
2018-09-19 00:53:38 Using data directory C:\Users\user\AppData\Roaming\DMDV3
2018-09-19 00:53:38 Using config file C:\Users\user\AppData\Roaming\DMDV3\diamond.conf
2018-09-19 00:53:38 Using at most 125 connections (2048 file descriptors available)
2018-09-19 00:53:38 Using 0 threads for script verification
2018-09-19 00:53:38 Old backup deleted: "C:\Users\user\AppData\Roaming\DMDV3\backups\wallet.dat.2018-08-27-15-33"
2018-09-19 00:53:38 Using wallet wallet.dat
2018-09-19 00:53:38 init message: Verificando monedero...
2018-09-19 00:53:38 CDBEnv::Open: LogDir=C:\Users\user\AppData\Roaming\DMDV3\database ErrorFile=C:\Users\user\AppData\Roaming\DMDV3\db.log
2018-09-19 00:53:38 Bound to [::]:17771
2018-09-19 00:53:38 Bound to 0.0.0.0:17771
2018-09-19 00:53:38 init message: Cargando el Ãndice de bloques...
2018-09-19 00:53:38 Opening LevelDB in C:\Users\user\AppData\Roaming\DMDV3\blocks\index
2018-09-19 00:53:38 Opened LevelDB successfully
2018-09-19 00:53:38 Opening LevelDB in C:\Users\user\AppData\Roaming\DMDV3\chainstate
2018-09-19 00:53:38 Opened LevelDB successfully
2018-09-19 00:53:38 LoadBlockIndexDB: last block file = 0
2018-09-19 00:53:38 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2018-09-19 00:53:38 Checking all blk files are present...
2018-09-19 00:53:38 LoadBlockIndexDB: Last shutdown was prepared: false
2018-09-19 00:53:38 LoadBlockIndexDB(): transaction index enabled
2018-09-19 00:53:38 Initializing databases...
2018-09-19 00:53:38 init message: Verificando bloques...
2018-09-19 00:53:38 block index 37ms
2018-09-19 00:53:38 Read 100 fee samples and 100 priority samples
2018-09-19 00:53:38 Read 47 fee samples and 32 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 Read 0 fee samples and 1 priority samples
2018-09-19 00:53:38 init message: Cargando monedero...
2018-09-19 00:53:38 nFileVersion = 3000102
2018-09-19 00:53:38 Keys: 0 plaintext, 3073 encrypted, 3073 w/ metadata, 3073 total
2018-09-19 00:53:38 wallet 158ms
2018-09-19 00:53:38 Waiting for genesis block to be imported...
2018-09-19 00:53:38 Reindexing block file blk00000.dat...
2018-09-19 00:53:38 CheckBlock: block=0000029b550c0095513d9bb9dd14f88442573baca94d70e49018a510979c0f9b is proof of stake=0 |
|
|
|
|
Where can I report a bug or find out if it has reported?
Looks like the Github page doesn't have issues activated.
My problem is that every time that I shut down Windows while I stacking, the DMD databases get corrupted and it needs a full index rebuild.
This takes the best part of one day if I'm lucky :-(
Cheers
|
|
|
|
|
I'm looking forward to see my daughter learning about Crypto!!!!
I think the idea has the right balance between technology and easy of use that will lead to mass crypto usage!!!
Cheers
MC
|
|
|
|
I love the project, but from what I can get from the WP, the tokens are just for a "one off" purchase of hash power from them... The SAM token doesn't represent a stake in the future of the company or its sucess and that is what I don't like, for something as promising as this I wold like to be part of their success. :-( The other usual option, hold the token and wait until the price goes up, doesn't work here either... What is the point buying expensive hash power if the token does 2x or 3x up??? I would love to be able to have more "permanent stack" in this project ... Cheers MC  expensive hash power? 14 TH for USD 4000 (2years)including electricity is expensiv? according to our experience we have to replace hardware after 2 years so i think its a fair deal! pls note that you can also buy the hardware and pay the electricity with sam tokens. I didn't say that the hash power was expensive... What I meant was that you can't hope for a token increase, because if the token doubles in price and those 4000 become 8000$ then is will be expensive... Cheers MC |
|
|
|
I love the project, but from what I can get from the WP, the tokens are just for a "one off" purchase of hash power from them... The SAM token doesn't represent a stake in the future of the company or its sucess and that is what I don't like, for something as promising as this I wold like to be part of their success. :-( The other usual option, hold the token and wait until the price goes up, doesn't work here either... What is the point buying expensive hash power if the token does 2x or 3x up??? I would love to be able to have more "permanent stack" in this project ... Cheers MC Isnt that classic approach,that you dont own stake when you join ICO? When it comes to ICO you don't own a share of the company or the project , you own a token and that is it.This is how it works with all ICO's and this is not exception, it's normal. Yes, you are right... you never own an actual share... But usually the token you own, has some mechanism for grant you some returns, depending on how good the project is doing and owing a token, you usually can even get rewarded on the long term in some way backed into the "token economics" But this is not the case, you only get the right to buy them some mining power... isn't it??? It is not even possible to just HOLD and hope for a price increase... Mainly because after a price increase of 20-30%, it will start to be more profitable to mine in another project and the token will loose its purpose... As I said, I see that this company has a BRIGHT FUTURE, but I don't see a way to benefit from that long term... A real pity Cheers MC |
|
|
|
I love the project, but from what I can get from the WP, the tokens are just for a "one off" purchase of hash power from them... The SAM token doesn't represent a stake in the future of the company or its sucess and that is what I don't like, for something as promising as this I wold like to be part of their success. :-( The other usual option, hold the token and wait until the price goes up, doesn't work here either... What is the point buying expensive hash power if the token does 2x or 3x up??? I would love to be able to have more "permanent stack" in this project ... Cheers MC |
|
|
|
Hi everybody,
the project looks very interesting and looking to invest in it, but I have some questions I'd like to ask.
The other thing that I don’t get is what the matter with mountain cabins and buildings, what is the links with your containers? Usually in Switzerland you cannot put what you want where you want, for the same law of the 2013 mentioned in your white paper. Containers falls in a particular situation because they are movable so they can temporally be placed but what the benefit for the “abandoned” cabins if you place near them a SAM cube?
My understanding is that they plan to put the cubes INSIDE those buildings and that doesn't require a permission because they are already there... Cheers MC |
|
|
|
you can but your accounts from other exchanges in the coindash app too not just your ethereum adress  .. for that you need to give them the login otherwhise that will not work. or? You don't know about read only API access keys?? You generate a Read only API key and that is what you give them, basically the same than when you give them you public ETH address Cheers MC |
|
|
|
|
Any updates?
When will be the web wallet online again?
When will be able to download a desktop wallet again? (Is there an old link somewhere?)
Any dates for ART or doing anything useful with the coin?
Cheers
MC
|
|
|
|
Yep, has been like this since earlier in August :-( Cheers MC |
|
|
|
What you can not do is send from an exchange where you dont have the private key, such as Bittrex.
This is not because there is anything wrong with Bittrex, it is just because Bittrex and other altcoin exchanges like it are not designed to be used as an online wallet.
You need to know the differerence between an online wallet and an altcoin exchange.
I think that you are confusing things.... That is a problem when you are buying a ETH tokens, because they send the tokens back to the address that you used and you don't own this address. In this case we are talking about a COIN, and they will be hold at my.electroneum.com until you can transfer them to a Pager wallet or desktop wallet. Basically, it is FINE to fund your account from an exchange. Cheers MC |
|
|
|
Okay guys i've crated an account there - aprox 4h left till presale.
But how do i deposit btc to buy in? Do i have to wait till its live to be able to deposit?
Yep, I would like to know that as well. Bitcoin and ETH take a long time to be confirmed, if we could "pre-deposit" it will be easier. Cheers MC I know what you mean. Some unlucky people, that havent been keeping track of everything, might not know how much the momentum of Electroneum has increased in the last few days. Some people are going to get shutout, there is nothing we can do about that. I believe IMO that if you are ready to send when the ICO opens at 12 Midnight UTC time zone, that you should be ok. Yes, there are simple solutions, like do an individual cap during the first 12 hours or so, that will leave time to everybody to invest and if a whale comes along, they can buy after that and nobody will be pissed. And if they take the time to create 1000s of accounts, it will take time... exactly what we are after... Cheers MC |
|
|
|
Okay guys i've crated an account there - aprox 4h left till presale.
But how do i deposit btc to buy in? Do i have to wait till its live to be able to deposit?
Yep, I would like to know that as well. Bitcoin and ETH take a long time to be confirmed, if we could "pre-deposit" it will be easier. Cheers MC |
|
|
|
Great News!Electroneum Android app is in the Play Store!https://play.google.com/store/apps/details?id=com.electroneum.appYou can download it now, if you have a Samsung or other Android device, and once you have any Electroneum coins from the ICO bounty or from buying coins during the ICO - they will arrive straight to your mobile wallet! Once in your wallet you'll be able to send or receive to other Electroneum users or send them to any Exchange (once they come online) to trade out for other cryptocurrency. We'll work hard to get listed on all the exchanges and Shapeshift as fast as we can after the ICO finishes. The iOS iPhone app should be released later this week!Mobile Mining for Electroneum One thing that I think it is missing from the App is to have an option to only mining when it is connected to the power socket, you don't want users complaining that the app eats their batteries without having the option to disable it when there is a worry to run out of battery. Cheers MC |
|
|
|
you are a true retard.
compcoin uses scrypt-n for starters.
nicehash has not offered scrypt-n for years now.
when compcoin was listed on novaexchange; novaexchange listed wallet source address (probably since removed) and someone with a bunch of scrypt-n miners (either gpu or KNC titan) started mining blocks; dev spotted this and put block explorer on hold temporarily. unable to stop it, block explorer has since resumed.
god damn.
 Here we have a perfect example of someone who talks shit but knows nothing Not only are you wrong, but also you're rude AND a fucking asshole - not a good look, guy. First off, I MINED 65,000 CMP MYSELF ON NICEHASH - so stfu with your nonsense.Does it mean that we can mine it again? Where can I download the wallet? Is there a pool that supports compcoin? Care to share it? I like the project but I'm not 100% convinced yet, if what you say is true, they handled the crisis VERY POORLY!!! You can let people know that you are still alive (nothing since Aug 4th) without communicate the exact nature of the problem. So much for "Most Transparent Coin"...  Cheers MC |
|
|
|
|
