Topic: [ANN][CASH] Crypto CASH | Proof of Stake & COIN CONTROL | On Cryptsy | 0 PREMINE - page 55. (Read 248249 times)
May 11, 2014, 09:25:58 AM
normaly i would not care, but i already sent 10k to my wallet, so i need to connect so i can move them again
May 13, 2014, 06:41:04 PM
Quote
Looking at my log a good IP to put in your conf file is
46.4.113.49
46.4.113.49
THANK YOU VERY MUCH! Im donwloading the blockchain now, finallyyyyy!
I will send you some cashcoin tip once im finished
maybe it would be good to update the conf file on page so other people dont have the same problems like me.
kind regards
Glad you got it working.
Unfortunately I don't have the ability to update the conf file as it is managed by someone else, hopefully they will drop by soon and be able to update the conf file.
May 11, 2014, 09:17:58 AM
Hi,
yes the file is in the right place. as you can see in the log, cash client trys to connect to the nodes that are listed inside the conf file, without success.
yes the file is in the right place. as you can see in the log, cash client trys to connect to the nodes that are listed inside the conf file, without success.
May 13, 2014, 05:43:43 AM
can you post your log file when you start up your client so i can compare?
but edit yout IP first so we can not see it
this would help me a lot, i dont know what else to do.
i have nearly 20 different wallets installed here, this is the only one i got problems with
thanks in advance.
but edit yout IP first so we can not see it
this would help me a lot, i dont know what else to do.
i have nearly 20 different wallets installed here, this is the only one i got problems with
thanks in advance.
Here is my log file with my username and IP addresss XXXX out.
I've left out the coupel of thousand lines as it updated and just gave you the first few and then the bit at the end when I shut it back down
Looking at my log a good IP to put in your conf file is
46.4.113.49
Code:
Cash version v1.1.0.0-g32a928e-CASH ($Format:%cD)
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 05/13/14 09:29:57
Default data directory C:\Users\XXX\AppData\Roaming\Cash
Used data directory C:\Users\XXXX\AppData\Roaming\Cash
dbenv.open LogDir=C:\Users\XXXX\AppData\Roaming\Cash\database ErrorFile=C:\Users\XXXX\AppData\Roaming\Cash\db.log
Bound to [::]:3352
Bound to 0.0.0.0:3352
Loading block index...
LoadBlockIndex(): hashBestChain=0000000037aa9b0cf29a height=160796 trust=285574692246 date=05/12/14 12:37:00
LoadBlockIndex(): synchronized checkpoint 000000004365345806623bc1b1824f1566904b95e80c753dead4d0a7b45d4458
Verifying last 2500 blocks at level 1
block index 77069ms
Loading wallet...
nFileVersion = 70200
wallet 36ms
Loading addresses...
Loaded 3635 addresses from peers.dat 13ms
RandAddSeed() 205780 bytes
mapBlockIndex.size() = 163126
nBestHeight = 160796
setKeyPool.size() = 101
mapWallet.size() = 332
mapAddressBook.size() = 7
Done loading
ThreadRPCServer started
send version message: version 70001, blocks=160796, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0
DNS seeding disabled
ThreadIRCSeed exited
ThreadMessageHandler started
ThreadOpenConnections started
ThreadSocketHandler started
ThreadOpenAddedConnections started
trying connection 206.72.206.148:3352 lastseen=361103.7hrs
ThreadStakeMinter started
CPUMiner started for proof-of-stake
Flushed 3635 addresses to peers.dat 12ms
refreshWallet
ipcThread started
trying connection 183.208.96.222:3352 lastseen=2191.1hrs
GetMyExternalIP() received [XXX.XXX.XXX.XXX] XXX.XXX.XX.XXX:0
GetMyExternalIP() returned XXX.XXX.XXX.XXX
AddLocal(XXX.XXX.XXX.XXX:3352,5)
connection timeout
connection timeout
trying connection 113.162.144.189:3352 lastseen=361103.7hrs
trying connection 176.57.195.78:3352 lastseen=1872.1hrs
connection timeout
connection timeout
trying connection 88.193.92.2:3352 lastseen=361103.7hrs
trying connection 46.4.113.49:3352 lastseen=21.0hrs
connected 46.4.113.49:3352
send version message: version 70001, blocks=160796, us=124.149.90.22:3352, them=46.4.113.49:3352, peer=46.4.113.49:3352
trying connection 78.8.132.230:3352 lastseen=2466.1hrs
Added time data, samples 2, offset -78 (-1 minutes)
receive version message: version 70001, blocks=162011, us=124.149.90.22:12884, them=46.4.113.49:3352, peer=46.4.113.49:3352
received block 000000001080064b4fed
SetBestChain: new best=000000001080064b4fed height=160797 trust=285574697867 date=05/12/14 12:38:12
ProcessBlock: ACCEPTED
received block 000000007f1b5fafbf7b
SetBestChain: new best=000000007f1b5fafbf7b height=160798 trust=285574703479 date=05/12/14 12:41:02
ProcessBlock: ACCEPTED
received block 000000003556cdc74b72
SetBestChain: new best=000000003556cdc74b72 height=160799 trust=285574709003 date=05/12/14 12:43:06
ProcessBlock: ACCEPTED
received block 000000001621c8a0bfe1
SetBestChain: new best=000000001621c8a0bfe1 height=160800 trust=285574714477 date=05/12/14 12:43:52
ProcessBlock: ACCEPTED
received block 0000000043c4de98f82d
SetBestChain: new best=0000000043c4de98f82d height=160801 trust=285574719962 date=05/12/14 12:44:48
ProcessBlock: ACCEPTED
received block 49905e25727392e17095
SetBestChain: new best=0000000024c3d21077f3 height=162009 trust=290517428265 date=05/13/14 09:30:03
SetBestChain: new best=0000000005d747ade2d5 height=162010 trust=290517432924 date=05/13/14 09:30:12
SetBestChain: new best=00000000d19365d0ae63 height=162011 trust=290517437618 date=05/13/14 09:30:14
SetBestChain: new best=0000000093c6e875a0d5 height=162012 trust=290517442352 date=05/13/14 09:30:50
SetBestChain: new best=00000000aa9fb8e64669 height=162013 trust=290517447102 date=05/13/14 09:31:40
ProcessBlock: ACCEPTED
getblocks 161940 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
getblocks 162013 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 30ms
Flush(false)
blkindex.dat refcount=0
blkindex.dat checkpoint
blkindex.dat closed
DBFlush(false) ended 8ms
StopNode()
ThreadMessageHandler exited
ThreadSocketHandler exited
ipcThread exited
connection timeout
ThreadOpenConnections exited
ThreadStakeMinter still running
Flushed 3637 addresses to peers.dat 15ms
Flush(true)
DBFlush(true) ended 0ms
Cash exited
May 12, 2014, 04:21:35 AM
shit i really have to get this working, i need my 0.1 btc back
My conf file is considerably shorter than the one on the front page it is just
rpcuser=user
rpcpassword=x
rpcallowip=192.168.2.*
rpcport=3491
daemon=1
server=1
noirc=1
addnode=206.72.206.148
addnode=113.162.144.189
addnode=88.193.92.2
addnode=94.22.75.142
My home network is 192.168.2.XXX whilst most peoples are 192.168.1.XXX
Try this for your conf file just change the IP range to what ever your home network is.
If that doesn't work and you have other wallets thst sync without a problem I'm out of ideas
May 10, 2014, 09:57:17 PM
thanks for your reply!
my firewall is turned off atm.
here is my Log, i just replaced my IP and Username.
just timeouts everywhere..could it be my router? this is the first coin i have problems with
thanks a lot for helping me.
my firewall is turned off atm.
here is my Log, i just replaced my IP and Username.
just timeouts everywhere..could it be my router? this is the first coin i have problems with
Code:
Cash version v1.1.0.0-g32a928e-CASH ($Format:%cD)
Using OpenSSL version OpenSSL 1.0.1e 11 Feb 2013
Startup time: 05/11/14 01:45:07
Default data directory C:\Users\xxx\AppData\Roaming\Cash
Used data directory C:\Users\xxx\AppData\Roaming\Cash
dbenv.open LogDir=C:\Users\xxx\AppData\Roaming\Cash\database ErrorFile=C:\Users\xxx\AppData\Roaming\Cash\db.log
Bound to [::]:3352
Bound to 0.0.0.0:3352
Loading block index...
LoadBlockIndex(): hashBestChain=00000d868295adeddd8a height=0 trust=1 date=01/20/14 05:43:30
LoadBlockIndex(): synchronized checkpoint 00000d868295adeddd8a03fe13d21b2cde03a2bddbd246e0d76214ebe85244c4
Verifying last 0 blocks at level 1
block index 2ms
Loading wallet...
nFileVersion = 70200
wallet 511ms
Loading addresses...
Loaded 1 addresses from peers.dat 0ms
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
Done loading
ThreadRPCServer started
send version message: version 70001, blocks=0, us=0.0.0.0:0, them=0.0.0.0:0, peer=127.0.0.1:0
refreshWallet
DNS seeding disabled
ThreadIRCSeed exited
ThreadSocketHandler started
ThreadOpenConnections started
ThreadStakeMinter started
CPUMiner started for proof-of-stake
ThreadMessageHandler started
ThreadOpenAddedConnections started
trying connection 206.72.206.148:3352 lastseen=361048.0hrs
Flushed 1 addresses to peers.dat 3ms
ipcThread started
GetMyExternalIP() received [XX.XX.XXX.XX] XX.XX.XXX.XX:0
GetMyExternalIP() returned XX.XX.XXX.XX
AddLocal(XX.XX.XXX.XX:3352,5)
trying connection 217.157.9.88:3352 lastseen=213.6hrs
connection timeout
trying connection 113.162.144.189:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.6hrs
connection timeout
trying connection 88.193.92.2:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.6hrs
connection timeout
trying connection 94.22.75.142:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.6hrs
connection timeout
trying connection 66.41.129.114:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.6hrs
connection timeout
trying connection 94.22.75.142:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.6hrs
connection timeout
trying connection 178.121.113.206:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.6hrs
connection timeout
trying connection 79.194.121.2:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.6hrs
connection timeout
trying connection 116.17.92.174:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.6hrs
connection timeout
trying connection 83.67.76.64:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.6hrs
connection timeout
trying connection 5.83.21.59:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 184.155.114.216:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 174.111.248.128:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 84.29.45.140:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 109.166.140.147:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 109.99.33.117:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 84.111.156.162:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 84.29.45.140:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 84.29.45.140:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
Flushed 1 addresses to peers.dat 3ms
connection timeout
trying connection 66.183.28.149:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 107.170.6.29:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 109.90.51.38:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 218.207.182.254:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 86.91.247.175:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 178.49.118.233:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 91.215.16.155:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 108.226.116.149:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 66.41.129.114:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 24.14.239.132:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 78.61.244.154:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 78.26.128.199:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 86.129.44.37:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 113.162.144.189:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 184.75.214.242:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 180.151.127.68:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 94.34.176.169:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 86.29.180.98:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
Flushed 1 addresses to peers.dat 3ms
connection timeout
trying connection 113.162.170.108:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 110.147.174.243:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 77.172.93.38:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 65.78.111.167:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 74.3.157.1:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 67.191.160.195:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 180.136.200.9:3352 lastseen=361048.0hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
connection timeout
trying connection 217.157.9.88:3352 lastseen=213.7hrs
thanks a lot for helping me.
May 11, 2014, 11:08:54 AM
Odd, you haven't got any rules on your router blocking ports have you?
Might be worth backing up your wallet, uninstalling it and reinstalling it and then restoring you old wallet and see what happens
Might be worth backing up your wallet, uninstalling it and reinstalling it and then restoring you old wallet and see what happens
May 10, 2014, 08:05:09 PM
Hi Cash Folks,
I cant sync my wallet somehow
got the .conf file from page 1..
any ideas what im doing wrong?
I cant sync my wallet somehow
got the .conf file from page 1..any ideas what im doing wrong?
May 11, 2014, 01:01:02 AM
It might be a silly question, but do you havethe conf file in the correct place?
I'm assuming you are running windows, if you are running Linux or Mac it will be different to this.
Click on your start bar and in the search window on your in your start menu type in
%appdata%
the percentage signs are important.
This will open up windows explorer with the following directory
C:\Users\XXXX\AppData\Roaming
Instead of XXXX it will be your user name for windows
Now look and you should see the subdirectory 'Cash'
Copy the file there and make sure its name is cash.conf, not cash.conf.txt which can happen if you use windows text editor
Cash is one of the coins I've never had troubles to get to sync
I'm assuming you are running windows, if you are running Linux or Mac it will be different to this.
Click on your start bar and in the search window on your in your start menu type in
%appdata%
the percentage signs are important.
This will open up windows explorer with the following directory
C:\Users\XXXX\AppData\Roaming
Instead of XXXX it will be your user name for windows
Now look and you should see the subdirectory 'Cash'
Copy the file there and make sure its name is cash.conf, not cash.conf.txt which can happen if you use windows text editor
Cash is one of the coins I've never had troubles to get to sync
May 10, 2014, 08:40:25 PM
Hi Cash Folks,
I cant sync my wallet somehow got the .conf file from page 1..
any ideas what im doing wrong?
I cant sync my wallet somehow
got the .conf file from page 1..any ideas what im doing wrong?
When you initially installed the wallet did you say yes to letting it through your firewall?
Have you installed the conf file in the correct folder?
It will also take a minute or two before it starts syncing whilst it connects to other nodes
May 08, 2014, 02:06:47 PM
Maybe you do not know enough about PoS. The number one objective is to get wallets open as long as poss., otherwise there is no robust network.
High % encourages that, and tapering ensures that the inflation effect is only temporary. Min. one day means that holders see some rapid action, and MAX 7 days ensures that wallets open more frequently.
*sigh*
Go to page one of this thread and look at the second line in the first post from the dev and you will see him thanking me for putting together the screen captures and the descriptions on how POS works
Go to the second last post on page 118 where I explain why its better for security of the coin not to group all your coins into just a couple of large amounts.
I am not a coder, but I do understand the principles.
OK, I read those, and all correct of course.... but it doesn't address (and is not relevant to) my points about % PoS and Min/Max coin age. (BTW, I wrote , rewrote, the OP, and website at an earlier stage, for the dev). Coin Control is another matter, and a weighting column is useful there to show the imminent forthcoming stakes at a glance.
The balance between PoW and PoS is really the only question, and my assumption is that PoW will decline in importance as PoS holders take up maintenance of the network. This would be desirable for energy considerations as well as the weight of GPUs which will be deployed on coins such as CASH when Scrypt ASICS appear.
May 08, 2014, 07:58:40 AM
Maybe you do not know enough about PoS. The number one objective is to get wallets open as long as poss., otherwise there is no robust network.
High % encourages that, and tapering ensures that the inflation effect is only temporary. Min. one day means that holders see some rapid action, and MAX 7 days ensures that wallets open more frequently.
*sigh*
Go to page one of this thread and look at the second line in the first post from the dev and you will see him thanking me for putting together the screen captures and the descriptions on how POS works
Go to the second last post on page 118 where I explain why its better for security of the coin not to group all your coins into just a couple of large amounts.
I am not a coder, but I do understand the principles.
May 08, 2014, 07:43:16 AM
A fork is needed, and sooner rather than later. There is huge competition from new coins with better PoS spec.
In a Fork, I would recommend changing coin age to Min 1 day, Max 7 days, 200% stake in year 1, tapering down.
Forking it is not as simple as just finding someone to host the checkpoint server and modifying the code.
You also need to get all the mining pools and exchanges onside and get them to all to agree to update their wallets, then you need all the users to do it.
It goes without saying you need to know the wallet will be rock solid before releasing it too.
Also even though the dev doesn't post he is keeping the checkpoint up to date, so he could still at any moment come back and request the exchanges not to accept a take ver as its his coin which would stop it all.
If you can get that all to happen then that would be great, but it involves people putting in a lot of effort..
Setting the stake to 1 day and setting it to 200% interest for the first year would completely kill the coin in my opinion.
The whole reason of POS is to get people to hold it in their wallets, if you only need to hold it for a day to get your stake and interest at 200% PA you would have to completely get rid of mining which would mean more radical changing of the source, I also believe it would still lead to rapid devaluation of the coin.
The whole concept of this coin was to keep its value balanced.
Maybe you do not know enough about PoS. The number one objective is to get wallets open as long as poss., otherwise there is no robust network.
High % encourages that, and tapering ensures that the inflation effect is only temporary. Min. one day means that holders see some rapid action, and MAX 7 days ensures that wallets open more frequently.
May 08, 2014, 06:54:41 AM
A fork is needed, and sooner rather than later. There is huge competition from new coins with better PoS spec.
In a Fork, I would recommend changing coin age to Min 1 day, Max 7 days, 200% stake in year 1, tapering down.
Forking it is not as simple as just finding someone to host the checkpoint server and modifying the code.
You also need to get all the mining pools and exchanges onside and get them to all to agree to update their wallets, then you need all the users to do it.
It goes without saying you need to know the wallet will be rock solid before releasing it too.
Also even though the dev doesn't post he is keeping the checkpoint up to date, so he could still at any moment come back and request the exchanges not to accept a take ver as its his coin which would stop it all.
If you can get that all to happen then that would be great, but it involves people putting in a lot of effort..
Setting the stake to 1 day and setting it to 200% interest for the first year would completely kill the coin in my opinion.
The whole reason of POS is to get people to hold it in their wallets, if you only need to hold it for a day to get your stake and interest at 200% PA you would have to completely get rid of mining which would mean more radical changing of the source, I also believe it would still lead to rapid devaluation of the coin.
The whole concept of this coin was to keep its value balanced.
May 07, 2014, 07:57:07 PM
have no doubt mullick built this coin, the OP is some kid who knows FA about anything.... people say it is is probably some relation to vern.
Forget the "dev" that's some kid, if you want the coin to go anywhere then community leadership is required.
Forget the "dev" that's some kid, if you want the coin to go anywhere then community leadership is required.
I have backed up all the sources and created another copy, just in case old CODE disapears, you can find it here: https://www.dropbox.com/sh/qsoszqtvk60l55c/Peu4eVvSbc
I am sure this coin will be soon forked, It is like a gold in a dust, very cheap, traded on Cryptsy, very nice and someone is buying it a lot. There is a thread on bitcointalk where some pro devs are saving abondoned coins, so in case CASH dev does not return, it is easy to write them, they will take care of it.
A fork is needed, and sooner rather than later. There is huge competition from new coins with better PoS spec.
In a Fork, I would recommend changing coin age to Min 1 day, Max 7 days, 200% stake in year 1, tapering down.
May 07, 2014, 11:28:15 AM
For those having problems with wallet syncing, I asked at Cryptsy for their CASH wallet IP node. Their replied, they can't tell me IP for security reasons, but that they are running alternative NODE on altexplorer.info, so the node to sync the wallet is: 50.7.135.34
May 07, 2014, 06:33:10 AM
have no doubt mullick built this coin, the OP is some kid who knows FA about anything.... people say it is is probably some relation to vern.
Forget the "dev" that's some kid, if you want the coin to go anywhere then community leadership is required.
Forget the "dev" that's some kid, if you want the coin to go anywhere then community leadership is required.
I have backed up all the sources and created another copy, just in case old CODE disapears, you can find it here: https://www.dropbox.com/sh/qsoszqtvk60l55c/Peu4eVvSbc
I am sure this coin will be soon forked, It is like a gold in a dust, very cheap, traded on Cryptsy, very nice and someone is buying it a lot. There is a thread on bitcointalk where some pro devs are saving abondoned coins, so in case CASH dev does not return, it is easy to write them, they will take care of it.
May 07, 2014, 06:27:49 AM
have no doubt mullick built this coin, the OP is some kid who knows FA about anything.... people say it is is probably some relation to vern.
Forget the "dev" that's some kid, if you want the coin to go anywhere then community leadership is required.
Forget the "dev" that's some kid, if you want the coin to go anywhere then community leadership is required.
May 07, 2014, 06:19:37 AM
is still a DEV for this coin or have they run away again
Is there any one who know how we can do a community take over of CASH
Is there any one who know how we can do a community take over of CASH
People do not be scared, CASH is alive. I asked BitJohn about delisting coins and he told me, they will not delist any coin until it has not some really serious issues with blockchain. I asked him about coins like Lk7, BEN, which are 100x more dead tha CASH and he told me, that they will not delist them, since they have no bugs. So CASH is alive and yesterday was pumped to 2000 satoshis. There is a whale who bought CASH worth of 4 BTC and I see another 3.5 BTC buy orders on CASH. Something big will happen. Since CASH has public source code, anyone can be new developer, there is no need to be worry, just because original dev is not responding, it doesn't mean, new developer can't fork it and continue with new Coin web/Thread, etc. If you have problems with wallet synchronization, just open cryptsy support ticket and ask for their node IP, since CASH is traded on CRYPTSY and their will not delist CASH, CASH blockchain is alive and so is CASH. I am gonna to make copy of that GitHub repository, so if something happen, I will be able to publish the copy of that source.
May 04, 2014, 04:35:48 AM
Well Dev I see you have found time to sort out the checkpoint, but not post here, on your facebook page or your home page, so the only possible reason I can think of you not posting here is to drive the price of cash down as low as possible to buy up heaps before 'reappearing' to raise the price back up and make yourself a tidy profit and everyone else's expense.
Please tell me I'm wrong, though I will take some convincing as your reappearance drove the price up to 45,000 and since you have been quiet it is now down to 635.
I'm guessing if this continues Cash will be de-listed and die within 2 or 3 weeks.
Please tell me I'm wrong, though I will take some convincing as your reappearance drove the price up to 45,000 and since you have been quiet it is now down to 635.
I'm guessing if this continues Cash will be de-listed and die within 2 or 3 weeks.
couldn't agree more
i think that to bro
can u recomend to me what coin is good for mining now?
I'm just using multipool at the moment and buying zeit with it.
Zeitcoin is now 100% POS so you can no longer mine it, but it 25% POS.
I still like Vertcoin but don't mine it now except for when the difficulty drops but hold a small amount of it as once the ASIC miners are all out I think a lot of the GPU miners may move to coins like Vert.
I also hold feathercoins as they are usually good for buying and selling and making small but steady profit on.
I think its all a bit of unknown territory at the moment though as I'm not sure what the massive influx of ASIC miners that is coming will do to all the alt coins.
Jump to: