Hoshimaru
|
|
September 15, 2014, 12:11:53 PM |
|
This coin is going to be de-listed soon: BTC VOL0.01997060 BTC Once it's gone, it's hard to re-list on an exchange... An additional hurdle if we want to keep this alive.
|
|
|
|
cryptouser
Full Member
Offline
Activity: 247
Merit: 100
O__o
|
|
September 15, 2014, 01:56:13 PM |
|
Okay guys I've finally come to getting Insight sync the Minerals block chain ~1 MByte (4031 blocks) of it for testing It's more work than I expected and I had to find required parameters at the core of the genesis block using the wallet daemon, base58.h and main.cpp from the source code. INSIGHT_NETWORK="livenet" node insight.js
____ _ __ __ ___ _ / _/___ _____(_)___ _/ /_ / /_ / | ____ (_) / // __ \/ ___/ / __ `/ __ \/ __/ / /| | / __ \/ / _/ // / / (__ ) / /_/ / / / / /_ / ___ |/ /_/ / / /___/_/ /_/____/_/\__, /_/ /_/\__/ /_/ |_/ .___/_/ /____/ /_/
v0.2.7 # Configuration: Network: livenet INSIGHT_NETWORK Database Path: /home/hoshi/.insight INSIGHT_DB Safe Confirmations: 6 INSIGHT_SAFE_CONFIRMATIONS Ignore Cache: no INSIGHT_IGNORE_CACHE # Bicoind Connection configuration: RPC Username: hoshi BITCOIND_USER RPC Password: Yes(hidden) BITCOIND_PASS RPC Protocol: http BITCOIND_PROTO RPC Host: 127.0.0.1 BITCOIND_HOST RPC Port: 33441 BITCOIND_PORT P2P Port: 33442 BITCOIND_P2P_PORT Data Dir: /home/hoshi/.Minerals/ BITCOIND_DATADIR
Change setting by assigning the enviroment variables in the last column. Example: $ INSIGHT_NETWORK="testnet" BITCOIND_HOST="123.123.123.123" ./insight.js
info: starting... insight server listening on port 3000 in development mode info: Could not find block files at: /home/hoshi/.Minerals//blocks/blk*.dat. Disabling file sync. info: Got 0 blocks in current DB, out of 4031 block at bitcoind info: syncing from RPC (slow) info: Starting from: 00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137 info: status: [0%] info: status: [0.025%] ... info: status: [99.752%] info: status: [100%] Done Syncing { status: 'finished', blockChainHeight: 4031, syncPercentage: '100.000', height: 4031, syncTipHash: undefined, error: null, type: 'from RPC calls', startTs: 1410726207968, endTs: 1410726304465 } info: status: [100%]
I hope to get the front-end up & running as well tonightFront-end can't seem to connect to back-end for some reason. Some troubleshooting required. But first things first: a good night's rest. Sent you 1800 MIN . Thanks for all the effort
|
|
|
|
shanecoins
|
|
September 15, 2014, 02:19:20 PM |
|
Devs please post something
lol
|
|
|
|
jacklord
Newbie
Offline
Activity: 31
Merit: 0
|
|
September 15, 2014, 04:02:16 PM |
|
Devs please post something
He is working on some important issue.Be patient. Like, what important issue.
|
|
|
|
qwbzerra
Member
Offline
Activity: 61
Merit: 10
|
|
September 15, 2014, 06:29:34 PM |
|
we need to get the multipool up and running...
|
|
|
|
Hoshimaru
|
|
September 15, 2014, 06:56:57 PM Last edit: September 15, 2014, 08:01:47 PM by Hoshimaru |
|
Thank you cryptouser I've hit a wall with Insight. The API gets the blockchain loaded and synced, but the front-end doesn't. That's strange, because it is built on that API and it is even included in the front-end, so I just had to use the same settings. Couldn't find a solution, so I opened an issue on github, as there's no support forum of any other way to contact them other than github.It's done Next on the agenda: - Load the live block chain
- Test different aspects
- Alter CSS and get it to show "MIN" iso "BTC", value for block reward, ...
- If everything's fine: host it on a VPS
Of course the coin would need revival, otherwise I don't see the point in paying for hosting
|
|
|
|
hotwired007
|
|
September 16, 2014, 11:17:33 AM |
|
we need to get the multipool up and running...
You can't mine Minerals any more... Youc an only earn them through POS staking.
|
This account was hacked & possibly sold during the period of August 1st and October 24th 2017. Anything done or said in this period wasnt me. Many thanks to Cyrus for his help restoring access to my account.
|
|
|
shanecoins
|
|
September 16, 2014, 11:20:20 AM |
|
we need to get the multipool up and running...
You can't mine Minerals any more... Youc an only earn them through POS staking. multipool would mine other coins to buy mins
|
|
|
|
shahim
Legendary
Offline
Activity: 1082
Merit: 1002
|
|
September 16, 2014, 02:15:52 PM |
|
Thank you cryptouser I've hit a wall with Insight. The API gets the blockchain loaded and synced, but the front-end doesn't. That's strange, because it is built on that API and it is even included in the front-end, so I just had to use the same settings. Couldn't find a solution, so I opened an issue on github, as there's no support forum of any other way to contact them other than github.It's done Next on the agenda: - Load the live block chain
- Test different aspects
- Alter CSS and get it to show "MIN" iso "BTC", value for block reward, ...
- If everything's fine: host it on a VPS
Of course the coin would need revival, otherwise I don't see the point in paying for hosting can you list, what you need to change for this?
|
|
|
|
Hoshimaru
|
|
September 16, 2014, 02:46:44 PM |
|
can you list, what you need to change for this? I don't know yet shahim. It also need as small fix to get the right locations for the blk*.dat files from the blockchain. It looks for blocks/blk*.dat from the error log I saw yesterday. It's not much of a problem, but loading the chain using rpc is way slower than the direct access to the files. I'll look into these things tonight when I'm back home.
|
|
|
|
shahim
Legendary
Offline
Activity: 1082
Merit: 1002
|
|
September 16, 2014, 03:38:45 PM |
|
can you list, what you need to change for this? I don't know yet shahim. It also need as small fix to get the right locations for the blk*.dat files from the blockchain. It looks for blocks/blk*.dat from the error log I saw yesterday. It's not much of a problem, but loading the chain using rpc is way slower than the direct access to the files. I'll look into these things tonight when I'm back home. no problem. I have just seen your posts in abe tread and now I saw you are also investigating into insight right now like me. Seems we are working paralell. perhaps you are interested in exchanging experience to make this explorer happen. I also hold minerals and want this project to come furhter! If you like you can pm me. Perhaps I can help with some stuff!
|
|
|
|
Hoshimaru
|
|
September 16, 2014, 06:39:53 PM Last edit: September 16, 2014, 09:36:44 PM by Hoshimaru |
|
can you list, what you need to change for this? I don't know yet shahim. It also need as small fix to get the right locations for the blk*.dat files from the blockchain. It looks for blocks/blk*.dat from the error log I saw yesterday. It's not much of a problem, but loading the chain using rpc is way slower than the direct access to the files. I'll look into these things tonight when I'm back home. no problem. I have just seen your posts in abe tread and now I saw you are also investigating into insight right now like me. Seems we are working paralell. perhaps you are interested in exchanging experience to make this explorer happen. I also hold minerals and want this project to come furhter! If you like you can pm me. Perhaps I can help with some stuff! Thanks for your offer Are you working with ABE? I've booked some progress with Insight. Two files needed to be modified in order to get it to load blocks from the .dat files > insight-bitcore@0.2.4 start /home/hoshi/insight > INSIGHT_PUBLIC_PATH=public node node_modules/.bin/insight-bitcore-api
____ _ __ __ ___ _ / _/___ _____(_)___ _/ /_ / /_ / | ____ (_) / // __ \/ ___/ / __ `/ __ \/ __/ / /| | / __ \/ / _/ // / / (__ ) / /_/ / / / / /_ / ___ |/ /_/ / / /___/_/ /_/____/_/\__, /_/ /_/\__/ /_/ |_/ .___/_/ /____/ /_/
v0.2.4
info: insight server listening on port 3000 in development mode info: Seeking file to:00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137 FOUND Starting Block! info: Got 0 blocks in current DB, out of 418260 block at bitcoind info: bitcoind dataDir configured...importing blocks from .dat files info: First file index: 0 info: Starting from: 00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137 info: status: [0%] Reading Blockfile /home/hoshi/.Minerals/blk0001.dat [236 MB] { '0': 'connecting to 127.0.0.1:33442' } Finished all files info: status: [0%] { '0': 'connected to 127.0.0.1:33442' }
Now it's figuring out how to get transactions visible for a specific address and such :+) Lol... It's really step by step ... Update: created a bootstrap.dat from the up-to-date wallet. It's at 25% of loading the block chain properly in the virtual machine. -rw------- 1 hoshi hoshi 59M Sep 16 21:45 blk0001.dat -rw-rw-r-- 1 hoshi hoshi 237M Sep 16 20:57 bootstrap.dat drwx------ 2 hoshi hoshi 4.0K Sep 16 21:03 database -rw------- 1 hoshi hoshi 0 Sep 16 21:03 db.log -rw------- 1 hoshi hoshi 15M Sep 16 21:45 debug.log -rw-rw-r-- 1 hoshi hoshi 197 Sep 16 18:55 Minerals.conf -rw------- 1 hoshi hoshi 5 Sep 16 21:03 Mineralsd.pid drwx------ 2 hoshi hoshi 4.0K Sep 16 21:45 txleveldb -rw------- 1 hoshi hoshi 80K Sep 16 21:00 wallet.dat When it's done, I'll reload the Insight DB and hopefully get rid of these unparsed addresses.Still having issues with it. Rebuild with the block chain version on my minipc is no good. It has no txindex=1 which seems to be a requirement :/ Insight loads the 87MB blk0001.dat (~140k blocks, up to a checkpoin?) in a blink (way too fast imo) and then returns shitty data in the explorer. Back from scratch again... You wouldn't want me as a crypto dev: it would take forever to get it done.
|
|
|
|
shoozooo
Newbie
Offline
Activity: 45
Merit: 0
|
|
September 16, 2014, 09:59:28 PM |
|
Minerals are dead or still alive ? oO
Dev is still in the project ? Nothing about anon features ?
|
|
|
|
hotwired007
|
|
September 17, 2014, 06:38:02 AM |
|
Minerals are dead or still alive ? oO
Dev is still in the project ? Nothing about anon features ?
Minerals is alive - not so sure about the Dev - we have a guy working on getting a blockchain explorer up and running ATM. Suspect the Devs have got bored and dropped it as minerals.pro site is down.
|
This account was hacked & possibly sold during the period of August 1st and October 24th 2017. Anything done or said in this period wasnt me. Many thanks to Cyrus for his help restoring access to my account.
|
|
|
shahim
Legendary
Offline
Activity: 1082
Merit: 1002
|
|
September 17, 2014, 11:59:34 AM Last edit: September 17, 2014, 01:26:19 PM by shahim |
|
can you list, what you need to change for this? I don't know yet shahim. It also need as small fix to get the right locations for the blk*.dat files from the blockchain. It looks for blocks/blk*.dat from the error log I saw yesterday. It's not much of a problem, but loading the chain using rpc is way slower than the direct access to the files. I'll look into these things tonight when I'm back home. no problem. I have just seen your posts in abe tread and now I saw you are also investigating into insight right now like me. Seems we are working paralell. perhaps you are interested in exchanging experience to make this explorer happen. I also hold minerals and want this project to come furhter! If you like you can pm me. Perhaps I can help with some stuff! Thanks for your offer Are you working with ABE? I've booked some progress with Insight. Two files needed to be modified in order to get it to load blocks from the .dat files > insight-bitcore@0.2.4 start /home/hoshi/insight > INSIGHT_PUBLIC_PATH=public node node_modules/.bin/insight-bitcore-api
____ _ __ __ ___ _ / _/___ _____(_)___ _/ /_ / /_ / | ____ (_) / // __ \/ ___/ / __ `/ __ \/ __/ / /| | / __ \/ / _/ // / / (__ ) / /_/ / / / / /_ / ___ |/ /_/ / / /___/_/ /_/____/_/\__, /_/ /_/\__/ /_/ |_/ .___/_/ /____/ /_/
v0.2.4
info: insight server listening on port 3000 in development mode info: Seeking file to:00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137 FOUND Starting Block! info: Got 0 blocks in current DB, out of 418260 block at bitcoind info: bitcoind dataDir configured...importing blocks from .dat files info: First file index: 0 info: Starting from: 00000c639b0fbf250ba63c6ef2952dbb44bb1051324a27383b8a56fb833d8137 info: status: [0%] Reading Blockfile /home/hoshi/.Minerals/blk0001.dat [236 MB] { '0': 'connecting to 127.0.0.1:33442' } Finished all files info: status: [0%] { '0': 'connected to 127.0.0.1:33442' }
Now it's figuring out how to get transactions visible for a specific address and such :+) Lol... It's really step by step ... Update: created a bootstrap.dat from the up-to-date wallet. It's at 25% of loading the block chain properly in the virtual machine. -rw------- 1 hoshi hoshi 59M Sep 16 21:45 blk0001.dat -rw-rw-r-- 1 hoshi hoshi 237M Sep 16 20:57 bootstrap.dat drwx------ 2 hoshi hoshi 4.0K Sep 16 21:03 database -rw------- 1 hoshi hoshi 0 Sep 16 21:03 db.log -rw------- 1 hoshi hoshi 15M Sep 16 21:45 debug.log -rw-rw-r-- 1 hoshi hoshi 197 Sep 16 18:55 Minerals.conf -rw------- 1 hoshi hoshi 5 Sep 16 21:03 Mineralsd.pid drwx------ 2 hoshi hoshi 4.0K Sep 16 21:45 txleveldb -rw------- 1 hoshi hoshi 80K Sep 16 21:00 wallet.dat When it's done, I'll reload the Insight DB and hopefully get rid of these unparsed addresses.Still having issues with it. Rebuild with the block chain version on my minipc is no good. It has no txindex=1 which seems to be a requirement :/ Insight loads the 87MB blk0001.dat (~140k blocks, up to a checkpoin?) in a blink (way too fast imo) and then returns shitty data in the explorer. Back from scratch again... You wouldn't want me as a crypto dev: it would take forever to get it done.Hi, yes ABE is up and running without any problems. Now I am trying to get insight to run smooth. But I did not manage to read the blk0001.dat file. Insight is looking into a wrong folder, so I made a softlink. But then he starts loading the DB with RPC calls. But then after 4% of syncing it aborts.... He is saying the same thing: info: status: [0%] Reading Blockfile /home/hoshi/.Minerals/blk0001.dat [236 MB] { '0': 'connecting to 127.0.0.1:33442' } Finished all files info: status: [0%] Looks like he is not loading anything from the dat file at all. Because of status 0%.... But nice to see, you managed to get the folder "blocks" away I will try more. EDIT: @HOSHIMARU : I have read something about insight and I came to the conclusion insight is not working for POW/POS or only POS coins. Insight only seem to support POW only coins! I will be happy with my abe running. btw. abe is running really stable
|
|
|
|
Hoshimaru
|
|
September 17, 2014, 02:28:49 PM |
|
Hi, yes ABE is up and running without any problems. Now I am trying to get insight to run smooth. But I did not manage to read the blk0001.dat file. Insight is looking into a wrong folder, so I made a softlink. But then he starts loading the DB with RPC calls. But then after 4% of syncing it aborts.... He is saying the same thing: info: status: [0%] Reading Blockfile /home/hoshi/.Minerals/blk0001.dat [236 MB] { '0': 'connecting to 127.0.0.1:33442' } Finished all files info: status: [0%] Looks like he is not loading anything from the dat file at all. Because of status 0%.... But nice to see, you managed to get the folder "blocks" away I will try more. EDIT: @HOSHIMARU : I have read something about insight and I came to the conclusion insight is not working for POW/POS or only POS coins. Insight only seem to support POW only coins! I will be happy with my abe running. btw. abe is running really stable That's very disappointing and indeed... Found something about it here: https://github.com/bitpay/insight-api/issues/18ABE is nice but awfully slow
|
|
|
|
shahim
Legendary
Offline
Activity: 1082
Merit: 1002
|
|
September 17, 2014, 05:11:33 PM |
|
Hi, yes ABE is up and running without any problems. Now I am trying to get insight to run smooth. But I did not manage to read the blk0001.dat file. Insight is looking into a wrong folder, so I made a softlink. But then he starts loading the DB with RPC calls. But then after 4% of syncing it aborts.... He is saying the same thing: info: status: [0%] Reading Blockfile /home/hoshi/.Minerals/blk0001.dat [236 MB] { '0': 'connecting to 127.0.0.1:33442' } Finished all files info: status: [0%] Looks like he is not loading anything from the dat file at all. Because of status 0%.... But nice to see, you managed to get the folder "blocks" away I will try more. EDIT: @HOSHIMARU : I have read something about insight and I came to the conclusion insight is not working for POW/POS or only POS coins. Insight only seem to support POW only coins! I will be happy with my abe running. btw. abe is running really stable That's very disappointing and indeed... Found something about it here: https://github.com/bitpay/insight-api/issues/18ABE is nice but awfully slow Abe is not that slow. I think you Need to change your setup. I have installed it on my Server and it is ok. You Need some mysql tuning! Do you still run it o your Thin Client?
|
|
|
|
chinchs
|
|
September 17, 2014, 06:12:30 PM |
|
Good to see Shahim and Hoshimaru working this, I have something to propose for the rest of us. I was thinking about funding for takeover. If someone would like to dedicate time to this coin (Hoshimaru, I know you said you don't have time, but you may be part of the team, I don't know), should be compensated somehow. So i thought about:
* Create a funding address (may be a scrow Service) * Donate as much as we can (I will donate 30.000 Mins if the rest gather 70.000) * Designate a new DEV, PR, Etc * Release funds based on predefined milestones * Anon Feature * Betting integration for new games (LOL, DOTA, etc) * Market cap (when we reach a predefined value per mineral)
I think this scheme could be great, if new dev delivers, he will get coins, and value will go up.
|
|
|
|
Hoshimaru
|
|
September 17, 2014, 07:35:50 PM |
|
@Shahim: I ran it in a limited Virtualbox guest with 1GB RAM based on Ubuntu Server 14.04. Insight as well by the way, but in another snapshot. @chinchs: 30000 MIN :p That's 3/4 of everything I have, but it's a good idea to work with milestones. More important matters: The Minerals network is crumbling and it might be best to find a way to avoid problems: The dns-seeds, which are hard coded in the wallet on line 1141-1144 in src/net.cpp are down since little more than 85 hours according to my wallet's log file. The effect is not to be underestimated. Any new installation won't received a list of seeding nodes to start and thus cannot sync with the block chain. I first thought it was due to some network settings of my VM, but it's not. The desktop on which I'm writing this post, that didn't have Minerals installed, can't get them either. static const char *strDNSSeed[][2] = { {"dnsseed1.minerals.pro", "dnsseed1.minerals.pro"}, {"dnsseed2.minerals.pro", "dnsseed2.minerals.pro"} }; $ ping dnsseed1.minerals.pro PING dnsseed1.minerals.pro (5.45.123.57) 56(84) bytes of data. From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=1 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=3 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=4 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=5 Destination Host Unreachable
$ ping dnsseed2.minerals.pro PING dnsseed2.minerals.pro (5.45.122.48) 56(84) bytes of data. From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=3 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=5 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=6 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=9 Destination Host Unreachable $ Wallets/Minerals/Mineralsd getinfo { "version" : "v1.0.0.0", "protocolversion" : 60013, "walletversion" : 60000, "balance" : 0.00000000, "newmint" : 0.00000000, "stake" : 0.00000000, "blocks" : 0, "timeoffset" : 0, "moneysupply" : 0.00000000, "connections" : 0, "proxy" : "", "ip" : "0.0.0.0", "difficulty" : { "proof-of-work" : 0.00024414, "proof-of-stake" : 0.00024414 }, "testnet" : false, "keypoololdest" : 1410627855, "keypoolsize" : 101, "paytxfee" : 0.00001000, "mininput" : 0.00000000, "errors" : "" }
Peers I have a connection with atm are: $ Wallets/Minerals/Mineralsd getpeerinfo [ { "addr" : "54.76.249.21:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981864, "conntime" : 1410892563, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418355, "banscore" : 0 }, { "addr" : "178.62.10.91:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981861, "conntime" : 1410892650, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418358, "banscore" : 0 }, { "addr" : "192.99.9.229:33442", "services" : "00000001", "lastsend" : 1410981861, "lastrecv" : 1410981861, "conntime" : 1410892663, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418359, "banscore" : 0 }, { "addr" : "198.100.146.163:33442", "services" : "00000001", "lastsend" : 1410981712, "lastrecv" : 1410981861, "conntime" : 1410892698, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418364, "banscore" : 0 }, { "addr" : "23.92.53.139:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981861, "conntime" : 1410892764, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418367, "banscore" : 0 }, { "addr" : "192.241.188.47:33442", "services" : "00000001", "lastsend" : 1410981794, "lastrecv" : 1410981864, "conntime" : 1410892816, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418367, "banscore" : 0 }, { "addr" : "[2607:5300:100:100::b4]:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981862, "conntime" : 1410904327, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418877, "banscore" : 0 }, { "addr" : "178.221.235.61:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981861, "conntime" : 1410952372, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 421302, "banscore" : 0 }, { "addr" : "77.120.190.129:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981861, "conntime" : 1410954201, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 421372, "banscore" : 0 }, { "addr" : "94.180.58.239:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410980841, "conntime" : 1410969382, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 422209, "banscore" : 0 } ] Only after copying this in Minerals.conf, it started to sync: addnode=54.76.249.21:33442 addnode=178.62.10.91:33442 addnode=192.99.9.229:33442 addnode=198.100.146.163:33442 addnode=23.92.53.139:33442 addnode=192.241.188.47:33442 addnode=[2607:5300:100:100::b4]:33442 addnode=178.221.235.61:33442 addnode=77.120.190.129:33442 addnode=94.180.58.239:33442 So... haven't work on the Explorer yet. But I'd start worrying about keeping the network alive Anyone knows how to setup a dnsseed?
|
|
|
|
shahim
Legendary
Offline
Activity: 1082
Merit: 1002
|
|
September 17, 2014, 08:22:51 PM |
|
@Shahim: I ran it in a limited Virtualbox guest with 1GB RAM based on Ubuntu Server 14.04. Insight as well by the way, but in another snapshot. @chinchs: 30000 MIN :p That's 3/4 of everything I have, but it's a good idea to work with milestones. More important matters: The Minerals network is crumbling and it might be best to find a way to avoid problems: The dns-seeds, which are hard coded in the wallet on line 1141-1144 in src/net.cpp are down since little more than 85 hours according to my wallet's log file. The effect is not to be underestimated. Any new installation won't received a list of seeding nodes to start and thus cannot sync with the block chain. I first thought it was due to some network settings of my VM, but it's not. The desktop on which I'm writing this post, that didn't have Minerals installed, can't get them either. static const char *strDNSSeed[][2] = { {"dnsseed1.minerals.pro", "dnsseed1.minerals.pro"}, {"dnsseed2.minerals.pro", "dnsseed2.minerals.pro"} }; $ ping dnsseed1.minerals.pro PING dnsseed1.minerals.pro (5.45.123.57) 56(84) bytes of data. From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=1 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=3 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=4 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=5 Destination Host Unreachable
$ ping dnsseed2.minerals.pro PING dnsseed2.minerals.pro (5.45.122.48) 56(84) bytes of data. From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=3 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=5 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=6 Destination Host Unreachable From 178.103.106.194.sta.estpak.ee (194.106.103.178) icmp_seq=9 Destination Host Unreachable $ Wallets/Minerals/Mineralsd getinfo { "version" : "v1.0.0.0", "protocolversion" : 60013, "walletversion" : 60000, "balance" : 0.00000000, "newmint" : 0.00000000, "stake" : 0.00000000, "blocks" : 0, "timeoffset" : 0, "moneysupply" : 0.00000000, "connections" : 0, "proxy" : "", "ip" : "0.0.0.0", "difficulty" : { "proof-of-work" : 0.00024414, "proof-of-stake" : 0.00024414 }, "testnet" : false, "keypoololdest" : 1410627855, "keypoolsize" : 101, "paytxfee" : 0.00001000, "mininput" : 0.00000000, "errors" : "" }
Peers I have a connection with atm are: $ Wallets/Minerals/Mineralsd getpeerinfo [ { "addr" : "54.76.249.21:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981864, "conntime" : 1410892563, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418355, "banscore" : 0 }, { "addr" : "178.62.10.91:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981861, "conntime" : 1410892650, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418358, "banscore" : 0 }, { "addr" : "192.99.9.229:33442", "services" : "00000001", "lastsend" : 1410981861, "lastrecv" : 1410981861, "conntime" : 1410892663, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418359, "banscore" : 0 }, { "addr" : "198.100.146.163:33442", "services" : "00000001", "lastsend" : 1410981712, "lastrecv" : 1410981861, "conntime" : 1410892698, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418364, "banscore" : 0 }, { "addr" : "23.92.53.139:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981861, "conntime" : 1410892764, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418367, "banscore" : 0 }, { "addr" : "192.241.188.47:33442", "services" : "00000001", "lastsend" : 1410981794, "lastrecv" : 1410981864, "conntime" : 1410892816, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418367, "banscore" : 0 }, { "addr" : "[2607:5300:100:100::b4]:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981862, "conntime" : 1410904327, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 418877, "banscore" : 0 }, { "addr" : "178.221.235.61:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981861, "conntime" : 1410952372, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 421302, "banscore" : 0 }, { "addr" : "77.120.190.129:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410981861, "conntime" : 1410954201, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 421372, "banscore" : 0 }, { "addr" : "94.180.58.239:33442", "services" : "00000001", "lastsend" : 1410981862, "lastrecv" : 1410980841, "conntime" : 1410969382, "version" : 60013, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 422209, "banscore" : 0 } ] Only after copying this in Minerals.conf, it started to sync: addnode=54.76.249.21:33442 addnode=178.62.10.91:33442 addnode=192.99.9.229:33442 addnode=198.100.146.163:33442 addnode=23.92.53.139:33442 addnode=192.241.188.47:33442 addnode=[2607:5300:100:100::b4]:33442 addnode=178.221.235.61:33442 addnode=77.120.190.129:33442 addnode=94.180.58.239:33442 So... haven't work on the Explorer yet. But I'd start worrying about keeping the network alive Anyone knows how to setup a dnsseed? Virtualbox uhhhahhh yeah that is the Problem i think. I only have a few minerals. I bought very expensive. Bit I can try to find out how to make a dnsseed for this. When you bring the explorer on an online server you will see a performance boost! If you like we can test on mine server how the performance is there. The other explorer I am running for another coin is running quite well... Give me a pm and we stay in contact for this.
|
|
|
|
|