Bitcoin Forum
October 19, 2017, 05:41:03 AM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 »
  Print  
Author Topic: [ANN] Philosopherstone - PHS | No Premine | Mandatory update 1.2Beta3  (Read 78688 times)
A L I E N
Hero Member
*****
Offline Offline

Activity: 756

Better now than never.


View Profile
August 09, 2013, 08:09:35 PM
 #381

digeros, what block is your client on?

We are currently at 8415:

{
"blocks" : 8415,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.75582133,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 26487206,
"pooledtx" : 0,
"testnet" : false
}

Yes use a lot of nodes once you are synced, but too many bad nodes can make you download the wrong chain or unable to sync.

Edit: Digeros, you must be on the same chain as us since your nodes are the same as mine. (Again, I think this is the correct/official chain)

CHANGE FINANCE First Decentralised Global Crypto Bank
LINK TO ICO | LINK TO DISCUSSION
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
r3wt
Hero Member
*****
Offline Offline

Activity: 686


always the student, never the master.


View Profile
August 09, 2013, 08:18:43 PM
 #382

you guys, i would like to make a public apology to Moray, who returned my litecoins earlier! now please fix this coins so that i can get my PHS and Moray can get his Litecoins!

My negative trust rating is reflective of a personal vendetta by someone on default trust.
Molitor
Member
**
Offline Offline

Activity: 70



View Profile
August 09, 2013, 08:22:17 PM
 #383

I am on Windows too and on the same chain as Trid (which I believe is correct).  We are synced and network hash is increasing.

{
"blocks" : 8390,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.16889024,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 41726100,
"pooledtx" : 0,
"testnet" : false
}


