Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 757. (Read 1260677 times)

Latency quite high. Over 300 ms.

Try a ping to 65.130.226.208 which is my current IP

I suppose I could set up a dynamic dns to my box in Utah USA, wallet open 24/7 but IP changes occasionally when modem lease renews.  Don't know if it would be of much help for overseas continent though ...

Nice. Seems we need some node/wallets in Asia. They are notoriously absent

This is the map of the IPs my wallet is currently connected to:

http://batchgeo.com/map/be075e876e5d72da828adf7ae996fd3f

(+ mine which is in northern Italy)

On the official Diamoind website in the section "Overview, it says that the "Block solving target time" is 600 seconds and 60 seconds.  Which one is correct?

BTW for those who are curious about 2nd hand prices, I managed to sell 2 of my R9 280X for 190 Euro each.

A pool has a wallet right? That wallet being located strategically in Singapore for example could also act as a permanent node, no?

That was my point.

The pool is different from the permanent node. An node helps wallet owners, while the pool helps local miners. Both being local help, but in general solve issues for different target group. It is of course best to have both as widely distributed as possible.

A very nice girl I met this spring in Singapore can surely convince me pay a visit again and setup such things, but... it's a long long way and setting up servers is the last thing I could think of in such environment.
But, if you guys need help, this is the right place to ask.

Setting up an node is more or less trivial. At worst, it could be on an always on desktop computer, just run the GUI wallet with listen=1 and server=1 in the config file. That's pretty much all one needs to do.
Or run the headless wallet in some VM at someone's datacenter. It does not require much CPU (especially if you don't have coins there trying to mint) and it's disk I/O requirements can be reduced by removing any debug=1 options to just redirecting the log file to /dev/null.

Setting up an pool is much more involved, because you need to deal with users and achieving good performance. But any decent computer can do the job. It is best to sit in a datacenter, but sitting on someone's desk is an option too.

A reason more to open a pool in Asia. Check my message in the bit.diamond project management community forum.

Follow the advice given by cryptonit, add the (one so far) permanent node and delete your old peers.dat. You will get new peers from that node and next time you start the wallet you will try connecting them as well.
It would be good to find other permanent (always on, running the latest wallet) nodes in Asia and the US -- that would speed up syncing for non-EU users.

In order to PoS, you need to have the wallet unlocked -- creating any blocks requires you being able to sign them and this is especially important for PoS, where you in fact spend your old amounts for interest.
We have implemented a fake, yet very popular "security" feature "unlock for minting only". It would not stop a real hacker to steal your coins, once they are *inside* your computer, but it would stop the script kiddie who would try to control your desktop (keyboard) and use the UI to send coins.

Another alternative is, to keep it open so that your larger/older amounts stake, then lock it for a while. Those amounts will be eligible after 7 days to stake again. So locking it for a week is ok. This time, they staked on their own. Next time, because they are 'big' and 'stake early' each will be split in two pieces. So next time they will take a bit longer to stake. When they get smaller than the combine threshold (100 DMD) and do not stake for 30 days, at the next stake chance these smaller amounts will be grouped into a 100 DMD (or around that number) piece and stake together. The split/combine cycles will repeat again.
If you don't want to be subject to the amount splitting, then lock it for at least a month.

It basically hashes a bit, then sleeps
Just reduce the sleep.

Thanks. Yes way much lower than here.

I have tested well over 20 IPs. They all give me similar lag. 

Having other nodes in Thailand wont serve me in any way as they will have the same problem.

There would need to be some node in Singapore since that's where most of Thai's IPS connects to the backbone. Japan would also be a good place.

Vote for Diamond DMD on

click pic or this link https://www.mintpal.com/voting#DMD

dont spend BTC for voting! (better spend btc to buy more dmd   )
create a mintpal account deposite some little btc amount buy some other coins
(or deposit and sell some other coins which are traded at mintpal)
after that u able to vote each hour for free
once u did one trade on mintpal u allowed to vote each hour without need to pay


place #143 now

i set a bounty from my own wallet (not foundation)

paying 1 DMD to everyone who reached a new rank

so first one reporting #142 and walletaddress
@ http://bit.diamonds/community/index.php/topic,16.0.html
gets 1 DMD by me (or alex if he faster and ninja rewarding again)

IMPORTANT only claim rewards on
http://bit.diamonds/community/index.php/topic,16.0.html

u have a diamond.conf file in diamond appdata folder as suggested on first page of this ANN?

also delete old peers.dat

regarding cryptsy we got used to their maintainaces take ages
we didnt tell them to upgrade wasnt a mandatory wallet release

I was reading around and came across this, and, the answer now is, YES!

The PM notifications just don't seem to get my attention. lol

Thanks again for the info. I'm sure it will help.

HR
I sent you a PM did you get it?
Poke

@danbi and @cryptonit: thanks!

Everything worked like a charm: in less than 30 minutes, I downloaded wallet and blockchain, and accessed my old DMD balance. However, I can't withdraw from cryptsy (it says their wallet is offline, updating to the new version...).

Two questions:
a) Must I leave the wallet open at all times to earn PoS? What if I encrypt/lock it? Will PoS still be active?
b) when launching the wallet, it takes ages to connect to the first nodes in the network. anything I can do to speed this up?

I used to compile it with the default setting of -O2.
Just tried with -O3 but I don't see any difference.
Maybe I should compile a newer gcc but it will take ages!