|
polanskiman
|
 |
July 16, 2014, 05:57:54 AM |
|
I've tested all peers currently connected to my wallet. All the IPs that responded have a response time over 280ms.
What do you guys get?
60ms Thanks. Yes way much lower than here. |
|
|
|
|
|
|
|
|
|
No Gods or Kings. Only Bitcoin
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
danbi
|
|
July 16, 2014, 06:26:04 AM |
|
How would you go on and make the wallet hash more without any external hasher?
It basically hashes a bit, then sleeps  Just reduce the sleep. |
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL
DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
|
danbi
|
|
July 16, 2014, 06:38:24 AM |
|
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?
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. |
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL
DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
|
polanskiman
|
|
July 16, 2014, 07:14:37 AM |
|
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?
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. A reason more to open a pool in Asia. Check my message in the bit.diamond project management community forum. |
|
|
|
|
|
danbi
|
|
July 16, 2014, 10:39:45 AM |
|
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?
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. A reason more to open a pool in Asia. Check my message in the bit.diamond project management community forum. 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. |
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL
DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
|
polanskiman
|
|
July 16, 2014, 10:46:19 AM |
|
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?
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. A reason more to open a pool in Asia. Check my message in the bit.diamond project management community forum. 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 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. |
|
|
|
|
|
polanskiman
|
|
July 16, 2014, 10:48:47 AM |
|
BTW for those who are curious about 2nd hand prices, I managed to sell 2 of my R9 280X for 190 Euro each.
|
|
|
|
|
Tyke
Legendary
 Offline
Activity: 1441
Merit: 1161
|
|
July 16, 2014, 10:50:28 AM |
|
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?
|
|
|
|
|
|
|
|
polanskiman
|
|
July 16, 2014, 10:58:57 AM |
|
Nice. Seems we need some node/wallets in Asia. They are notoriously absent  |
|
|
|
|
|
utahjohn
|
|
July 16, 2014, 11:07:02 AM |
|
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 ... |
|
|
|
|
|
utahjohn
|
|
July 16, 2014, 11:11:39 AM |
|
Try a ping to 65.130.226.208 which is my current IP
|
|
|
|
|
|
polanskiman
|
|
July 16, 2014, 11:20:53 AM |
|
Try a ping to 65.130.226.208 which is my current IP
Latency quite high. Over 300 ms. |
|
|
|
|
|
utahjohn
|
|
July 16, 2014, 11:25:13 AM |
|
Try a ping to 65.130.226.208 which is my current IP
Latency quite high. Over 300 ms. Just as I figured, I get 287 ms to the permanent official node in the UK? We need permanent nodes on each continent with high speed backbone connections to each other ... I had high latency problems with Danbi's pool also ... |
|
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
July 16, 2014, 11:27:45 AM |
|
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?
both...... the POW difficulty try to adjust to find a block each 60 sec the POS difficulty try to adjust find a block all 600 sec |
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
July 16, 2014, 11:33:17 AM |
|
|
|
|
|
|
|
Tyke
Legendary
Offline
Activity: 1441
Merit: 1161
|
|
July 16, 2014, 12:24:33 PM |
|
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?
both...... the POW difficulty try to adjust to find a block each 60 sec the POS difficulty try to adjust find a block all 600 sec I am confused now lol - I thought these figures, 60 seconds (PoW) and 600 seconds (PoS) were the block times. It says below that the difficulty retarget is every block. |
|
|
|
|
Tyke
Legendary
Offline
Activity: 1441
Merit: 1161
|
|
July 16, 2014, 12:26:11 PM |
|
Diamond is in my book called Cryptocurrency "The Alt-ernative" Beginner's Reference. Here is first draft of IFC: https://bitcointalk.org/index.php?topic=356065.msg7131241#msg7131241MAIN CRYPTOCURRENCY BOOK THREAD: https://bitcointalk.org/index.php?topic=483187.0All 50 coins were chosen via a bitcointalk.org vote back on the 16th of March. Any coins released after the 16th of March have not reached this book and won't have a chance of substituting these coins. All coins by now have existed long enough in order for substantial cotent to be written about them. Diamond will look similar to this. Coin specifications, history, exchanges and other miscellaneous details will be included. Please help fund the publication of this book which I plan to publish this summer. dU7eT1yAqAMiUDfKtgzE5cUTmaoS6SuuQv   |
|
|
|
|
|
utahjohn
|
|
July 16, 2014, 01:43:36 PM |
|
Nice. Seems we need some node/wallets in Asia. They are notoriously absent My solution is to mine on Wafflepool (has endpoints in uswest, useast, europe, and asia) and just buy DMD with WP profits ... @Danbi maybe you should set up a MP proxy that uses WP as a backend and pays out in DMD (for example as KTK mining pool does). Unfortunately I have a lot of DMD stuck on Cryptsy until they pull their heads out of their asses and get wallet working ... |
|
|
|
|
|
