★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit

[pringles1901]

perhaps we should get Jared to approach this site & ask them to add DGB

https://p2pwallet.cc/

[pringles1901]

i am sorry if i seem a little worried about the price drop i now have rather a lot in DGB more than i planned & i would like to see some sort of price stability, as it stands since the hard fork & the investment DGB seems to be in a far worse place than before

I have enough BTC to pump this baby up & TBH get out but as i have been informed a pump is not whats needed, maybe then all you wise investors could point me in the direction of what is needed to make the price move up a little or at least stabilize to a set price.

I am all eyes & ears to any suggestion you all may have

I don't like to speak about the actual value of DGB because we (the fairly supporters/investors) are here for the long haul... BUT I agree that DGB has been and is actually too much undervalued.

Digibyte team doesn't want a simple pump, because this will create an artificial growth of its market. But regarding the market cap, it will be kinda easy for some BTC holders who have interests in seeing DGB price going up to make a regular increase, for few days/weeks... in order to give more attention to this market.

Doing a pump alone will not be profitable for sure... but what about doing it in a group of investors who will be able to planned this regular increase (for exemple to 40 satoshis in 2 weeks for a first step)? And this can be easily improved by doing it when the time is coming for a new great announcement. The thing is that more people will join into DGB community when its price/market cap will growth... as well as everything which is arround the coin... BUT if DGB will hit a critical point (let's say @10 satoshi), it will be hard to give it to the moon one day because the market will kill DGB before the team will have the time to implement everything they are working on.

I don't know what you think about what i'm saying, but even if Digibyte team doesn't want a simple pump, I would be glad to know what they think about a regular increase day after day, artificially made by investors themselves, but which will improved the market health if it will be done properly, in GROUP.

I agree something needs to be done to stop this going down to low, its a bit like owning a retail store once you lose customers its much harder to get them to come back...meaning if DGB has no support & the price drops down below 10 sats the interest in it will have gone & so will any new investors want to buy into it....we long haul will still be around but thats not going to be much use in the longterm

[HR]

I'm experiencing a sync issue with v3.0.3.0-g354c0f3-MultiAlgo (64-bit) running on Windows 7, SP1.

Stuck on 406312.

[24hralttrade]

I'm experiencing a sync issue with v3.0.3.0-g354c0f3-MultiAlgo (64-bit) running on Windows 7, SP1.

Stuck on 406312.

Starting computer and wallet now.   Running same windows.

[MadGhost]

May be someone can post nodes so that it will be synced.

[bogglor]

I'm experiencing a sync issue with v3.0.3.0-g354c0f3-MultiAlgo (64-bit) running on Windows 7, SP1.

Stuck on 406312.

Looks like you're on the "old" blockchain. It was stuck at 406312 at the time you posted this. It's on 406314 now. Seems to be a scrypt miner still mining on the old wallet.

Try deleting and re-downloading the blockchain with the new wallet.

[24hralttrade]

I'm experiencing a sync issue with v3.0.3.0-g354c0f3-MultiAlgo (64-bit) running on Windows 7, SP1.

Stuck on 406312.

Starting computer and wallet now.   Running same windows.

Fully synced.  receiving Digibytes from android app.

[ReSl]

Im sync on Win7x64SP1. Transactions work fine.
Please resync your blockchain.

[Ivanech]

Please suggest me the working exchange for DGB at this moment.

I noticed both Cryptsy and Bittrex have deposit issues after hardfork.

[DigiByte]

I'm experiencing a sync issue with v3.0.3.0-g354c0f3-MultiAlgo (64-bit) running on Windows 7, SP1.

Are you still having a sync issue? We just checked the seed nodes to make sure they are working as expected.

[24hralttrade]

Please suggest me the working exchange for DGB at this moment.

I noticed both Cryptsy and Bittrex have deposit issues after hardfork.

CEX.io ?

[DigiByte]

Please suggest me the working exchange for DGB at this moment.

I noticed both Cryptsy and Bittrex have deposit issues after hardfork.

Are other people still experiencing these issues?

[24hralttrade]

Please suggest me the working exchange for DGB at this moment.

I noticed both Cryptsy and Bittrex have deposit issues after hardfork.

Are other people still experiencing these issues?

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?

[DigiByte]

Please suggest me the working exchange for DGB at this moment.

I noticed both Cryptsy and Bittrex have deposit issues after hardfork.

Are other people still experiencing these issues?

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?

+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.

[Arsenay]

Please suggest me the working exchange for DGB at this moment.

I noticed both Cryptsy and Bittrex have deposit issues after hardfork.

Are other people still experiencing these issues?

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?

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

they have good support
I liked it 

[Ivanech]

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.

[Oldminer]

May be someone can post nodes so that it will be synced.

[
{
"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
}
]

[halinyo]

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?

[DigiByte]

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.

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.

[HR]

I'm experiencing a sync issue with v3.0.3.0-g354c0f3-MultiAlgo (64-bit) running on Windows 7, SP1.

Are you still having a sync issue? We just checked the seed nodes to make sure they are working as expected.

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:

Code:

listen=1
daemon=1
server=1
txindex=1
debug=1
algo=groestl
rpcuser=user
rpcpassword=password
rpcport=14022
port=12024
rpcallowip=127.0.0.1
addnode=216.250.125.121
addnode=74.208.230.160
addnode=69.164.206.169
addnode=192.99.215.234
addnode=96.126.114.208
addnode=54.204.36.33
addnode=192.99.41.108
addnode=199.83.128.91
addnode=199.83.132.91
checkpoints=1

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