Topic: BTCD is no more - page 222. (Read 1328507 times)

Maybe you could answer this question. It would be appreciated, as I have gone to hell and back testing the Mac build...

Is it even necessary to create a BitcoinDark.conf file with a Mac that seems to be synching out of the gate after downloading the wallet app?

Is it necessary to make a BitcoinDark.conf file at all on a Mac?

If you don't know, maybe James can answer the question.

Thanks!

No, I only updated the source code. Haven't released a binary as it's still in development.

I'm thinking we'll just have a list of trusted, donation-funded nodes hardcoded into the source. If you don't have a BitcoinDark.conf, it will automatically create it for you and generate a random rpcpassword.

Is that why I didn't need to do anything special on the most recent Mac wallet download I tested today?

Also, I deleted my giant "how to", because I don't want people to screw up their systems once they encrypt their wallet. I saved it if we deem it valuable for any reason later.

Anyhow, if any Mac users are having issues, please feel free to mention it. I will try to help you if you need it.

I added auto BitcoinDark.conf generation today to the test repo.  

Matthew

any gambling sites using BTCD yet?

Hey Smiley35,

I am testing a number of different Mac configurations. In the beginning, my wallet wouldn't synch for months, and following the exact procedure I laid out in my "how to" was the only way to get it to work eventually. However, now that I have uninstalled everything, erased all support files (including my original download of the wallet app), and then restarted the process from zero, I didn't need to do anything at all mentioned in my "how to".

In fact, I am testing the "how to" on a few other machines to see if it is even necessary. It might not be. My computer might have been an isolated problem (but maybe not if you are also having issues). I am not sure if someone switched out whatever Mac wallet we were downloading in the night to something that actually works, but maybe that's what happened, in which case, I would suggest uninstalling the BitcoinDark app and deleting the folder ~/Library/Application Support/BitcoinDark (EXCEPT FOR THE wallet.dat file). DO NOT DELETE THE wallet.dat FILE IF YOU ACTUALLY HAVE COINS IN THAT WALLET (OR COINS ON THE WAY TO AN ADDRESS GENERATED BY THAT WALLET). You will need that wallet.dat file in that case. If you don't know, the wallet.dat file will be found in ~/Library/Application Support/BitcoinDark. Just stick that aside until you get up and running. Anyhow, after doing whatever you choose to do, start from scratch with the download link to the Mac wallet on page 1 of this thread (using Firefox or Chrome). You might not need to do any of the steps in my "how to." I might actually delete my "how to". Let me know how that works out for you. Additionally, it sometimes takes up to five minutes for my wallet to connect and start synching, so if you have understandably been inpatient after first opening your wallet, give it a few minutes. Take a walk, get something to eat, and see when you come back if it started to synch while you were gone.

As for your problem, did your wallet ever synch at all? Does the wallet open to the point where you can see a wallet? Did it ever get a single active connection to the network? Also, what OS X version are you on? YOU DEFINITELY NEED TO USE CHROME OR FIREFOX FOR THE INITAL WALLET APP DOWNLOAD. SAFARI DOES NOT WORK. Safari will look like it worked because it will give you a BitcoinDark-QT.dmg file that will open, but when you go to open the wallet, nothing will happen (as in you won't even get to the point where you can see a wallet open).

I can tell you this, my "how to" will kill any active connections once you encrypt the wallet. What then fixes it is to delete the BitcoinDark.conf file from the folder ~/Library/Application Support/BitcoinDark. Once I delete that file, it starts synching again. It seems the BitcoinDark.conf file is not even necessary in the Mac build. Maybe I am wrong about it not being necessary, but that worked for me with an encrypted wallet. I just deleted the file that seemed to initially get me starting to synch.

I will continue to test on a few other machines and then let you know what happens. If you continue being unable to synch, PM me, and I will help you to the best of my abilities.

 +1 I like this community. If I had programming knowledge I would be offering help as well.

Hey,

I have some c programmers on staff, I have previously sent details in but haven't heard anything, if you need some help I would like to get involved, let me know what you want done.


http://www.wittechnologies.com.au

There will be a buywall at NAV so that people who want to dump can get out without losing money on their initial investment.
No way of knowing price immediately after launch. Wait and see.

There seems to be a pattern with IPO's and dumps, from what I've read there is at least a plan and budget set aside for SuperNet/Token to hopefully deal with this, what are thoughts on the coming days/weeks price etc?

Just let me know when it's ready, and I'll create a new Windows Installer.

You must be new around here.

I dont worry about boosting the price
I work to add value
The price will bounce around the value.

HODL

100x in two months has been a good ROI. The next 100x will take longer than 2 months and will require completing all the SuperNET and BTCD tech and probably take 2 years+. If you cant be patient and HODL, I suggest to sell, everything wont be done before end of the year and even then there will be loose ends not done.

I am pretty much coding all the heavy lifting stuff myself now, plus financing which actually takes precedence as without the financing all the tech wont really matter. With the financing, the userbase is much bigger.

So, please stop with the impatient schedules stuff. Look at the big picture of what will be done by year end: SuperNET, Teleport, InstantDEX, Tradebots and some initial Privatebet, also halfanon card and hopefully the full anon card, all with a full 2.0 crypto HTML GUI SuperWallet. Once SuperNET starts getting revenues, then this will flow into BTCD.

It is not any one thing that will boost the price, but the combined effect of everything

James

you mean by 1400 GMT on Thursday?

only from the command line, i am a day or two away from testing Teleport on SuperNET, but since Teleport basics worked with the loopback and now the onion routing is working, there is some chance it will be possible to do some super teleports before thursday.

however, there are only a few people who are actually helping me and I wont be racing against any arbitrary clock. this is a marathon and sprinting will just slow down the overall completion.

We still need the GUI, OS builds and validation programs to be written and a lot of testing. This is something that HAS to be done by people that are not me. There is only so much testing I can do and certification has to be done by someone other than the dev.

James

So, anything to look forward to that might boost the price?

Hey,

Is BTCD Teleport going to be live before superNET IPO/Token goes live on the exchange?

debugging is a real pain, but its gotta be done. I can see the finish line now.

With the different OS and GUI things coming in place and of course SuperNET by early next month we should see some nice advances. Still need to really test things, I will start looking for a test programmer. that will really make things a lot more solid

James

Go James! Good on ya!

well, a rough day debugging, over 40 builds
I got a lot of little things added, but somehow it crashed as soon as it received any packet. I got it to just barebones to try to isolate the problem, still crashed. I rarely do this, but reverting to a version from 30 hrs ago was needed.

so after a day, I was back to where I started. But, I had a couple dozen improvements that I could add back in a bit at a time and with 90% of the new stuff in there, it is still working.

So, lost a full day, but recovered most of it. Of course, the 10% that didnt make it in was what I needed next

Been spot testing various local API calls and these seemed to be fine. Now that I can do the remote API again, I can start testing Teleport, but need to verify that narrowcasting (point to point via BitcoinDarkd) works as a backup comm path for when UDP is cranky (it happens) and of course making an IP based set of data structures.

Now that Windows and Mac builds are being worked on, we are days away from getting a release all put together for beta testing, so I need to get these last few things done in the next day or two

James

if I can help any further let me know