Author

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

full member
Activity: 391
Merit: 100
Just looks like a mass exodus for DGB at this moment in time something has gone very wrong...sell orders are staking up on Poloniex & its only set to get worse...shorter block times & half rewards may not be the best way forward at this time well at least a lot of so called investors seem to think so...lets hope the NEW gift for DGB is going to be something worth singing about this Sunday
sr. member
Activity: 443
Merit: 251
The leaching continues. Good luck convincing anyone here...in the DGB community...to dump their DGB and buy Myriad. Comical but applaud your effort.
hero member
Activity: 622
Merit: 504
Your only Amigo, in the World of Crypto
What is going on here first we get the hard fork & then we get a 24 million hard dump on Poloniex....yes i know Bitcoin is going up but i am certain this has nothing to do with it...just seems to be far to much DGB out there for the price to rise anytime soon...just saying.

I thought 48-50 was a stable price but someone obviously wanted out
Or buy lower.

When there is an hardfork, there is always doubt. So the price have a lot of chance to go down. Specialy when price wall already on a down trend.
It may not be a bad move to dump at 45 & buy at 40 later


I think dumping now & hoping to buy back at 40 is a crazy idea, given there is some NEWS to be announced tomorrow the price is more than likely to rise if said news is a good one....sell now to buy back lower would be suicide if you dont get back in....i would rather keep it & sit tight


Well i keep buying when it goes lower.  If they dump to buy back lower and miss out thats their problem.
And if it does goes lower, that means i get more DGB.

2016 Is a big year for Digibyte with digispeed and alot of interesting projects + marketing out there.

The future is bright with Digibyte  Cheesy Grin

There is a reason myraid never went with lower block times.

You again Smiley

There is also a reason why Myriad only has 0.01725582 24hr Volume @ polo







◈◈◈ Trading Tip ◈◈◈
When trading altcoin/BTC, don't leave any amount of BTC sitting in the exchange's wallet.
Instead, sit them in Buy Orders at extremely low price ranges (or near All-Time Low range). Whenever you need BTC, simply cancel them.
Just remember - Don't put up a huge buy order as doing so will most likely result in not getting filled up.
hero member
Activity: 756
Merit: 500
Community Liaison,How can i help you?
What is going on here first we get the hard fork & then we get a 24 million hard dump on Poloniex....yes i know Bitcoin is going up but i am certain this has nothing to do with it...just seems to be far to much DGB out there for the price to rise anytime soon...just saying.

I thought 48-50 was a stable price but someone obviously wanted out
Or buy lower.

When there is an hardfork, there is always doubt. So the price have a lot of chance to go down. Specialy when price wall already on a down trend.
It may not be a bad move to dump at 45 & buy at 40 later


I think dumping now & hoping to buy back at 40 is a crazy idea, given there is some NEWS to be announced tomorrow the price is more than likely to rise if said news is a good one....sell now to buy back lower would be suicide if you dont get back in....i would rather keep it & sit tight


Well i keep buying when it goes lower.  If they dump to buy back lower and miss out thats their problem.
And if it does goes lower, that means i get more DGB.

2016 Is a big year for Digibyte with digispeed and alot of interesting projects + marketing out there.

The future is bright with Digibyte  Cheesy Grin

There is a reason myraid never went with lower block times.

You again Smiley

There is also a reason why Myriad only has 0.01725582 24hr Volume @ polo
sr. member
Activity: 351
Merit: 250
What is going on here first we get the hard fork & then we get a 24 million hard dump on Poloniex....yes i know Bitcoin is going up but i am certain this has nothing to do with it...just seems to be far to much DGB out there for the price to rise anytime soon...just saying.

I thought 48-50 was a stable price but someone obviously wanted out
Or buy lower.

When there is an hardfork, there is always doubt. So the price have a lot of chance to go down. Specialy when price wall already on a down trend.
It may not be a bad move to dump at 45 & buy at 40 later


I think dumping now & hoping to buy back at 40 is a crazy idea, given there is some NEWS to be announced tomorrow the price is more than likely to rise if said news is a good one....sell now to buy back lower would be suicide if you dont get back in....i would rather keep it & sit tight


Well i keep buying when it goes lower.  If they dump to buy back lower and miss out thats their problem.
And if it does goes lower, that means i get more DGB.

2016 Is a big year for Digibyte with digispeed and alot of interesting projects + marketing out there.

The future is bright with Digibyte  Cheesy Grin
full member
Activity: 391
Merit: 100
What is going on here first we get the hard fork & then we get a 24 million hard dump on Poloniex....yes i know Bitcoin is going up but i am certain this has nothing to do with it...just seems to be far to much DGB out there for the price to rise anytime soon...just saying.

I thought 48-50 was a stable price but someone obviously wanted out
Or buy lower.

When there is an hardfork, there is always doubt. So the price have a lot of chance to go down. Specialy when price wall already on a down trend.
It may not be a bad move to dump at 45 & buy at 40 later


I think dumping now & hoping to buy back at 40 is a crazy idea, given there is some NEWS to be announced tomorrow the price is more than likely to rise if said news is a good one....sell now to buy back lower would be suicide if you dont get back in....i would rather keep it & sit tight
legendary
Activity: 1198
Merit: 1000
What is going on here first we get the hard fork & then we get a 24 million hard dump on Poloniex....yes i know Bitcoin is going up but i am certain this has nothing to do with it...just seems to be far to much DGB out there for the price to rise anytime soon...just saying.

