I noticed last night something was up when the stratum kept failing on felix so I stopped my miner. I was too tired to even think about it so I just waited till this morning. Got wallet vs 1.0.1.0 and I'm back in business. Thanks for the quick response guys. 
Topic: [ANN][AID] AidBit | Digital-currency redefined | POW/POS | Groestl | Charity - page 37. (Read 101116 times)
July 26, 2014, 09:26:23 AM
Looks like some stuff went down. That's exciting. I noticed last night something was up when the stratum kept failing on felix so I stopped my miner. I was too tired to even think about it so I just waited till this morning. Got wallet vs 1.0.1.0 and I'm back in business. Thanks for the quick response guys.
I noticed last night something was up when the stratum kept failing on felix so I stopped my miner. I was too tired to even think about it so I just waited till this morning. Got wallet vs 1.0.1.0 and I'm back in business. Thanks for the quick response guys. July 26, 2014, 09:23:53 AM
I managed to get the new 1.0.1.0 wallet by clicking the link in the OP.
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
Try to restart the wallet or delete the blockchain database (%appdata%/AidBit - be careful you don't delete wallet.dat).
Worked for me.
Everything confirmed up to a little over 12 hours ago. Waiting . . .
Should we expect to lose coins that were possibly mined on an old/bad fork?
Add: thought it had worked - showed as having finished the sync - now "downloading 12172 of 12824 . . . last block received 32 seconds ago" - "647 block remaining" Weird!
If your on Linux Wallet, please check:
./aidbitd getblockhash 12138
0000000011e73e1aa8c10e14b5d7bb8b48b0994a07a3a92bd694671c395560ec
Using the windows 1.0.1.0 wallet,
Looking at the block explorer, the 12203 looks good as the last block . . . where the 12823 is coming from and the 620 block remaining, I don't know.
I am running as a server and solo mining, if that matters.
BTW, all of my rewards with exclamation marks were mined on maya.aidbit.net - 23 payouts from 10:34 PM 07/25/2014 to 4:59 07/26/2014 UTC/GMT.
Are you sure you have the latest version? ./getblockhash 12203
0000000003d954fd87fdd01f74b9e09681a8f188d83911dff49be9ce56e178d2
15:20:02
getblockhash 12203
15:20:02
0000000003d954fd87fdd01f74b9e09681a8f188d83911dff49be9ce56e178d2
15:21:03
getblockhash 12206
15:21:03
0000000000851198689ffa8aa55cf8596d4cc6611c81bfb597ee8b4119dee698
You're OK, don't worry. If it still won't sync, just delete the blockchain and reload. Thanks.
July 26, 2014, 09:23:43 AM
BTW, all of my rewards with exclamation marks were mined on maya.aidbit.net - 23 payouts from 10:34 PM 07/25/2014 to 4:59 07/26/2014 UTC/GMT.
I'll check the databases. Approximate ammount and address, please and I'll see what I can do.
Okay. Sounds good. It's not urgent, so I'll PM you that data once the dust settles and you've got time to look at it.
July 26, 2014, 09:19:07 AM
I managed to get the new 1.0.1.0 wallet by clicking the link in the OP.
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
Try to restart the wallet or delete the blockchain database (%appdata%/AidBit - be careful you don't delete wallet.dat).
Worked for me.
Everything confirmed up to a little over 12 hours ago. Waiting . . .
Should we expect to lose coins that were possibly mined on an old/bad fork?
Add: thought it had worked - showed as having finished the sync - now "downloading 12172 of 12824 . . . last block received 32 seconds ago" - "647 block remaining" Weird!
If your on Linux Wallet, please check:
./aidbitd getblockhash 12138
0000000011e73e1aa8c10e14b5d7bb8b48b0994a07a3a92bd694671c395560ec
Using the windows 1.0.1.0 wallet,
Looking at the block explorer, the 12203 looks good as the last block . . . where the 12823 is coming from and the 620 block remaining, I don't know.
I am running as a server and solo mining, if that matters.
BTW, all of my rewards with exclamation marks were mined on maya.aidbit.net - 23 payouts from 10:34 PM 07/25/2014 to 4:59 07/26/2014 UTC/GMT.
Are you sure you have the latest version? ./getblockhash 12203
0000000003d954fd87fdd01f74b9e09681a8f188d83911dff49be9ce56e178d2
15:20:02
getblockhash 12203
15:20:02
0000000003d954fd87fdd01f74b9e09681a8f188d83911dff49be9ce56e178d2
15:21:03
getblockhash 12206
15:21:03
0000000000851198689ffa8aa55cf8596d4cc6611c81bfb597ee8b4119dee698
July 26, 2014, 09:16:03 AM
Is this OK? SGMiner is showing different difficulty than the newest Wallet. When I was mining Solo, the DIFF in SGMiner was the same as in Wallet.
My SGMiner config is:
gminer -k groestlcoin --difficulty-multiplier 0.00390625 -o stratum+tcp://maya.aidbit.net:3032 -u AKBu9nZBMRphGAuZssyoZZkdsTDLPsiXqj -p x -I 21,21,22 -g 1,1,1 --gpu-engine 1200,1200,1100 --gpu-memclock 1050,1050,1000 --gpu-fan 70 -w 256,256,256 --thread-concurrency 8192,8192,16384
My SGMiner config is:
gminer -k groestlcoin --difficulty-multiplier 0.00390625 -o stratum+tcp://maya.aidbit.net:3032 -u AKBu9nZBMRphGAuZssyoZZkdsTDLPsiXqj -p x -I 21,21,22 -g 1,1,1 --gpu-engine 1200,1200,1100 --gpu-memclock 1050,1050,1000 --gpu-fan 70 -w 256,256,256 --thread-concurrency 8192,8192,16384
July 26, 2014, 09:15:58 AM
We'll keep posted for developments with your coin!
July 26, 2014, 09:15:34 AM
I managed to get the new 1.0.1.0 wallet by clicking the link in the OP.
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
Try to restart the wallet or delete the blockchain database (%appdata%/AidBit - be careful you don't delete wallet.dat).
Worked for me.
Everything confirmed up to a little over 12 hours ago. Waiting . . .
Should we expect to lose coins that were possibly mined on an old/bad fork?
Add: thought it had worked - showed as having finished the sync - now "downloading 12172 of 12824 . . . last block received 32 seconds ago" - "647 block remaining" Weird!
If your on Linux Wallet, please check:
./aidbitd getblockhash 12138
0000000011e73e1aa8c10e14b5d7bb8b48b0994a07a3a92bd694671c395560ec
Using the windows 1.0.1.0 wallet,
Looking at the block explorer, the 12203 looks good as the last block . . . where the 12823 is coming from and the 620 block remaining, I don't know.
I am running as a server and solo mining, if that matters.
BTW, all of my rewards with exclamation marks were mined on maya.aidbit.net - 23 payouts from 10:34 PM 07/25/2014 to 4:59 07/26/2014 UTC/GMT.
Are you sure you have the latest version? ./getblockhash 12203
0000000003d954fd87fdd01f74b9e09681a8f188d83911dff49be9ce56e178d2
July 26, 2014, 09:12:42 AM
I managed to get the new 1.0.1.0 wallet by clicking the link in the OP.
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
Try to restart the wallet or delete the blockchain database (%appdata%/AidBit - be careful you don't delete wallet.dat).
Worked for me.
Everything confirmed up to a little over 12 hours ago. Waiting . . .
Should we expect to lose coins that were possibly mined on an old/bad fork?
Add: thought it had worked - showed as having finished the sync - now "downloading 12172 of 12824 . . . last block received 32 seconds ago" - "647 block remaining" Weird!
If your on Linux Wallet, please check:
./aidbitd getblockhash 12138
0000000011e73e1aa8c10e14b5d7bb8b48b0994a07a3a92bd694671c395560ec
Using the windows 1.0.1.0 wallet, but that "weirdness" has cleared up now.
BTW, all of my rewards with exclamation marks were mined on maya.aidbit.net - 23 payouts from 10:34 PM 07/25/2014 to 4:59 07/26/2014 UTC/GMT.
I'll check the databases. Approximate ammount and address, please and I'll see what I can do.
July 26, 2014, 09:09:26 AM
Is this correct?
Code:
./aidbitd getblockhash 12198
0000000001b84b76b792634839e9dec0d1cadb1bc013610d490c90067b89c239
YES!
July 26, 2014, 09:08:17 AM
I managed to get the new 1.0.1.0 wallet by clicking the link in the OP.
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
Try to restart the wallet or delete the blockchain database (%appdata%/AidBit - be careful you don't delete wallet.dat).
Worked for me.
Everything confirmed up to a little over 12 hours ago. Waiting . . .
Should we expect to lose coins that were possibly mined on an old/bad fork?
Add: thought it had worked - showed as having finished the sync - now "downloading 12172 of 12824 . . . last block received 32 seconds ago" - "647 block remaining" Weird!
If your on Linux Wallet, please check:
./aidbitd getblockhash 12138
0000000011e73e1aa8c10e14b5d7bb8b48b0994a07a3a92bd694671c395560ec
Using the windows 1.0.1.0 wallet,
Looking at the block explorer, the 12203 looks good as the last block . . . where the 12823 is coming from and the 620 block remaining, I don't know.
I am running as a server and solo mining, if that matters.
BTW, all of my rewards with exclamation marks were mined on maya.aidbit.net - 23 payouts from 10:34 PM 07/25/2014 to 4:59 07/26/2014 UTC/GMT.
July 26, 2014, 09:07:58 AM
Is this correct?
Code:
./aidbitd getblockhash 12198
0000000001b84b76b792634839e9dec0d1cadb1bc013610d490c90067b89c239
July 26, 2014, 09:07:01 AM
Is this the correct chain?
Code:
./aidbitd getblockhash 12138
00000000b9f9aafa1882bd331f93fb8caae7649efafc21600b69fcb2160cf4e4
No, it forked after the first POS block (12120). You have the old code. Sorry
./aidbitd getblockhash 12138
0000000011e73e1aa8c10e14b5d7bb8b48b0994a07a3a92bd694671c395560ec
I'm using the latest git update.
I pushed these two later: Please check again:
https://github.com/AidBit/aidbit/commit/612d49144dfd5cc4969821062e4bb37114bfe3a0
https://github.com/AidBit/aidbit/commit/6f98ae5b0f256e821dae1d9cbd63a917debf894b
Thanks!
Yes I have these commits. I deleted everything in ~/.aidbit and resyncing again.
July 26, 2014, 09:06:13 AM
hi
problem?
aid have 500 min (8hours) to mature.
no aid since this morning 07h00 (french time) where are the coins who will be matured during this laps of time?
15h00 now
some aid are "blocked" in stake?
my wallet is the last 1.0010
problem?
aid have 500 min (8hours) to mature.
no aid since this morning 07h00 (french time) where are the coins who will be matured during this laps of time?
15h00 nowsome aid are "blocked" in stake?
my wallet is the last 1.0010
Need some sleep now, will check the databases later and send the funds to the owners.
July 26, 2014, 09:04:01 AM
Is this the correct chain?
Code:
./aidbitd getblockhash 12138
00000000b9f9aafa1882bd331f93fb8caae7649efafc21600b69fcb2160cf4e4
No, it forked after the first POS block (12120). You have the old code. Sorry
./aidbitd getblockhash 12138
0000000011e73e1aa8c10e14b5d7bb8b48b0994a07a3a92bd694671c395560ec
I'm using the latest git update.
I pushed these two later: Please check again:
https://github.com/AidBit/aidbit/commit/612d49144dfd5cc4969821062e4bb37114bfe3a0
https://github.com/AidBit/aidbit/commit/6f98ae5b0f256e821dae1d9cbd63a917debf894b
Thanks!
July 26, 2014, 09:02:59 AM
hi
problem?
aid have 500 min (8hours) to mature.
no aid since this morning 07h00 (french time) where are the coins who will be matured during this laps of time? 15h00 now
some aid are "blocked" in stake?
my wallet is the last 1.0010
problem?
aid have 500 min (8hours) to mature.
no aid since this morning 07h00 (french time) where are the coins who will be matured during this laps of time?
15h00 nowsome aid are "blocked" in stake?
my wallet is the last 1.0010
July 26, 2014, 08:59:00 AM
Is this the correct chain?
Code:
./aidbitd getblockhash 12138
00000000b9f9aafa1882bd331f93fb8caae7649efafc21600b69fcb2160cf4e4
No, it forked after the first POS block (12120). You have the old code. Sorry
./aidbitd getblockhash 12138
0000000011e73e1aa8c10e14b5d7bb8b48b0994a07a3a92bd694671c395560ec
I'm using the latest git update.
July 26, 2014, 08:56:32 AM
Is this the correct chain?
Code:
./aidbitd getblockhash 12138
00000000b9f9aafa1882bd331f93fb8caae7649efafc21600b69fcb2160cf4e4
No, it forked after the first POS block (12120). You have the old code. Sorry
./aidbitd getblockhash 12138
0000000011e73e1aa8c10e14b5d7bb8b48b0994a07a3a92bd694671c395560ec
July 26, 2014, 08:50:20 AM
Is this the correct chain?
Code:
./aidbitd getblockhash 12138
00000000b9f9aafa1882bd331f93fb8caae7649efafc21600b69fcb2160cf4e4
July 26, 2014, 08:32:44 AM
I managed to get the new 1.0.1.0 wallet by clicking the link in the OP.
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
However, despite having connections to the network and a spinning "sync wheel", My blockchain seem to be stuck 7 hours in the past.
Could this be an issue caused by connecting to nodes running the old wallet, and if so could you provide nodes that are using the new wallet/fork so I can update my conf file?
Try to restart the wallet or delete the blockchain database (%appdata%/AidBit - be careful you don't delete wallet.dat).
Worked for me.
Everything confirmed up to a little over 12 hours ago. Waiting . . .
Should we expect to lose coins that were possibly mined on an old/bad fork? Answered my question reading previous posts - exclamation marks mean the coins were mined on a bad fork, correct?
Add: thought it had worked - showed as having finished the sync - now "downloading 12172 of 12824 . . . last block received 32 seconds ago" - "647 block remaining" Weird!
July 26, 2014, 08:31:19 AM
Which pool is now operational? Maya seems not to respond. I can only mine Solo.
I also have lot of transactions in my wallet which have questionmarks and exclamation marks. What does it mean? My wallet is fully re-synchronized. I deleted whole Roaming\AidBit folder, restored Wallet.dat and redownloaded blockchain. Currently I'm at block 12118.
I also have lot of transactions in my wallet which have questionmarks and exclamation marks. What does it mean? My wallet is fully re-synchronized. I deleted whole Roaming\AidBit folder, restored Wallet.dat and redownloaded blockchain. Currently I'm at block 12118.
Yes these coins originated from a fork. If it bothers you export your private key & delete the wallet.dat and imported the key back. dumpprivkey/importprivkey console commands.
OK thanks I will try, but which pool is now operational?
Now, they should all work.
Jump to: