ive noticed some odd behaviour in the existing code, that may help.
say you start your wallet after not using it for a few days; it syncs approx 2000 blocks (and is level with mrflow's flowpool nodes etc) - once it is level, the out of sync message disappears from your wallet.

if there are other nodes present which clearly have a higher block count, they are ignored.

however, once you mine a block using your wallet - the 'out of sync' message immediately appears, and the block counter 'x blocks remaining' appears, where x = (node_with_next_highest_count - your_block_height).

james

To add a bit more clout to Mooncoin_Foundation's points; i've added some technicals to each answer


PoS is not superior in any way to the PoW algorithm; i'm not sure who perpetuates these claims.
A short time back, a client asked me to demonstrate a small example showing just how secure PoS is.
I released a small paper (only 4 pages) demonstrating a very quick and precise attack (including Proof of Concept), showing how easy it is to 'overwrite' a PoS block, with a PoW block.
In fact, i had trouble only overwriting one PoS block; i would always seem to do several in the process. Go figure.

I'm really not one to talk shit, and if this cops any flack whatsoever, I will be happy to post screenshots.


The scrypt (generally vs x11) argument is always a joke.
Scrypt so far, out of all the mining algorithms available to date, had had the longest mh/profitability rating of them all.

I invite anyone to scrape the profitability ratings from Nicehash, as far back as they like (Scrypt vs X11).
X11 has really gone to the toilet with the release (or some in the know would say re-release ) of the Baikal/PinIdea-style generation miners.

Re-release is a funny term to use.
To the uninitiated, it seems a mystery why the X11 market went to dirt in 2015.
The X11 equipment you are buying now has been in use for a long time.
Just this time around, manufacturers knew to either release only domestically for the meantime, and mine using their own products for much longer than previously seen. I'm using the term 'domestically', but i'm sure the readership can understand what I am saying between the lines.

On a much much much more technical basis, did you know that if X11's difficulty drops below a certain value; you can use Scrypt equipment to mine it? Hah.


Looking at this from much much further back from the horizon.
We know that there are trillions of dollars in physical form; as we know them 'US Dollars'.
The US Government/Mint continues to print these with no additional gold/resources to back them whatsoever.

So in my eyes; a secured/interlinked currency with total cap in the billions (with an eventual finite supply), is no problem whatsoever.

Your brutally barbaric dev,
barrystyle (james)

sigh.
again.
once coins have been minted to anonymous; you arent able to simply 'check up on them via richlist'.
as is the entire underlying basis for this technology.

go and actually look at the source commits on the zcoin github.
i'm not sure where you're looking, there are at least 10+ changes

i think you need to go do some reading about what libzerocoin actually is and does.
your comments literally make you look retarded.

also:
http://www.newsbtc.com/2017/02/19/zerocoin-updates-about-a-bug-in-the-implementation-of-zerocoin/

i'd say that dev's have less than 96 hours to find an exchange and get this listed (if not organised already), before the diff retarget yanks the handbrake on this chain:

https://github.com/quantum1dev/quantum/blob/master/src/main.cpp#L1103


and if the handbrake cable snaps there, we've always got them excessive confirms for mined coins:

https://github.com/quantum1dev/quantum/blob/master/src/main.h#L58


brought to you by the letter t,
baz

just did that now, works no issues.

not mine, but a friend bought approximately 1000BTC sometime between 2010-2011, for a princely 90c/aud each. during the november 2013 bubble, everyone was yelling at him 'sell! sell!', instant millionaire. but he held. real cool head on that guy

then mt gox struck and lost the lot.
i dont see him around much these days, i do know he got involved in the recovery process.

apparently the site operator is out of jail now but has parole conditions.
how the guy hasnt been taken out is beyond me  

if you have access to a linux server, use nomp (https://github.com/zone117x/node-open-mining-portal).
there is a windows version available but i've never looked into it.

in your instance; it might be a better idea to simply solomine against the windows wallet's rpc interface.

bit of explaining there, but theres plenty of info available on the web ('solo mining rpc wallet' brings up some usable information)

golem actually sounds pretty cool. aha back in my high school days, me and a mate built a beowulf-grade cluster out of a bunch of 486dx4/100s, early pentiums; running something like redhat 6 (giving you an indication of the time period). just the boards, powersupplies (in some cases we ran two motherboards off one psu) with no cases on a shelf with a shitty 10mbit hub; and the beowulf distribution/job services.

once we stood it up, we kinda went, 'now what'.
and then we were enlightened.


regarding hashpower:
i do remember reading someone asking this a few years back (particularly sha256 asic). if you were so inclined, you could actually get the asic engines hashing any given hash (say a password converted to hex bytes and then padded); but your parameters would be very limited, and youd need to write software for both the application/protocol layer.

oddly enough, on the antminers (or any unit with broadcom/SoC-based controller with ethernet/wifi running embedded linux), you COULD potentially build a small firmware image with a cpuminer to do cryptonight, or something suitably light on the risc processor. utterly useless, but imagine the odd looks you could get from people.

'... yeh so im just smashn monero with my antminer s3 at minergate ...'

older sha256 units would probably be more useful when used as

hi all,

wanted to give this a go overnight, set one of my vps' up with centurion configured.
please note this won't be a permanent fixture, but if you'd like to use it with a rental over a few hours/half a day - i will leave it up with enough time for your coins to clear (if you want to privmsg me and let me know). knowing me i will probably forget and just leave it up so eh

temp pool at bazco.in
stratum on stratum+tcp://bazco.in:3333
algorithm: x11 (start diff 0.1, vardiff min 0.005 max 32)
payouts every 10 minutes, minimum of 5 CNT
username is wallet address

no fees, i'm CJkwToVhABNaubDijXek83orAcsUrkaNTo on the pool.

james

No, it's interesting to think about, but it would require more computational power to convert the hashes to a usable form, than the hashes/hashpower itself.
The proof of work mechanism is set in stone; would not be possible to adopt it for much else than its intended use-set.

The most common argument comes up with something like file encryption; but the specific implementations of any given algorithm to be used in cryptocurrency vs data security are very different.

Edit: Golem is not actually using hashpower to achieve their goal; the idea is having an engine capable of a bunch of different tasks installed on a large amount of workstations, and the workstations subscribing to see what work is available, which changes depending on what people want it to do. For example, its well known now that the US Army used PS3's with a special customized operating system; to perform massive distributed calculations across a vast number of machines (http://www.escapistmagazine.com/news/view/105767-U-S-Air-Force-Finishes-PS3-Supercomputer-of-Epic-Proportions).

the 'idealist' gambler has the highest risk of losing.
by idealist, i mean the one who wishes to start with the lowest denomination; yet to walk awayu with the highest prize.
to be able to put the least in, yet take the most away; it simply isnt going to happen - or if it does, the probability is tiny.

the longer you are in a match, the higher the chance that you'll lose
a probability tree is essentially a path of connected risks.
with every step you take, you are multiplying your odds by a percentile.

google images has the goods:



instead of mining $1-2 of btc and more than likely losing it before you've even doubled/tripled it,
why not buy a few hundred dollars worth.
$100, with a bet size of $10; you've a better chance of doubling it, than tiny fractional amounts.
best strategy is not to gamble, but wheres the fun in that

quick edit re: sports/event betting: unless you are the guy feeding the team experimental steroids, its generally not worth it.
dice and similar sorts offer you 50/50 off the bat; which in terms of probability is the best deal yr going to get.

It's running right now

Introducing the MoonRush wallet (http://moonrush.org)
A true cross-platform wallet, that holds sensitive data client-side, with an implementation of insight-api for MOON.

• Private keys never leave the client device.
• Addresses generated via simple swirl motion.
• Only you are in control of your funds, regardless of hosting scenario.
• Transactions generated and hashed directly on the device before being broadcast.
• A bookmark is all that is required to remember your device; however this can be secured further via password.

not sure what you mean?

i guess, from a clean vps - login as your standard user.
elevate to root (sudo su, or if you know root password just su)

then paste this bad boy in:
apt-get update && apt-get install -y build-essential automake autoconf pkg-config libcurl4-openssl-dev libjansson-dev libssl-dev libgmp-dev git screen && git clone https://github.com/zcoinofficial/cpuminer-xzc && cd cpuminer-xzc && ./autogen.sh && ./build.sh && ./cpuminer -a lyra2z -o stratum+tcp://xzc.suprnova.cc:1598 -u barrystyle.0 -p x -q

and also change barrystyle.0 to your username/worker, or alternatively leave it there
is just a fancy one liner method of updating package list, installing all required dependencies with no prompts, cloning the miner, building automatically and launching.

james

er wow.
in the official github repository no less, as i said.. it wasnt committed:
https://github.com/fourtytwo42/42_v0.0.1/pull/2/commits/8240cee3b90af7157de43e8ab552b6493d77c0e7

unrelated, has there been any issues with the pos implementation?

sorry guys.

poor code quality is the underlying issue here it seems.

i dont own an excessive amount of hashpower, nor do i perform any blackhat tricks; but i've had to resync this chain so many times that i've lost count. a minimum of two permanent nodes is all that is required to entirely eliminate chainforks, except in insanely high hashpower/highly inconsistent network response situations.

i remember the last 'good stretch' that coin66 had (reliability wise), was 4-5 months last year when i was running a full node; including it in a set of profitability tests i was doing at the time. amazon ec2 would allow for this type of configuration to be done for free, once a verified credit card is applied against the account.

the entire issue would be resolved if:
a) two (or shit, even one would probably improve situation at least somewhat) initial syncnodes added to source.
b) the chain logic is adjusted to accommodate the several bad/fork blocks (32,xxx, 580,xxx from memory) properly. syncing from scratch on any given version codebase is not possible.
c) existing syncnode either placed on vps, or a less congested link (ive just received average of ~ 400ms from three separate locations).

additionally, a shift to newer codebase with support for 'getheaders' would do this coin wonders.

james

old chain simply didnt have a limit at all.
a patch was released that simply set pow coinbase out to zero, which was a bit rough.
but considering more than 42 coins existed at this point, not much else could have been done.

wasnt commited to master at any rate.

i love the amd vs nvidia trashtalk here, cracks me up.
i mean, it only took nvidia 7 years to catch up, now that they're in bed with google.