|
Huh, getting a few random "securecoin-qt.exe has stopped working" on one of my boxes.
Any ideas?
edit: I'm an idiot. Gotta make sure "minimize to tray" is enabled.
|
|
|
|
Launch will be tomorrow (Wednesday) at 8 PM UTC time. An alternative launch time if that causes too much conflict is Friday at 1 PM UTC.
I will have a guide and the QT ready. Although I'm sure someone will make a better guide.
The details of the ascending rewards will be posted shortly. That is the final decision to be made.
I guess it's about time to update the main post? </nag nag nag> |
|
|
|
|
Lots of minor tweaks! Many small bugs quashed!
See main post for details.
|
|
|
|
|
Updated script to keep it in line with main Primecoin script. See main post for details.
|
|
|
|
so? you're still trying to sell open source software...
No, I am selling modified open source software which is legal in my country. Yep, according to the copy protection cgminer is listed under, you are correct. https://github.com/ckolivas/cgminer/blob/master/COPYINGHOWEVER, as per the copy protection: For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
I highly doubt you're upholding the copy protection, just hiding behind it. |
|
|
|
And for Windows too, Please.
... you mean "extract this .zip file, double click this .exe?" As for linux, assuming that they built this in the same fashion as other coins, it should include a "makefile.unix" by default. If they include a github, it's even easier. |
|
|
|
|
Two things: 1) can you go into details about the ascending rewards and 2) you might want to update the main post.
|
|
|
|
Cool, thanks for the clarification. Just FYI, I did a major test (500-1000 machines from 4 to 16 cores for several hours) of both HP9 and HP10 on mainnet and for the most part found that the default settings you had selected were the optimal.
Holy balls, and I thought running 20x cc2.8xlarge AWS instances was nuts. Out of curiosity, how does one come across so much computing power? Were you using AWS as well? aws with increased limits. Incidentally the cc2.8xlarge is not the most cost effective for xpm as the L1 cache appears to be a bottleneck. To prove it, try running just 16 threads instead of all 32 and you'll see little difference!! Or at least that was true for hp9. You can get more bang for buck with 8 cores. Which would you recommend? Multiple c1.xlarge or just using cc2.8xlarge with threads = core/2? |
|
|
|
Cool, thanks for the clarification. Just FYI, I did a major test (500-1000 machines from 4 to 16 cores for several hours) of both HP9 and HP10 on mainnet and for the most part found that the default settings you had selected were the optimal.
Holy balls, and I thought running 20x cc2.8xlarge AWS instances was nuts. Out of curiosity, how does one come across so much computing power? Were you using AWS as well? |
|
|
|
UPDATE: I am satisfied with the coin's performance and it is on track for a Tuesday/Wednesday launch. I will specify a definite time as it approaches.
Thank you for your support, help, comments, and suggestions. It is much appreciated.
Bter will work with us to offer trading from launch.
We're going to have a full 24 hour heads up before the release, right? I don't want to be caught off guard and miss out on the festivities.  |
|
|
|
Usually that's one of two things: 1) your wallet is encrypted and you haven't unlocked it or 2) that key exists in your wallet, but just isn't on your "addresses" screen. |
|
|
|
Thank you for your answer you two !
Did you notice any difference between the already compiled primecoind and the one compiled on the server ?
Some vps I have only have 256mb of ram and swap so I can't compile on them so I use the already compiled one and did not notice any difference in performance.
Why compile on an openvz ? You will get suspended for unfair cpu usage on those !
Usually compiled locally gives better results if you include compile flags like "-mtune=native -march=native" so the binary is tailored to your hardware. The reason it's difficult to compile on OpenVZ is because you cannot use swapon to use a swapfile, you're forced to use only the memory you have available. You can compile with certain memory restrictions, but it makes the compile literally take over 20 times as long. It ends up triggering a garbage collection at almost every step of the process and limits how much working space it's allowed. The compiled binary will work perfectly fine, but the compile time goes through the roof. Also, I don't think the virtualization platform matters as much for account suspension as much as the network administration does. Some virtualizations may have more/less support for load monitoring, but it eventually all comes down to whoever is running the show. |
|
|
|
As a rule of thumb what is the ram requirement per core ?
The most that the Primecoin-Qt process uses with 8 cores on any of the machines I'm running is 112 MB. Running it is cake. Compiling it will require at least 1 GB of memory (RAM/Swap). You can compile it with less (for example, on an OpenVZ VPS), but it'll take forever. |
|
|
|
I'm not sure if I did this right, but I made a tweak to the "primemeter" section of the code to get a peek at what solving difficulty+1 would be like. If this is right, all I have to say is "oof". If I've done this wrong, please tell me.I really really hope I've done this wrong. Original main.cpp: if (nMillisNow - nLogTime > 59000)
{
nLogTime = nMillisNow;
printf("%s primemeter %9.0f prime/h %9.0f test/h %4.0f %d-chains/h %3.6f chain/d\n", DateTimeStrFormat("%Y-%m-%d %H:%M:%S", nLogTime / 1000).c_str(), dPrimesPerMinute * 60.0, dTestsPerMinute * 60.0, dChainsPerMinute * 60.0, nStatsChainLength, dChainsPerDay);
} Tweaked main.cpp: if (nMillisNow - nLogTime > 59000)
{
nLogTime = nMillisNow;
double next_prob = EstimateCandidatePrimeProbability(nPrimorialMultiplier, TargetGetLength(pblock->nBits));
double est_next = dChainsPerDay * next_prob;
printf("%s primemeter %9.0f prime/h %9.0f test/h %4.0f %d-chains/h %3.6f chain/d %u RoundPrimorial %3.6f est_next %3.6f next_prob\n", DateTimeStrFormat("%Y-%m-%d %H:%M:%S", nLogTime / 1000).c_str(), dPrimesPerMinute * 60.0, dTestsPerMinute * 60.0, dChainsPerMinute * 60.0, nStatsChainLength, dChainsPerDay, nPrimorialMultiplier, est_next, next_prob);
} Result (1 vCPU VPS): 2013-08-22 15:23:44 primemeter 892352 prime/h 14610791 test/h 60 5-chains/h 0.153438 chain/d 47 RoundPrimorial 0.013593 est_next 0.088589 next_prob
2013-08-22 15:24:44 primemeter 878830 prime/h 14379729 test/h 0 5-chains/h 0.152076 chain/d 41 RoundPrimorial 0.013928 est_next 0.091584 next_prob
2013-08-22 15:25:44 primemeter 885159 prime/h 14521363 test/h 180 5-chains/h 0.152199 chain/d 43 RoundPrimorial 0.013710 est_next 0.090079 next_prob
2013-08-22 15:26:44 primemeter 877952 prime/h 14345645 test/h 60 5-chains/h 0.150436 chain/d 43 RoundPrimorial 0.013551 est_next 0.090079 next_prob
2013-08-22 15:27:44 primemeter 879141 prime/h 14404795 test/h 60 5-chains/h 0.152234 chain/d 43 RoundPrimorial 0.013713 est_next 0.090079 next_prob So yeah, 0.152 chain/d now at diff 9, only 0.013 chain/d at diff 10? I really hope I'm wrong. edit: I did spot an inconsistency issue. chain/d is measured over the entire 60 second interval of various values for RoundPrimorial, but the est_next/next_prob values are based on the current value of it. I imaging it can skew the results +/- 10%. |
|
|
|
|
I'd be interested in seeing an optional login system for uploaders. You can upload anonymously (as you currently can) or you can upload with an account. The account itself should have minimal info requirement for signup for privacy sake: just a username and a password, no email address. Should the site become compromised somehow, there will be minimal information on-hand about a user. The most they'll get are 1) username, 2) files uploaded, 3) payment address. No email, no personally identifiable information.
When you upload with an account, you should have the option to have your username displayed and optionally, the BTC address where coins will be sent. That way, reputable individuals can gain trust. I'd be much more likely to buy something from Satoshibox if 1) I know who the seller is and 2) I can verify which address the coins will be sent to.
For example, (completely hypothetically) if I see a file called "NineInchNails_Discogrophy.zip", I wouldn't download it unless it's free. I have no way to get a refund in the case that's it's just a zip file full of cat pictures. It's just simply too risky to spend coins on. If I see the same file, uploaded by Trent Reznor and the BTC addresses matches the BTC address on his website, I'd be much more likely to 1) trust the file and more importantly 2) have some means of verifying who the uploader is and that they uploaded it themselves. Worst case scenario, the zip file is full of cat pictures and Trent Reznor got some bitcoins, not some random scammer.
Lastly, having an uploader account would allow for better customer support between the sellers and the buyers. Sellers should/could be able to see a log of transaction IDs of when their uploads were purchased. If somebody wants a refund or disputes a download, the seller can verify that they actually brought the product without revealing who the buyer was.
Just my $0.02
|
|
|
|
|
yPool makes me sad because of my luck, so I've gone back to solo mining.
I've mined about 18 XPM from yPool, but in that time I minted SIX BLOCKS. Had I been mining solo, I would have walked out with 60+ XPM.
So yeah, I'm sticking with solo mining + VPS.
Besides, you can still pool mine with VPS if it comes down to it.
|
|
|
|
|
Oh for shit's sake, put away your pitchforks and get off your high horses.
This amount of kicking and screaming contributes nothing.
If you were scammed and mtrlt never comes back, just cut your losses and move on. You won't be getting your coins back.
If mtrlt does release a beta to everybody who donated, all of you personally owe him an apology.
Bitching and moaning contributes to neither of these ends, so they should be put to a stop.
|
|
|
|
|
Will any of the source code be posted? A bit of transparency when coins are changing hands is always a good thing.
|
|
|
|
|
Show Posts
