@JordanLee We need a Mac OX developer.
it now seems obvious to me that v2.1.1 is not very stable, but i did manage to build it with icons and everything. I have built 2.0.3 as well just to see that my setup is working for different branches. Let me know if these builds are needed by anyone.
1 Like
In what way?
for some reason it’s very slow to synchronise, 2.0.3 seems faster to me, i’ll do some tests to provide more concrete information, also i read a thread here about problems with reindexing, is it outdated?
That’s a known problem (the slow download speed).
Have a look here:
The important part is
git merge origin/download_optimizations_r2great stuff, I built with this merge and it does seem to be a tad faster.
here’s the download link https://rbfi.io/dl.php?key=/scJS/Nu-Qt.dmg
shasum -a 256 Nu-Qt.dmg
3439a6e466b3feca9daf81eee08070b7ef6cd7642e8ac4b89762f5647cb7d19b
1 Like
From my experience with that “download optimizations patch” on a RaspberryPi I remember that increased the speed approximately by a factor 5 to 10.
I was able to download the whole blockchain in approximately one day with that patch.
hm, weird, i had to delete the blockchain and start again and it does seem to work much faster.
I am very happy to see this @backpacker. The team is discussing how we can invite you to help us on a regular basis and we will be contacting you shortly.
2 Likes
finally finished syncing the Nu blockchain, it seems like there’s an absolute boatload of ORPHANS that have to be dealt with during initial sync, does anyone know why?
im guessing because the 1 minute block spacing?
of course shorter block period increases likelihood of orphans, but why would they be sent during initial sync? shouldn’t they have been long forgotten?
We’ve had multiple discussions about how to proceed and unfortunately, we cannot come up with a solution.
The nature of the problem is that creating a build requires quite a bit of trust. It would be easy to add code to the build that sent private keys to a remote database, for instance. We can’t seem to coordinate the work of experts like @backpacker with people we trust like sigmike in a way that produces secure builds.
The developers we trust know nothing about OS X. This is an open source project working on decentralised infrastructure. Our culture revolves around the values associated with Linux and is far from the centrally controlled world of Apple. With a small team and small budget, this has been difficult for us to manage, as all OS X users of NuBits and B&C Exchange are aware.
There is no question in my mind that NuBits and B&C Exchange should support OS X. It is equally clear that neither myself nor anyone on the team can make the builds. I am utterly ignorant of all things Apple and as a result have nothing to offer in this effort. But the code is open source, so anyone anywhere on the planet can make OS X builds at any time, as @backpacker has demonstrated. Trusted builds are another matter.
The combination of the fact that the source code needed to create builds is completely accessible to all at all times and that our team has no expertise in OS X builds means the responsibility for creating OS X builds should be outsourced beyond the team.
I am happy to facilitate payment to someone creating OS X builds from development funds for each organization, but that will be the extent of my involvement and responsibility for OS X builds. I won’t be making any attempts to coordinate OS X builds going forward. As a decentralised organization, that responsibility can and should be taken up by others.
Can we compile bcexchanged daemon on Mac OS since Mac OS is indeed a Unix system?
We can easily port apt-get on Mac OS even a jailbreak iOS device. Both iOS and Mac OS’s core(Darwin) is open sourced, with many other open softwares like Ruby、Python、Perl, and SWIFT language +LLVM complier are also open source.
- Please MoD or others write a mannual on how to creat a command line for Mac OS.
- Could @backpacker wirte a instruction of how to build a QT GUI version on Mac OS? It takes less than 1 hour for u to finish it, so I guess the procedure is not very difficult. And what compensation do you wanna to finish that compiling handbook?I guess NBT or BKS may sent to you.
It would be easy to add code to the build that sent private keys to a remote database, for instance.
@JordanLee , Theoritically, our B&C website can also be hacked, and the Linux/Windows QT versions are also prone to this kind of risk. So, can you provide a mannual on how to build QT app on these platforms? I suggest big B&C holders build their own application from source codes by themselves.
Alas, I have no affiliation with Apple products - never owned one, never will.
Apple might offer convenient, sophisticated and technologically sound products, but I can’t get along with the ideology…
Ok, I’ll try to use “apt-get” to complie a daemon on Macbook.
BTW, u don’t need to buy a hardware from apple, Hacintosh is good.
I think the Apple hardware always is a fine piece of tech.
Only I don’t like how closed the operating systems (iOS, MacOS) are.
But I don’t want to sidetrack this thread with resentments 
really? a mouse with just one button? how, why, … it hurts my hand just thinking of it
I agree that running any kind of software requires trust, downloading applications from the internet and running on your computer always irked me myself and many others no doubt. Best thing is to review the source and compile it yourself, of course. However, it is difficult to expect many people to invest so much of their time in order to become proficient enough to build open source software with numerous dependencies including qt. Exchange with such high requirements for entry won’t receive much business.
Instructions on how to set up the build system are more or less up to date in your documentation, carefully following them is all that’s needed and takes only few hours depending on your existing level of knowledge. I am not really sure if my report of doing it would be helpful to others, since everyone is missing different bits of information in their head while attempting to set up.
What I do offer is to provide regular builds of your organisations software until you have set your own macosx machine in the cloud, that I can help set up to build new releases. I’ve spent some time on the project so far and still willing to do more if community needs it and is willing to compensate the efforts as was stated in original post. Like I said before, I do hope that your organisations are successful, because the success would most likely be passed on to parent projects.
1 Like
There is no official binary download for RaspberryPi now, but some of share holders have set up their minting machine via an instruction.
I believe your QT@MacOS compiling handbook espically with screenshot is useful for some B&C shareholders, this is business, since they’ve put quite some money into such company, trying to learn some knowledge is natual.
Linux users are usually only 3-5% among PC users, so why B&C provide Linux QT version to them? Because it’s good manner to provide service to minority.