Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1119. (Read 3058816 times)

test for about 15 min , and how to set the data folder , use -datadir = D:\\coin ,  nothing happened

http://www.whattomine.com/
dgb qubit and skein are 8 and 9.

so . now i can't find digibyte the top 100 coins ..

That is great to hear! Thanks for letting us know!

Done, 18 minutes.

https://www.cryptocoinsnews.com/chinese-government-official-believes-bitcoin-can-coexist-government-money/

I have a test deposit into cryptsy, will pipe up when complete.

Okay i got contact with cryptsy,
The wallet is having updates. So nothing on Digibytes side.
It is still in maintenance but you can now send/receive Digibytes

Bought some more DGB just need Cryptsy to finish maintenance and then I can withdraw Long live DGB

Hi, I have set up a new p2pool node for mining DGB Qubit:

http://104.131.153.196:5041/static/

P2Pool is a descentralized mining, so you earn coins directly in your wallet.
You must use miners that support Qubit algorithm.

Thanks ! Happy mining.

Quite big 

I said 157K marketcap not satoshis... big difference

I'm kind of in and out all day today, and I've been letting it run, but, no, it still hasn't budged. (I have another install on a laptop that "was taking its time", but did fully sync.)

I was taking a look at the nodes I was connecting to using getpeerinfo, and I remembered I had a previously configured digibyte.conf file in use. I am going to rename so it doesn't load, and I'll let you know.


Add: I just got a "you need to reconstruct the database being used - reindex to change - twindex" message (I've translated so that might not be the exact wording in English). I've accepted, and it's reindexing.

Add2: I've got a perfect sync.

In case it's of interest, this is the conf file I was using:


I'm inclined to think that checkpoints=1 was the culprit . . .

A quick domain to IP search for Cryptsy shows their IP is: 199.83.131.5 and 199.83.134.5

We do not see those IP's on any of our seed node "getpeerinfo" lists. But this does not mean they don't run their wallets from a separate server (which is more secure & most likely.)

Transactions are working as expected, the network is moving along as expected.

I have been watching for sometime and I think sell pressure is still there but much lower than the old scheme.
This is great to see balancing the miners short term profit (at the cost of providing security to network) and investors benefit (longer term believers) in some way.

Regarding to the issue, cryptsy has already been in maintenance mode for 2-3 days?
Maybe they are having issues with something else, not DGB related?

[
{
"addr" : "[2001:0:5ef5:79fd:1c2e:32b2:a5f8:6d4f]:56424",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547490,
"lastrecv" : 1418547515,
"bytessent" : 443600,
"bytesrecv" : 606855,
"conntime" : 1418403137,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : true,
"startingheight" : 405746,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "212.129.1.77:12024",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547490,
"lastrecv" : 1418547515,
"bytessent" : 217956,
"bytesrecv" : 1532338,
"conntime" : 1418432124,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : false,
"startingheight" : 406719,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "188.165.223.132:12024",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547515,
"lastrecv" : 1418547515,
"bytessent" : 244219,
"bytesrecv" : 2619333,
"conntime" : 1418432141,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : false,
"startingheight" : 406719,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "68.15.110.38:12024",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547515,
"lastrecv" : 1418547515,
"bytessent" : 182329,
"bytesrecv" : 1134098,
"conntime" : 1418432203,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : false,
"startingheight" : 406721,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "216.250.125.121:12024",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547456,
"lastrecv" : 1418547515,
"bytessent" : 183710,
"bytesrecv" : 1826721,
"conntime" : 1418432244,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : false,
"startingheight" : 406722,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "74.208.230.160:12024",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547457,
"lastrecv" : 1418547515,
"bytessent" : 160172,
"bytesrecv" : 1863171,
"conntime" : 1418432244,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : false,
"startingheight" : 406722,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "[2001:0:9d38:6abd:da:3314:b592:fa6c]:58530",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547515,
"lastrecv" : 1418547515,
"bytessent" : 392714,
"bytesrecv" : 323362,
"conntime" : 1418449303,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : true,
"startingheight" : 407293,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "[2001:0:9d38:6ab8:2402:218b:ed90:9492]:57307",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547515,
"lastrecv" : 1418547490,
"bytessent" : 332073,
"bytesrecv" : 565847,
"conntime" : 1418455897,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : true,
"startingheight" : 407507,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "92.222.28.13:12024",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547515,
"lastrecv" : 1418547515,
"bytessent" : 104750,
"bytesrecv" : 493885,
"conntime" : 1418486855,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : false,
"startingheight" : 408532,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "94.23.31.223:12024",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547490,
"lastrecv" : 1418547515,
"bytessent" : 91979,
"bytesrecv" : 503973,
"conntime" : 1418507534,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : false,
"startingheight" : 409222,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "[2001:0:5ef5:79fd:20ec:3bb8:a9ed:b33a]:49739",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547490,
"lastrecv" : 1418547515,
"bytessent" : 179090,
"bytesrecv" : 113420,
"conntime" : 1418527099,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : true,
"startingheight" : 409859,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "198.100.146.216:12024",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547515,
"lastrecv" : 1418547515,
"bytessent" : 69454,
"bytesrecv" : 307635,
"conntime" : 1418528887,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : false,
"startingheight" : 409933,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "[2001:0:5ef5:79fd:189c:54d:3de2:c1c2]:61192",
"addrlocal" : "115.166.10.121:12024",
"services" : "00000001",
"lastsend" : 1418547515,
"lastrecv" : 1418547515,
"bytessent" : 116946,
"bytesrecv" : 12930,
"conntime" : 1418544549,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : true,
"startingheight" : 410438,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "[2001:0:5ef5:79fd:2878:fbff:57c0:c3e2]:55403",
"addrlocal" : "[2001:0:9d38:6abd:2c49:1c0:8c59:f586]:12024",
"services" : "00000001",
"lastsend" : 1418547515,
"lastrecv" : 1418547515,
"bytessent" : 79831,
"bytesrecv" : 75969,
"conntime" : 1418546367,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/DigiByte:3.0.3/",
"inbound" : true,
"startingheight" : 410500,
"banscore" : 0,
"syncnode" : false
}
]

Well, let's check. Here is Cryptsy deposit transaction with 8125 confirmations:



but not deposited to Cryptsy. All subsequent transactions are stuck too.

This transaction included in block >400000 and I suppose it is not hardfork issue. Maybe Cryptsy (and Bittrex?) really in maintenance for DGB now.

https://cryptsy.freshdesk.com/support/home

they have good support
I liked it 

+1

We are seeing a lot of wallets in maintenance mode on Cryptsy as well. The DigiByte network appears to be working great. There were a few people still mining on the old chain, but this was to be expected after the hard fork.

cryptsy in maintenance, tryed to contact a admin/chatbox admin but i did not get any response.
I also see on the exchange that there are allot of wallets in maintenance mode.  maybe some server issues?