|
did you get the Github code
|
|
|
|
|
Fingers crossed, my wallet is running with connections to the network
|
|
|
|
|
IF YOU HAVE BEEN INVOLVED IN PREVIOUS LAUNCH ATTEMPTS - DELETE %APPDATA%/BITZ AND ANY OTHER BITZ SOFTWARE AND CONFIG FILES BEFORE LAUNCH
|
|
|
|
Whats the story with the Mac-qt wallet???  |
|
|
|
|
Ok, so at the same time then, that seems to be what you want. I ultimately want people to mine and use the coin so if the consensus is that; then I can post the links to wallets on the OP and then push the source to Github in that order but more or less at the same time. How is that?
|
|
|
|
In Bitcoin Core version v0.10.0 (64-bit) (Mac in this case) there is an option for sending BTC with low fee or zero fee if possible. The transactions will be a lower priority but will eventually be processed. I have now tried this for the first time and the transaction appears to be stuck or is being processed very slowly. Does anyone else have any experience with this?
- snip -
Any thoughts?
I have used the feature several times now and never had problems. You might want to uncheck the "send w/o fee when possible" to get the confirmation within the 25 blocks as promised. As others have already said your TX is without fee and its priority is not that high. The fee with the modified settings would have been ~400-500 satoshi. That should be low enough. oh and a link is nice, here -> https://www.blocktrail.com/BTC/tx/346b28808cbfd0e1e61485324ac48a398f814a76ecde85da113f4c0b39f0e350Yeah, it was a test only, and obviously I will pay the fee the next time, just wanted to try
Sending without a fee is fine, but you need a higher priority. Im not sure how bitcoin core/qt determines whether its fine to pay no fee or not in the new version. If you have an .1 BTC input and want to send it w/o fee it should be confirmed for at least 10 days. This is a bit of a rule of thumb but it usually works out. Its easy to remember as 1 BTC confirmed for 1 day or 1 bitcoin day. So this: Priority - 39,646,535 > 28,800,000 means that the transaction has to reach 28,800,00 to be processed?? |
|
|
|
|
It's impossible to please everyone and at some level it's about who clicks first and fastest so 1-2 min. before launch to Github and then I have to post the links and by the time I have done that there will a minute or so...
It's the same for me, I have to rent a rig as well and connect to the pool etc. I don't have any X11 equipment at home. So I'll probably be the last one to start mining after doing this.
|
|
|
|
|
Yeah, it was a test only, and obviously I will pay the fee the next time, just wanted to try
|
|
|
|
In Bitcoin Core version v0.10.0 (64-bit) (Mac in this case) there is an option for sending BTC with low fee or zero fee if possible. The transactions will be a lower priority but will eventually be processed. I have now tried this for the first time and the transaction appears to be stuck or is being processed very slowly. Does anyone else have any experience with this?  I initiated the 0.3BTC transaction at 2312 hours (GMT) London and now almost 9 hours later, still no confirmations.  Any thoughts? |
|
|
|
Yeah should release source and wallets at the same time.
There are differences of opinion on this. The pools will get ready and won't start to mine until the launch of the wallet. This seems to be the normal way of doing it. |
|
|
|
|
It will work like this:
- We have set up two seed nodes and the IPs are hardcoded into the Windows wallet bitz-qt.exe so it should connect when started.
- We will post a suggested bitz.conf file before launch.
- We have tested the Windows wallet bitz-qt.exe on three Windows system and it runs fine and connects to the nodes.
- We have mined 4 blocks to test and the wallets sync.
- Before launch I will make sure my wallet is running and synced and connects to the nodes.
- I will push the source to Github two minutes before launch to give pools a chance to get up and running.
- I will publish a link to download the Windows wallet bitz-qt.exe at launch.
- The Windows wallet bitz-qt.exe will also be available to download from the website at launch.
Wallets are compressed with 7zip with no password.
Hope it all goes well...
|
|
|
|
What coin are you trying to mine solo? Is your coin wallet fully synced?
Have you set a coin.conf file in %appdata%/roaming/coin with the correct user and pass you're using on cpuminer?
I am trying to mine my own X11 coin which currently had 0 blocks. I have put a xxxx.conf file in %appdata% and set the ports and the server settings and I have two nodes running and the wallet connects to the nodes and appears ready. I am using cpuminer X11. I have turned off all the anti-virus stuff and turned off the firewall. I have also started the wallet with -conf=%appdata%/xxxxx/xxxxx.conf I have Windows 7 pro, 64 bit When I run netstat -a I can not see the wallet or anything listening on the port I have set and this is why cpuminer can not connect but why is the wallet not listening. |
|
|
|
|
Please, everyone, delete %appsdata% and anything else Bitz before running the new one
|
|
|
|
I'll be around  Excellent, I'll get you the source before launch. I have tested this time and we have two nodes up and a couple of wallets and we mined 4 blocks to test so the network is synced. Hopefully that should do it. |
|
|
|
|
Is anyone going to run a pool, I need to rent some rigs and mine some Bitz myself. The network is synced now.
|
|
|
|
14 hours 18 minutes till launch?
Yeah, tomorrow morning at 1100 hours GMT (London) |
|
|
|
|
Show Posts
