hey tried solo mining for a while but getting nothing, anyone know why?
depends what u mining with, it can take awhile to generate a block solo. mine is working tho.
Topic: [ANN][GRA] Graincoin - New PoW/PoS coin | Fast, secure | Version 1.5 Released! - page 126. (Read 177059 times)
December 24, 2013, 11:07:54 PM
depends what u mining with, it can take awhile to generate a block solo. mine is working tho.
December 24, 2013, 10:47:24 PM
hey tried solo mining for a while but getting nothing, anyone know why?
December 24, 2013, 10:36:04 PM
I fixed my wallet and it was running good, pos blocks were coming though and everything. Then it suddenly jumped back to the old chain. Are we under attack again?
Use the client I provided or build your own client with the main.cpp from the zip. You need to block the old block at 38847 so it won't go back to the old chain.
I wouldn't have a clue how to do that. I am going out for xmas lunch with family so I won't be able to try anything for about 8 hours.
Is it safest for me just to leave my wallets open and running?
These are some friendly steps on how to do it.
1. Download the zip file from Bosian on page 22.
2. Extract the file.
3. Move grain-qt-withblock28857reject to your grain directory (Where grain-qt is)
4. Go to run and enter %appdata%
5. Find the Grain directory and open it. (Should be something like C:\Users\NAME\AppData\Roaming\Grain)
6. Create a new folder(oldBlockChain) and move blk0001.dat, blkindex.dat, and database directory to your new folder. (For backup of old blockchain if we ever need it)
7. Move the 3 files from the blockchain dir in the zip to the grain dir to replace the 3 files you just moved.
8a. If you never done so make a grain.conf file (not grain.conf.txt like many people do) in the %appdata% grain dir
Example conf file:
listen=1
daemon=1
server=1
rpcconnect=127.0.0.1
addnode=66.187.67.233
addnode=72.20.18.200
rpcuser=*USERNAME*
rpcpassword=*PASSWORD THAT IS VERY LONG AND BUTTON MASHING*
rpcport=11055
8b. If grain.conf file is already created add the 2 addnode lines to it.
9. Start up the grain-qt-withblock38857reject and it should sync.
If someone finds an error in these steps please fix/let me know. These are the steps I did and it works.
I did exactly as you said.... it was syncing and saying the correct block at the time, once it synced it them jumped to the old chain and is now trying to sync again. it is at 41906 of 43661
I believe that is normal. It did the same for me and fixed it self after a few blocks. 41927 is the correct block atm and I assume your 41906 is now 41927. Just keep it running and it should fix.
December 24, 2013, 10:22:00 PM
Bosian,
can you please confirm which nodes are supposed to be added... I have found a used a few difference ones now but I don't know which ones I SHOULD be using for sure.
Thanks in advance
can you please confirm which nodes are supposed to be added... I have found a used a few difference ones now but I don't know which ones I SHOULD be using for sure.
Thanks in advance
December 24, 2013, 10:19:24 PM
I fixed my wallet and it was running good, pos blocks were coming though and everything. Then it suddenly jumped back to the old chain. Are we under attack again?
Use the client I provided or build your own client with the main.cpp from the zip. You need to block the old block at 38847 so it won't go back to the old chain.
I wouldn't have a clue how to do that. I am going out for xmas lunch with family so I won't be able to try anything for about 8 hours.
Is it safest for me just to leave my wallets open and running?
These are some friendly steps on how to do it.
1. Download the zip file from Bosian on page 22.
2. Extract the file.
3. Move grain-qt-withblock28857reject to your grain directory (Where grain-qt is)
4. Go to run and enter %appdata%
5. Find the Grain directory and open it. (Should be something like C:\Users\NAME\AppData\Roaming\Grain)
6. Create a new folder(oldBlockChain) and move blk0001.dat, blkindex.dat, and database directory to your new folder. (For backup of old blockchain if we ever need it)
7. Move the 3 files from the blockchain dir in the zip to the grain dir to replace the 3 files you just moved.
8a. If you never done so make a grain.conf file (not grain.conf.txt like many people do) in the %appdata% grain dir
Example conf file:
listen=1
daemon=1
server=1
rpcconnect=127.0.0.1
addnode=66.187.67.233
addnode=72.20.18.200
rpcuser=*USERNAME*
rpcpassword=*PASSWORD THAT IS VERY LONG AND BUTTON MASHING*
rpcport=11055
8b. If grain.conf file is already created add the 2 addnode lines to it.
9. Start up the grain-qt-withblock38857reject and it should sync.
If someone finds an error in these steps please fix/let me know. These are the steps I did and it works.
I did exactly as you said.... it was syncing and saying the correct block at the time, once it synced it them jumped to the old chain and is now trying to sync again. it is at 41906 of 43661
December 24, 2013, 09:48:22 PM
I fixed my wallet and it was running good, pos blocks were coming though and everything. Then it suddenly jumped back to the old chain. Are we under attack again?
Use the client I provided or build your own client with the main.cpp from the zip. You need to block the old block at 38847 so it won't go back to the old chain.
I wouldn't have a clue how to do that. I am going out for xmas lunch with family so I won't be able to try anything for about 8 hours.
Is it safest for me just to leave my wallets open and running?
These are some friendly steps on how to do it.
1. Download the zip file from Bosian on page 22.
2. Extract the file.
3. Move grain-qt-withblock28857reject to your grain directory (Where grain-qt is)
4. Go to run and enter %appdata%
5. Find the Grain directory and open it. (Should be something like C:\Users\NAME\AppData\Roaming\Grain)
6. Create a new folder(oldBlockChain) and move blk0001.dat, blkindex.dat, and database directory to your new folder. (For backup of old blockchain if we ever need it)
7. Move the 3 files from the blockchain dir in the zip to the grain dir to replace the 3 files you just moved.
8a. If you never done so make a grain.conf file (not grain.conf.txt like many people do) in the %appdata% grain dir
Example conf file:
listen=1
daemon=1
server=1
rpcconnect=127.0.0.1
addnode=66.187.67.233
addnode=72.20.18.200
rpcuser=*USERNAME*
rpcpassword=*PASSWORD THAT IS VERY LONG AND BUTTON MASHING*
rpcport=11055
8b. If grain.conf file is already created add the 2 addnode lines to it.
9. Start up the grain-qt-withblock38857reject and it should sync.
If someone finds an error in these steps please fix/let me know. These are the steps I did and it works.
December 24, 2013, 09:42:42 PM
I fixed my wallet and it was running good, pos blocks were coming though and everything. Then it suddenly jumped back to the old chain. Are we under attack again?
Use the client I provided or build your own client with the main.cpp from the zip. You need to block the old block at 38847 so it won't go back to the old chain.
I wouldn't have a clue how to do that. I am going out for xmas lunch with family so I won't be able to try anything for about 8 hours.
Is it safest for me just to leave my wallets open and running?
you will need to do the changes to get on the right block chain, its not that hard. maybe someone else will know if you will get paid later for sending pool work now.
follow this directions:
put the addnodes in your .conf file
ok the PoW mining is back... if you can not sync with addnode above, you need to download this file here, please read the following before you download the file:
https://mega.co.nz/#!Mk1HzYpA!eeddQXV3DvRHNbSMLeVuLycfde8sm5mFH-qtlEgxUQA
This is a big zip file (31.7M), which contains 3 parts:
- A Blockchain directory which contains the correct blockchain.
- A file main.cpp, that contains the above code change.
- A windows qt client (grain-qt-withblock38847reject.exe), contains the above change.
If you can not sync with addnode, the first thing you should try is to replace the blockchain. This is what you do:
1. Quit qt client.
2. Go to Grain config dir. create a new directory (for example called oldchain), move the database dir, blk0001.dat, blkindex.dat files to the new dir you created, then move these files from Blockchain in the downloaded unzipped file, to config dir. This way you can always go back to your old chain if anything happens.
3. Now start grain-qt-withblock38847reject.exe, always with the addnodes as above, you should sync and then start to mine.
Let me know if anyone has issue.
Good mining
https://mega.co.nz/#!Mk1HzYpA!eeddQXV3DvRHNbSMLeVuLycfde8sm5mFH-qtlEgxUQA
This is a big zip file (31.7M), which contains 3 parts:
- A Blockchain directory which contains the correct blockchain.
- A file main.cpp, that contains the above code change.
- A windows qt client (grain-qt-withblock38847reject.exe), contains the above change.
If you can not sync with addnode, the first thing you should try is to replace the blockchain. This is what you do:
1. Quit qt client.
2. Go to Grain config dir. create a new directory (for example called oldchain), move the database dir, blk0001.dat, blkindex.dat files to the new dir you created, then move these files from Blockchain in the downloaded unzipped file, to config dir. This way you can always go back to your old chain if anything happens.
3. Now start grain-qt-withblock38847reject.exe, always with the addnodes as above, you should sync and then start to mine.
Let me know if anyone has issue.
Good mining
December 24, 2013, 09:26:53 PM
I fixed my wallet and it was running good, pos blocks were coming though and everything. Then it suddenly jumped back to the old chain. Are we under attack again?
Use the client I provided or build your own client with the main.cpp from the zip. You need to block the old block at 38847 so it won't go back to the old chain.
I wouldn't have a clue how to do that. I am going out for xmas lunch with family so I won't be able to try anything for about 8 hours.
Is it safest for me just to leave my wallets open and running?
December 24, 2013, 09:24:27 PM
Both my wallets are now synced to 41801. I didnt change anything it just happened. I sent 1 coin from one wallet to the other and back again and it all worked fine.
December 24, 2013, 09:22:07 PM
I tried sending some coins but got a message that the coins may have already been sent even though it deducted the coins from my balance? Now I'm getting confirms on the transactions and al seems to be working normally again. The other odd thing though is I can start mining even though I've closed my wallet & reopened it and its still syncing? A good sign though is I'm at block 41806 of 43656 which is right on the money.
December 24, 2013, 09:17:09 PM
I fixed my wallet and it was running good, pos blocks were coming though and everything. Then it suddenly jumped back to the old chain. Are we under attack again?
Use the client I provided or build your own client with the main.cpp from the zip. You need to block the old block at 38847 so it won't go back to the old chain.
December 24, 2013, 09:15:35 PM
I fixed my wallet and it was running good, pos blocks were coming though and everything. Then it suddenly jumped back to the old chain. Are we under attack again?
December 24, 2013, 09:12:18 PM
I'm stuck at 41711 of 43651...
Forkpool is updating my valid shares but not my balance...
Edit: moved to 41802 now. Lets see how it goes now...
Forkpool is updating my valid shares but not my balance...
Edit: moved to 41802 now. Lets see how it goes now...
December 24, 2013, 09:12:12 PM
I have two separate wallets running a different machines
one says fully synced at 41784
the other says it is syncing and is at 41784 of 43651
Was all working ok (with the wallets not cgminer) until I added the new node and started them again
one says fully synced at 41784
the other says it is syncing and is at 41784 of 43651
Was all working ok (with the wallets not cgminer) until I added the new node and started them again
This is perfectly fine. Also sometimes it can go from sync'd to unsync'ed or vice versa. As we do have two chains now. The new one is at 41784, old one at 43651. Once everyone switches over and the new surpass the old, then there will be one chain only. This will probably take another day. Before this happens, please use the client or build the client with the blacklist. This way we don't go back to old chain.
December 24, 2013, 09:11:37 PM
I have two separate wallets running a different machines
one says fully synced at 41784
the other says it is syncing and is at 41784 of 43651
Was all working ok (with the wallets not cgminer) until I added the new node and started them again
one says fully synced at 41784
the other says it is syncing and is at 41784 of 43651
Was all working ok (with the wallets not cgminer) until I added the new node and started them again
yes earlier my wallet was fully synced and on correct chain, then I broke it, now its fixed and my grains are back, but it shows like yours, not synced yet.
I think its ok and it will be fine as long as it says the correct blocks and new ones are coming in, and your balance is correct
December 24, 2013, 09:10:38 PM
some big guys jumped in and now solo mining cgminer diff at 129K, impossible for me to get anything now...
guess we'll need to wait pool owner to checkout the pool if everything is fine. I guess only the display stuck, but it could be that the pool is stuck too.
Bounty distribution is pending until we make sure everything is fine.
guess we'll need to wait pool owner to checkout the pool if everything is fine. I guess only the display stuck, but it could be that the pool is stuck too.
Bounty distribution is pending until we make sure everything is fine.
ya my cgminer diff just showed the same, and the Diff:0 was Diff:1 so it was > 1 for a second there. now its back to diff 48.7K Diff:0
it must be some huge solo mining, or maybe something to do with the pool?
December 24, 2013, 09:09:14 PM
I have two separate wallets running a different machines
one says fully synced at 41784
the other says it is syncing and is at 41784 of 43651
Was all working ok (with the wallets not cgminer) until I added the new node and started them again
one says fully synced at 41784
the other says it is syncing and is at 41784 of 43651
Was all working ok (with the wallets not cgminer) until I added the new node and started them again
December 24, 2013, 09:07:06 PM
some big guys jumped in and now solo mining cgminer diff at 129K, impossible for me to get anything now...
guess we'll need to wait pool owner to checkout the pool if everything is fine. I guess only the display stuck, but it could be that the pool is stuck too.
Bounty distribution is pending until we make sure everything is fine.
guess we'll need to wait pool owner to checkout the pool if everything is fine. I guess only the display stuck, but it could be that the pool is stuck too.
Bounty distribution is pending until we make sure everything is fine.
December 24, 2013, 09:06:44 PM
Here is my adress:
9Qyimky7i3RezQdYC8wWgnopQFLoTEgSFB
There still seems to be something wrong, atleast in forkpool. No blocks showing for several hours and my balance ain't changing although it shows my current hashrate.
9Qyimky7i3RezQdYC8wWgnopQFLoTEgSFB
There still seems to be something wrong, atleast in forkpool. No blocks showing for several hours and my balance ain't changing although it shows my current hashrate.
December 24, 2013, 09:02:58 PM
I have just started having an error on cgminer. But it says the error and then closes straight away. How do I get it to print to file or stay on the screen so that I can see what error it is?
Thanks in advance
Thanks in advance
Everything was working fine and I was mining all ok. Then my computer froze and I had to restart it and it hasn't worked since.
Now whenever I try to use cgminer (doesn't matter which pool/coin) and it comes up saying probing for alive pool and stays there for a bit and then just shuts down.
Anyone have any ideas?
oh I have idea, make sure your cgminer .conf isn't configured all messed up, back it up then see if there is anything in there u don't want. remove it, look up what is supposed to be in there, load a default one. I know sometimes cgminer saves things in there u don't want by accident.
gl
Jump to: