|
difficulty has ramped right up, which is why the chain isnt moving
|
|
|
|
|
wow, don't even bother.
someones first attempt at a coin it seems, surprised it lasted as long as it did.
|
|
|
|
i've been looking at this since i saw it listed on an exchange a few days back. listed as pow in some descriptions, pure pos in others. interesting algo 2xsha256.. haha  so technically that makes it sha256d, however i think they mean a total of four rounds of sha256 (keccak is three). just compiling the cgminer-dmc to see how it goes; sync'd the coin daemon, has a unsurprising 2 million blocks. |
|
|
|
OCminer could you compile your miner for windows and upload it on git ?  pulled it down as i've got a better source, but given some of the attitudes cant be bothered. MSVCR120.DLL missing |
|
|
|
ocminer - miner not working - reject
You have to use new version of the miner Yes, the link to your pool, the port is changed, but ..... start cpuminer.exe -t 3 -a lyra2rev2 -o stratum+tcp://xzc.suprnova.cc:5596 -u с -p x reject reject spuminer not an executable file..  What he lacks? are you running windows 64bit? |
|
|
|
testing.. fuck i swear it wanted to include every dll cygwin had... :|
21 dll's. ohyeah! there are 1000 more missing.  settle man, you're flooding my link with those two posts. |
|
|
|
|
testing.. fuck i swear it wanted to include every dll cygwin had... :|
|
|
|
|
thanks, i don't have cygwin installed at the moment, in vs15 cannot compile need to run make first
still going with cygwin64.. bandwidth here in australia is a joke |
|
|
|
Some are linux some are windows.
OCminer do you have a .exe version of the new miner for windows ?
ill compile one up for you |
|
|
|
Well ok, what can i do , right ? ssh and plink are great for running commands remotely on multiple hosts (assuming your machines are *nix based) |
|
|
|
case ALGO_LYRA2REV2:
if (stratum.bloc_height >= 8192)
{
rc = scanhash_lyra2rev2(thr_id, &work, max_nonce, &hashes_done, 8192);
}
else
{
rc = scanhash_lyra2rev2(thr_id, &work, max_nonce, &hashes_done, stratum.bloc_height);
}
break;Groundbreaking change  https://github.com/zcoinofficial/zcoin/issues/12block height will increase to the point where the difficulty will become unworkable. groundbreaking, no. necessity, yes. |
|
|
|
wtf why algo change now, i have to change my miners now on 20 computers.
this has been discussed for some time, had been implemented in testnet and changed on the main codebase nearly 2 weeks ago. |
|
|
|
Guys, question. Is there any connection between zcoin and zoin?
It's just a fork of ZCoin Its funny how this open-source thing works. . Someone spent many months (if not years) developing something, then he publishes it as open-source, and in 1-5 days it is being copied and exploited, often without giving any credit to the original. I know open-source is good, but sometimes it is getting ridiculous. I am coming from closed-source business world myself, and though I like open-source, but sometimes I think there should be limits on that (maybe a grace period of few months/years before the source is opened). Do you guys think those clones are harming the original or are good for it...? In a perfect world they should help (by working in parallel and finding and fixing issues), but in reality I am not sure... I don't want to get involved in this thread, but you'll find quite the opposite. ZCoin does not give credit to the Zerocoin developers (see Copyright statements in Github and GUI): https://github.com/zcoinofficial/zcoin/blob/master/README.md90% of the work done in ZCoin for Zerocoin was from the Zerocoin library: https://github.com/Zerocoin/libzerocoinZoin on the other hand, gives full credit to ZCoin (for their contribution) and ZeroCoin in the Copyright statements and GUI: https://github.com/zoin/zoin/blob/master/README.mdits not so much that; implementing libzerocoin in itself is not easy. it'd be like building a drag car, and then not giving credit to whoever manufactured the pistons, both things are not easy tasks but one won't work without the other. |
|
|
|
Supercoindev implemented the "normal" scenario for supersend, but there are 3-4 exception conditions he did not implement. When we tested it, about 10% cases there are some exception conditions (such as mixer unexpectedly quit), in which case the supersend may be stuck (that guarantor should sign off the transaction depends on the cases). He was planning to implement them, but unfortunately he was too busy with his work so he decided to quit. Also he was pissed by the fact that many inferior coins put a lot of people to promote, such that these coins have much more people despite have nothing new. The supercoin has some truly new technologies. Anyway, if you are good, fix these problems and make Supercoin better I hear what you're saying, if you know of (or find posts from the past) any variables/conditions that the behaviour has been noted to occur under; i'd be more than happy to investigate. From everyone's point of view so far, they just see revised front end design.. theres a bit more going on now, not just a nip and tuck, and this will be shown once I upload the codebase to gihub (hats off to CryptoJohn though, simply awesome designs). Anyway, if you are good, fix these problems and make Supercoin better  I have to admit I laughed at that, good one man. |
|
|
|
No it's not a bought account, I am what I am I was referring to the other chap there.. marseille. The PoW/PoS coin never fully sync'd with Bitcoin or Litecoin. All PoS coins are based on novacoin, the latest I think is with protocol version = 70049 and database version = 80609. The current SUPER codebase is way old, it has protocol version 60013 (I think) and database version 70508. As I said, numerous bugs are fixed there.
All PoS coins are actually based around Peercoin (which has been updated to 0.6 codebase); with Novacoin being an older clone which is still late 0.5 codebase. Novacoins latest protocol being 60018 and database 70507. Supercoin is currently at protocol 60013 and database 70508. Seeing as you're quite insightful, with an eye for detail, i'd be more than happy to merge some newer code in there; provided the bugs that the code fixes are deemed a serious-enough issue. |
|
|
|
Great to see SuperCoin still there alive. I looked at the codebase, it is pretty old, the dev should upgrade it to the newer codebase, where there are many bugs fixed.
Also it seems to me that the SuperSend code, many exceptions are not handled, which need to be fixed.
Which codebase are you referring to in particular? Bitcoin 0.9/0.10/0.11/0.12/0.13? Feel free to tackle this if you like - which bugs are you running into, in particular? Please feel free to list any exceptions (with screenshots) that you've experienced. Not sure the current dev if any understands fully the code, looks to me SUPER is in maintenance mode instead of actively developed now.
If you'd like to see some quicker developments, feel free to contribute towards Super/Super+'s future (contact Griffith or myself directly). Oh - you're a bought account, my bad  |
|
|
|
far out.. i swear the world of cryptocurrency never stops, have only just loaded the sources up on github: https://github.com/barrystyle/electrum-moonhttps://github.com/barrystyle/electrum-moon-server i posed this to Mooncoin_Foundation about a week ago; nothing like an early release no binaries just yet - however if you're keen, obtain python 2.7.11 and a copy of git, at the command line run: git clone https://github.com/barrystyle/electrum-moon.git
cd electrum-moon
python electrum-moon |
|
|
|
|
Show Posts
