I like Coinomi, but import/sweep p.key daes'nt work.
Ok - interesting; will look into this. Can you pm me any specifics? I've a fairly good idea why it may not be working. Electrum ok but it daes'nt show the confirmation number and our blockchain (Btc now) and you can send coins before 6 confirmation. This creates wrong transaction if you are not careful...
Zeroconf spends are part of the Electrum featureset (if you have a play with the litecoin, bitcoin or dogecoin versions; they allow the same). I will check the confirmation issue; i'm guessing the BTC reference is something i missed. I did quite a bit of testing with all wallets to ensure funds sent and received came through correctly; no funds will be lost (there was a small amount lost during alpha testing, this was since resolved). I use iOS device and in this moment i have not mobile wallet. Coinspot au and cointopay in maintenance ....  The use creates value  iOS apps are a bit tricky. Developing for iOS requires a developers account/certificate (anyone please correct me if this is not true); the other option being an online RPC webwallet via webkit, however this becomes a major attack vector. baz |
|
|
|
not sure how much interest this will get but here goes. have been playing with the original cpuminer since zcoin's release; and seem to have found a slight edge last night. performance gains are in the realm of about 25-50%, earning about 0.5 XZC from one quad cpu VPS overnight (9-10hr). please note that the reported hash below is wildly incorrect, it should be around 20H/s or slightly higher from a standard 10H/s.  as some of you know, i'd been toying with a GPU miner since launch as well; with some partial luck; probably more to ocminer's annoyance with the invalid shares he keeps seeing on his pool from me  going to give it another go night and will report how i go. baz (the black spaces are just some debug information ive removed) |
|
|
|
Could have gotten it listed on Alcurex, haven't been keeping up too much, what is super+ supposed to be? Same coin or another?
its the same codebase adjusted for 90s pos; as the existing chain is nearly 3.8 million blocks. i've written some code that detects specially crafted sends, and can receive coins sent from supercoin. james so you created a fork coin by copying supercoin code and made it compatible with supercoin and thus doubled its supply? a simple copy-paste coin called original name and a plus? what an originality! lol BTW, I likle your icon, better than the last one once coins are sent from supercoin, they are no longer spendable; as the private keys behind the addresses are unknown. they either exist on one, or the other. and of course they are going to share the same codebase; isnt supersend one of the original features that you guys like? james what's the point with supercoin+? it is a copy-paste coin like other shitcoins. Why not fix some bugs in supercoin and move it along. You said you are "dev" for supercoin, I did not see you do anything there! the entire reason i got involved was to get rid of the bloated blockchain. |
|
|
|
Could have gotten it listed on Alcurex, haven't been keeping up too much, what is super+ supposed to be? Same coin or another?
its the same codebase adjusted for 90s pos; as the existing chain is nearly 3.8 million blocks. i've written some code that detects specially crafted sends, and can receive coins sent from supercoin. james so you created a fork coin by copying supercoin code and made it compatible with supercoin and thus doubled its supply? a simple copy-paste coin called original name and a plus? what an originality! lol BTW, I likle your icon, better than the last one once coins are sent from supercoin, they are no longer spendable; as the private keys behind the addresses are unknown. they either exist on one, or the other. and of course they are going to share the same codebase; isnt supersend one of the original features that you guys like? james |
|
|
|
Could have gotten it listed on Alcurex, haven't been keeping up too much, what is super+ supposed to be? Same coin or another?
its the same codebase adjusted for 90s pos; as the existing chain is nearly 3.8 million blocks. i've written some code that detects specially crafted sends, and can receive coins sent from supercoin. james |
|
|
|
naw, i moved onto much more productive activities, with supportive communities. not just a bunch of trollish bagholders. considering how 'critical' this thread got, im surprised noone has offered to get it listed james I didn't expect anything else then this from this wannabe developer. A big mouth and nothing to show.... It would take him 4 hours but in reality he wanted to launch a new coin called Supercoin+ I still hope my wish for 2017 comes true so that the original SUPERCOIN developer picks it up where he left. With those wannabe developers Supercoin will be dormant for now LOL; show me one implementation of sending coins between chains that is written in 4 hours, seems you forgot the original intentions here like i said, feel free to put up the money to get it listed. james |
|
|
|
Ok, so im connected to the network now but its not downloading anymore of the blockchain. Been stuck on 84% all day. Ive tried updating to the most recent wallet, but no luck. Any ideas? try addnode aux.bazco.in, this has a full copy of the chain and has been running for the past month. to be blunt guys, i'm pretty much over this coin. i've the new chainswap code, client and crosschain code ready; all that is required is someone to pay to get it listed somewhere (SUPER+). additionally i'm still waiting on CryptoJohn for the new logos; paid him 0.05BTC and haven't seen anything since. support your dev until he turns sour, james wow, you launched a new supercoin? that is quite an achievement... somehow I missed it I suppose you fixed many issues like we discussed earlier, not just a copy-paste coin, right? naw, i moved onto much more productive activities, with supportive communities. not just a bunch of trollish bagholders. considering how 'critical' this thread got, im surprised noone has offered to get it listed james |
|
|
|
Ok, so im connected to the network now but its not downloading anymore of the blockchain. Been stuck on 84% all day. Ive tried updating to the most recent wallet, but no luck. Any ideas? try addnode aux.bazco.in, this has a full copy of the chain and has been running for the past month. to be blunt guys, i'm pretty much over this coin. i've the new chainswap code, client and crosschain code ready; all that is required is someone to pay to get it listed somewhere (SUPER+). additionally i'm still waiting on CryptoJohn for the new logos; paid him 0.05BTC and haven't seen anything since. support your dev until he turns sour, james |
|
|
|
still alive?oh ,amazing
IMO. This just a revive coin. I'm waiting for further announcement of the devs about new features and development plan this year. I think it deserves a better a promotion if the devs really want to revive this coin because many existing coin out there. It is so hard to be notice without a promotion. you must still be drunk from new years this coin has recently been migrated from an aging 0.8.6 codebase to the latest stable litecoin core release (0.10.40), which was no small effort. not to mention a ton of additional functionality (read the first page); as well as being one of the few cryptocurrencies that currently receives zero virus alarms on virustotal.com. please think before posting, but feel free to download the new client and give it a go. love, baz/james |
|
|
|
|
sometimes i dislike this forum, but then i remember that at least its not reddit.
reddit is full of obnoxious, opinionated faggots; who feel they can request literally anything from the bitcoin team, or programmers in general.
having an opinion is fantastic; however if you have no skills or talent (or means), then shut the fuck up until someone else with the same opinion does it.
not to mention the 10000 shill accounts, or the headlines which just piss you off (<insert some vaguely irritating statement here>, then in the post itself <some meaningless opinion or farrrr paranoid thinking>).
then, the worst part, if someone is given a good answer that disagrees with their thinking, regardless of proof, they will just post some wordy, know it all, 'im not listening' to you response.
reddit does not control bitcoin or its future, i dont know where this thinking started, but its gotta go.
|
|
|
|
|
hey guys,
cheers for repeating what i've basically just said in one post (up there).
i can confirm the chain cgt99 has posted is correct, as it matches the chain running on mrflow27's node, up to block 1051847 as i write this.
ive posted several times in this thread regarding not being able to sync from scratch.
first you have to use 0.7 source to get to block 580xxx, then to latest to sync full chain.
i'd offered a few days back to provide a fix/patch for mrflow27's sources so it corrects the problem and we all just move on (as i had in the past).
honestly cant be stuffed now see how i go for time later this week
james
|
|
|
|
Was a fork ever chosen? I thought people where getting on the c-cex chain to send coins? is other exchange still on another chain?
actually those checkpoints secure the blockchain (see https://bitcointalk.org/index.php?topic=194078.0) to prevent additional chains with really fast asics now the chain used by ccex and dutch-mining is off of the "official" one, but thats another matter if one wants to sync to the official chain i suggest using the addnodes provided by nova the other way round use those by ccex well aware of the reasons for having checkpoint blocks, just as well as their potential for abuse. trying connection 208.163.158.201 lastseen=0.0hrs
received block 00000f8923e2585d5cbd
SetBestChain: new best=00000f8923e2585d5cbd height=1 trust=2097154 blocktrust=1048577 date=11/08/16 17:38:49
ProcessBlock: ACCEPTED
received block 00000047b8d42ab011bc
SetBestChain: new best=00000047b8d42ab011bc height=2 trust=3145731 blocktrust=1048577 date=11/21/16 05:06:15
ProcessBlock: ACCEPTED
received block 0000004b8b45189977df
* hyuck, we're gonna need minimum PoW 1e0fffff
SetBestChain: new best=0000004b8b45189977df height=3 trust=4194308 blocktrust=1048577 date=11/21/16 05:08:17
ProcessBlock: ACCEPTED
received block 000000299fe41f7a5aa0
* hyuck, we're gonna need minimum PoW 1e09a06c
ERROR: AcceptBlock() : incorrect proof-of-work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 92.63.57.24:5556 (0 -> 100) DISCONNECTING
disconnecting node 92.63.57.24
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
for the sake of being a team player, rather than a dick; check the 'hyucks' above. some debug code i've thrown in whilst attempting to sync against the 'official' nodes. block 4 needs to be 1e09a06c, but in xenixblockchain.com; it is listed as 1e0340dac-cex has been on the correct chain from the start; not sure what happened with nova. one page back. novaexchange runs a chain that doesnt currently sync with any source. just tried (2 minutes ago, with official dev source https://github.com/xenixcoin/xenixcoin.git):  i've forked the existing repo, fixed it and it syncs to c-cex's chain in minutes ( https://github.com/barrystyle/xenixcoin.git). even dev's own repo will sync to c-cex's chain if sufficient nodes are available. I was still going to tell you. Anyway I remove the coin of my pool at the end of the month
You must comment on lines 2149 and 2150 in main.cpp
And recompile.
Once syncro decomment the lines and recompile again
And even to watch that its does not happen again
// Check proof-of-work or proof-of-stake
if (nBits != GetNextTargetRequired(pindexPrev, IsProofOfStake()))
return DoS(100, error("AcceptBlock() : incorrect %s", IsProofOfWork() ? "proof-of-work" : "proof-of-stake")); you're kidding right? you mean 'oh, just uncomment the code that verifies each block as it comes through'. im gonna throw a bit of hashrate at this shortly via rental if anyone else would like to join in |
|
|
|
|
like ive said from the start, c-cex has been on the correct chain since launch.
other pools/exchanges have an invalid block for block 4 (which has been admitted by the other pools).
seems to fall on deaf ears.
|
|
|
|
Hello all (and happy 2017 in Australia), A new client has been long overdue; and what better way to start off the new year, than with a new Mooncoin client. Mooncoin's existing codebase has been ported across to the latest Litecoin source (0.10.40), bringing it right up to stable/current code. The client is fully compatible with both the blockfiles and wallet.dat from older versions of Mooncoin. A hardfork is planned to start at block 1,100,000; with several features in place. More about this later. Mooncoin 0.10 Github Repository:https://github.com/mooncoindev/mooncoinWindows QT wallet (suit 32/64bit processors):https://github.com/mooncoindev/mooncoin/releases/download/0.10.5-public/Mooncoin-qt.zip( https://virustotal.com/en/file/cc5ae5fcb8bb70bcf8d80f65ff061e10d8efa73d4e7ceece051e0753fd13a5ea/analysis/1483169855/) Windows QT wallet (paranoid version, WARNING do not use with wallet.dat files from the other clients READ BELOW):https://github.com/mooncoindev/mooncoin/releases/download/0.10.5-public/Mooncoin-paranoidqt.zip( https://virustotal.com/en/file/864f510a6925f2025a8b01c3c3dbf2b856a87fb3cbcc3c21ed063484043c9239/analysis/) Windows Electrum wallet (suit 32/64bit processors):https://github.com/mooncoindev/mooncoin/releases/download/0.10.5-public/electrum-moon.zip( https://virustotal.com/en/url/101423534d9e4184850769ae3ffc6cb24bc88b8dbf24d6e644ef81c1d89a1034/analysis/1483169647/) Windows CLI Daemon and tools (suit 32/64bit processors):https://github.com/mooncoindev/mooncoin/releases/download/0.10.5-public/Mooncoind.zip( https://virustotal.com/en/url/59ce4649e7cad69e76a6c218a36c142f2636851ae27f003d4b80e897ded510c0/analysis/1483170086/) Linux QT wallet (suit 32/64bit processors):https://github.com/mooncoindev/mooncoin/releases/download/0.10.5-public/Mooncoin-qt.tgz( https://virustotal.com/en/url/ae687314e86f452925c51589656ddfe891ffff489632286a192349de870e7e74/analysis/1483169793/) Linux CLI Daemon and tools (suit 32/64bit processors):https://github.com/mooncoindev/mooncoin/releases/download/0.10.5-public/Mooncoind.tgz( https://virustotal.com/en/url/11e1a3ac5758b22e2fe48cdb4d384e2b439b38134c78124a0386baef341d2a50/analysis/1483170010/) Android Coinomi Wallet BETA (Tested on Android 4+):https://github.com/mooncoindev/mooncoin/releases/download/0.10.5-public/coinomi-moon-beta.zip( https://virustotal.com/en/url/95ee187f4567c04965739519114281e123bafa15e4415f729769376fb1f46618/analysis/1483169737/)     Please do not be alarmed regarding the Windows QT wallet, Baidu seems to target all altcoins now (for example):https://github.com/dogecoin/dogecoin/releases/download/v1.10.0/dogecoin-1.10.0-win32-setup-unsigned.exe ( https://virustotal.com/en/file/2b096491a2b08c09fca9b6e25809311a33d6ffde691960c9425543ec15c99573/analysis/1477471431/) https://download.litecoin.org/litecoin-0.10.4.0/win/litecoin-0.10.4.0-win32-setup.exe ( https://virustotal.com/en/file/21783cccfb4dc9d7de8f7e902613b6c1252819e7eb4f2e7a25eacedc7ff2ecf6/analysis/1475526704/) https://www.dash.org/binaries/dash-0.12.0.58-win32-setup.exe ( https://virustotal.com/en/file/8d5985275b78e09d527a306fcecca86390b7e1c9777ab57e8f89adfbce528464/analysis/1468739107/) https://bitcoin.org/bin/bitcoin-core-0.13.1/bitcoin-0.13.1-win32-setup.exe ( https://virustotal.com/en/file/a7d1d25bbc46b4f0fe333f7d3742c22defdba8db9ffd6056770e104085d24709/analysis/1479157427/) This is due to virus detection software using db-4.8.30 (the library that supports wallet.dat) as a generic signature for cryptocurrency; possibly the cheapest most of in the book. For the extra paranoid; i've compiled a version using db-5.1.29 which shows no alerts, however using it with an existing wallet.dat file from other versions of Mooncoin will cause corruption and you may lose your balance. You will need to export your private keys from your old client and import them into the new client. The new client corrects some older behaviour like transactions sometimes not immediately being committed to a block. In addition to this, a change of difficulty retargetting algorithm (DigiShield) has been implemented. Additionally; the new client prevents sends from accounts containing funds known to be stolen.
This code is already in place at the exchanges, so good luck trying to spend them (even from the old client) if you happen to be BigVern or.. you know, two exchanges didn't have an issue with the code - the third suddenly delisted MOON; you can make your mind up regarding that.I hope to be around for some time, so heres to MOON in 2017! james (barrystyle) |
|
|
|
|
After his initially damaging tweet, I responded to him privately in a gentleman-like manner, to which I heard nothing.
Personally I dont have anything against Hex, however smearing an entire community for little to no reason is just childish.
Delisting a coin nearly immediately after a new codebase has been released, initially provided me with the impression that he had been 'spooked'.
He is welcome to contact me and discuss in a civil manner, as I had attempted to pre-tweet.
|
|
|
|
If people interested in this coin took 3 minutes of their time, and read calmly the whole process this was not happening.At the end of 2014 I took charge of this coin after the original dev turned off its servers 66coin, and decided to continue giving it maintenance When the original dev turned off the 66coin server that happened? Wallet 7.0 only synchronized to block 580364, which I did?  Create a new version 8.2 which is working perfectly that I did with the new version here the fixes that I made correcting 1. Fix 2 bad blocks 2. Fix synchronization 3. Add more Checkpoint 4. Cosmetics Missing 5. added more checkpoints 6. Modified the reward system to the next version of wallet delete the OLD SUPER BLOCK REWARD and create a different formula for SUPER BLOCK REWARD 7. Added 2 more Nodes for backup In case the primary server fails If they read as I said above I understand that the problem of synchronization with the wallet, was a thing of the past. Once again and for the last time here the instructions on how everything works !!!!! READ THIS POST AND ALL RESOLVED!!!http://Https://bitcointalk.org/index.php?topic=647324.msg12428046#msg12428046Here is a clear example of a person who does not read and who is honestly using an old version of 66coin Difficulty Retarget - Kimoto Gravity Well PastRateAdjustmentRatio = 0.265361 Before: 1d52cd90 00000052cd900000000000000000000000000000000000000000000000000000 After: 1d53165c 00000053165c807d0dd558c40cdb43f6ca5f07832c84d720cbdd81ae0aac4250 FOUND BONUS BLOCK! ERROR: AcceptBlock() : missing bonus block reward tx ERROR: ProcessBlock() : AcceptBlock FAILED disconnecting node 2.38.64.73:52746 Disconnected 2.38.64.73:52746 for misbehavior (score=100) Hi mrflow27, I'd just like to clarify that the issue still does exist; i've just tested using the latest source from https://github.com/mrflow27/66coins. After: 1d012e29 000000012e2964d2c50adc50adc50adc50adc50adc50adc50adc50adc50adc5c
SetBestChain: new best=f65cf5e96766f3f44a9c height=32004 work=178320990108971 date=03/03/14 13:13:24
ProcessBlock: ACCEPTED
received block 90d76fba35db706855e5
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 0.7993
Before: 1d012e29 000000012e290000000000000000000000000000000000000000000000000000
After: 1d0138e7 0000000138e702caadaf777f4ff660745639d6c5971a2d326d18aeb8423a875f
InvalidChainFound: invalid block=90d76fba35db706855e5 height=32005 work=178324504022016 date=03/03/14 13:33:52
InvalidChainFound: current best=f65cf5e96766f3f44a9c height=32004 work=178320990108971 date=03/03/14 13:13:24
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED I agree with the comment by mycoinsstore, however Cryptopia is well-aware of the fix and is choosing to be difficult.  If i get some time later this evening, I will look into coding a patch that gets around this problem. james |
|
|
|
Need more developers to make it forward.  Need a devoted developer Let's try to find the guy Only the original developer is good enough....  where'd he go? until i have more time, anyone is free to take the reigns |
|
|
|
I'm on the right chain.
I installed the coin of the beginning and run everything. All the coin generating on my pool were to pay
I even win 33 xen
The bug is produced between block 511 and 575
Just when the dev has to change the block reward
And you know as well as me that he passed the block reward to 0.084
Not to generate too many coin so that the xen course remains high
It still has 10000000 xen to sell the dev (premine)
Many blocks are mining on other pools while they are already falling
So I do not know if the miners will pay or not
You've admitted you had to comment out lines in dev's source in order for the blockchain to synchronise correctly: I was still going to tell you. Anyway I remove the coin of my pool at the end of the month
You must comment on lines 2149 and 2150 in main.cpp
And recompile.
Once syncro decomment the lines and recompile again
And even to watch that its does not happen again
The reason you are able to then recompile it with these lines afterwards, and launch using the incorrect chain, is because the daemon does not check all blocks on each launch. Again, i've outlined in previous posts where the issue lies, how i came across it and how to fix it; without having to butcher the code which has basically formed your own chain (an extension on an incorrect chain due to wrong PoW for block 4). I'm not sure why Nova is on the same chain (C-Cex has been on the correct chain as per dev launch), but I get a feeling they've followed your advice. Of course you are going to support the incorrect chain as it owes you money, thats understandable, but to continue saying its the correct chain just makes you an idiot. |
|
|
|
I do not joke. There is a problem on blocks. Comment on his passes and then handed the original And recompile the source Its done at least 10 to 15 days that I'm syncro on my pool and the payments are done correctly Check on the official explorer address on my pool adresse = XH4QVr6vrkp4wCyATU8yropWTbs6KQ94sj http://xenixexplorer.comcompiling and running the source from dev's repo previously worked until he released this commit ( https://github.com/xenixcoin/xenixcoin/commit/a65b401d2011fbddfd2dc0e0827e17c8a22efb53). i fork'd a copy of his repository before this change was made, and additionally added this commit ( https://github.com/barrystyle/xenixcoin/commit/a9c30ec9a37ee738fc3d20605fd271fedfb8979f); which adds a few known 'honest' nodes. why you continue to support this chain, where you've literally admitted to removing validatory checks just to sync, is beyond me. it is not a valid chain, you know this, i know this, the whole thread knows this? just suck it up - recompile your code, sync and start your pool again. |
|
|
|
I was still going to tell you. Anyway I remove the coin of my pool at the end of the month
You must comment on lines 2149 and 2150 in main.cpp
And recompile.
Once syncro decomment the lines and recompile again
And even to watch that its does not happen again
// Check proof-of-work or proof-of-stake
if (nBits != GetNextTargetRequired(pindexPrev, IsProofOfStake()))
return DoS(100, error("AcceptBlock() : incorrect %s", IsProofOfWork() ? "proof-of-work" : "proof-of-stake")); you're kidding right? you mean 'oh, just uncomment the code that verifies each block as it comes through'. c-cex's chain verifies the entire way through. i'm done with this thread, unwatching. |
|
|
|
|
Show Posts
