POS code uploaded at github.com/Pakcoin-project/pakcoin
Ewallet will close at 00:00 Hours tonight (GMT)
Is Novaexchange already swapped? Meaning, can we withdraw now to the new wallet from above github and start staking? TIA Edited to add: Why are there already 30728 blocks on the new PoS chain? Seems like this chain launched on around 1.1. |
|
|
|
Only issue I noticed is: the miner goes inactive/dead when connected to auto exchanging pools like zergpool or blockmasters etc and then it comes back again after x amount of time. Guess it's BFGMiner not liking something the pool does?
Besides from that it's spot on.
As mentionned before, make sure you do not have a backup pool configured when trying to mine on a multi/profitswitching pool. |
|
|
|
Downloading from link provided, 500 KB/s... (I have 75 Mbps Fibre if you ask)
Is there chance for torrent or something? Torrent could be even hosted in Apollo itself and distributed to people. So no need for AWS.
I could download it just right now with 25MB/s in less than a minute from home. You must be holding it wrong  (or your providers pipe to amazon is a tad slow). |
|
|
|
How many locked in hacked cryptopia ?
Hard to say with only one deposit address to check, but I'd estimate a minimum of 20-30 mio SJW are still in their wallets, probably much more. |
|
|
|
Tell me please, is there anything heard about tether? I have had 3,000 of them there  TFTFY P.S.: Not making fun of your loss just pointing out the facts. I myself have had ~0.35 BTC in alts, BTC and LTC in topia when they went dark. |
|
|
|
How do you propose that an exchange detects 51% attacks ?
Off the top of my head: - Watch for reorganisation messages in the debug log showing excessive (say 10+ blocks) disconnects. - Regular audit to check that deposit transactions are still marked as valid and have sufficient confirmations. - Watch for large negative changes in computed/reported coin supply. Good points, watching the debug.log for consecutive orphans/disconnects is probably best and easiest, I guess in its simplest form that are a few dozen lines of shell/python script. Or instead of delisting coins out of nowhere, they could have asked them to implement the NLR feature that Ravencoin and Flo recently implemented which limits the number of blocks in a reorg. If they then set the required deposit confirmations twice as high they should be safe against any malicious reorgs. I believe for many coins that are based on something more recent than Bitcoin core 0.8 this could be as easy as cherrypicking the commits from the Flo or Ravencoin repo. I wildly guess this could even be done unilaterally from an exchange without the support of the respective coins community, in worst case the exchanges wallet would just disagree with the rest of the network but would not credit transactions from later orphanized chains to their customers accounts. |
|
|
|
ich hoffe mal es ist nicht ganz so schlimm, hört sich zwar nicht gut an, aber ich hoffe wir hören zu gegebener Zeit noch etwas von Dir, wer, wie wo was... Drücke euch die Daumen, bin mal gespannt, ob meine Funds bei euch auch betroffen sind  Gehört dieser Beitrag in diesen Thread? Oder hat vielleicht jemand seinen Beitrag vor dir gelöscht? Aktuell liest es sich nämlich so als wäre hier etwas schief gelaufen  Ja, da ist gestern in der Tat was schiefgelaufen: https://www.newsbtc.com/2019/01/15/breaking-crypto-exchange-cryptopia-hacked-police-starts-investigation/HTH |
|
|
|
Has the exchange between TIPS and the FED been completed?
If the exchange is not complete,
What time does it start?
Hi LJ, The TIPS -> FED swap is still in progress, currently running at altilly.com. It will also be happening on coinexchange but we don't have a confirmed date from them yet. Cheers, Robots. Hi robotsoutofcontrol, Has already been decided what happens with the swapped TIPS (i.e. burning them)? I see on the richlist that one address has accumulated short of 30% of whole supply: https://tipsbe.netcraft.ch/richlistTIA |
|
|
|
Also on the insolvent radar: Noteably quite a long outage already today. I sincerely hope they don't go TITSUP*. *Total Inability To Service User Portfolios |
|
|
|
Hey everyone. Nova Exchange is back, we have opened our doors, but BOB stopped receiving new blocks on 27th of December. http://explorer.scrypt.ovh/dobbscoin/If we do not receive new blocks, we will have to delist the currency. Let us know if there are any updates within the community of BOB's that we should know. Regards I moved a few blocks, hope this helps the coin survive. |
|
|
|
Upgraded from source, installed, started with -reindex-chainstate as advised by debug.log but was then stuck with 10 connections and 0 blocks (and naturally no balance).
Removed everything except wallet.dat, but still the node doesn't start synching, still 0 blocks after ~15mins (having currently 7 connections).
Thanks for any hints in advance.
This behavior is normal. You can get a clearer picture by issuing "getblockchaininfo" in the console. The top of the output will contain a 'blocks' and 'headers' entry. The headers entry will climb and after the headers are verified, it will start moving through the blocks. As the blocks are verified, your transactions will begin to get verified also, and your balance will move accordingly. I have always used -reindex instead of -reindex-chainstate. reindexing takes more time than I like, but much less than redownloading the blockchain. <snip> Thanks for your swift reply, you are perfectly right with all, have a merit on me. I am now back synched and look forward to mine the first auxpow blocks in ~2 days. One thing I noticed is that the daemon doesn't start if you do not specify the rpcport in the conf file or as cmdline parameter (or have listen=0). I guess the culprit is in this line: https://github.com/sexcoin-project/sexcoin/blob/master/src/chainparamsbase.cpp#L35 : which seems to conflict with https://github.com/sexcoin-project/sexcoin/blob/master/src/chainparams.cpp#L142 : I guess the first should read 9561 to stick with the previous RPC port number. |
|
|
|
Hei Sexcoineers, is this the latest wallet ?
Sexcoin Core Version v0.10.4.0-2067064 (64-Bit)
Thanks, and happe SE X-Mas.
Upgrade will be out in the next two days. As of four hours ago, we are live with version 15! You must upgrade to version 15. Version 15 is now on GitHub! https://github.com/sexcoin-project/sexcoin (exe to follow very shortly) From Lava: Ok.. I've created the release on github. We're official Upgraded from source, installed, started with -reindex-chainstate as advised by debug.log but was then stuck with 10 connections and 0 blocks (and naturally no balance). Removed everything except wallet.dat, but still the node doesn't start synching, still 0 blocks after ~15mins (having currently 7 connections). Also: At which block height will the fork to auxpow happen?Sorry, it is in the release notes: Sexcoin will activate merge-mining and Segwit at block 3080000 Thanks for any hints in advance. |
|
|
|
However the Wifi doesn't work for me (tested just for fun, don't need it), I have 2 wireless networks (WPA2-PSK only) that the apollos should see but only saw them once upon "scan" and that was after the first boot of the image, since then I don't see them anymore on both apollos (and not even the dozen or so neighbouring WiFis that my notebook sees from the same location). Do you know if you are running your APs in mixed mode? If you switch to mixed mode, you'll likely be able to see and connect to them. Make sure once you associate, reboot them and remove the ethernet cable. I was able to get all of my Apollos to successfully connect and run reliably on my WiFi. Let me know if you need more troubleshooting help. Peace, r00t If you mean by mixed mode 802.11b/g/n, yes that's the case on all AFAICS. Though no need to worry, I won't use WiFi, that just adds unnecessary delay und unreliability when ethernet is available just 1m from the miners. In the meantime I tried "iwlist wlan0 scanning" in the shell and after an "ifconfig wlan0 down; sleep 3; ifconfig wlan0 up" I saw my networks. It might be that they are just shielded wifi-wise pretty good when standing on a metal surface as in my case with the antenna on the bottom. When I saw my networks on first boot they were in a different place on a wooden surface. |
|
|
|
Bug report: https://imgur.com/a/6szEf9oArrows up and down don't work (tested on Mozilla Firefox and Google Chrome). I can't change priorities in pool order. Also, it's not possible to EDIT entries. These fields here are just greyed out display fields, not text entry fields. If I want to edit the main pool, for example, I need to delete all of them and enter them all again in the correct order. I believe something is messed up between UI and backend, because if you delete one pool, the backend often deletes another pool (not the one you clicked to delete). Might be that sometimes there are entries in the database with the same number in the 'index' field. I also dislike that you can't edit them (nor can't copy-paste the entries), not even directly in the apollo itself - the only way I found is mounting the apollo disk via sshfs and running sqliteman against the db in /opt/apolloapi/. This was for me necessary since at some point after some trying to shuffle, re-add, delete from the UI I suddenly got litecoinpool and a multipool running in parallel which made the apollo freak-out pretty much. On the positive side I finally managed to run them stable against a multipool, since 24hrs stable at 100MHs with ~1.6-1.9% errors. If you want to mine on profit switching pools / multipools, make sure you do not have a backup pool configured (unlike cgminer, bfgminer seemingly requires primary and failover pool to run on the same coin/network). For mine I also set the fans to 45% resulting in 56-58°C. Worth mentioning is also the fact that these are the first miners in my hands that are IPv6 capable, according to bfgminer release notes this should allow the apollo to connect to pools via IPv6 and for later releases to allow full nodes to run dual-stack which gives much more connections to the coind. However the Wifi doesn't work for me (tested just for fun, don't need it), I have 2 wireless networks (WPA2-PSK only) that the apollos should see but only saw them once upon "scan" and that was after the first boot of the image, since then I don't see them anymore on both apollos (and not even the dozen or so neighbouring WiFis that my notebook sees from the same location). |
|
|
|
Thanks again for your reply. I tried creating a new rule in my firewall for the slimcoin wallet app, and even disabled my firewall for a period of time....unfortunately none of these options were able to get my wallet to sync.
Here is what I have written in my slimcoin.conf file. Can you kindly take a look at it? Maybe I've forgotten to include something? Or if possible, could you share what you've written in your .conf file? Thanks again for you help!
addnode=78.46.37.209
addnode=145.239.189.106
addnode=85.10.208.71
addnode=37.187.100.75
addnode=112.113.96.138
addnode=123.2.121.70
addnode=188.134.72.213
addnode=5.9.38.137
addnode=178.222.61.137
addnode=81.207.93.95
addnode=146.200.136.172
addnode=212.186.174.90
addnode=5.9.39.9
addnode=86.56.74.0
addnode=213.165.83.122
addnode=217.65.8.75
addnode=46.160.104.75
addnode=5.105.63.14
addnode=195.19.128.122
daemon=1
rpcallowip=127.0.0.1
rpcport=41683
port=41682
server=1
listen=1
rpcuser=*******
rpcpassword=********
That looks all good, you could even do without conf file. Your problem connecting to the network lies probably somewhere between you and other nodes as hinted before. |
|
|
|
Just checked, my rather ancient 5.0.15-alpha is having 22 connections atm. When you say you had 8 connections, you probably had only outgoing connections and are not a listening node. I see only three peers of my 22 are outgoing, all other 19 are incoming connections. You might want to try these three listening nodes in your conf file: addnode=78.46.37.209
addnode=145.239.189.106
addnode=85.10.208.71
Current block height at the time of posting this is # 1601088. HTH Thanks for your reply. I tried adding these nodes to my config file and unfortunately the wallet still was unable to find any connections. I took a look at the debug file and it keeps on saying "connection timed out." Would you happen to have any idea what the problem is? Thank you! "connection timed out" sounds a lot as if you had a problem connecting to thses nodes. Maybe some security product, personal firewall or "smart" consumer router does block these connections? If you can ping above nodes but still do not get any connections, make sure that nothing blocks access to port tcp/41682 . HTH |
|
|
|
Hello,
has anyone had any issues with their wallet recently? Up until a few hours ago, it had 8 connections and now it's down to zero. I tried adding nodes to the .conf file but that didn't help. Can someone else confirm that they are having the same issue? I just wanted to see if it's "me" or if it's the network.
Thanks!
Just checked, my rather ancient 5.0.15-alpha is having 22 connections atm. When you say you had 8 connections, you probably had only outgoing connections and are not a listening node. I see only three peers of my 22 are outgoing, all other 19 are incoming connections. You might want to try these three listening nodes in your conf file: addnode=78.46.37.209
addnode=145.239.189.106
addnode=85.10.208.71
Current block height at the time of posting this is # 1601088. HTH |
|
|
|
|
I received two units last Monday, both in perfect shape and no broken panels.
So far working nicely on a profit switching pool. I got the same problems shuffling pool order around that were described by AltScope, simply didn't work until I had three pools configured, then it started working. That's not a biggie really.
But I also found that switching back from secondary pool when primary pool is back up doesn't work and needs a manual restart of the miner to go back to primary.
Otherwise it is a really nice piece of well-thought work, great job I'd say and absolutely worth the money.
Oh, one last wish: It would be great to be able to see the current stratum difficulty in the interface, I am running on a vardiff port and like to see what it gets assigned from the pool.
Btw: I metered power consumption of my two units connected to one Corsair CS850M (gold) and got ~240W @230VAC input. I'd assume running of a platin PS could get that figure down to 210-220W for two units.
|
|
|
|
|
Show Posts
