Could you please check current hashrate?
4.29Gh |
|
|
|
@barrystyle - received the manual payout over an hour ago. Nothing since even though I've increased my hash rate.
Is pool stalled? Miners are saying they're hashing.
hey all, not to worry - am still waiting to hear back from dev. ive a feeling i'm going to have to hack NOMP to allow this coin to do payouts properly. and here i was just wanting to have a few beers and relax saturday night  root@capnmagneto:~/bitpokemongo/src# ./bitpokemongod -server -daemon -rpcuser=barrystyle -rpcpassword= -rpcbind=127.0.0.1 -rpcallowip=127.0.0.1 getbalance
5525.00008500
all coins after first send are still at pool address james Hi james, not really engage with NOMP code. Try asking to other pools operators. Since difficulty and hash is quite interesting right now, some of you could also try solo-mining. problem lies in your var definitions; both int64's COIN and CENT need to be defined in main.h, not utils.h.. just compiling and retesting, if successful will fork your github source and add code in, then you just need to accept changes. |
|
|
|
@barrystyle - received the manual payout over an hour ago. Nothing since even though I've increased my hash rate.
Is pool stalled? Miners are saying they're hashing.
hey all, not to worry - am still waiting to hear back from dev. ive a feeling i'm going to have to hack NOMP to allow this coin to do payouts properly. and here i was just wanting to have a few beers and relax saturday night root@capnmagneto:~/bitpokemongo/src# ./bitpokemongod -server -daemon -rpcuser=barrystyle -rpcpassword= -rpcbind=127.0.0.1 -rpcallowip=127.0.0.1 getbalance
5525.00008500
all coins after first send are still at pool address james |
|
|
|
I have pointed my miner to the pool but I haven't received anything yet, is everything ok ?
please read above. |
|
|
|
hi all, just did a manual payout. also cleaned up redis afterwards and kicked pool in the guts; checked config - its all good, however the payment system in nomp doesnt know how to deal with the reward structure. dev: please pm me. james root@capnmagneto:~/bitpokemongo/src# ./manualpay.sh
3796086e00200a2ad29dbbdfbe5bc3d1be833db5d3cacba57a7ebdf915991d66
2b99d4cd230135bfa16223090dd0b1cb252983044f8cc8840ab5b38d0353cc59
107cf2b03d77ab3537013e25365e4d966e8e30e1fd5c9f5b9cb4838b75c701c0
71102c009e158d8a9cf7689618147263094a024e5b86074528389e1bb0798124
db2c71848a8ebf0b351b0ada380dfa9976c937c0ba99013cc6f63fff4b10713b
97e12b8da3d2d098e6b290f9bf5124828eb7d93e8264b77486780d6c5d44f632
9ed00d058da4ccbe3801bb8c81087d19d9c4daf0b4de07981ec31d36ee46983a
156c85cf6173a51616ef7abc23425ef7c2c005672847e1ea3f88af30a27e2797
7373a21f4845d7f7dd22c1c0baa9b9e0223cf15522e75513e579a11359b1a54d |
|
|
|
Hi guys, Due to the nonstandard block reward structure - payouts will be slightly delayed: 2016-07-30 20:24:23 [Payments] [bitpokemongo] Error detecting number of satoshis in a coin, cannot do payment processing. Tried parsing: {"result":2500.00000000,"error":null,"id":1469881463972}
/root/nomp/node_modules/async/dist/async.js:844
if (fn === null) throw new Error("Callback was already called.");
^
Error: Callback was already called.
at /root/nomp/node_modules/async/dist/async.js:844:36
at /root/nomp/node_modules/async/dist/async.js:3676:17
at /root/nomp/node_modules/async/dist/async.js:339:31
at /root/nomp/libs/paymentProcessor.js:98:21
at itemFinished (/root/nomp/node_modules/stratum-pool/lib/daemon.js:156:36)
at /root/nomp/node_modules/stratum-pool/lib/daemon.js:169:17
at parseJson (/root/nomp/node_modules/stratum-pool/lib/daemon.js:85:17)
at IncomingMessage.<anonymous> (/root/nomp/node_modules/stratum-pool/lib/daemon.js:95:17)
at IncomingMessage.emit (events.js:117:20)
at _stream_readable.js:944:16
2016-07-30 20:24:23 [Master] [Payment Processor] Payment processor died, spawning replacement...
2016-07-30 20:24:24 [Pool] [bitpokemongo] (Thread 1) Share accepted at diff 0.81818182/1.38080520 by 8KMnUd2SDo2QqAsfR6QTgs5CCASnGG3jR6 [104.238.158.185]Will have to manually calculate; all good. Dev: comments? James When will payouts commence or are we mining for our coins to disappear into thin air 
10000.00000000
Coins are currently in pools default address; no need to stress. I'm currently writing some quick python to parse the stats api ( http://bazco.in/api/stats) to send them out evenly. |
|
|
|
Hi guys, Due to the nonstandard block reward structure - payouts will be slightly delayed: 2016-07-30 20:24:23 [Payments] [bitpokemongo] Error detecting number of satoshis in a coin, cannot do payment processing. Tried parsing: {"result":2500.00000000,"error":null,"id":1469881463972}
/root/nomp/node_modules/async/dist/async.js:844
if (fn === null) throw new Error("Callback was already called.");
^
Error: Callback was already called.
at /root/nomp/node_modules/async/dist/async.js:844:36
at /root/nomp/node_modules/async/dist/async.js:3676:17
at /root/nomp/node_modules/async/dist/async.js:339:31
at /root/nomp/libs/paymentProcessor.js:98:21
at itemFinished (/root/nomp/node_modules/stratum-pool/lib/daemon.js:156:36)
at /root/nomp/node_modules/stratum-pool/lib/daemon.js:169:17
at parseJson (/root/nomp/node_modules/stratum-pool/lib/daemon.js:85:17)
at IncomingMessage.<anonymous> (/root/nomp/node_modules/stratum-pool/lib/daemon.js:95:17)
at IncomingMessage.emit (events.js:117:20)
at _stream_readable.js:944:16
2016-07-30 20:24:23 [Master] [Payment Processor] Payment processor died, spawning replacement...
2016-07-30 20:24:24 [Pool] [bitpokemongo] (Thread 1) Share accepted at diff 0.81818182/1.38080520 by 8KMnUd2SDo2QqAsfR6QTgs5CCASnGG3jR6 [104.238.158.185]Will have to manually calculate; all good. Dev: comments? James |
|
|
|
hi all, pool will be available at http://bazco.in at or shortly after launch. it won't show anything at the moment, the moment it does tho - the pool is running. point your mining equipment/hash at: stratum+tcp://bazco.in:3333 username: your coin address password: anything algo x11 setup from diff 0.005 to 262144, 45 second retarget payouts per 5 minutes james I've got my rig pointed to it & waiting for the GO  Same here. Solo-mining while I wait, though. Already hit 5 blocks. I have the same idea, rental pointing towards pool, solo with personal rig, already hit 20 blocks  already got a bunch of blocks... join in folks |
|
|
|
groestl.c: At global scope: groestl.c:3122:1: fatal error: opening dependency file obj/groestl.d: No such file or directory } ^ compilation terminated. makefile.unix:181: recipe for target 'obj/groestl.o' failed make: *** [obj/groestl.o] Error 1 EDIT: Fixed (mkdir obj) - you need to have this folder present in your src dir (add it to your github repo dev) |
|
|
|
hi all, pool will be available at http://bazco.in at or shortly after launch. it won't show anything at the moment, the moment it does tho - the pool is running. point your mining equipment/hash at: stratum+tcp://bazco.in:3333 username: your coin address password: anything algo x11 setup from diff 0.005 to 262144, 45 second retarget payouts per 5 minutes james |
|
|
|
Very curious about the true anonimity that you mentioned.
Do you just mean current implementation of SuperSend or has it been improved?
The current implementation of SuperSend is currently among the best in anonymous transaction technology; however it can be a bit slow to send due to the large blockchain, however this should be allievated with the new release. I can see that there is some testing going on with a new version of the SuperCoin wallet V1.4.2. When can we expect the new wallet or is there no release planned yet? Is there a new version out? v1.4.2.. better let baz know, oh.. wait... You may have seen this in error - the new release may not even be known as SuperCoin. Anyway now for an update, thought I would let everyone know that we are at tops a week away from a release. - I've got a successful tamper-proof implementation of my crosschain code working at the moment; fully compatible with existing SuperCoin, MultiWalletCoin and ECCoin wallets, via a side-plugin which communicates via RPC-JSON. It can also be used standalone for the ultra-paranoid; outputting the appropriate command for you to send coins between blockchains, which you paste into your debug console manually. I'm not sure if this has been done before, whilst preserving the original client completely; it just seemed the most logical way to do it and it works very well.
- I've got (most of) a very lightweight blockexplorer/monitor required for the crosschain sends, more an informational update as this sits in the backend and you dont see it (but it still has feelings).
- Transactional-based chain mining/movement is very simple yet works very well, ensuring that the chain will grow at a much more acceptable rate; without sacrificing speedy sends.
- Currently I am investigating the best method to calculate the rate at which coins are exchanged from the existing ECC/SUPER/MWC wallets to the new chain, not an easy task nor an easy answer.
I might put up a few screenshots later on tonight to demonstrate how seamlessly it all works. james |
|
|
|
unless you've a couple million dollars behind you; or a fat stack of 16nm chips ready to solder to a chinese cloned PCB - i'd probably advise against wasting your time. the mining paradigm has evolved from companies releasing machines to home users, then exclusively large mining outfits; to then hoarding their own equipment for their own exclusive use (knc, bitfury, anyone remember the bitcoin brothers?)..
if the end goal is still mining for profit; set up a pool and rent some hashrate at an agreed price, and hope you beat the cut. this will be your most successful option; as the only people making money are the ones who either stole the equipment they use, are not paying for power or have a large amount of space at their disposal (not to mention those who mine selfishly.. f2pool/btcc/antpool).
get some interested candidates to throw some btc at a reasonable amount of hashrate; then split it accordingly. this is still more than possible and worthwhile
still a viable option; hashrate can be directed at a PPS/PPLNS pool or a pool owned by the group (to earn full blockreward if found). |
|
|
|
user with these ip 91.204.214.250 please resynchronize your wallet, to the latest version, as this causing the 66coin main node can not be connected to cryptopia!!!
here error
accepted connection 91.204.214.250:63305
send version message: version 60001, blocks=925537, us=24.139.103.236:36666, them=91.204.214.250:63305, peer=91.204.214.250:63305
receive version message: version 60001, blocks=923621, us=24.139.103.236:36666, them=91.204.214.250:36667, peer=91.204.214.250:63305
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 1.08826
Before: 1d0b3761 0000000b37610000000000000000000000000000000000000000000000000000
After: 1d0b3848 0000000b3848fba4d719e9b59206ee9b813db086b1683fd786e554bd4496ddf9
FOUND BONUS BLOCK!
ERROR: AcceptBlock() : missing bonus block reward tx
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 91.204.214.250:63305
Disconnected 91.204.214.250:63305 for misbehavior (score=100)
to synchronize, use the ip of the main node
24.139.103.236:36666,
seed.flowpool.cf:36666
seed.66coins.com:36666
24.139.103.239:36691
24.139.103.239:36693
THANKSSS
Hi mrflow27, I get these exact messages whether directly connected to your central node (ie. -connect=) or using your standard node with addnode. Please note I've deleted my peers.dat and made sure that at no time my pc is contacting 91.204.214.25. I've sync'd my chain several times only using your node. received block 215a60f61aed25e9fd60 Difficulty Retarget - Kimoto Gravity Well PastRateAdjustmentRatio = 1.96396 Before: 1e074b29 0000074b29000000000000000000000000000000000000000000000000000000 After: 1e074996 000007499637af7b6b8f6adee3b7697dd568750aad3db44f1da3c271f04d0bb2 FOUND BONUS BLOCK! ERROR: AcceptBlock() : missing bonus block reward tx ERROR: ProcessBlock() : AcceptBlock FAILED disconnecting node 24.139.103.236:36666 Disconnected 24.139.103.236:36666 for misbehavior (score=100) Added 414 addresses from 24.139.103.239: 3 tried, 3635 new Added 159 addresses from 24.139.103.239: 3 tried, 3631 new This is with your standard client for Windows (v0.8.2.0-gofficial-beta). Please note that your nodes also seem to drop-out whenever i submit more then 7 or 8 blocks. I had a permanent 66coin node around March this year; and things ran swimmingly. Please let me know if you'd like it to be re-established. James |
|
|
|
If it's not a malware we should get a pool for it  i'm happy to setup a pool for it, long as someone's happy to cover the vps costs.. already tested local pool at home with nomp and works fine. |
|
|
|
ah these forums are amusing at times |
|
|
|
Are you a Therapist ? I would gladly listen to your ways of understanding & living life seems like your lonely... wanna hug Yeah man, 5 BTC/30min session and get your damn feet off my couch. Hugs are extra. |
|
|
|
Ummmm WTF ? Why so many hits instead of just the usual 2 from the built-in bitcoin miner if this is just a direct clone of Litecoin.... https://virustotal.com/en/file/6b23566fd100d18dbff029940c5a56333e7d32f4893d96d113b487042334af58/analysis/1468888844Avast Win32:Malware-gen 20160719 ESET-NOD32 a variant of Win32/BitCoinMiner.BJ potentially unsafe 20160719 K7AntiVirus Unwanted-Program ( 004baab71 ) 20160718 K7GW Unwanted-Program ( 004baab71 ) 20160719 McAfee Artemis!ECA4C2CC3E9C 20160719 McAfee-GW-Edition Artemis 20160719 Sophos Bitcoin Miner (PUA) 20160718 Also the dev account was created in 2011 with a handful of posts in all those years + the users password was recently reset....... VERY IFFY ! Do you think it's some kind of malware? I scanned it using virustotal before I initially ran it and it seemed to be fine. Yes I do in fact, did you scan the .rar file or the actual .exe ? Or are you just trusting what the dev posted with his virus check ? The above scan is from the actual 9000coin.exe file... These are the worrying ones, if you google what they are I would be deleting the wallet & roaming data & doing a full system + rootkit scan. Avast Win32:Malware-gen 20160719 K7AntiVirus Unwanted-Program ( 004baab71 ) 20160718 K7GW Unwanted-Program ( 004baab71 ) 20160719 McAfee Artemis!ECA4C2CC3E9C 20160719 McAfee-GW-Edition Artemis 20160719 its a fucking crypted trojan im sure. I also just done a VirusTotal scan just out of curiosity & I would reccomend to stay far away from this !
With that many warnings and files named like those I would be running ! keyloggers, remote accesss, automatic background downloads of more malware & viruses..... NO THANKS !
Wow. Artemis is the "Active Protection" component of McAfee's Security Center which uses a combination of signature and behavior analysis to check with McAfee servers in real-time to identify possible new malware threats. Artemis is not the name of an actual virus, but an alert displayed by McAfee when it thinks it may have found a new virus. These detected files may or may not be malicious. Its heuristics guys; settle down christ. People like you are ruining Cryptocurrency. People entering without much in the way of computer skills are scaring off the newcomers en masse. You know that there are runtime and scantime fully undetectable trojans. They crypt the trojans with specific tools. At first we had only 2 detections . Now we have more with same file. So that means the anti virus scan tools got updated and maybe the wallet.exe is dangerous ! Sure do. Theres two with 'Artemis' as I described above, two with UnwantedProgram/Nuisance program qualifying as BitcoinMiner-style detection, two with BitcoinMiner and an unknown, which lo and behold is more than likely using a BitcoinMiner signature. I'm guessing this program is related to Bitcoin somehow If I were to write a trojan or something that stole private keys; just a bit of C, threw it in the wallet and compiled today - it would not show up as a virus/malware. Antivirus companies lag behind the real world, as they need people to submit examples of viruses before they can agree on a common 'signature' which is then used to detect code in future. Now stfu and stop scaremongering. LMFAO are you serious barry ? can you not see the tell tail signs in all aspects of this ? Holy fuck ! The "DEV" registered in 2011, it took him 2 years to post anything & his first post was "Now I am registered" .... OK but I thought he was already registered 2 years ago with the same account he posted with lol Next the "DEV" has posted 14 times in a matter of 3 years with all different kinds of things that don't quite add up to a standard personality of someone talking, this guy seems like he has multiple personalities by the way he talks in his posts. Next he randomly comes back and releases a "CLONE" of a very old Litecoin base coin that still has heaps of Vulnerabilities.... and expects people to mine ? I think he means he want's people to open the wallet/file He has also reset his password in his profile if you go have a look, another tell tail sign right there unless this guy has a very bad memory, I'm surprised how he copy and pasted a coin lol yet alone remember his password lol If you ever watched how these kinds of scams played out back when it was a thing & nobody knew about how they worked then you would know this is a sure sign of one instead of shooting your mouth off at others for having an opinion, here is another guy (ME) that is stating his opinion just like everyone does when they post on this forum, if nobody posted then nobody would talk. By all means mine this coin, good luck with getting it on an exchange yet alone keeping your other altcoin funds, it might be encrypted but they will get it lol 2 weeks ago computers were infected from a new virus that wasn't detectable through antivirus software or scans until the detection was update after users started reporting a foul, so what is the difference with an altcoin ? Here is an example why you are so defensive of the coin  "Oh a coin, lets mine it !, oh I forgot to virus scan it but I own the majority of coins... I'll back it up and say its a clean wallet & they are just false positives" put down the pipe brother; seek help. |
|
|
|
|
Show Posts
