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

No stress mate, only one way to find out and that's if you give it a shot huh! I'm still happy with how things are going with my current plan of attack so no harm done here

I ship from the Netherlands, a couple of days ago i shipped to Jumbley in the UK, The land of OZ, Is that in USA?
No problem to send it over there but need to figure what the transport costs are.

I'm sorry.  I mean that ... I am sorry because I would like to help give you advice.  But, I don't quite understand.  I guess it's good that you have been able to get a smaller machine running on the pool.

Hey there's some nice T's you've got there Hralttrade! Where do you ship from?... I'm all the way over in the land of OZ here

Yep, indeed! I'm working on some things that will work very well with a micropayments system such as DGB, so there's a bigger picture which I want to capitalize on from both ends. For now the main aim is to build my portfolio.

They are more total GH contracts, so they run as fast as they can till the total Gigahashes have been run. I have limited ability to control the speed, so I can get it to hover around 6GH/s but the service is spread over many IP's/Machines so it's a little hit and miss IE: It can spike quite a bit. This may very well have something to do with the probs on Digihash. My traffic might be getting seen as DDOS attack due to the nature of its delivery.

This means allot of dedicated buy support when you turn everything into Digibytes   

Hi digitaldoxy.  I'm a bit confused about the cost to run your equipment.  You had it running for about 4-5 hours in the pool - for the period you're referencing above - right?  So, does that mean you pay over $500 per day to run your equipment?

All good, I'm here for the long haul so 100 dollars will be a drop in the ocean in a year or so with any luck

EDIT: I must say, I think the responsiveness of the DGB community and you guys managing the network will be a key factor in growing DGB, so I've got to take my hat off to you! Cheers

Sounds like a much better plan you have now, considering the tools you have. the first day you ran, the scrypt network speed was around 3GH you doubled it when you mined. The next day it was around 6GH when you made your run and you took it up to nearly 9GH, that's why your revenue was much lower. If you were running at a steady continuous speed over the day, things would have balanced out more for you.
I'm sorry you ended up so badly out of pocket but it was very interesting to watch!
Thanks for supporting DigiByte and as long as you hold your coin for a while, I think you will still end up making a profit but obviously not as soon.

No problems at all mate DGB has all the makings of the next big player in cryptocurrency and I'm looking forward to the ride!

Ouch that is a big loss indeed and we can understand that you do not want to put more hashes into DGB because that would just be insane!
I dont have any explanation for this but maybe some others can help you.

But  hey,Again thank you for the support you still give to the Digibyte network!

Return was very low for the cost to run it (understatement)... Seems to be a quirk with running the miners used for my contract on the Digihash pool as I get expected returns on any other alt or pool. I can't run these contracts any slower than 6GH/s scrypt algo and I think that's got something to do with the problem where Digihash is concerned. Anyhow, final figures were as follows...

Hashes Run: 100,000 GH
DGB Earned: Approx 24650
DGB USD Value: Approx $2.40
Cost to run USD: Approx $105.00
ROI USD: -$102.40

I'd love to support Digihash with my scrypt contracts but that's a bit too rich for me! I now run my contracts on other Alt's where I get the expected returns and then convert it to DGB. I get some losses for fees etc but it's nowhere near what I lost above, a couple dollars at most. The wierdest thing is i ran a 30,000 GH test the day before the above one, and it all went fine (76,000 DGB earned). Next day I committed to 100,000 GH and everything went to pot... This was also the day that payouts froze so I can't help but think something went wrong on Digihash's end, but I could be wrong, so it's not worth creating a fuss over it.

I've also got about 400MH/s of dedicated hardware in our datacentre but I don't want to push that onto Digihash until I can be sure of returns, as my connections are power metered so I stand to lose alot if anything goes wrong and I can't make it out to the datacentre for a few days (travel alot for business).

Still want to support the developers of Digibyte however, so I'm running a much smaller remotely accessible 90MH/s rig on Digihash which seems to be going okay

More nodes = more people confirming blocks and transactions are valid. I'm still doing some work on the backend and the screenshot I showed won't be the final list of nodes. With that being said satoshi never meant for everyone on the network to be using "Full Nodes" (Core client holding the entire blockchain and synced to the network). The current list is pretty good in terms of an altcoins nodes, bitcoin itself usually sits around the 6k mark.

More nodes means more safety right?  Do we need more nodes?
Awesome to see Digibyte really is world wide!

PM sent.

We are not aware of a Skype community. Is this possible? Or is it a matter of adding several contacts?

Remember we also have the IRC chat room #digibytecoin, we also like to stay in #digibyte

Does anyone speak Korean, Japanese or Hindi? We can use help validating these translations.

Edit: Also looking for Russian, Arabic, Bengali, Polish and any other suggested languages.

https://digibytetip.com/