Download either stops or it is blocked by firefox. I finally arrived with IE by pausing and restart 4 times 20 minutes to download the wallet...I hope this is the last update  I just noticed that the new Firefox v. is blocking the download. I will address the issue very soon. Bandwidth should be sufficient on our side. Of course it is not the last update.  |
|
|
|
3 Rigs and impossible to download new Wallet  What is the problem? |
|
|
|
Please, upgrade your wallet immediately! I don't want to see this error message ever again in my life! I agree but ... Please update Git repository immediatly ! It's lagging one revision behind the real wallet This was done intentionally, the wallet's code is the same in both builds. We did this to see how many users fixed their blockchains, because Linux users have to use manual method to clean up the database and it is not certain they did it. Couple of hours ago I tried syching with a new client (with all nodes allowed) and it synched fine. |
|
|
|
Hi guys, sorry I was a bit absent these last couple of days. I was buried in the code and I can say with pride, I think we did it. V. An outstanding job! Thank you! The more I think, the more I like the idea that the problems appeared or better that they appeared so early, although it was stressful as hell and still is. We've optimized so much stuff, adjusted the POS target spacing, polished the code, introduced blockchain delivery in the installer, which will later, when the blockchain grows in size, help new user to get synchronized instantly. I apologize for so many versions but it was the only way to fix the problems in shortest possible time. Cheers, V. |
|
|
|
With the following informations, could you explain me how you calculate the block reward ? $ aidbitd getinfo
{
"version" : "v1.0.2.0",
"protocolversion" : 60015,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 17965,
"timeoffset" : 0,
"moneysupply" : 4054901.95566341,
"connections" : 3,
"proxy" : "",
"ip" : "82.229.26.235",
"difficulty" : {
"proof-of-work" : 12.67447368,
"proof-of-stake" : 0.00060976
},
"testnet" : false,
"keypoololdest" : 1405716160,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}
The error message will be corrected soon, when wallet will get updated Thanks. Well, with the above information you could only estimate the reward for block 19765, since the reward is now based on previous block's height and difficulty. But you could call getblockhash 17964 and getblock #hash to get the correct difficulty, then you'd just need to calculate it using: ceil(8 * dDiff / (525600 + 17964) * 525600). Or you could use getmininginfo command. Regards, AidBit I don't want to see this error message ever again in my life! |
|
|
|
Hi guys, sorry I was a bit absent these last couple of days. I was buried in the code and I can say with pride, I think we did it. V. |
|
|
|
Can you fix the link to new wallet please.
I am on it... Very good job guys! |
|
|
|
Difficulty based block reward according to: ceil(8 * dDiff / (525600 + nHeight) * 525600)
Block reward scaling factor on 12 month periods
I can only get close with this: 8 * dDiff / ((525600 + nHeight) / 525600) Which looks wrong since that would be an increasing subsidy into a complete double by day 356 (and forget what multiplication instead of division gets you!). 8 * dDiff / ((525600 - nHeight) / 525600) would be a decreasing subsidy and gets me closer, for now, but that would take us to a complete 0 subsidy by day 365.  I'm sure I'm missing something here and really showing my ignorance.  nHeight is block height or block number. 1 year = ~525600 blocks So lets calculate the reward for dDiff = 1 and block 525600 (~365th day) 8 * 1 / ((525600 + 525600) / 526500) = 8 * 1 / (1051200 / 525600) = 8 * 1 / 2 = 4Realtime rewards are closer to a simple 8 * 1 dDiff, but off by a good fraction (even after taking into account the 10% charity factor). I can't get anything to work consistently. Also, I understand nHeight to mean current block height, being the highest block in existence to date. 12194 as of 2014-07-25 22:50:26. Am I wrong on this? Please let me get back to you a bit later. I just noticed a problem and have to fix it as soon as possible. |
|
|
|
Difficulty based block reward according to: ceil(8 * dDiff / (525600 + nHeight) * 525600)
Block reward scaling factor on 12 month periods
I can only get close with this: 8 * dDiff / ((525600 + nHeight) / 525600) Which looks wrong since that would be an increasing subsidy into a complete double by day 356 (and forget what multiplication instead of division gets you!). 8 * dDiff / ((525600 - nHeight) / 525600) would be a decreasing subsidy and gets me closer, for now, but that would take us to a complete 0 subsidy by day 365. I'm sure I'm missing something here and really showing my ignorance. nHeight is block height or block number. 1 year = ~525600 blocks So lets calculate the reward for dDiff = 1 and block 525600 (~365th day) 8 * 1 / ((525600 + 525600) / 526500) = 8 * 1 / (1051200 / 525600) = 8 * 1 / 2 = 4 |
|
|
|
I created an aidbit subreddit with links to this thread and your webpage and such. Got 3 members so far but looking forward to the influx after cryptsy. http://www.reddit.com/r/AidBitThanks! Subreddit link added to Social Networks. |
|
|
|
Pool operators, please disable staking on main pool wallets to prevent
any possible problems with payouts.
Thank you, Vger
|
|
|
|
It would be nice to sort the NOMP Worker Stats page somehow as it seems to be unsorted. I would sort it by miner hashrate descending as it is usual on most pools.
I agree, will fix it as soon as I find the time. Thanks, V. |
|
|
|
Actually this was ment to be like this. The fourth number is just a build number. I can of course fix that if the community insists. Thanks, V-Ger I'm convinced and truly believe in success for AidBit, from that reason I notice every details. (mining with my, about 140Mh/s) Best wishes for AidBit team and miners comunity! Thank you so much for your kind words. |
|
|
|
Hi my friends.
I'm mining on kei.aidbit.net:3032.
I'm using URL (difficulty 1) with "--difficulty-multiplier 0.00390625 --no-submit-stale".
It's OK?
I use Xubu 12.04, how can I correct sgminer.conf with "difficult multiplier and no submint-stale?
Thanks a lot
Actually the difficulty is set to dynamicaly adjust (1-512), so the shares come in 15 sec intervals. I'm not sure if I understand you question. You can use the above commands as arguments or edit the config file (nano configname.conf) and start sgminer with ./sgminer --config configname.conf Cheers, V. I don't know how to edit config file with difficult multiplier and no submint-stale. I can't find it in the web... 2. So what is the difference between: URL (difficulty  : stratum+tcp://kei.aidbit.net:3008 URL (difficulty 1): stratum+tcp://kei.aidbit.net:3032 URL (difficulty 256): stratum+tcp://kei.aidbit.net:3256 Share time adjust? Thanks Actually ports 3008 and 3256 use fixed difficulty but are currently closed, so you'll have to use the stratum+tcp://kei.aidbit.net:3032. It really isn't that difficult. Perhaps the most easy way would be to start the ./sgminer with arguments as shown in first post then save the settings with S and R. Then just use the command nano sgminer.conf, edit the settings and save the changes with CTRL+O. Good luck. |
|
|
|
Hi my friends.
I'm mining on kei.aidbit.net:3032.
I'm using URL (difficulty 1) with "--difficulty-multiplier 0.00390625 --no-submit-stale".
It's OK?
I use Xubu 12.04, how can I correct sgminer.conf with "difficult multiplier and no submint-stale?
Thanks a lot
Actually the difficulty is set to dynamicaly adjust (1-512), so the shares come in 15 sec intervals. I'm not sure if I understand you question. You can use the above commands as arguments or edit the config file (nano configname.conf) and start sgminer with ./sgminer --config configname.conf Cheers, V. |
|
|
|
Actually this was ment to be like this. The fourth number is just a build number. I can of course fix that if the community insists. Thanks, V-Ger |
|
|
|
I noticed you have added "--difficulty-multiplier 0.00390625" parameter in your example of GPU configuration. Is it mandatory ? And about "--no-submit-stale" ?
BTW, the change on Git repo is only a cosmetic change for the RPC port number, no change in code.
Thanks.
Neither of settings is mandatory. Yeah, I know, I fixed the wrong default RPC port setting and all the .ts files and decided to reset everything to make it clean. (Sorry, OCD kicked in). I won't do it again, I promise. Just delete the clone and DL the source again. |
|
|
|
Please post NOMP pool instructions / codes .. or if done p2pool but this is going to require some more work?
I will make a new pool..
Or can you just use a pool with support for groestl?
Please see necessary stratum modifications, posted on our git: https://github.com/AidBit/node-stratum-pool/tree/AidBitConfiguring NOMP is a pretty straight forward process. Due to our modifications, first two reward recipients in the pool config must be configured with 0 percentages: "rewardRecipients": {
"ANhmhMCxJZkV7M5nmBMaXZWVfRuba79B3m": 0,
"AVBLFaezaUM83odu4x3Rr8dQ8vHVFHEddC": 0
},
Cheers, V |
|
|
|
|
OK fixed, now we can test the update notification functionality in the "production env".
V.
|
|
|
|
Windows has left the building Not sure if everybody would agree with, especially in the 3D-Design department. I am talking about Win vs Mac of course. OS X has also left the building, into a VM though, need it for writing music. Well, I need them all, so I'm tripple booting. |
|
|
|
|
Show Posts
