Globalcoin still uses IRC to communicate nodes. Make sure you don't have IRC being blocked for globalcoin-qt.exe on your personal computer...I did on my personal wallet computer ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
my globalcoin.conf file:
addnode=216.177.81.87 addnode=195.154.185.5 addnode=108.173.241.118 addnode=98.115.147.74 addnode=71.207.13.6 addnode=162.255.117.105 addnode=37.187.96.15 addnode=85.236.188.28 addnode=129.21.131.183 addnode=203.20.114.252 addnode=109.144.133.4 addnode=74.132.75.138 addnode=162.243.239.107 addnode=162.243.106.159 addnode=162.243.104.134 addnode=globalcoin.ddns.net addnode=100.42.224.37
|
|
|
I've noticed someone has started mining the other chain again. It should be advisable that anyone using GLC not transfer any GLC during this time until this fork situation is resolved. I would be mostly concerned if you on the shortest chain as that one will most likely not survive.
I was going to say not a lot of transactions have occurred on the shortest chain but then yesterday 174,825 GLC was transferred. Most likely to an exchange on the short chain. Someone could sell all their GLC on an exchange that is on the short chain but would actually still have it in their wallet on the longest chain.
The exchanges should be contacted as they will be left holding the bag.
|
|
|
Longest chain (currently) has the most hashrate. Generally, the rule in cryptos is the longest chain wins. Longest chain is not having any client issues.
Not much point in the coin if the strongest chain has only miners. I hear you...but the longest chain is also not having any issues (that I am aware of). It also has the most nodes (GLC wallets).
|
|
|
Longest chain (currently) has the most hashrate. Generally, the rule in cryptos is the longest chain wins. Longest chain is not having any client issues.
|
|
|
216.177.81.87 is a node on the longest chain. Try syncing with that one.
|
|
|
The 3 peers I can see are at 2 different starting heights, so I guess there's been a fork, and there are now two competing chains.
Yes, I've noticed the same thing. Perhaps you can try syncing from scratch.
|
|
|
Without miners you have no network hash....and slow confirms. How is that stable? ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) One thing for sure....you're rid of this one. Don't waste your time...the devs don't seem to understand the importance of a secure blockchain. I have tried to gently communicate it in the past but to no avail. At this point the only thing that will show them the danger is a demonstration of an attack but I am not the one to do so. I fear that if/when we see a higher value in this coin it will be too tempting for someone to take advantage of. Even before the fork with 2 Gh/s it was in danger but now it is just a joke. One thing saving the blockchain from an attack is a low enough value that someone won't bother...other than to prove a point.
|
|
|
Hello everybody!
Sorry i'm French!
But we need a link to download craftcoin wallet windows QT!!!
So can you give us a link to download this?
Thank's!
Someone will probably have to create one again. The website and it's downloads are gone. The source is still in github: https://github.com/craftcoin/craftcoinWe still offer CRC trading on CoinGather and the block chain is moving along.. Here ya go... Craftcoin-v1.2.0.0-jeb.zip
|
|
|
Will update GitHub in the next day so others can get their own CSC p2pool nodes going. If you don't want to wait here are the changes that need to be made: DELETE the data directory at the root! p2pool\networks\casinocoin.py from p2pool.bitcoin import networks
PARENT = networks.nets['casinocoin'] SHARE_PERIOD = 10 # seconds CHAIN_LENGTH = 24*60*60//10 # shares REAL_CHAIN_LENGTH = 24*60*60//10 # shares TARGET_LOOKBEHIND = 20 # shares SPREAD = 60 # blocks IDENTIFIER = '7A1B73A729CF5FC1'.decode('hex') PREFIX = '79A544E00296E8BA'.decode('hex') P2P_PORT = 23640 MIN_TARGET = 0 MAX_TARGET = 2**256//2**20 - 1 PERSIST = False WORKER_PORT = 8840 BOOTSTRAP_ADDRS = 'xpool.net'.split(' ') ANNOUNCE_CHANNEL = '#p2pool-csc' VERSION_CHECK = lambda v: True VERSION_WARNING = lambda v: None
p2pool\bitcoin\networks\casinocoin.py import os import platform
from twisted.internet import defer
from .. import data, helper from p2pool.util import pack
P2P_PREFIX = 'fac3b6da'.decode('hex') P2P_PORT = 47950 ADDRESS_VERSION = 28 RPC_PORT = 47970 RPC_CHECK = defer.inlineCallbacks(lambda bitcoind: defer.returnValue( 'casinocoinaddress' in (yield bitcoind.rpc_help()) and not (yield bitcoind.rpc_getinfo())['testnet'] )) SUBSIDY_FUNC = lambda height: 1*100000000 POW_FUNC = lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data)) BLOCK_PERIOD = 30 # s SYMBOL = 'CSC' CONF_FILE_FUNC = lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'casinocoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/casinocoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.casinocoin'), 'casinocoin.conf') BLOCK_EXPLORER_URL_PREFIX = 'http://csc.blockexp.info/block/' ADDRESS_EXPLORER_URL_PREFIX = 'http://csc.blockexp.info/address/' TX_EXPLORER_URL_PREFIX = 'http://csc.blockexp.info/tx/' SANE_TARGET_RANGE = (2**256//1000000000 - 1, 2**256//1000 - 1) DUMB_SCRYPT_DIFF = 2**16 DUST_THRESHOLD = 0.03e8
|
|
|
It should work on ubuntu 14.04 or debian 7 and 8 just fine with libboost 1.54.
Ubuntu 14 works! DL'ing chain....pool will be back once that is done.
|
|
|
Going to bring the pool back up using a temporary daemon (Windows QT) as the Linux one will not build or run. Downloading the blockchain now...will post when it is done.
This is just a temporary deal since I may still shut down the CSC pool for good if I can't compile on Ubuntu server 12.04.5 LTS.
MINERS: Please use a fallback pool!
Tried Ubuntu server 16 (new install using ubuntu-16.04-server-amd64.iso) with no luck using the pre-compiled daemon with the same error as Ubuntu server 12. Did not try to compile again on Ubuntu server 16 as I figured at this point it is just broken.
Edit: Ubuntu server 14 worked.
|
|
|
xPool.net is shutting down it's CSC p2pool node after the fork since I cant get the new daemon running. I've tried a few things but can't devote any more time to it.
Kinda sad since it is the first (at launch) and longest lasting pool ever for CSC but oh well...need to let people know.
Also, I will not be updating the p2pool source code to support the new coin specs. If anyone else wants to fork from my repository you will need to change at least the subsidy function...maybe more.
|
|
|
For the members here who are placing a large order and going directly to Inno as part of the group buy offer. If you feel comfortable letting us know that you ordered using the group buy that would be awesome. I would love to get an idea how many people are able to take advantage of this offer. Thanks!
I am trying, but having no luck in reaching sales or any of the other emails since last Saturday. Either they are going into a spam folder or they are pissed at all the email I have been sending... No luck ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) Im in Arizona, and was going to buy the 3 units. 5 units was a bit too much, but 3 I can handle. If anyone want's to piggy-back on my order (assuming I can get through to them to place it), let me know. I would also be willing to piggy-back on someone else order if they have actually managed to get a response from them... They have trouble receiving email from some domain names (blame China)...specifically (most likely) domain names registered through godaddy. Try sending them an email from an alternate email address with a different domain name.
|
|
|
Do not forget about shipping costs. I don't remember how much it was but it was not cheap with my A2s. Also wire transfer fee's.
I personally think this first batch will be slower than later batches due to quality improvements in future chip dies. My hunch is that this first batch did not turn out as expected although I have nothing to base that on other than experience in chip production.
|
|
|
Crash on launch with the win64 version of anoncoin-qtc.exe. Anyone else? Edit: Same with the win32 version. Edit2: Had to delete everything except wallet.dat and rebuild blockchain from scratch. ![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
|