I thought 48-50 was a stable price but someone obviously wanted out
Or buy lower.

When there is an hardfork, there is always doubt. So the price have a lot of chance to go down. Specialy when price wall already on a down trend.
It may not be a bad move to dump at 45 & buy at 40 later
full member
Activity: 391
Merit: 100
What is going on here first we get the hard fork & then we get a 24 million hard dump on Poloniex....yes i know Bitcoin is going up but i am certain this has nothing to do with it...just seems to be far to much DGB out there for the price to rise anytime soon...just saying.

I thought 48-50 was a stable price but someone obviously wanted out
sr. member
Activity: 804
Merit: 251
what does (SA) mean on DGB gaming on ranking next to someone's username
legendary
Activity: 2002
Merit: 1051
ICO? Not even once.
Which node is guaranteed to be on the right fork? I'm running 3 wallets for each algo with the same nodes and they always have different block heights.
legendary
Activity: 1532
Merit: 1205

Awesome!
Is it possible to buy the book with DGB?

It would be great to see the book on the DigiByte Marketpalce site.  Personally I am not sure how I could go about selling it for DGB.  Any ideas are welcome please.
hero member
Activity: 756
Merit: 500
Community Liaison,How can i help you?
legendary
Activity: 1198
Merit: 1000
I've added new (4.0.1) nodes manually on all suprnova pools now to get the orphan rate down, however my logs are still full of old "misbehaving" versions...
same here

Assuming you mean 4.0.1 the changes that have been pushed in the last couple of hours? If so on line 35 of src/version.h it reads

"static const int MIN_PEER_PROTO_VERSION = 70002;"

If you change that to "static const int MIN_PEER_PROTO_VERSION = 70003;" it should boot all old nodes.

I've made that change locally and now instead of connecting to previous nodes I get "2015-12-05 11:51:09 partner 178.33.209.212:12024 using obsolete version 70002; disconnecting" in my debug.log.

Can't say for sure that it will help though but I am grabbing blocks from someone.

    "version" : 4000100,
    "protocolversion" : 70003,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 1435246,
    "timeoffset" : 0,
    "connections" : 2,
    "proxy" : "",
    "pow_algo_id" : 0,
    "pow_algo" : "sha256d",
    "difficulty" : 542228.07741643,
    "difficulty_sha256d" : 542228.07741643,
    "difficulty_scrypt" : 43.05482915,
    "difficulty_groestl" : 212.18662653,
    "difficulty_skein" : 1154.42586898,
    "difficulty_qubit" : 50.70482811,
    "testnet" : false,
    "keypoololdest" : 1449115190,
    "keypoolsize" : 101,
    "paytxfee" : 1.00000000,
    "relayfee" : 1.00000000,
    "errors" : ""

so only 4.0.1 node can connect to your wallet

edit : 70002 node should be able to connect , I think
member
Activity: 96
Merit: 10
I've added new (4.0.1) nodes manually on all suprnova pools now to get the orphan rate down, however my logs are still full of old "misbehaving" versions...
Hope this new version gonna clean the network! Same as you ocminer, logs are full of "obsolete version".
legendary
Activity: 1198
Merit: 1000
I've added new (4.0.1) nodes manually on all suprnova pools now to get the orphan rate down, however my logs are still full of old "misbehaving" versions...
same here
legendary
Activity: 988
Merit: 1000
I am going to keep my wallet offline until this is all sorted out.
legendary
Activity: 2688
Merit: 1240
I've added new (4.0.1) nodes manually on all suprnova pools now to get the orphan rate down, however my logs are still full of old "misbehaving" versions...
full member
Activity: 181
Merit: 100
Hi, my DGB wallet (v4.0.0) is stuck at block 1431876 4 hours ago , i have 11 active connections but not scynchronising, what can i do ?

thks for yr help
hero member
Activity: 517
Merit: 500
aka alaniz
New list of active v4.0 nodes if this helps anyone resolve their issues

['188.165.223.132', '176.31.126.191', '198.27.97.172', '86.235.174.30', '92.129.238.39', '71.198.11.116', '216.250.125.121', '149.202.44.159', '109.190.65.26', '71.125.4.22', '88.198.76.188', '36.83.55.99', '104.131.113.153', '108.61.10.90', '192.52.166.35', '104.131.112.56', '24.28.92.13', '195.154.223.134', '0.0.0.0', '104.236.189.117', '46.246.58.132', '124.155.108.193', '212.251.123.0', '115.70.4.78', '189.174.246.255', '88.127.210.106', '83.83.161.46', '104.34.30.238', '149.210.215.250', '98.115.147.74', '24.115.186.59', '90.224.42.77', '66.228.56.115', '104.131.170.147', '104.236.32.184', '84.127.218.159', '189.226.127.23', '87.98.178.140', '69.164.198.161', '84.90.100.92', '37.187.27.4', '178.33.228.14', '181.39.238.154', '157.161.128.58', '90.255.166.238', '45.79.10.59', '79.70.9.80', '82.232.14.27', '74.216.82.141', '77.58.253.73', '79.20.18.148', '206.225.141.127', '113.254.169.34', '212.129.1.77', '50.46.211.57', '113.254.165.193']
Jump to: