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

This is why we need 'DigiKnights', people that understand this and keep their hardware, no matter how small, on our network permanently. People that believe in DigiByte and its future because the more of us there are, the more expensive it becomes to play with us like this. 

Yep sorry, I was using the wrong term lol "digishield" is what I was referring to. And yep, your right, it does pull back quite quickly, that's why I can see how it looks like a good plan of attack to dissuade that kind of activity. The only winners are still the ones with huge hash power though. They still earn blocks at high difficulty while all of us well intentioned and globally distributed miners lose out.... Rock and a hard place for sure.... I'm still not convinced that kind of hash power is bothering with DGB at this early stage, even though I'm normally a stickler for a conspiracy theory

That's DigiShield. It is an expensive way to annoy a service, I agree but I still susspect someone of doing just that. The good thing for us, is that when they pull their hardware back, difficulty drops quickly too so we don't suffer because of it.

I hear you, but it's extremely unusual for difficulty to jump like that (aka DigiSpeed), you don't even see it ramp up slowly like one would expect as hash rates increase. That's why I mentioned Digispeed doing more harm than good, increasing difficulty like that only penalises people putting their hard earned and costly hash power on DGB IMO.

DDOS type traffic shouldn't affect coin difficulty, it may affect network availability of a particular pool, but only hash power should affect coin difficulty and jumps like I mention above mean hundreds of scrypt GH/s would theoretically have to appear and disappear just as quickly. That's a very expensive way to annoy a service.

I think that is quite normal on this coin. The total  scrypt and sha network speeds jump about as people add and remove hardware, not all of them DigiByte friendly I'm sure.

Ah I see, thank you for putting me out of my misery.  

Well if it hasn't something is seriously wrong, I saw difficulty go from 127 to nearly 500 and then back to 135 in the space of a couple hours on scrypt :/

Best take this one up with Jared, himself i guess and see what can be done to improve the situation.  
Has DigiSpeed been implemented yet? i didn't think it had.

Could be, this is a current issue with Cryptsy and why I don't like that they allow such miniscule transactions to take place while DGB value is so low.
You should be able to prove this by moving the largest amount and then attempting to move the rest, I'm not sure which is the best way to merge the inputs in the wallet, HR?

LOL! Well I did get a payment just after my last post as luck would have it, still a dismal ROI with difficulty bouncing around like a squirrel with rabies though.... I think DigiSpeed while being a good idea in theory, is actually doing more harm than good in some ways if I'm understanding how it works... Just my opinion though...

Does not look like there is a problem with payouts on the digihash pool to me, i received a payment around 15 mins ago but I am mining on sha. I do get a latency problem and never achieve 100% efficiency. I'm in the UK, so I was expecting a bit of latency, I thought it was possibly due to GCHQ piping traffic to CIA first.

I think I have the answer! HR Thanks for your forum: http://asistec-ti.com/

"It means that your transaction size in bytes is too larger (bytes, not DigiBytes). In a nutshell, it has to do with the number of inputs that are going into your output. If your inputs are very small, the total number of DGB that you will be able to send will also be very small. ~675 inputs would be the maximum you could currently combine for an output send, so if you're mining with a CPU and you've got inputs of, let's say an average of 5 DGB, the most DGB you could send would be 3,375, and you'd pay 2 DGB just like you'd pay 2 DGB if your inputs were 1,000 and you were sending a total of 675,000 DGB. It all comes down to the number of bytes in each input and is completely independent of the DGB amount.
"

do you think it is that ??

Thanks for the response HR, I'm in Australia mate.

We are running the bigger rigs from our offices in Melbourne, the internet can slow down when we have offsite backups coming in, but otherwise it's pretty good (dedicated 100Mb pipe running to main infrastructure) The other units are running from my house over NBN (100Mb network).

I was mining to Coinmine.pw previously which was connecting to their US located servers... Also have some EC2 instances on Amazon AWS which I run a couple of P2Pools from. Several instances are located in the US and some here in Australia. All of these have run very reliably with low reject rates.

You raise a very good point though, just pinged Digihash.co from my house and got a 296ms ping time! If I ping coinmine.pw in the USA it's a 14ms round trip, and all Amazon instances are sub 10ms.... Where in gods name is Digihash located... The Arctic Circle?? lol

On another note, I tried Digihash sometime ago and found I wasn't getting payments for hours, am now experiencing the very same issue after getting a couple of payments, nothing for nearly two hours, is there still an issue with payments freezing up?

EDIT: Just remoted into a work PC and got 270ms to digihash, and then another ping to Digihash from an EC2 Amazon instance located in the USA, got 210ms... All other pools I tested were sub 10ms with most sub 5ms.

Where are you located? Where were you mining before?

I suspect it's a latency issue, but your answers to those 2 questions are needed in order to confirm.

I personally wonder if there is any legal issues with the project Jared is involve in for DigiByte?... And if there is, wondering how they are planning to solve it...
Best,

Hello, I'm using GOOGLE translation, so I'll keep it short.

I am contacting you because I have a problem with my wallet DigiByte 64bit Core v3.0.3.0
My available balance appears to be 3,000,000, but I can't send more than 1.1 million to my other address.

my two addresses:
- http://www.richlist.eu/digibyte/stats/DCS2wZvFPfDtKufUEpRQDmXt3GHEkE726J
- http://www.richlist.eu/digibyte/stats/DAAVsbhoprWeQ2b4y4QDoZNZPLZCqi5ND8

If required I can also send you the transaction statement

Here are some screenshots :

http://img11.hostingpics.net/thumbs/mini_689911img1.png
http://img11.hostingpics.net/thumbs/mini_593350img2.png


Thanks for your help !

Lol sorry 

Theres no link

Edit: Nevermind, I found it. https://www.youtube.com/watch?v=os_akxn8ZS4&feature=youtu.be&a

Nothing huge, Digibyte with an aura reflecting its power but if you see a cushion I totally missed my gif. 

No problem, I cant help you with your mining rejects but i'm sure someone will reply to you.