Hi, can someone help me out with configuring my .bat.
SGminer giving me some troubles and I can't figure out what the problem is (Though I suspect it might be intensity related).
I' running two R9 280x's.
Cheers for your troubles.
I run R9 280's as well, but with all default setting, no overclocking, so im not sure i'll be able to help much. One thing to try it a new .bat file similar to this, and also delete any .bin files in the SGminer folder timeout /t 10
setx GPU_MAX_ALLOC_PERCENT 100
sgminer -k marucoin -I 19 --auto-gpu --auto-fan --no-submit-stale -o stratum+tcp://<<pool address>> -u username -p password
|
|
|
|
|
There is something funky about block 537. if you are resyncing a new wallet it may stop at block 537, if it does, simply restart the wallet to get past it.
|
|
|
|
The boost.suprnova.cc pool is online with active miners who tries to solve the high diff block, but in my opinion it's waste of hash power. We should start mining after block height 1300. Block are resolved with PoS now.
so what is the plan? after this block the coin will be OK to mine again? I want to point my ati card to nova pool but my resources are limited and I want to w8 till its surely fixed! Yes we need to wait for word from nova pool that their wallet has been updated |
|
|
|
The boost.suprnova.cc pool is online with active miners who tries to solve the high diff block, but in my opinion it's waste of hash power. We should start mining after block height 1300. Block are resolved with PoS now.
Agreed, let the PoS blocks solve automatically until after 1300, shortly after that the diff will drop, then start pumping again  |
|
|
|
mammix is this minable with nvidia ccminer? Or not? They havent replied in cuda miner thread(I guess not?)
Unfortunately not, cudaminer will need to be able to hash the 13 different algos that make up x13. Maybe someone has already looked into an x11 version of Cuda i'm not sure. if they have then adding the extra 2 hash algos should not be too difficult |
|
|
|
Any ETA on the fix, other than the at block 2000?
Very soon, i've got the fix coded in and has been proven on testnet and on a private fork of the Main chain. All i need to do is compile both Windows and OSX wallets and release them. Im away today but should be able to get them done this evening when i'm back I would suggest reconsidering releasing only a difficulty fix to the wild without doing a proper hard fork from a specific block number. (fortunately the coin has PoS blocks). I'm not an expert but as far as I know without a proper hard fork and giving enough time for everybody to update, the chances for blockchain forks are pretty high. One coin that I know of and had similar problems and succeed to do a proper update, was Goodcoin ( https://github.com/stolenjs/gcfinal) Ah yes GOODcoin, i helped them with that coin too To confirm, this release will cause a hard fork at the determined block number. This is because anyone on the old wallet will get an invalid Proof of Work for any blocks mined after. Once the wallets are released the seednodes will be updated, so its advisable to delete the peers.dat file to make sure the first time the new wallet connects is to the new updated wallets |
|
|
|
Any ETA on the fix, other than the at block 2000?
Very soon, i've got the fix coded in and has been proven on testnet and on a private fork of the Main chain. All i need to do is compile both Windows and OSX wallets and release them. Im away today but should be able to get them done this evening when i'm back |
|
|
|
exchang?
Not yet, i want to get the coin working correctly first, that is why i put a 30 day PoW period on it |
|
|
|
Update:As we all know the difficulty value is fluctuating too much at the moment as as a result the average block rate is about 2 - 3 minutes when it should be 1 minute. At the moment we are at about block 650 when we should be at about 1600. So as a result the PoW phase will probably over run by a few days. I've identified the fixes that need to go into the wallet. I'm aiming to get the following tasks complete before block 2000 - Coding complete - Tested on TestNet - New wallets compiled - Publish the new wallets This will cause a mandatory wallet update which everyone will need to do. Thanks for sticking with BoostCoin
|
|
|
|
Hey everyone. I'm still here. i dont want you to think i've abandoned you all.. At the moment i'm looking into if it is possible (technically) to changes KC into a PoS coin without some crazy relaunch or exchange the coins you already have kind of deal.... Hang in there, i have a few jobs on the go at the moment, but i will be back! Thanks |
|
|
|
|
Hey everyone. hang in there. i'm testing a final fix this evening.
|
|
|
|
|
When SummerCoin was in its PoW phase, did the difficulty value jump all over the place ?
|
|
|
|
|
Hey everyone,
Is there anyone willing to help out test a wallet update on testnet?
Ive updated the code to fix the crazy difficulty retargeting that we are all experiencing. but i only have a 4MHs rig so need extra power to check the move into the new retargeting method works correctly.
If this update works well then there will be a mandatory wallet update, if it does not work, then i may have to relaunch the coin as the current block chain holds a history of the wrong retargeting method.
PM me if you can help?
Thanks
|
|
|
|
bootcoin x13 = DRk ?  Nope Darkcoin used X11 Algo |
|
|
|
Think i have found the issues with the crazy retargeting. Looks like it is currently retargeting as if the coin is in its POS phase. a section of the code that i had overlooked. This section of the code controls 2 different types of retargeting... unsigned int GetNextTargetRequired(const CBlockIndex* pindexLast, bool fProofOfStake)
{
int change;
if(fTestNet)
change = 10;
else
change = 100;
if(pindexLast->nHeight + 1 > change)
return GetNextTargetRequired_(pindexLast, fProofOfStake);
else
return GetNextWorkRequired_legacy(pindexLast);
}
I think the problem is the wallet is set to start the GetNextTargetRequired function after block 100, i think it should be 43200, which is our PoS start block. Just testing this theory now on Testnet. If it is the case there will be a mandatory wallet update to fix this. Thanks |
|
|
|
|
hey people, i have a question about the retargeting code in SUMC. if anyone here is experienced with it can you pm me?
Thanks
|
|
|
|
i'm looking into the crazy retargeting, and seeing if its possible to replace it with something like DIGISHIELD, as i've done before on other coins. Everything else seems to be working fine |
|
|
|
|
I'm getting 1.35Mh on R9 290 using Intensity 19 and the rest of the settings default
|
|
|
|
A really careless dev and the launch time is confusing people.Boost Should be relaunched!
Dude its not as if this knowledge is for sale down the local shop... It takes time and effort (yes with errors) to get this stuff right! To my knowledge this is the 2nd ever x13 coin to launch and the first x13 PoS coin.... I have mined some maru and I feel as though you really hung everyone out to dry on that coin. Are you planning to put forth effort into this new iteration? Sorry dude, im nothing to do with Marucoin |
|
|
|
|
Show Posts
