|
Yes it seems like a priority to get the windows client out.
if nobody can compile one, I will setup a VPS running windows and compile one ASAP.
I wanted to include some more features into the Qt before releasing the windows client but I think the issue with the forking is of a bigger priority right now
I think that with automatic checkpointing, the forking issue is going to be a thing of the past.
|
|
|
|
I'm still not sure what the problem is.
It could be the number of nodes not being high enough
It could also be the way PoS blocks that are being generated that causes forks.
I've also experienced a bunch of PoS blocks being generated one right after the other. It doesn't seem right.
This isn't a good sign. Is there anything a non-technical (at least in this sense) person can do to help figure out the problem? I think now is a good time to setup a checkpoint node. This should help the situation as checkpoints are established automatically and on a constant basis rather than by issuing a new release everytime |
|
|
|
|
I'm still not sure what the problem is.
It could be the number of nodes not being high enough
It could also be the way PoS blocks that are being generated that causes forks.
I've also experienced a bunch of PoS blocks being generated one right after the other. It doesn't seem right.
|
|
|
|
Hey guys here are the new commits to the source. I activated the DNS seeds witch greatly improves the get connection time when the client is freshly installed or the peers.dat file deleted. I managed to get connected within seconds with a fresh install... no config file to mess with  I have setup a dns seed host (seed.grw.blockx.info). I plan to make it an automated process so the host can scan for good nodes to connect to in realtime. If someone wants to host another dns seed host for redundancy please do so. send me the link and I will add it to the source. If you can setup a static node, that will also be a great addition for the network. I can host DNS seed host but need some directions how to setup it properly - never did it before Already run two GRW static nodes on my servers. The quick and dirty way is to manually add ip addresses of connected nodes of the network using the default port 17177, to the A records of an address (seed.growthco.in for instance) The more proper way would be to setup https://github.com/iamunick/bitcoin-seeder on a server so it can scan periodically the network and return active nodes. you can check these 2 repositories to find out the changes made to the bitcoin-seeder so it listen on the correct network. https://github.com/JoiBlumen/auroracoin-seederhttps://github.com/Bushstar/worldcoin-seeder |
|
|
|
I'm loving your updates! Do you have a listing of your "to-do" stuff so we know what to look forward to? Or just kind of knocking out things randomly?
My goal is to bring the wallet close to the security and features of the HoboNickels wallet. Plus some of the features mentioned by users on this thread. So you have that to look forward too  |
|
|
|
Those are cool I'll let people choose and I will include the one people chose in the final release of version 1.3.0.0 |
|
|
|
I hate to be "that guy," but for us newbies... what changed in terms of functionality? Like "URI fixes," I have no idea what that is. Just a quick overview of what we can expect from the new version would be awesome. And hopefully someone gets the Windows version up soon, :p. Don't worry, I put this up mainly so people can follow the changes and to be as transparent as possible  the URI fixes is to be able to link a growthcoin://ADDRESSHERE to the client (when you click on an address on a website to make a payment for instance). I still have a few minor changes I want to include before I set to build the windows version. That being said, if you or someone else wants to compile, they are free to do so |
|
|
|
Does the updated version cause a network fork, or is it just the local db which needs to be regenerated?
No these updates are mainly wallet improvements, no need to hard fork As far as compiling for Windows, check out Gitian - this is a set of scripts that automagically use a preconfigured Linux VPS to cross compile to a Windows EXE (and optionally Linux, too). Gitian is intended to allow multiple people to independently compile an identical binary to prove that a release is clean, but it's also very handy for one-step 'doze compiling. (Once you figure out its quirks ) Thanks I'll check into that |
|
|
|
Unick does. I think he is away right now. If he is not back after the long weekend I will contact him. Thanks. It is back up and running again with 20+ connected nodes Sorry about the downtime guys  It is indeed back up and running again |
|
|
|
Oh this is going to save me some time thanks! |
|
|
|
Does noot sync!
Add to your conf addnode=cap.nodes.btcrypt.net:7685 and it will sync. I've updated it to the latest version flound did above. Connected to 39 peers at the moment. S. Hi sheffters. I have added this as a dns node. I was able to get connected and sync'd using this without anything else. However there are a few things. When I do a nslookup I only see one address. It should be many addresses. See below Yours: nslookup cap.nodes.btcrypt.net
Non-authoritative answer:
Name: cap.nodes.btcrypt.net
Address: 87.106.246.28
Here is hbns: nslookup seed.hobonickels.info
Non-authoritative answer:
Name: seed.hobonickels.info
Addresses: 162.243.251.173
176.31.250.94
5.39.90.17
5.249.152.30
24.93.183.133
71.91.14.102
82.146.37.116
84.45.63.205
98.232.23.64
Your peer did supply me with other peers. About 2,000 worth. So I would be good for the future, but better for the dns node to point to other peers address right away. Anyway it is working for now, so thanks! Also if anyone wants to be a dns node, it would be good. 3 or 4 is a good number to keep the network healthy. do you have a link handy to how to set this up? Maybe something like that one https://github.com/sipa/bitcoin-seeder ? I can host a dns node on my servers but have no skill to modify this software for the coin. I also stumbled upon that, I'll give a look to see if this can be used. If someone already modified it for some alt coin, please share, it will save us some time |
|
|
|
thank you ,unick.the new wallet can be used now? Yes, keep in mind that a reindexing of the blockchain is required, you can either let it do it's magic by itself (about 6 hours of redownload) or get to pace with the copy of the blockchain I provided. Always make sure to backup your wallet.dat (and in this case your current app folder if anything goes wrong) how to download the new wallet?  If you have a Mac the link is right above. If you have Windows, I will setup a VPS with windows on it to compile future builds. Meanwhile, if you can compile, go ahead. The link to the github is also above. I'm focusing on getting updates rolling out, so the VPS solution for me is less prioritized (but will be done!) |
|
|
|
Does noot sync!
Add to your conf addnode=cap.nodes.btcrypt.net:7685 and it will sync. I've updated it to the latest version flound did above. Connected to 39 peers at the moment. S. Hi sheffters. I have added this as a dns node. I was able to get connected and sync'd using this without anything else. However there are a few things. When I do a nslookup I only see one address. It should be many addresses. See below Yours: nslookup cap.nodes.btcrypt.net
Non-authoritative answer:
Name: cap.nodes.btcrypt.net
Address: 87.106.246.28
Here is hbns: nslookup seed.hobonickels.info
Non-authoritative answer:
Name: seed.hobonickels.info
Addresses: 162.243.251.173
176.31.250.94
5.39.90.17
5.249.152.30
24.93.183.133
71.91.14.102
82.146.37.116
84.45.63.205
98.232.23.64
Your peer did supply me with other peers. About 2,000 worth. So I would be good for the future, but better for the dns node to point to other peers address right away. Anyway it is working for now, so thanks! Also if anyone wants to be a dns node, it would be good. 3 or 4 is a good number to keep the network healthy. do you have a link handy to how to set this up? |
|
|
|
thank you ,unick.the new wallet can be used now? Yes, keep in mind that a reindexing of the blockchain is required, you can either let it do it's magic by itself (about 6 hours of redownload) or get to pace with the copy of the blockchain I provided. Always make sure to backup your wallet.dat (and in this case your current app folder if anything goes wrong) |
|
|
|
there's a new rpc command addnode NODE add where NODE is a known node. give it a few seconds to connect or jump to the console and add a couple of nodes from this list http://grw.blockx.info/connected-nodesNo need to restart the client, it's all done in real time Great ,, within minutes I'm getting more connections that my windows wallet, Im enjoying this and not to mention coin control! sweet update unick Excellent news I still think the connection rates is too low... I'm hopping to see better results as I'm going through the updates ahead. I think automatic checkpoints and hardcoded seed nodes should help this issue. |
|
|
|
This is great work! Already checked out the mac wallet and will move my coins from windows wallet to mac. Reaaly impressed, looks and feels more responsive so far! Great work. The only issue I have is...0 peers there's a new rpc command addnode NODE add where NODE is a known node. give it a few seconds to connect or jump to the console and add a couple of nodes from this list http://grw.blockx.info/connected-nodesNo need to restart the client, it's all done in real time |
|
|
|
Site is back up, sorry about that |
|
|
|
|
Show Posts
