 Show Posts
|
|
Pages: « 1 [2] 3 4 5 6 »
|
|
the name Ethereum makes sense. Comes from latin Aether, Aetherum is just the "plural" of Aether, that means "heaven", "air", "sky", so it means, "many skies"... that's all Ethereum is about, endless possibilities, like many horizons, without a "set in stone" begin and end.
|
|
|
|
when you click the 'trash can' on the 'Active peers' list, it will go to the bottom of the 'Known peers' list with a orange icon, you need to click the trash can again to remove it completely. |
|
|
|
|
the client really must to have a built-in function to ignore nodes versions lower than it's own version. my version 0.6.1 still connects to some 4.9 nodes, wtf. I have to manually go removing them and blacklisting them
|
|
|
|
|
what error is it giving you? are you using the refactor branch?
|
|
|
|
|
my version works, and I'm also using it on ypool
|
|
|
|
|
great, NXT client isn't sending any money, it says "money is sent" but nothing goes out... what gives?
|
|
|
|
|
actually, it seems that the Makefile is broken, since the miner uses mpir (that's a "fork" from GMP lib), and it contains all the needed sources for it to compile (openssl, etc). I'll try to fix that.
EDIT: actually I don't know how to make it "linux proof". and I have no linux machine to test on... don't know if you need GMP or if mpir works... try removing the <gmpxx.h> and <gmp.h> lines inside "global.h" file
|
|
|
|
|
@PeaMine, you need to install GMP dev package before trying to build. After installing the devel package, it need to be available either in /usr/local/include or /usr/include
|
|
|
|
You can generate the next block in 60261 days 18 hours 31 minutes 11 seconds
NICE! You can generate the next block in 1 hour 12 minutes 58 seconds 55557 14571285356259793594 1 Feb 2014 11:17:23 GMT
1 10 + 1 128 B
2 332192480158058296 335 % <sarcasm>are you serious? from an account with 29,277,260 NXT? I would never ever guess that would be possible to be close to 1 hour </sarcasm> |
|
|
|
You can generate the next block in 60261 days 18 hours 31 minutes 11 seconds
NICE! *Anxious* |
|
|
|
I've fixed the build on Windows 7 jrovins, doing some tests now and will report back (and a pull request just in case) EDIT: Working amazingly well for solo mining (testing on testnet right now), build on Windows 7 64 bits, outputting x64 binaries, using Visual Studio 2013. Mined 2 22XPM blocks within 2 minutes at testnet diff 6.65094072. Had to fix some Windows specific code, and I hope not to break anything for the linux counterpart  New Block: 327721 - Diff: 6.651355 / 6.651355
Total/Valid shares: [ 0 / 0 ] - Max diff: 7.586425
6ch/h: 10.75 - 1 [ 0 / 1 / 0 ]
7ch/h: 10.75 - 1 [ 1 / 0 / 0 ]
Share Value submitted - Last Block/Total: 0.000000 / 0.000000
Current Primorial Value: 37
 EDIT2: Refactored A LOT of code to conform with C99 best practices (code warnings are my pet peeve). Working really fast on both 32 and 64 bits. Still need to finish refactoring the prime.cpp, because there are a lot of doubles being used where should be floats, and vice-versa EDIT3: On my fork branch from your repo https://github.com/pocesar/jhprimeminer/tree/refactor |
|
|
|
I'm tired of people making these dumb assumptions that proof of stake forging makes the rich richer, leading to some sort of financial crisis when they have all the nxt. this is only true if they hoard them forever and never trade them... also, the only reason someone has >10k in transaction fees is because of the alias landslide... im sure the fees each day is pretty insignificant right now.
says the guy that had 28 million NXT in the account... http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=7579216551136708118Has he forged something? check his forwarded accounts  in case you won't: 6635869272840226493 5,799NXT 2576421397261863186 2,515NXT |
|
|
|
I'm tired of people making these dumb assumptions that proof of stake forging makes the rich richer, leading to some sort of financial crisis when they have all the nxt. this is only true if they hoard them forever and never trade them... also, the only reason someone has >10k in transaction fees is because of the alias landslide... im sure the fees each day is pretty insignificant right now.
says the guy that had 28 million NXT in the account... http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=7579216551136708118 |
|
|
|
|
An account with 2 million NXT generated 28 NXT... the 50 million NXT guy generated almost 100k NXT lol
The concept is pretty flawed. Whoever gets the most coins makes most coins, how is that different from ASICs on Bitcoin? Someone care to explain?
|
|
|
|
There's one guy at one address (4747512364439223888) with 50 million NXT, creating block after block... not really fair I guess, but neither is Bitcoin mining. check in http://87.230.14.1/nxt/nxt.cgi?action=100Quote: the concept of ‘fair’ doesn’t apply to the universe, and it makes no sense to force it. The world just is—it is what it is—and you can complain about it, sulk, hate it all you want—or, you can pay attention to the averages, to the rules that work most consistently, try to learn and apply those rules consistently, and hope for the best. David A. Johnston From http://www.nxtcrypto.org/: [...]
This allows everyone on the Nxt network to have the same reward potential no matter the amount of Nxt you own.
At least, misleading. |
|
|
|
There's one guy at one address (4747512364439223888) with 50 million NXT, creating block after block... not really fair I guess, but neither is Bitcoin mining. check in http://87.230.14.1/nxt/nxt.cgi?action=100 |
|
|
|
|
the only thing that I see is "unequal" (as in capitalism) is that, the more the person has, the more he will have. what if it was truly random instead of giving huge amount of coins for people with already a lot of coins. that's the thing I don't understand.
|
|
|
|
Why doesn't Ethereum use Javascript for it's "high level language", since it's easy as hell to write and there are plenty of fast javascript parsers out there?
Good question. I thought about it when saw Vitalik reply about Python. Also JS has more fans than Py. plus it can be sent over the wire, "packed", "minified", eval'ed at will, etc... no idea why trying to reinvent the wheel  PS: I would greatly benefit from it, since JS is my main coding language  |
|
|
|
|
