Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now. You can connect directly to one of our pool nodes. #aidbit.conf connect=maya.aidbit.net connect=felix.aidbit.net connect=kei.aidbit.net
This way you'll limit connection to other nodes. I know it's frustrating, but it's no better on this side. Regards, AidBit I was looking at the Litecoin Wiki looking for something else and came across the -checkpoints switch for the conf file which limits connectivity to only accepting the block chain matching built-in checkpoints.
|
|
|
Any team that sticks with their coin this long in this current environment is worth a lot of praise and patience (imho). Regarding mass adoption, all a coin really needs is to leverage their brand/tech. for a specific valuable purpose or service, it becomes a vehicle for proper use and your coins (shares) become a valuable piece of that system. It's a pipe-dream for daytraders and used by BS artists with scam coins to make BTC, but it does and will continue to happen. Let BTC be mass adopted, but if you were to assume the ZETA case were real (another can of worms) then it is easy to see where particular technologies may very well end up in the years to come. DGB seem to be taking that path and have remained professional all year. They've proven they can dev. and adapt and have stuck with DGB through all the shit 2014 has thrown at altcoins. Use it like the rest to yoink some BTC it's an unfortunate reality, but if they continue and find a place or service to slot their brand/coin into then you have a longer term winner. It seems they aren't going anywhere, and I'm sure they will continue to evolve until they are just right for their place on the board. You also can't underestimate the relationships they continue to solidify. This isn't even me shilling. I won't lie much earlier in the year I wanted DGB out of the equation (they are a tough, stubborn and respected competition despite their market cap), but after so long of Jared and his team remaining polite and doing what they can in this environment I now watch and support DGB developments from the side. TLDR: Multi-algo fork must be a tough gig and it's hard to agree upon which algos. I like DGB and good luck. That’s a real nice endorsement!
|
|
|
yes i agree with you but i see my wallets ans it s very not cool :/ i think i mine wind... edit:9h30 continue mining since this morning,a lot a block this morning when diff was 0---->0.0000000000000000000000000000000000000000000000000000 AID in my wallet i m loosing faith The mining reward is designed to be less (or more) depending on the diff. It’s roughly an approximate 8:1 ratio (still working on understanding it better). In general terms, as the network hashrate and diff fall, so does the reward, and vice versus with the opposite. Put in other terms, you should basically expect the same reward for your hashrate submitted regardless of network hashrate and difficulty (that is if my understanding is correct). I’m thinking it would be a good idea to put together some FAQ’s with stuff like this.One of the two other currently important areas for FAQ’s that immediately come to mind would be install instructions and install issues with known possible solutions. Sometimes deleting data files from the AidBit folder/directory works to correct a failed install, sometimes using the default install fix sync issues works, etc. Putting that into an FAQ for newcomers should be helpful. Helping out with, and encouraging further troubleshooting would be the main thrust behind the creation of these FAQ. The second of my two most important currently key issues is the forking issue. An FAQ instructing on how to insure you’re on the correct blockchain and the need for vigilance would be very useful I would think. We have a shared responsibility and are all in this together. Unfortunately I personally don't have the time to do more with this than make the suggestion. Thank you very much for your suggestions. Actually, the FAQ and help sections were scheduled for now. Unfortunately, the current priority is to diagnose and fix all low level problems. Regarding missing coins, don't worry, pools' wallets are safe and everything mined on the correct blockchain will be sent to you, one way or the other. Regards, AidBit Thanks! Good to hear that about the missing coins . . . another possible FAQ. But seriously, it's not like I was targeting the devs with more of "what you should be doing"; I wasn't limiting the suggestion to just you guys and was actually thinking more of the community - the community is made up of some very bright and knowledgeable folks who could help to put together ad hoc rough drafts right here, right now, you know, contributing what we can.
|
|
|
yes i agree with you but i see my wallets ans it s very not cool :/ i think i mine wind... edit:9h30 continue mining since this morning,a lot a block this morning when diff was 0---->0.0000000000000000000000000000000000000000000000000000 AID in my wallet i m loosing faith The mining reward is designed to be less (or more) depending on the diff. It’s roughly an approximate 8:1 ratio (still working on understanding it better). In general terms, as the network hashrate and diff fall, so does the reward, and vice versus with the opposite. Put in other terms, you should basically expect the same reward for your hashrate submitted regardless of network hashrate and difficulty (that is if my understanding is correct). I’m thinking it would be a good idea to put together some FAQ’s with stuff like this.One of the two other currently important areas for FAQ’s that immediately come to mind would be install instructions and install issues with known possible solutions. Sometimes deleting data files from the AidBit folder/directory works to correct a failed install, sometimes using the default install fix sync issues works, etc. Putting that into an FAQ for newcomers should be helpful. Helping out with, and encouraging further troubleshooting would be the main thrust behind the creation of these FAQ. The second of my two most important currently key issues is the forking issue. An FAQ instructing on how to insure you’re on the correct blockchain and the need for vigilance would be very useful I would think. We have a shared responsibility and are all in this together. Unfortunately I personally don't have the time to do more with this than make the suggestion.
|
|
|
Price drives mining, right now..its not profitable to mine..infact..it hasent been in at least a month. When it is, it just gets dumped, just like all alts. Sad but true, its cheaper to buy this than mine it.. and even then, no one is buying it. I feel a lil stuck.. have a bunch, and just keep seeing its value drop. That tells me, that there are no investors behind the sceens with NDA's. I can only imagine how un profitable it will be to mine this in 2 years, 5 yrs, 8 yrs, 15 yrs.. how long does mining go on for? 28 years? Just dis-heartened, every alt is down, because..well.. face it.. its just gambling. Dreams of being some world wide, mass adopted way of paying for things is lunacy. The price fluctuation are sometimes 50x of what any credit card fee could possibly ever be on some coins. Unless you have a ton of BTC to make markets do what you want.. its pointless.
I agree with you on almost every point, but it could be worse: https://bitcointalk.org/index.php?topic=408268.msg7936677#msg7936677https://bitcointalk.org/index.php?topic=408268.msg7938747#msg7938747At least DGB has been keeping its head above water. I agree on almost every point, except your view on possible mass adoption. My view is that there WILL BE a handful of winners who do achieve mass adoption. The opposite is practically an impossibility. Someone WILL WIN BIG. Who will that someone be? IMVHO it will be the people who focus on bringing the best core product possible to market (i.e., coin, wallet, and network) and everything else will fall into place. Digibyte is one of my highest probability contenders. And yes, again, I agree with you on almost everything, not everything, but almost everything, including the part about this being a dream, which it still is (there's a gigantic chasm between every idea and its realization, and there's still a very long ways to go).
|
|
|
I've seen 2 invalid checkpoint errors today, one on the laptop and one on the PC, both just prior to updating (the laptop to 1.0.1.1 and the PC to 1.0.1.2). The laptop was then getting a aidbit-qt has stopped working and was closed by Windows before finally updating it to 1.0.1.2. Just updated the PC to 1.0.1.2 and I'm still getting the invalid checkpoint warning.stuck at 13593 of 13599 block explorer at 3117 ?? resyncing again? The laptop has synced on the other hand. Both updates were done with default options selected. Add: just did a manual clean up of AidBit folder (left only the wallet and .conf files) and reinstalled. It has done a successful sync, but reports a current block of 13601 while the laptop reports 13639!They report different blockhash values for 13601. Add2: block explorer now working again - the laptop is on the correct blockchain - how is it that a clean install on the PC went so awry? Going to reinstall again. We were once again targets of deliberate or non deliberate attack. We're not totally sure but it seems that somebody with huge hashrate is trying to mine with wrongly configured stratum. At least logs show that. We've just activated pos on our charity account to keep this fork safer. As you said, AidBit will be stronger for it. Good idea to do everything possible to keep the fork safer. BTW, the program mini-hang that always seems to happen on initial sync that I mentioned in my last post, there might be something there to take a closer look at. Weird things with the block explorer in general where sometimes it generates very low block values that make it look like the entire blockchain is being resynchronized . . .
|
|
|
I've seen 2 invalid checkpoint errors today, one on the laptop and one on the PC, both just prior to updating (the laptop to 1.0.1.1 and the PC to 1.0.1.2). The laptop was then getting a aidbit-qt has stopped working and was closed by Windows before finally updating it to 1.0.1.2. Just updated the PC to 1.0.1.2 and I'm still getting the invalid checkpoint warning.stuck at 13593 of 13599 block explorer at 3117 ?? resyncing again? The laptop has synced on the other hand. Both updates were done with default options selected. Add: just did a manual clean up of AidBit folder (left only the wallet and .conf files) and reinstalled. It has done a successful sync, but reports a current block of 13601 while the laptop reports 13639!They report different blockhash values for 13601. Add2: block explorer now working again - the laptop is on the correct blockchain - how is it that a clean install on the PC went so awry? Going to reinstall again. Add3: installed and doing a re-sync, program not responding with 2203 blocks remaining and block explorer just went off-line at the same time. I've noticed the "program not responding" several times when syncing, always around the same place. Could there be a problem somewhere around block 11460? Has now completed sync. Block Explorer is back online. PC confirmed on the correct blockchain now. (Last install was a default install leaving everything in place and letting the installer do its job.)
|
|
|
Taking a look at the .csv file I saved before upgrading to the new wallets for the first time, I see that rolling share payouts from p2poolcoin.com:14715 (where I also had some miners) continued until 2014-07-26 05:55:20 GMT on what must have been a bad fork since the new block chain has those P2Pool payouts stopping at 2014-07-25 19:18:56 GMT, some 10 hours earlier.
That can certainly be addressed and reversed, and I should see those payouts come good once that pool is back up and running, correct?
BTW, on a more positive note, this from Cryptsy:
Hello XXXX,
Thank you for contacting us about this issue I have submitted the coin request to our development team who will review it to see if it meets our requirements for addition to the Cryptsy exchange.
If you have further issues, concerns or questions please do not hesitate to contact us again. Thank you for choosing Cryptsy and enjoy trading!
Sincerely,
XXXX Customer Service Manager
|
|
|
As for scheduling? One POS every 10 minutes, for example? Or is it more dynamic? Actually it uses the same target spacing as POW but can extend the POW target spacing x3 in cases of many concurrent blocks. Looking sweet. See ya tomorrow!
|
|
|
As for scheduling? One target POS every 10 minutes, for example? Or is it more dynamic?
|
|
|
We went pass another POS, great! Looking good. BTW, what should the block generation look like for POS?
|
|
|
Reopened my wallet a few minutes ago, junked everything except for wallat.dat, and got a complete sync done. Wallet reporting block 12574, but block explorer is still on 12564. My wallet's on the same chain as the block explorer up to 12564. 12564 was first POW after 7 straight POS (according to the block explorer). Add: browser refresh issue - block explorer keeping up now mixing POW with POS. Add2: 12592 and block hashes match. Rolling right along. Purdy sight to behold. Add3: diff rising and we just got another POS!!! Sorry, that was wrong. Add4: there we go, POS on Block #12615. Looking good. Expecting to see 2 GH/s net hash again tomorrow morning (it's late night over here). See you all then.
|
|
|
Do NOT mine AidBit yet. Something wrong with their network (reward jumped from 200 to 6 and difficulty is about 0. . That would be about right since their reward is a dynamic reward based loosely on an 8:1 diff ratio (8 * dDiff, roughly, for now).
|
|
|
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?
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. no it hasn't - just came back - now it's "downloading 12203 of 12823 ... with 620 blocks remaining". 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. I'm on the miner now. Snooping around. Guess what? The block explorer is now reporting different values for those blocks we had double checked before. http://columbus.aidbit.net/chain/AidBit Add: anything you'd like to see before I shut down?
|
|
|
Waiting for an active node. I put in these addnode=columbus.aidbit.net addnode=felix.aidbit.net Good. I got 3 nodes before and then lost them. Now, with your addnodes I've got two stable connections, but it's still out of sync and not syncing. 2 minutes out, more or less, and it's starting to sync (am being patient with hitting the "Post" button). 5 connections, 84 blocks remaining - on 12471 - This is my laptop by the way, the test miner is still mining solo - let me check - it's still mining, and obviously on a fork This laptop's wallet is still stuck on 12471 (a good 10 minutes now). Block Explorer reporting 12558 as Proof of Stake http://columbus.aidbit.net/chain/AidBit
|
|
|
Waiting for an active node.
|
|
|
Anyone else getting serious AV headaches?
|
|
|
I was solo mining and last I checked I was on the main blockchain until block 12545 (I'm still finding blocks now but it looks like the main blockchain is resyncing?)
Diff was down to 1-2 so I knew I was practically the only one.
p2poolcoin.com hasn't come back online at all (still reporting block 13054 from yesterday)
Lots of other weirdness though that I've mentioned before (not to mention a radical change in the total balance of my wallet by more than 1000 coins - even if I don't see where they've gone when looking at transactions, but I still haven't done a spread sheet analysis yet...).
|
|
|
My thinking is that as long as profitability is defined by ASIC technology, that’s going to be the defining determinant regarding price, and nothing else. And if the GPU were to set profitability (in the absence of ASIC) then price would be higher. The multi-pool is only an intermediary, and theoretically neutral. That having been said, while I look upon the multi-pools as being benign, I don’t like the idea of merged mining at all. I really like the Myriad combo though - that much I do know.
|
|
|
|