Is the site accepting registrations ?
I tried, and I get dumped back to the registration screen. Nothing in the mail.
|
|
|
I think the denomination change seems like a good idea, though I have to admit I'm more than hazy about the consequences The main consequence would be BTC trading. Right now if you want to buy some KMC you first have to buy LTC, which makes it more difficult and ties our price to LTC. Our community is small enough that it should not be a major disruption. In fact KIMO and KMC would still be compatible, if you send 1 KIMO to a KMC wallet, 1000 KMC will show up. If you send 1000 KMC to a KIMO wallet, 1 KIMO will show up. If you have 1M KMC in your wallet, and you upgrade to the KIMO wallet, you will see 1K KIMO. The new wallet just moves the decimal left. What other consequences are you unsure or concerned about? Yes, I got that. What I meant is that there might be consequences on trading, like higher volume, liquidity, that kind of thing. Which I don't know much about, so I only gave my agreeing opinion on the points you gave. I did not have any particular thing I was concerned about. Just... hazy about second order effects (and I don't mean necessarily bad ones )
|
|
|
Fitting for a sloth coin if you ask me
|
|
|
I think the denomination change seems like a good idea, though I have to admit I'm more than hazy about the consequences
|
|
|
Congrats everyone! List your hyp address for bounties!
p7CjeohAjPSKs9jR9q6Wev5n9StyLnTMHH Thanks!
|
|
|
Just to say that this quiz is a great initiative, I enjoyed researching the history of crypto from the questions Worth the time spent, even before any PMP I might get (hopefully close to 10 though:P)
|
|
|
Which one of kussaka's do you vote for, moneromoo? I assume the same as me, although, like me, you probably have a hard time deciding between the two Oops! I prefer the rightmost one. Though if I may offer a suggestion, I feel the background lighting would work better if it was more uniform (and maybe the rim a bit thinner (I'll stop now )).
|
|
|
The voting is pretty much certain now, but I'll register my own preferences anyway:
I'll give 3 voices to zeewolf's last. I don't like the way the inner part of the triangular H is shaped, but I'd prefer the triangular version if that part was reshaped. As it is now, I can't decide between those two last ones from zeewolf. Overall very nice, kinetic, and very evocative.
I'll give 2 voice to kussaka, mostly for the reasons davidlatapie also gave.
I don't really like rugrat's (sorry). It's clearly well polished and the result of a lot of work, but it just seems out of place to me.
|
|
|
I prefer when it's low, so my pool finds more blocks
|
|
|
I took some time anyway to rework, and while I didn't get anything approching the vividness of zeewolf's, this is more like what I had envisaged originally. Nova gone, it's too symmetric, it may come back as a soft background if I get to make a good mask for it. Softer clouds too. And the graininess in the glow is gone.
|
|
|
Yes, the kinetic effect in zeewolf's is nice. I wanted to have that kind of "blueish glowing embers whooshing past" effect, similar in idea to zeewolf's logo, but, being only occasional amateur at this, could not get anything looking right, so I ended up using the rays as a fallback. I might try again but I'm not sure I'll get the time. Also, looking again now, the cloud is too strong and drowns the starry background, I'll tone it down too.
|
|
|
On the hyperspace theme. Maybe a bit heavy on the nova rays, but here goes:
|
|
|
In the last,give me a explication . Why the hast rate of extempool often is more than the hast rate of all network?
The hash rate of the network is in fact NOT the hash rate of the network. It is an estimation of what the hash rate of the network should be in order to keep blocks coming at an average of 1 every 4 minutes. After looking at that hash rate over days, it seems to have a fair amount of hysteresis, so will wobble around as actual network hash rate (which is unknown at any point in time) varies. If a pool has the vast majority of the network hash rate, this will cause that pool's hash rate (which it knows) to sometimes be above the estimated (from difficulty, itself a function of recent past block times) network hash rate. If you try any other pool, this effect will be the same, but you will not notice it if the pool is a lot smaller (like mine, for instance, hovering at 4 or 5 kH/s currently), because the values are so different. By the way, this effect, if what I described is real, causes the pool's "luck" factor to give me really lucky blocks (eg, my pool found a block at 1469% luck recently) when that hysteresis causes the difficulty to go keep going up when the actual network hash rate starts going down. So it's all a bit inexact/approximate. (OK, the 1469% is mostly down to actual luck, but I'm pretty sure the hysteresis effect also plays a role).
|
|
|
So I managed to get my hands on 5 HYP (at overpriced TRK prices, but hey), and I'm a bit confused. This morning, the client shows weight of 2, for a network weight of 370000 or so, Reward in a monht. OK.
Now, it's showing weight of 4 (coins aged I think ?), but network weight of 7870. Reward in 2 days. With my paltry 5 HYP, I can't possibly be a tenth of a percent of the whole network ? I have 6 active connections to the network, it seems to be fine there. What happened ?
|
|
|
I'm a bit confused as to what I should do now. I have the new wallet running with -connect 192.241.233.70, I have a few HYP in my wallet, but I'm not sure how to set those coins to stake. Stake says 0.00. I see the OP says the min age is 8 days, does this mean I have to run my wallet open for 8 days and it will start staking automatically ? Or do I ahve to do something to move the balance to stake ?
|
|
|
Dear pool owners and users, please recompile your duckNote to the latest fixes.
I've just updated my pool - http://duckpool.mooo.com, both the code and the transaction fee to 0.1 ducks. All seems to work fine so far. (Pool open to all, only 0.75% pool fees, and we love ducks). _o<
|
|
|
When was the last time this happened?
...right now... two rigs are working @your pool [2014-07-01 22:10:42] Stratum connection timed out [2014-07-01 22:10:42] Stratum connection interrupted I'm not 100% sure, but as far as I know, this is OK. The miner will reconnect and will not lose its current work. This happens if there is no communication for 2 minutes (either a new block found notification from the pool to the miner, or a work results sent by the miner). In other news, I just updated my pool ( http://duckpool.mooo.com) to the latest pool code. All welcome It's been a lean time for the lucky ducky after its crazy luck at the beginning, we did find a block just before the halving, phew _o<
|
|
|
Whether true or not, they do seem to have issues with simple maths with their "lowest fees on the market" at 2%. I think they meant "highest fees on the market"
|
|
|
This thread is my last hope, as all my attemps to install wallet and miner in lubuntu 14.04 failed. This are the errors I got: /home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp: In function ‘void cryptonote::mul(uint64_t, uint64_t, uint64_t&, uint64_t&)’: /home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:33:22: error: expected unqualified-id before ‘__int128’ typedef unsigned __int128 uint128_t; ^ /home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:34:5: error: ‘uint128_t’ was not declared in this scope uint128_t res = (uint128_t) a * (uint128_t) b; ^ /home/user/bitmonero/bitmonero/src/cryptonote_core/difficulty.cpp:35:22: error: ‘res’ was not declared in this scope low = (uint64_t) res; ^ make[3]: *** [src/CMakeFiles/cryptonote_core.dir/cryptonote_core/difficulty.cpp.o] Fehler 1 make[3]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release' make[2]: *** [src/CMakeFiles/cryptonote_core.dir/all] Fehler 2 make[2]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release' make[1]: *** [all] Fehler 2 make[1]: Verlasse Verzeichnis '/home/user/bitmonero/bitmonero/build/release' make: *** [build-release] Fehler 2
I would be very glad to find help here, but have to say that my knowledge in Linux is pretty limited. I think you may be building on an architecture which doesn't have support for 128 bit wide types. Like something built without SSE. If your hardware (or VM) does support SSE, maybe your compiler does not. Or you might need to add the right flags (eg, -msse or whatever, not sure what exactly). Logs of configuration may also have error messages related to that, though I'd half expect the build to fail then if it can't find what it needs.
|
|
|
|