I think the nethash you guys are seeing at 6100 is the historical quote, ie the networkhash was ~71mh/s on that block when it was made but no one is mining at that block currently (I don't think you could, but not 100% sure).

Has anyone tried to create a new wallet.dat and connect direct to a node?  If that was able to sync, then you could dump your private keys and import them into the working wallet.



I redownloaded 1.2; got rid of everything except the .conf which contained only the single line "connect=188.252.16.109" and with one connection, it goes fine until it hits 6084; est. total blocks 4193. Then the log chokes slowly with those ERROR: CheckProofOfStake() things. It's consuming 0% CPU, so it's not doing much. Also, the greenbar disappears, but I never get the green checkmark, and it still says (out of sync).

Plus, I've mined on the 6084 fork and got some blocks, about 10x faster than I should, which obviously means this is the correct fork. Wink

Gonna reredownload 1.2 from another source, maybe one is corrupted.

I wouldn't trust just one connection... use a bunch of nodes then the nodes have to aggree on the blockchain... here are my current connection IP  add to config file

addnode=24.16.169.96
addnode=188.252.16.109
addnode=72.23.76.121
addnode=46.150.89.173
addnode=198.50.233.22
addnode=188.81.161.38
addnode=64.120.17.149
addnode=50.149.211.203
addnode=46.229.50.42
addnode=81.27.169.82
addnode=81.105.30.173
addnode=24.6.21.198
addnode=183.187.168.120
addnode=184.88.62.170


I usually do, but I was just running a single test. Fresh everything and only your addnodes gives me about 17 connections:

{
"blocks" : 6465,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.34124814,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 10302732,
"pooledtx" : 0,
"testnet" : false
}


Then it stalls with a ton of these:

getblocks 5808 to 00000000000000000000 limit 500
  getblocks stopping at limit 6307 00000002169a80613373
getblocks 5804 to 00000000000000000000 limit 500
  getblocks stopping at limit 6303 000000016d0641fca5a3
getblocks 5304 to 00000000000000000000 limit 500
  getblocks stopping at limit 5803 000000008aadecc2c12f


Est. Total Blocks is 8408, so that's something. It looks like it's creeping slowly in the right direction, but it's done that before and reverted, so we'll see. I'm just gonna let it sit for a few.



bholzer
Hero Member
*****
Offline Offline

Activity: 490

The Murraycoin Project ▪ Lead Developer


View Profile WWW
August 09, 2013, 08:45:38 PM
 #384

I am on Windows too and on the same chain as Trid (which I believe is correct).  We are synced and network hash is increasing.

{
"blocks" : 8390,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 1.16889024,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 41726100,
"pooledtx" : 0,
"testnet" : false
}


I think the nethash you guys are seeing at 6100 is the historical quote, ie the networkhash was ~71mh/s on that block when it was made but no one is mining at that block currently (I don't think you could, but not 100% sure).

Has anyone tried to create a new wallet.dat and connect direct to a node?  If that was able to sync, then you could dump your private keys and import them into the working wallet.



I can mine at the 6100 fork...and it even confirms found blocks pretty quickly. People are definitely mining on both.

murrayCOIN The Only Currency Worthy of the NameBitcointalk Thread BTC: 1KY5kptnac4HLbF9Rn1Y6J8wPrM734db42
sheinsha
Sr. Member
****
Offline Offline

Activity: 420


View Profile WWW
August 09, 2013, 09:20:20 PM
 #385

I think we need another client update with checkpoints updated on every fork we know exists, that way we should be able to get all on the same chain.
The problem is, which one is the correct one, because there are many that are mining pretty fast on more than one fork. And all will be pissed if they were not on the right one.

Minar.cc | DMD Diamond Coin Pool: dmd.minar.cc | CGB CryptogenicBullion Coin Pool: cgb.minar.cc | PHS Philosopherstone Coin Pool: phs.minar.cc | KDS Kudos Pool: kds.minar.cc | CRC CraftCoin Pool: crc.minar.cc | CIN Cinnamon Coin Pool: cin.minar.cc | PXL PXLCoin Pool: pxl.minar.cc | TAG TagCoin Pool: tag.minar.cc | BAC BaseCoin Pool: bac.minar.cc | STR Star Coin Pool: str.minar.cc | JPC Jupiter Coin Pool: jpc.minar.cc
xavenged
Member
**
Offline Offline

Activity: 104


View Profile
August 09, 2013, 09:22:29 PM
 #386

so version 1.1 syncs all the way up to current block 8444... 1.2 does not
sheinsha
Sr. Member
****
Offline Offline

Activity: 420


View Profile WWW
August 09, 2013, 09:27:16 PM
 #387

so version 1.1 syncs all the way up to current block 8444... 1.2 does not
Let me check the client code that was updated, maybe it broke some earlier checkpoint, i dont know.

Minar.cc | DMD Diamond Coin Pool: dmd.minar.cc | CGB CryptogenicBullion Coin Pool: cgb.minar.cc | PHS Philosopherstone Coin Pool: phs.minar.cc | KDS Kudos Pool: kds.minar.cc | CRC CraftCoin Pool: crc.minar.cc | CIN Cinnamon Coin Pool: cin.minar.cc | PXL PXLCoin Pool: pxl.minar.cc | TAG TagCoin Pool: tag.minar.cc | BAC BaseCoin Pool: bac.minar.cc | STR Star Coin Pool: str.minar.cc | JPC Jupiter Coin Pool: jpc.minar.cc
digeros
Sr. Member
****
Offline Offline

Activity: 280



View Profile
August 09, 2013, 09:29:23 PM
 #388

so version 1.1 syncs all the way up to current block 8444... 1.2 does not

I have been running V 1.2 since it was released and have been connect to the PHS network for the last week with a mining wallet and a retaining wallet on another computer  - both agree on block @8444 now

and I think that I have been connected to the network by a large number of peers @50 on average in the early days to @ 25 now.  so, I doubt that My blockchain is the forked one.
digeros
bholzer
Hero Member
*****
Offline Offline

Activity: 490

The Murraycoin Project ▪ Lead Developer


View Profile WWW
August 09, 2013, 09:30:47 PM
 #389

The problem is, which one is the correct one, because there are many that are mining pretty fast on more than one fork. And all will be pissed if they were not on the right one.

This is a major problem -- especially since the dev has pretty much checked out and doesn't seem to care. No matter what, a lot of people will get screwed here...but now this has been going on for way too long. This is one of the worst responses I've seen yet this early in a currency's life. Basically, people will be pissed, exchanges will be put-off, people will lose coins, and we're rapidly losing confidence in the dev team. Value is going to get slaughtered here.

I think you'd have to be nuts to still be mining at this point - even if you happen to be on the correct chain and PHS survives it likely won't be worth mining for a while.

murrayCOIN The Only Currency Worthy of the NameBitcointalk Thread BTC: 1KY5kptnac4HLbF9Rn1Y6J8wPrM734db42
bholzer
Hero Member
*****
Offline Offline

Activity: 490

The Murraycoin Project ▪ Lead Developer


View Profile WWW
August 09, 2013, 11:52:14 PM
 #390

If anybody is interested in buying 21,000 pre-fork PHS (which is guaranteed) I'll throw in another 15,000 post-fork PHS (which could potentially become orphaned - it's on the 7000 chain.)

The dev's lack of involvement in this discussion means I'm walking away. Make me an offer - could end up being a steal.

murrayCOIN The Only Currency Worthy of the NameBitcointalk Thread BTC: 1KY5kptnac4HLbF9Rn1Y6J8wPrM734db42
digeros
Sr. Member
****
Offline Offline

Activity: 280



View Profile
August 10, 2013, 01:06:03 AM
 #391

digeros, what block is your client on?

We are currently at 8415:

{
"blocks" : 8415,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.75582133,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 26487206,
"pooledtx" : 0,
"testnet" : false
}

Yes use a lot of nodes once you are synced, but too many bad nodes can make you download the wrong chain or unable to sync.

Edit: Digeros, you must be on the same chain as us since your nodes are the same as mine. (Again, I think this is the correct/official chain)

update:


{
"blocks" : 8544,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.47088875,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 15196882,
"pooledtx" : 0,
"testnet" : false
}


so I am only supplying 1/15th of the mining hash rate so I could not have created a fork.

RUning Version 1.2 since the launch
xavenged
Member
**
Offline Offline

Activity: 104


View Profile
August 10, 2013, 01:32:46 AM
 #392

40k+ phs for sale... 35k are pre-fork/ before all this bullshit. im walking away from this one also.. devs lack of involvement on resolving this issue is ridiculous
2Kool4Skewl
Sr. Member
****
Offline Offline

Activity: 392


Suretified Jeanius


View Profile
August 10, 2013, 02:28:01 AM
 #393

I deleted the blockchain, added the suggested nodes and I am attempting to resync.  Stuck at 6084 like everyone else.

xavenged
Member
**
Offline Offline

Activity: 104


View Profile
August 10, 2013, 02:29:11 AM
 #394

I deleted the blockchain, added the suggested nodes and I am attempting to resync.  Stuck at 6084 like everyone else.

delete the blockchain and fire up 1.0 or 1.1 and see if you get further than 6084
Molitor
Member
**
Offline Offline

Activity: 70



View Profile
August 10, 2013, 02:44:24 AM
 #395

I deleted the blockchain, added the suggested nodes and I am attempting to resync.  Stuck at 6084 like everyone else.

delete the blockchain and fire up 1.0 or 1.1 and see if you get further than 6084

Funny thing. Last night when the trouble started, I cashed out my pool balance, and I never saw it on any of the blockchains, even when I got up in the ~8000s. I thought it was lost in the ethers, but when I fired up 1.0 up a few minutes ago, it showed up and confirmed. So now I'm all happily synced, 7 connections, the logfile isn't a wall of errors, and all's right with the world. It looks like the Titanic has settled on the bottom of the sea...


{
"blocks" : 8598,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.76224760,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 30350697,
"pooledtx" : 0,
"testnet" : false
}


The last 20 or so blocks took a long time to sync.

Edit: the last mining transaction that showed up was 8/9/13 21:51 U.S. Eastern Time.

2Kool4Skewl
Sr. Member
****
Offline Offline

Activity: 392


Suretified Jeanius


View Profile
August 10, 2013, 02:47:02 AM
 #396

I deleted the blockchain, added the suggested nodes and I am attempting to resync.  Stuck at 6084 like everyone else.

delete the blockchain and fire up 1.0 or 1.1 and see if you get further than 6084

I pulled 1.2 from github and I don't have the source for 1.0 or 1.1 anymore.  Does anyone have a link to 1.0 or 1.1 source?

xavenged
Member
**
Offline Offline

Activity: 104


View Profile
August 10, 2013, 02:50:03 AM
 #397

I deleted the blockchain, added the suggested nodes and I am attempting to resync.  Stuck at 6084 like everyone else.

delete the blockchain and fire up 1.0 or 1.1 and see if you get further than 6084

I pulled 1.2 from github and I don't have the source for 1.0 or 1.1 anymore.  Does anyone have a link to 1.0 or 1.1 source?

sorry im running the windows versions
Molitor
Member
**
Offline Offline

Activity: 70



View Profile
August 10, 2013, 02:51:09 AM
 #398

I deleted the blockchain, added the suggested nodes and I am attempting to resync.  Stuck at 6084 like everyone else.

delete the blockchain and fire up 1.0 or 1.1 and see if you get further than 6084

I pulled 1.2 from github and I don't have the source for 1.0 or 1.1 anymore.  Does anyone have a link to 1.0 or 1.1 source?

I think I have 1.1 or 1.0. I pulled the zip from my garbage can, and it doesn't identify the version.

EDIT: 1.0?
#define DISPLAY_VERSION_MAJOR       1
#define DISPLAY_VERSION_MINOR       0
#define DISPLAY_VERSION_REVISION    0
#define DISPLAY_VERSION_BUILD       0
2Kool4Skewl
Sr. Member
****
Offline Offline

Activity: 392


Suretified Jeanius


View Profile
August 10, 2013, 02:56:49 AM
 #399

I deleted the blockchain, added the suggested nodes and I am attempting to resync.  Stuck at 6084 like everyone else.

delete the blockchain and fire up 1.0 or 1.1 and see if you get further than 6084

I pulled 1.2 from github and I don't have the source for 1.0 or 1.1 anymore.  Does anyone have a link to 1.0 or 1.1 source?

I think I have 1.1 or 1.0. I pulled the zip from my garbage can, and it doesn't identify the version.


Compile it and check the version.  If it isn't 1.2, can you post it somewhere?

A L I E N
Hero Member
*****
Offline Offline

Activity: 756

Better now than never.


View Profile
August 10, 2013, 02:58:06 AM
 #400

I deleted the blockchain, added the suggested nodes and I am attempting to resync.  Stuck at 6084 like everyone else.

delete the blockchain and fire up 1.0 or 1.1 and see if you get further than 6084

I pulled 1.2 from github and I don't have the source for 1.0 or 1.1 anymore.  Does anyone have a link to 1.0 or 1.1 source?

I think I have 1.1 or 1.0. I pulled the zip from my garbage can, and it doesn't identify the version.


Can you update to v1.2 now that you have the block chain and still stay synced?

CHANGE FINANCE First Decentralised Global Crypto Bank
LINK TO ICO | LINK TO DISCUSSION
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 [20] 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!