Search content
Sort by
Showing 20 of 41 results by ejhuff
Re: MAXCOIN LOTTERY NOW ON - WIN UP TO AN AMAZING 7000 MAX!!!!!!!!!
I fear that way is open to abuse and leave it out of my hands for some smart hackers to manipulate one way or another. How about we all get Max Keiser to draw the lottery on his show, THAT would be awesome 
There are quite a few bitcoin gambling sites, starting with Satoshi Dice, that use this method. The hashcode of any specific future block is definitely random. There is definitely no way for a hacker to control it, and everyone can agree on what the hashcode is after the block is confirmed.
However, on reflection, I think it would be simpler to use specific block numbers. Then I can give a link to the block explorer page with the hash code, as follows:
The winning lottery ticket numbers will be calculated using the total number N of tickets sold, and the confirmed hash code H of MAXcoin hashchain block number 106520, obtained after block number 106620 has been found (100 confirmations).
That is, once the the cryptoexplore search for block 106620 returns a block rather than
Search Results For "106620"
No Result Found
then H will be the hash value given at cryptoexplore's page for block 106520. This value may also be found using the MAXcoind or MAXcoin-qt client, or using webcoin (dead link) or maxchain.info.For example, no one can dispute these facts with a straight face, and everyone can easily check them (click the link):
The hash of block 50000 is 00000000000059b7b1670117eeb04f472036c073f275cd50decce15d3894c8f5 in hex.
The decimal value of that hash is 144170545449846795252878978589069370515757698399706647721462005.
You can calculate and check that decimal value using this arbitrary precision hex to decimal to hex converter.
If N is 10000, you can compute the winning ticket numbers in your head given the decimal value of the hash.
First prize would go to ticket 2005, second prize to ticket 2146, and third prize to ticket 6477. Note: the 12 least significant digits are 647721462005.
The decimal value of the hash, and the winning ticket numbers for more difficult values of N, are easily calculated using the bc command line tool which comes standard on most every Linux:
Code:
$ echo 'ibase=16; 00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;' | bc
144170545449846795252878978589069370515757698399706647721462005
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=10000;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 2005
Second prize: 2146
Third prize: 6477
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=9999;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 9555
Second prize: 4693
Third prize: 2067
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=1000;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 5
Second prize: 462
Third prize: 721
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=997;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 72
Second prize: 550
Third prize: 848
144170545449846795252878978589069370515757698399706647721462005
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=10000;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 2005
Second prize: 2146
Third prize: 6477
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=9999;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 9555
Second prize: 4693
Third prize: 2067
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=1000;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 5
Second prize: 462
Third prize: 721
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=997;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 72
Second prize: 550
Third prize: 848
Another place where the lottery operator is asking for unnecessary trust: The assignment of ticket numbers must occur in an automatic and indisputable manner, with no discretion on the part of the lottery operator. The best way to ensure this would have been to state ahead of time that any deposit transaction which is not for an integral number of MAXcoin would be returned. This can be fixed:
Starting March 1, all transactions must deliver an integral number of MAXcoin, or they will be returned.
The ticket numbers for earlier transactions will be published on March 2, and any disputes will be resolved before the drawing.
Subsequent ticket numbers will be assigned in the order the transactions are listed on the block explorer websites. (Experts should be consulted to be certain that this is the same as the order transactions occur in the actual block).
The lottery will close early enough so that the list of ticket numbers can be published before the drawing.
Regarding payout addresses:
Starting March 1, the payout address will be the first sending address in the transaction.
Users of online wallets should send a small amount to the lottery address, and verify that they receive the refund to their online account. If they don't, they would be well advised to switch to a different wallet, or better, to run the standard wallet software on their PC.
If some vandal tries to DOS the lottery by sending lots of small amounts, the promise to return them is void. Users should check the lottery address before sending their test amount to be sure this is not happening.
See also my earlier posting, which used blockchain timestamps instead of specific block numbers.
I fear that way is open to abuse and leave it out of my hands for some smart hackers to manipulate one way or another. How about we all get Max Keiser to draw the lottery on his show, THAT would be awesome
There are quite a few bitcoin gambling sites, starting with Satoshi Dice, that use this method. The hashcode of any specific future block is definitely random. There is definitely no way for a hacker to control it, and everyone can agree on what the hashcode is after the block is confirmed.
However, on reflection, I think it would be simpler to use specific block numbers. Then I can give a link to the block explorer page with the hash code, as follows:
The winning lottery ticket numbers will be calculated using the total number N of tickets sold, and the confirmed hash code H of MAXcoin hashchain block number 106520, obtained after block number 106620 has been found (100 confirmations).
That is, once the the cryptoexplore search for block 106620 returns a block rather than
Search Results For "106620"
No Result Found
then H will be the hash value given at cryptoexplore's page for block 106520. This value may also be found using the MAXcoind or MAXcoin-qt client, or using webcoin (dead link) or maxchain.info.For example, no one can dispute these facts with a straight face, and everyone can easily check them (click the link):
The hash of block 50000 is 00000000000059b7b1670117eeb04f472036c073f275cd50decce15d3894c8f5 in hex.
The decimal value of that hash is 144170545449846795252878978589069370515757698399706647721462005.
You can calculate and check that decimal value using this arbitrary precision hex to decimal to hex converter.
If N is 10000, you can compute the winning ticket numbers in your head given the decimal value of the hash.
First prize would go to ticket 2005, second prize to ticket 2146, and third prize to ticket 6477. Note: the 12 least significant digits are 647721462005.
The decimal value of the hash, and the winning ticket numbers for more difficult values of N, are easily calculated using the bc command line tool which comes standard on most every Linux:
Code:
$ echo 'ibase=16; 00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;' | bc
144170545449846795252878978589069370515757698399706647721462005
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=10000;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 2005
Second prize: 2146
Third prize: 6477
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=9999;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 9555
Second prize: 4693
Third prize: 2067
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=1000;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 5
Second prize: 462
Third prize: 721
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=997;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 72
Second prize: 550
Third prize: 848
144170545449846795252878978589069370515757698399706647721462005
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=10000;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 2005
Second prize: 2146
Third prize: 6477
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=9999;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 9555
Second prize: 4693
Third prize: 2067
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=1000;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 5
Second prize: 462
Third prize: 721
$ echo 'ibase=16;
> h=00000000000059B7B1670117EEB04F472036C073F275CD50DECCE15D3894C8F5;
> ibase=0A;
> n=997;
> print "first prize: ", h%n, "\nSecond prize: ", (h/n)%n, "\nThird prize: ", ((h/n)/n)%n, "\n"' | bc
first prize: 72
Second prize: 550
Third prize: 848
Another place where the lottery operator is asking for unnecessary trust: The assignment of ticket numbers must occur in an automatic and indisputable manner, with no discretion on the part of the lottery operator. The best way to ensure this would have been to state ahead of time that any deposit transaction which is not for an integral number of MAXcoin would be returned. This can be fixed:
Starting March 1, all transactions must deliver an integral number of MAXcoin, or they will be returned.
The ticket numbers for earlier transactions will be published on March 2, and any disputes will be resolved before the drawing.
Subsequent ticket numbers will be assigned in the order the transactions are listed on the block explorer websites. (Experts should be consulted to be certain that this is the same as the order transactions occur in the actual block).
The lottery will close early enough so that the list of ticket numbers can be published before the drawing.
Regarding payout addresses:
Starting March 1, the payout address will be the first sending address in the transaction.
Users of online wallets should send a small amount to the lottery address, and verify that they receive the refund to their online account. If they don't, they would be well advised to switch to a different wallet, or better, to run the standard wallet software on their PC.
If some vandal tries to DOS the lottery by sending lots of small amounts, the promise to return them is void. Users should check the lottery address before sending their test amount to be sure this is not happening.
As of 2014-02-24 01:00 UTC, 59 MAX have been deposited into the lottery payment address.
Sr. Member subSTRATA has questioned whether or not this is a trustworthy lottery. (Well, actually he called it a "SCAM", presumably based on the fact that the sponsor is unnecessarily asking us to trust him to conduct the random drawing. He pointed out that the hash of a future MAXcoin block is a good way to conduct a random drawing.)
Lottery sponsor and Jr. Member zaloultra ignored the suggestion for using the hash of a future block, and replied with "calling it a scam is a bit over the top."
subSTRATA judged, based on the fact that zaloultra ignored the suggestion, that zaloultra is not interested in making the lottery more transparent. He concludes that this makes it a "confirmed scam."
zaloultra again ignores the substance of the complaint and accuses subSTRATA of "posting lies and untruthful bullshit...."
Subsequent posting degenerate further.
I am sorry but I must agree with subSTRATA, unless zaloultra agrees to the following method of choosing winners, possibly with justified modifications. This does not change the terms of the lottery, since previously, the method was up to zaloultra, and the drawing date in case the lottery sold out early was ambiguous (the conjunction was "or," not "unless").
In particular, if zaloultra will enlarge upon the specifications as follows, I will agree that this lottery is not a scam. If he insists on using his own method of choosing the winning ticket numbers, this will confirm subSTRATA's judgment, and this lottery will definitely be a "confirmed scam," and I will endeavor to have his trust set negative so his postings are flagged in red with "trade with caution."
The winning lottery ticket numbers will be calculated using the total number N of tickets sold, and the hash code H of the first confirmed MAXcoin blockchain block with timestamp > 1394899200 (2014-03-15 16:00:00 UTC). Such a block was scheduled (assuming one block every 30 seconds) to occur in the vicinity of blockchain height 106520, but of course, blocks are not found at exact 30 second intervals. 106520 is (1394913600-1391717999)/30. 1391717999 is the timestamp of MAXcoin block 1.
The lottery will close for payments after timestamp 1394841600 (2014-03-15 00:00:00 UTC), with refunds for late payments before timestamp 1394870400 (2014-03-15 00:00:00 UTC). (That is to say, payments received in MAXcoin blockchain blocks with 1394841600 < timestamp < 1394870400 will be refunded. Subsequent payments are forfeit).
The first prize ticket number is calculated by taking the remainder after dividing the hash code H by the number of tickets N.
The second prize ticket number comes from the remainder after dividing the quotient from the first prize division, H ÷ N, by the number of tickets N.
The third prize ticket number comes from the remainder after dividing the quotient from the second prize division, (H ÷ N) ÷ N, by the number of tickets N.
In the unlikely event that two or all three prizes are won by the same ticket, the lucky winner is the lucky winner!
All payments received after the balance at the lottery payment address exceeds 10,000 MAX will be refunded, so long as the payment arrives in a MAXcoin blockchain block with timestamp < 1394870400.
Ticket numbers will be assigned starting with zero, in the order that deposit transactions were received, as shown on the MAXcoin blockchain, transcribed for example, at cryptoexplore.com. Thus:
In cases where multiple sending addresses were used, such as tickets 0010 and 0011, the owner must specify a payout address.
Payment to winning tickets will be sent back to the sending address, or to a payment address specified on the lottery thread.
Payment to an address different from the sending address is offered because some online wallets cannot credit payments to their sending address to the correct account holder. In the case of forged postings, messages signed with the sending private key take precedence. (Arbitrary messages can be signed using the standard MAXcoin client). If the private key is not available because only the online wallet knows it, ask for help from senior members of the community, or ask customer service at your wallet company to prepare a signed message. Payout to a disputed payment address will be delayed until the dispute is resolved.
Sr. Member subSTRATA has questioned whether or not this is a trustworthy lottery. (Well, actually he called it a "SCAM", presumably based on the fact that the sponsor is unnecessarily asking us to trust him to conduct the random drawing. He pointed out that the hash of a future MAXcoin block is a good way to conduct a random drawing.)
Lottery sponsor and Jr. Member zaloultra ignored the suggestion for using the hash of a future block, and replied with "calling it a scam is a bit over the top."
subSTRATA judged, based on the fact that zaloultra ignored the suggestion, that zaloultra is not interested in making the lottery more transparent. He concludes that this makes it a "confirmed scam."
zaloultra again ignores the substance of the complaint and accuses subSTRATA of "posting lies and untruthful bullshit...."
Subsequent posting degenerate further.
I am sorry but I must agree with subSTRATA, unless zaloultra agrees to the following method of choosing winners, possibly with justified modifications. This does not change the terms of the lottery, since previously, the method was up to zaloultra, and the drawing date in case the lottery sold out early was ambiguous (the conjunction was "or," not "unless").
In particular, if zaloultra will enlarge upon the specifications as follows, I will agree that this lottery is not a scam. If he insists on using his own method of choosing the winning ticket numbers, this will confirm subSTRATA's judgment, and this lottery will definitely be a "confirmed scam," and I will endeavor to have his trust set negative so his postings are flagged in red with "trade with caution."
The winning lottery ticket numbers will be calculated using the total number N of tickets sold, and the hash code H of the first confirmed MAXcoin blockchain block with timestamp > 1394899200 (2014-03-15 16:00:00 UTC). Such a block was scheduled (assuming one block every 30 seconds) to occur in the vicinity of blockchain height 106520, but of course, blocks are not found at exact 30 second intervals. 106520 is (1394913600-1391717999)/30. 1391717999 is the timestamp of MAXcoin block 1.
The lottery will close for payments after timestamp 1394841600 (2014-03-15 00:00:00 UTC), with refunds for late payments before timestamp 1394870400 (2014-03-15 00:00:00 UTC). (That is to say, payments received in MAXcoin blockchain blocks with 1394841600 < timestamp < 1394870400 will be refunded. Subsequent payments are forfeit).
The first prize ticket number is calculated by taking the remainder after dividing the hash code H by the number of tickets N.
The second prize ticket number comes from the remainder after dividing the quotient from the first prize division, H ÷ N, by the number of tickets N.
The third prize ticket number comes from the remainder after dividing the quotient from the second prize division, (H ÷ N) ÷ N, by the number of tickets N.
In the unlikely event that two or all three prizes are won by the same ticket, the lucky winner is the lucky winner!
All payments received after the balance at the lottery payment address exceeds 10,000 MAX will be refunded, so long as the payment arrives in a MAXcoin blockchain block with timestamp < 1394870400.
Ticket numbers will be assigned starting with zero, in the order that deposit transactions were received, as shown on the MAXcoin blockchain, transcribed for example, at cryptoexplore.com. Thus:
Code:
TKT# Sending address
0000 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0001 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0002 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0003 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0004 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0005 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0006 mMRTZtXwSQSfFrnpgfyoqc1bXE7xpGsku6
0007 mQEHKNh91js5t5Y9EfXqGXCscdzSjx6Q4g
0008 mQEHKNh91js5t5Y9EfXqGXCscdzSjx6Q4g
0009 mQEHKNh91js5t5Y9EfXqGXCscdzSjx6Q4g
0010 mV3aX3QEgRmh1vZywKu9h1RhMW63cxVADQ
and mRoEyeproB6hX2DY8Bfng8rfnaXk2ppVLm
0011 mV3aX3QEgRmh1vZywKu9h1RhMW63cxVADQ
and mRoEyeproB6hX2DY8Bfng8rfnaXk2ppVLm
... etc. ...
0000 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0001 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0002 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0003 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0004 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0005 mJ7sEL2hswp5EaXbv4a6FLcmoPA7TSUtDK
0006 mMRTZtXwSQSfFrnpgfyoqc1bXE7xpGsku6
0007 mQEHKNh91js5t5Y9EfXqGXCscdzSjx6Q4g
0008 mQEHKNh91js5t5Y9EfXqGXCscdzSjx6Q4g
0009 mQEHKNh91js5t5Y9EfXqGXCscdzSjx6Q4g
0010 mV3aX3QEgRmh1vZywKu9h1RhMW63cxVADQ
and mRoEyeproB6hX2DY8Bfng8rfnaXk2ppVLm
0011 mV3aX3QEgRmh1vZywKu9h1RhMW63cxVADQ
and mRoEyeproB6hX2DY8Bfng8rfnaXk2ppVLm
... etc. ...
In cases where multiple sending addresses were used, such as tickets 0010 and 0011, the owner must specify a payout address.
Payment to winning tickets will be sent back to the sending address, or to a payment address specified on the lottery thread.
Payment to an address different from the sending address is offered because some online wallets cannot credit payments to their sending address to the correct account holder. In the case of forged postings, messages signed with the sending private key take precedence. (Arbitrary messages can be signed using the standard MAXcoin client). If the private key is not available because only the online wallet knows it, ask for help from senior members of the community, or ask customer service at your wallet company to prepare a signed message. Payout to a disputed payment address will be delayed until the dispute is resolved.
Code:
Note that blockchain timestamps are represented in Unix/Linux internal date format, i.e., seconds since 1970-01-01 UTC.
maxchain.info displays them in this format. max.cryptoexplore.com seems to display them as date and local time in
timezone UTC-0600.
$ date --date="2014-03-15 UTC" +%s
1394841600
$ date --date="2014-03-15 08:00:00 UTC" +%s
1394870400
$ date --date="2014-03-15 16:00:00 UTC" +%s
1394899200
Just to be complete, we specify with great precision what the % operator means for operands greater or equal to zero.
These calculations are done using infinite precision positive integer arithmetic.
% denotes the remainder after integer division, 1 % 2 = 1.
x % y is always less than y.
÷ denotes integer division, 1 ÷ 2 = 0.
y * (x ÷ y) + (x % y) is always equal to x.
(x % y) is therefore always equal to x - y * (x ÷ y).
1st prize goes to ticket number (H % N).
2nd prize goes to ticket number ((H ÷ N) % N).
3rd prize goes to ticket number (((H ÷ N) ÷ N) % N).
maxchain.info displays them in this format. max.cryptoexplore.com seems to display them as date and local time in
timezone UTC-0600.
$ date --date="2014-03-15 UTC" +%s
1394841600
$ date --date="2014-03-15 08:00:00 UTC" +%s
1394870400
$ date --date="2014-03-15 16:00:00 UTC" +%s
1394899200
Just to be complete, we specify with great precision what the % operator means for operands greater or equal to zero.
These calculations are done using infinite precision positive integer arithmetic.
% denotes the remainder after integer division, 1 % 2 = 1.
x % y is always less than y.
÷ denotes integer division, 1 ÷ 2 = 0.
y * (x ÷ y) + (x % y) is always equal to x.
(x % y) is therefore always equal to x - y * (x ÷ y).
1st prize goes to ticket number (H % N).
2nd prize goes to ticket number ((H ÷ N) % N).
3rd prize goes to ticket number (((H ÷ N) ÷ N) % N).
Any changes to 0.5.4?
--------------------------------------- EDIT notes --------------------
This post is becoming more about getting the Asus Radeon R9 290X running on Fedora 19 than just about vertminer-gpu 0.5.4.pre2. It will also provide material for the vertcoin.org gpu-miner-build-howto.
I will be fixing some confusion between ADL-SDK and AMD-APP-SDK below, and adding more details about what it took to get an Asus Radeon R9 290X running on Fedora 19. But I can't get it all done today
so I want to post the incomplete revisions to avoid losing them and to avoid leaving incorrect information online.
ICD files:
The OpenCL ICD (Installable Client Driver) is a means of allowing multiple OpenCL implementations to co-exist and applications to select between them at runtime. The files seem to give the names of the shared library files for the AMD-APP-SDK.
The vertcoin.org gpu-miner-build-howto suggests editing these files to add full path to the library. I don't think that is what the designers of ICD expected, but apparently it works. AMD expects to use LD_LIBRARY_PATH to specify where to look for the named libraries...
-------------------------------------- end EDIT notes ---------------
I was just following the build instructions for linux, which specified downloading the latest git version. Then I tried to follow sample configurations from this thread, but the meaning of the --scrypt option has changed.
vertminer-gpu 0.5.4 adds support for ADL (AMD Display Library), version 6, among other things.
Code:
2014-02-12 20:54 Bufius o [master] [origin/HEAD] [origin/master] fixed unexpected build issues
2014-02-12 20:22 Bufius o fixed wrong variable type in ocl.c
2014-02-12 20:08 Bufius o miner prepared for normal scrypt + nfactor scrypt
2014-02-08 22:10 Bufius o remove unneeded files
2014-02-08 22:08 Bufius o autogeneration
2014-02-08 21:35 Bufius o and again the adl stuff...
2014-02-08 21:27 Bufius o correct adl_functions.h
2014-02-08 21:24 Bufius o Revert "include corrrect adl_functions.h"
2014-02-08 21:21 Bufius o include corrrect adl_functions.h
2014-02-08 21:05 Bufius o ADL6 support
2014-02-03 18:02 Bufius o [origin/0.5.3] bump to 0.5.3
2014-02-12 20:22 Bufius o fixed wrong variable type in ocl.c
2014-02-12 20:08 Bufius o miner prepared for normal scrypt + nfactor scrypt
2014-02-08 22:10 Bufius o remove unneeded files
2014-02-08 22:08 Bufius o autogeneration
2014-02-08 21:35 Bufius o and again the adl stuff...
2014-02-08 21:27 Bufius o correct adl_functions.h
2014-02-08 21:24 Bufius o Revert "include corrrect adl_functions.h"
2014-02-08 21:21 Bufius o include corrrect adl_functions.h
2014-02-08 21:05 Bufius o ADL6 support
2014-02-03 18:02 Bufius o [origin/0.5.3] bump to 0.5.3
You could see all the gory details at the github site, if only you already knew how to use github... (I just learned yesterday, and can't explain it).
I have an Asus R9 290X and I installed catalyst 14.1 beta for linux, (with some difficulty because the 14.1beta Fedora package is not available yet).
So I think I needed ADL6. If so, I also needed vertminer-gpu 0.5.4.
(Someone please draw the attention of the maintainer of http://vertcoin.org/gpu-miner-build-howto.html to these comments about the problems with the AMD-APP-SDK installer).
I highly disrecommend the AMD installer for the AMD-APP-SDK. It puts global definition of LD_LIBRARY_PATH into /etc/profile, which impacts load time of everything on the system forever more unless you erase it. See http://www.cc.dtu.dk/?page_id=304, "LD_LIBRARY_PATH or: How to get yourself into trouble!"
Also, if you did happen to have "export LD_LIBRARY_PATH and some other stuff on the same line" in /etc/profile, it erases it the other stuff without notice, replacing it with just export LD_LIBRARY_PATH.
The AMD installer also does nice things like executing (as root) rm -rf $dirname, when it is not immediately obvious that dirname cannot be /. So I don't trust it. Also it is written, for no good reason, in perl. The person who wrote it is obviously not an experienced sysadmin.
To install AMD-APP-SDK 2.9, I just untarred it: mkdir AMD-APP-SDK; cd AMD-APP-SDK; tar zxvf AMD-APP-SDK-v2.9-lnx64.tgz.
Code:
-rw-rw-r-- cas/cas 150269240 2013-10-30 06:52 AMD-APP-SDK-v2.9-RC-lnx64.tgz
-rwxr-xr-x cas/cas 11466 2013-10-30 06:40 default-install_lnx_64.pl
-rwxr-xr-x cas/cas 226 2013-10-30 06:40 icd-registration.tgz
-rwxrwxrwx cas/cas 289 2013-10-30 06:40 Install-AMD-APP.sh
-rwxr-xr-x cas/cas 6678 2013-10-30 06:40 ReadMe.txt
Note the inappropriate permissions, and the user/group not being root:root. I fixed them with chown root:root * and chmod go-w * and chmod a-x *.tgz *.txt-rwxr-xr-x cas/cas 11466 2013-10-30 06:40 default-install_lnx_64.pl
-rwxr-xr-x cas/cas 226 2013-10-30 06:40 icd-registration.tgz
-rwxrwxrwx cas/cas 289 2013-10-30 06:40 Install-AMD-APP.sh
-rwxr-xr-x cas/cas 6678 2013-10-30 06:40 ReadMe.txt
(Actually, I should have used the tar option to ignore the specified user/group, since this is always happening when root untars something.)
icd-registration.tgz untars to
Code:
drwxr-xr-x cas/cas 0 2013-06-10 01:33 etc/
drwxr-xr-x cas/cas 0 2013-06-10 01:33 etc/OpenCL/
drwxr-xr-x cas/cas 0 2013-06-10 01:34 etc/OpenCL/vendors/
-rwxr-xr-x cas/cas 15 2013-06-10 01:34 etc/OpenCL/vendors/amdocl64.icd
-rwxr-xr-x cas/cas 15 2013-06-10 01:33 etc/OpenCL/vendors/amdocl32.icd
drwxr-xr-x cas/cas 0 2013-06-10 01:33 etc/OpenCL/
drwxr-xr-x cas/cas 0 2013-06-10 01:34 etc/OpenCL/vendors/
-rwxr-xr-x cas/cas 15 2013-06-10 01:34 etc/OpenCL/vendors/amdocl64.icd
-rwxr-xr-x cas/cas 15 2013-06-10 01:33 etc/OpenCL/vendors/amdocl32.icd
I put those files into /etc, correcting the ownership and removing the execute permission from the .icd files.
Code:
$ find /etc/OpenCL -ls
1493085 0 drwxr-xr-x 1 root root 14 Feb 18 22:43 /etc/OpenCL
1493086 0 drwxr-xr-x 1 root root 48 Feb 19 08:58 /etc/OpenCL/vendors
1609357 4 -rw-r--r-- 1 root root 15 Jun 10 2013 /etc/OpenCL/vendors/amdocl64.icd
1613003 4 -rw-r--r-- 1 root root 15 Jun 10 2013 /etc/OpenCL/vendors/amdocl32.icd
$ head /etc/OpenCL/vendors/amdocl*
==> /etc/OpenCL/vendors/amdocl32.icd <==
libamdocl32.so
==> /etc/OpenCL/vendors/amdocl64.icd <==
libamdocl64.so
1493085 0 drwxr-xr-x 1 root root 14 Feb 18 22:43 /etc/OpenCL
1493086 0 drwxr-xr-x 1 root root 48 Feb 19 08:58 /etc/OpenCL/vendors
1609357 4 -rw-r--r-- 1 root root 15 Jun 10 2013 /etc/OpenCL/vendors/amdocl64.icd
1613003 4 -rw-r--r-- 1 root root 15 Jun 10 2013 /etc/OpenCL/vendors/amdocl32.icd
$ head /etc/OpenCL/vendors/amdocl*
==> /etc/OpenCL/vendors/amdocl32.icd <==
libamdocl32.so
==> /etc/OpenCL/vendors/amdocl64.icd <==
libamdocl64.so
The I untarred AMD-APP-SDK-v2.9-RC-lnx64.tgz, which happens to produce a single directory named AMD-APP-SDK-v2.9-RC-lnx64. I corrected the ownership, removed group other write permissions, moved or removed any existing /opt/AMDAPP directory, and moved AMD-APP-SDK-v2.9-RC-lnx64 to /opt/AMDAPP.
Then, instead of using LD_LIBRARY_PATH forever more, I just told the build process where the libraries are going to be:
Code:
CFLAGS="-g -O2 -Wall" LDFLAGS="-L/opt/AMDAPP/lib/x86_64/" ./configure --prefix=$HOME
You can also avoid doing any of this as root if you take the hint from http://devgurus.amd.com/message/1299447 and use OPENCL_VENDOR_PATH to give the path to the data from icd-registration.tgz, and use the configure time LDFLAGS variable to give the path to where you put the contents of AMD-APP-SDK-v2.9-RC-lnx64.tgz. (Just don't move it afterward or you need to rebuild or use LD_LIBRARY_PATH).
--
VTC: VefY8KPvoN3xrdj9Gpr8Pzo6YgTRCsqkGt
BTC: 12XQ7bpdHamJV61KgQ8p5tjLSUFWv7ZCAx
I compiled HEAD branch of https://github.com/Bufius/vertminer-gpu.git on Fedora 19, but didn't look at the NEWS file, so didn't see that now the --scrypt option means litecoin scrypt, and I was getting 100% rejects. As soon as I changed the option to --nscrypt, I started getting 100% accepts.
I doubt there are any precompiled versions. I don't run windows.
diff --git a/NEWS b/NEWS
index b1b30a5..5c935d3 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,10 @@
+Version 0.5.4pre2 - 12 February 2014
+- include more ADL6 stuff
+- prepared miner to mine scrypt and nfactor scrypt
+ --> option --scrypt => normal scrypt
+ --> option --nscrypt => nfactor scrypt (e.g. vertcoin)
+
+
--- a/README
+++ b/README
@@ -192,7 +192,8 @@ Options for both config file and command line:
--scan-time|-s Upper bound on time spent scanning current work, in seconds (default: 60)
--sched-start Set a time of day in HH:MM to start mining (a once off without a stop time)
--sched-stop Set a time of day in HH:MM to stop mining (will quit without a start time)
---scrypt-vert Use the scrypt algorithm for mining (vertcoin only)
+--scrypt Use the scrypt algorithm for mining (NORMAL scrypt coins only)
+--nscrypt Use the adaptive nfactorscrypt algorithm for mining (NFACTOR based scrypt coins only)
--sharelog Append share log to file
--shares Quit after mining N shares (default: unlimited)
--socks-proxy Set socks4 proxy (host:port) for all pools without a proxy specified
I doubt there are any precompiled versions. I don't run windows.
diff --git a/NEWS b/NEWS
index b1b30a5..5c935d3 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,10 @@
+Version 0.5.4pre2 - 12 February 2014
+- include more ADL6 stuff
+- prepared miner to mine scrypt and nfactor scrypt
+ --> option --scrypt => normal scrypt
+ --> option --nscrypt => nfactor scrypt (e.g. vertcoin)
+
+
--- a/README
+++ b/README
@@ -192,7 +192,8 @@ Options for both config file and command line:
--scan-time|-s Upper bound on time spent scanning current work, in seconds (default: 60)
--sched-start Set a time of day in HH:MM to start mining (a once off without a stop time)
--sched-stop Set a time of day in HH:MM to stop mining (will quit without a start time)
---scrypt-vert Use the scrypt algorithm for mining (vertcoin only)
+--scrypt Use the scrypt algorithm for mining (NORMAL scrypt coins only)
+--nscrypt Use the adaptive nfactorscrypt algorithm for mining (NFACTOR based scrypt coins only)
--sharelog Append share log to file
--shares Quit after mining N shares (default: unlimited)
--socks-proxy Set socks4 proxy (host:port) for all pools without a proxy specified
Try http://max.hashfaster.com/index.php?page=statistics&action=pool
I made an account before launch but they were always "working on multiple issues" yesterday. Now they say they are up but no-one is mining there. Guess I'll try it.
I made an account before launch but they were always "working on multiple issues" yesterday. Now they say they are up but no-one is mining there. Guess I'll try it.
Hashfaster is still working on stratum, so no go yet.
Quote
Duh... I though I saw "Wallet up and running, mining is working on Stratum."
Try http://max.hashfaster.com/index.php?page=statistics&action=pool
I made an account before launch but they were always "working on multiple issues" yesterday. Now they say they are up but no-one is mining there. Guess I'll try it.
I made an account before launch but they were always "working on multiple issues" yesterday. Now they say they are up but no-one is mining there. Guess I'll try it.
[2014-02-07 09:49:58] accepted: 0/69 (0.00%), 5211 khash/s (booooo)
Anyone know how to debug this? max.1gh.com, and the setup did work early on when they weren't getting any blocks, I have 0.0988 MAX
Anyone know how to debug this? max.1gh.com, and the setup did work early on when they weren't getting any blocks, I have 0.0988 MAX
Code:
[2014-02-06 18:08:03] accepted: 1/1 (100.00%), 5287 khash/s (yay!!!) ...
[2014-02-06 18:25:03] accepted: 17/17 (100.00%), 5254 khash/s (yay!!!)
[2014-02-06 18:25:08] accepted: 17/18 (94.44%), 5044 khash/s (booooo)...
[2014-02-06 19:00:19] accepted: 40/41 (97.56%), 5219 khash/s (yay!!!)
[2014-02-06 19:03:46] accepted: 40/42 (95.24%), 4908 khash/s (booooo)...
[2014-02-06 19:09:27] accepted: 45/47 (95.74%), 4852 khash/s (yay!!!)
they still had no blocks so I went back to solo... Saw they got a block so I decided to try again.
[2014-02-06 20:58:49] accepted: 0/1 (0.00%), 5030 khash/s (booooo)
[2014-02-06 21:13:07] accepted: 0/9 (0.00%), 5151 khash/s (booooo)...
[2014-02-06 21:26:51] accepted: 0/24 (0.00%), 5144 khash/s (booooo)
[2014-02-06 21:27:07] accepted: 0/1 (0.00%), 5196 khash/s (booooo)
[2014-02-06 21:42:12] accepted: 0/6 (0.00%), 5032 khash/s (booooo)
went back to mining vertcoin... and went to sleep... try again this morning...
[2014-02-07 08:53:54] accepted: 0/1 (0.00%), 2284 khash/s (booooo)...
[2014-02-07 09:50:50] accepted: 0/70 (0.00%), 5067 khash/s (booooo)...
[2014-02-07 10:01:39] accepted: 0/75 (0.00%), 4847 khash/s (booooo)
[2014-02-06 18:25:03] accepted: 17/17 (100.00%), 5254 khash/s (yay!!!)
[2014-02-06 18:25:08] accepted: 17/18 (94.44%), 5044 khash/s (booooo)...
[2014-02-06 19:00:19] accepted: 40/41 (97.56%), 5219 khash/s (yay!!!)
[2014-02-06 19:03:46] accepted: 40/42 (95.24%), 4908 khash/s (booooo)...
[2014-02-06 19:09:27] accepted: 45/47 (95.74%), 4852 khash/s (yay!!!)
they still had no blocks so I went back to solo... Saw they got a block so I decided to try again.
[2014-02-06 20:58:49] accepted: 0/1 (0.00%), 5030 khash/s (booooo)
[2014-02-06 21:13:07] accepted: 0/9 (0.00%), 5151 khash/s (booooo)...
[2014-02-06 21:26:51] accepted: 0/24 (0.00%), 5144 khash/s (booooo)
[2014-02-06 21:27:07] accepted: 0/1 (0.00%), 5196 khash/s (booooo)
[2014-02-06 21:42:12] accepted: 0/6 (0.00%), 5032 khash/s (booooo)
went back to mining vertcoin... and went to sleep... try again this morning...
[2014-02-07 08:53:54] accepted: 0/1 (0.00%), 2284 khash/s (booooo)...
[2014-02-07 09:50:50] accepted: 0/70 (0.00%), 5067 khash/s (booooo)...
[2014-02-07 10:01:39] accepted: 0/75 (0.00%), 4847 khash/s (booooo)
Call it CPU coin. With GPU rate > 100Mh/s, CPU i7 can only mine 200Kh/s. What's hash rate now ? ~28Gh/s!!!
CPU miners are kicked off at launch.
CPU miners are kicked off at launch.
Well, I'm getting 3.5 Mh/s... still that is 3580221 / 32373766525 = 0.011059019 %
Or 1 chance in 9042.3933
Who has a pool working? hashfaster is still "working through problem after problem."
net 32,373,766,525
CPU i7 3,580,221
{
"blocks" : 348,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 240.21993127,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 3580221,
"networkhashps" : 32373766525,
"pooledtx" : 0,
"testnet" : false
}
Warning - while you were reading 19 new replies have been posted. You may wish to review your post.
Warning - while you were typing 84 new replies have been posted. You may wish to review your post.
Warning - while you were typing 80 new replies have been posted. You may wish to review your post.
Warning - while you were typing 52 new replies have been posted. You may wish to review your post.
Warning - while you were typing 10 new replies have been posted. You may wish to review your post.
Warning - while you were typing a new reply has been posted. You may wish to review your post.
Warning - while you were typing 4 new replies have been posted. You may wish to review your post.
Got it to compile! Thanks ernie-
Warning - while you were typing 84 new replies have been posted. You may wish to review your post.
Warning - while you were typing 80 new replies have been posted. You may wish to review your post.
Warning - while you were typing 52 new replies have been posted. You may wish to review your post.
Warning - while you were typing 10 new replies have been posted. You may wish to review your post.
Warning - while you were typing a new reply has been posted. You may wish to review your post.
Warning - while you were typing 4 new replies have been posted. You may wish to review your post.
Got it to compile! Thanks ernie-
cd cryptopp
make
problem solved.
make
problem solved.
Code:
% git clone https://github.com/Max-Coin/MaxCoin.git
% cd MaxCoin/src
% chmod a+x src/leveldb/build_detect_platform
% cd src
% vi makefile.unix
% cd cryptopp
% make
% cd ..
% git diff
diff --git a/src/leveldb/build_detect_platform b/src/leveldb/build_detect_platform
old mode 100644
new mode 100755
diff --git a/src/makefile.unix b/src/makefile.unix
index 39e0b09..ebe6e14 100644
--- a/src/makefile.unix
+++ b/src/makefile.unix
@@ -51,7 +51,7 @@ ifndef USE_UPNP
override USE_UPNP = -
endif
ifneq (${USE_UPNP}, -)
- LIBS += /usr/lib/libminiupnpc.a
+ LIBS += /usr/lib64/libminiupnpc.so
DEFS += -DUSE_UPNP=$(USE_UPNP)
endif
% make -f makefile.unix
% ./maxcoind --help
MaxCoin version v0.8.9.0-g8c5e74e-beta
...
% cd MaxCoin/src
% chmod a+x src/leveldb/build_detect_platform
% cd src
% vi makefile.unix
% cd cryptopp
% make
% cd ..
% git diff
diff --git a/src/leveldb/build_detect_platform b/src/leveldb/build_detect_platform
old mode 100644
new mode 100755
diff --git a/src/makefile.unix b/src/makefile.unix
index 39e0b09..ebe6e14 100644
--- a/src/makefile.unix
+++ b/src/makefile.unix
@@ -51,7 +51,7 @@ ifndef USE_UPNP
override USE_UPNP = -
endif
ifneq (${USE_UPNP}, -)
- LIBS += /usr/lib/libminiupnpc.a
+ LIBS += /usr/lib64/libminiupnpc.so
DEFS += -DUSE_UPNP=$(USE_UPNP)
endif
% make -f makefile.unix
% ./maxcoind --help
MaxCoin version v0.8.9.0-g8c5e74e-beta
...
linux build in progress:
Warning - while you were reading 19 new replies have been posted. You may wish to review your post.
Warning - while you were typing 24 new replies have been posted. You may wish to review your post.
Warning - while you were typing 3 new replies have been posted. You may wish to review your post.
Warning - while you were typing a new reply has been posted. You may wish to review your post.
Code:
% git clone https://github.com/Max-Coin/MaxCoin.git
% cd MaxCoin/src
% make -f makefile.unix
/bin/sh: ./build_detect_platform: Permission denied
% find . -name build_det* -ls
% chmod a+x $(find . -name build_det*)
% find . -name build_det* -ls
% make -f makefile.unix
alert.cpp:260:1: fatal error: opening dependency file obj/alert.d: No such file or directory
% mkdir obj
% make -f makefile.unix
g++: error: cryptopp/libcryptopp.a: No such file or directory
g++: error: /usr/lib/libminiupnpc.a: No such file or directory
% locate libminiupnpc
/usr/lib64/libminiupnpc.so
/usr/lib64/libminiupnpc.so.8
% locate libcryptopp
/usr/lib64/libcryptopp.so.6
/usr/lib64/libcryptopp.so.6.0.0
% cd MaxCoin/src
% make -f makefile.unix
/bin/sh: ./build_detect_platform: Permission denied
% find . -name build_det* -ls
% chmod a+x $(find . -name build_det*)
% find . -name build_det* -ls
% make -f makefile.unix
alert.cpp:260:1: fatal error: opening dependency file obj/alert.d: No such file or directory
% mkdir obj
% make -f makefile.unix
g++: error: cryptopp/libcryptopp.a: No such file or directory
g++: error: /usr/lib/libminiupnpc.a: No such file or directory
% locate libminiupnpc
/usr/lib64/libminiupnpc.so
/usr/lib64/libminiupnpc.so.8
% locate libcryptopp
/usr/lib64/libcryptopp.so.6
/usr/lib64/libcryptopp.so.6.0.0
Warning - while you were reading 19 new replies have been posted. You may wish to review your post.
Warning - while you were typing 24 new replies have been posted. You may wish to review your post.
Warning - while you were typing 3 new replies have been posted. You may wish to review your post.
Warning - while you were typing a new reply has been posted. You may wish to review your post.
linux build in progress:
git clone https://github.com/Max-Coin/MaxCoin.git
cd MaxCoin/src
make -f makefile.unix
/bin/sh: ./build_detect_platform: Permission denied
find . -name build_det* -ls
chmod a+x $(find . -name build_det*)
find . -name build_det* -ls
make -f makefile.unix
alert.cpp:260:1: fatal error: opening dependency file obj/alert.d: No such file or directory
mkdir obj
make -f makefile.unix
g++: error: cryptopp/libcryptopp.a: No such file or directory
g++: error: /usr/lib/libminiupnpc.a: No such file or directory
git clone https://github.com/Max-Coin/MaxCoin.git
cd MaxCoin/src
make -f makefile.unix
/bin/sh: ./build_detect_platform: Permission denied
find . -name build_det* -ls
chmod a+x $(find . -name build_det*)
find . -name build_det* -ls
make -f makefile.unix
alert.cpp:260:1: fatal error: opening dependency file obj/alert.d: No such file or directory
mkdir obj
make -f makefile.unix
g++: error: cryptopp/libcryptopp.a: No such file or directory
g++: error: /usr/lib/libminiupnpc.a: No such file or directory
What is the RPC port? How can you start mining without it?
+1Try looking here, maybe?
Quote
http://max.hashfaster.com/index.php?page=gettingstarted
3. Configure your miner.
Settings for Stratum (recommended):
STRATUM: stratum+tcp://stratum1.max.hashfaster.com
PORT: 4004
Username: Weblogin.Worker
Password: Worker Password
3. Configure your miner.
Settings for Stratum (recommended):
STRATUM: stratum+tcp://stratum1.max.hashfaster.com
PORT: 4004
Username: Weblogin.Worker
Password: Worker Password
Max Keiser says it's all his fault. (See also http://www.nasdaq.com/article/the-next-altcoin-to-hit-20-million-cm323873).
Quote
http://www.reddit.com/r/maxcoinproject/comments/1x4m4w/maxcoin_launch_official_statement/
We're postponing the launch of MaxCoin by 24 hours after today's events. The new launch time will be 7.30PM GMT Thursday, 24 hours after original launch.
To keep you guys in the loop, here's our thought process for this decision.
After we prepped our ANN for [Suspicious link removed] 7.30PM GMT launch the site crashed under heavy load for around 10 minutes. The MaxCoin site crashed simultaneously for a similar time. This happened a few more times before it came to our attention that a stable launch from BitcoinTalk would not be possible.
While preparing alternative options for launch (the launch channels will now be via Reddit, Twitter and MaxCoin.co.uk) one of our prepared pool operators withdrew their support claiming they were uncertain they would be able to support the load of miners.
We are uncomfortable launching without two stable pools, not to mention doing so in the midst of confusion between a last minute launch location switch and large traffic spikes. With these three issues combined, we have made the decision to delay the launch until this infrastructure is better established and the news is able to spread about the new sites to participate in the launch from.
Our apologies to everyone that this inconveniences, we're as disappointed as you, but feel this is the correct way to proceed under the circumstances. It is our hope that by postponing and making sure this is done properly we will achieve a more stable debut than by gritting our teeth and crossing our fingers through an already chaotic launch.
To avoid similar issues, we will be distributing the software from tomorrow morning (GMT) under password protected archives so it is possible to download these throughout the day, both via official site download and torrents, assuring everybody has access to the files in time for the launch. All guides will be available in advance and mining will begin upon password announcement.
The screenshots and claims of advance mining are of course fake, one reason we must move to more stable announce channels is to ensure everybody is able to have a fair chance to mine from the commence of the network.
Thanks for your patience, and sorry once again.
We're postponing the launch of MaxCoin by 24 hours after today's events. The new launch time will be 7.30PM GMT Thursday, 24 hours after original launch.
To keep you guys in the loop, here's our thought process for this decision.
After we prepped our ANN for [Suspicious link removed] 7.30PM GMT launch the site crashed under heavy load for around 10 minutes. The MaxCoin site crashed simultaneously for a similar time. This happened a few more times before it came to our attention that a stable launch from BitcoinTalk would not be possible.
While preparing alternative options for launch (the launch channels will now be via Reddit, Twitter and MaxCoin.co.uk) one of our prepared pool operators withdrew their support claiming they were uncertain they would be able to support the load of miners.
We are uncomfortable launching without two stable pools, not to mention doing so in the midst of confusion between a last minute launch location switch and large traffic spikes. With these three issues combined, we have made the decision to delay the launch until this infrastructure is better established and the news is able to spread about the new sites to participate in the launch from.
Our apologies to everyone that this inconveniences, we're as disappointed as you, but feel this is the correct way to proceed under the circumstances. It is our hope that by postponing and making sure this is done properly we will achieve a more stable debut than by gritting our teeth and crossing our fingers through an already chaotic launch.
To avoid similar issues, we will be distributing the software from tomorrow morning (GMT) under password protected archives so it is possible to download these throughout the day, both via official site download and torrents, assuring everybody has access to the files in time for the launch. All guides will be available in advance and mining will begin upon password announcement.
The screenshots and claims of advance mining are of course fake, one reason we must move to more stable announce channels is to ensure everybody is able to have a fair chance to mine from the commence of the network.
Thanks for your patience, and sorry once again.
Launch delayed, apparently because of [Suspicious link removed]ervers overloaded today (I saw 502 bad gateway many times earlier today).
Quote
http://www.reddit.com/r/maxcoinproject/comments/1x4cel/delay_official_730_pm_tomorrow/
After some issues arising from the huge traffic we will be delaying the launch of MaxCoin to 7.30PM GMT tomorrow
After some issues arising from the huge traffic we will be delaying the launch of MaxCoin to 7.30PM GMT tomorrow
If there was a guide for how to run a static-IP / VPS node, I might be willing to do it.
It's the same as running a local node. Just set ur IP in web.xml.
I've been looking all over for this little piece of information... It is not available on the wiki, or the OP, etc.
There is something on the wiki
http://www.thenxtwiki.org/wiki/How-To:CreatePublicNode
I havent checked to see how you nav to it from the wiki frontpage though, so you may have given us a littly job to do.
It's linked off the menu on the left-hand side, through "How To Guides". You can also use the search bar; in this case, "VPS" is a particularly useful search term.
Remind me not to compose replies in the browser window. This is the third time I am writing this (second rewrite) because of "Bad Gateway." I am replying on https://forums.nxtcrypto.org/viewtopic.php?f=15&t=738. If I ever get this to post, it was because I used the firefox "reload" button instead of the "back" button, and replied "yes" to the "resend info" question.
If there was a guide for how to run a static-IP / VPS node, I might be willing to do it.
It's the same as running a local node. Just set ur IP in web.xml.
I've been looking all over for this little piece of information... It is not available on the wiki, or the OP, etc.
Re: [NEM] NEM -New Economy Movement - No Envy Movement - Updates+Discussion thread
Regarding the copyright notice on NEM source code:
https://github.com/NxtEM/nem/blob/master/LICENSE.txt
vs. https://github.com/NxtEM/nem/blob/master/nxt_0.4.7e/MIT-license.txt
I believe it is necessary for the new file to read as follows:
https://github.com/NxtEM/nem/blob/master/LICENSE.txt
Code:
The MIT License (MIT)
Copyright (c) 2014 Jaguar0625
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), ...
Copyright (c) 2014 Jaguar0625
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), ...
vs. https://github.com/NxtEM/nem/blob/master/nxt_0.4.7e/MIT-license.txt
Code:
Copyright (c) 2013-2014 BCNext and the Nxt core developers.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), ...
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), ...
I believe it is necessary for the new file to read as follows:
Code:
The MIT License (MIT)
Copyright (c) 2013-2014 BCNext and the Nxt core developers.
Copyright (c) 2014 Jaguar0625
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), ...
Copyright (c) 2013-2014 BCNext and the Nxt core developers.
Copyright (c) 2014 Jaguar0625
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), ...
Re: [NEM] NEM -New Economy Movement - No Envy Movement - Updates+Discussion thread
So am I the only one who has associated the acronym POS with something other than proof of stake for decades???
No. And I thought the whole point of strong crypto was to make it impossible to forge blocks.